meraki network box sucks

Discussion in 'Johnson & Johnson IT' started by anonymous, Jul 24, 2017 at 11:13 PM.

Tags: Add Tags
  1. anonymous

    anonymous Guest

    thanks to our BU IT I got saddled with putting this new meraki device into our site. we've had like over 50 calls on this with accenture, verizon, and some good network guys. the box can't do what its supposed to and its been like 3+ months stuck on this never ending saga of being sold the kool aid on this box. it can't do some basic things that my verizon modem at home can and it seems we can now get to some sites that were previous blocked due to legal reasons - not a good thing if audit finds out. real question is does network engineering even test the devices before handing them out to the field or do they just expect us to test this for them? This install should've been like 1-2 weeks and its been excruciating having to deal with this non-stop.
     

  2. anonymous

    anonymous Guest

    Yup definitely agree. Network engineering has not put much thought into how this impacts use at sites. From the calls we have been having looks like basic testing was missed - bunch of units were ordered and now they are trying to figure out how to dump this on us.
     
  3. anonymous

    anonymous Guest

    Hear you brother. Don't be so quick to judge the network engineers though. These decisions are made at the director level and at that level we all know there is no technical experience or knowledge .
     
  4. anonymous

    anonymous Guest

    insane issues and they have no clear documentation. Site people have to develop solutions and workarounds on their own - what does network engineering do ? They ask me to open up another stupid ticket with accenture - who suck and never respond. Spoke to the network engineering director who flooded the call for over two hours with his sugar coating used car salesman attitude and utter gibberish. Got nowhere - we developed a workaround internally and have shared it with other sites. He then emails us to understand details of our workaround - we all ignored the emails.