Hello, At a remote location, we have 4 switches(MS350) running in a stack and performed a routine upgrade from 10.25 to 11.22. After the upgrade we started seeing the following: Dropped pings (from data center to servers, computers at the remote location) Could not ping the SVIs on the switch stack from the data center Computers on the local LAN could not ping their default gateway (SVI on the switch stack). However, the SVI could still pass traffic, meaning the computers could still access resources on/off the network segment, but could not ping the its default gateway. High packet loss and latency when pinging the individual switches in the stack from the Meraki portal The main applications it impacted for us were VoIP and Video conferencing. Phones would re-register several times a day or hang while trying to re-registers. Additionally, Zoom video conferencing was choppy, etc. Uses complained the network was slow. Switches turning yellow and green, (I only caught this because i happened to be in the portal monitoring the sites) Meraki performed packet captures and said they did not see return traffic from the upstream devices. Initially Meraki thought the issue was 11.22 (as there is a known bug related to stack switches in the release). They recommended the following: Upgrade to 11.28 (new release candidate) at that time. During the upgrade most of the switches upgraded, but a few 220s didn't..we hard power cycled the Meraki switches, removed most of the aggregate ports and the upgrade was finally successful on those Meraki switches. Move Management network for switch stack (only) off the stack: There is a known issue\design best practice with Meraki (with stack switches only), where the management IPs of switches in a switch stack should not be on a SVI that is housed on the switch stack. We moved our management network from the switch stack and put it on our router. Remove all aggregate ports None of those next steps fixed issues 1-6. The network performance got even worse, we lost ospf connectivity between the switch stack and our mpls router. Per Meraki, the switch stack was having issues fetching its configuration, ospf was no longer established and now the site was down hard. The switch stack in the portal alerting something similar to "stack configuration in member different from dashboard" After finally getting to the Meraki escalation team (going through 5-6 engineers, 2 days later, escalating to account team and finally a down hard network), they were able to isolate the issue to the following: port mirroring on the stack triggered an issue with switch stack being unable to fetch its configuration from the cloud. We removed ALL port mirroring, rebooted the switch stack, ospf re-established and issues 1-6 immediately cleared. The site is back up and performing normal. UPDATE 12/14: We continued to have poor performance (demonstrated by high packet loss, error messages indicating that the merakis were having a difficulty reaching the cloud, user complaints of slowness, etc) with the switch stack (after all the changes above). We ended up having to remove the stack....no reported issues after removing the stack.
... View more
Thanks everyone, however, I am looking for the uptime and last reload, similar to show version on the cisco IOS. The switch can have power, but no IP connectivity to the cloud, etc. I am trying to determine if there was a loss of power to the device..in cisco IOS, you can do a show version and get that information.
... View more