14.33 is now a stable release so I'd upgrade to that if you haven't already? ... View more

Hi. We are having an issue connecting a new Meraki MS390 to 2 production Nexus 7000 switches using vPC.  The Nexus 7K switches have been confirmed to be configured correctly by a Cisco employee & we have multiple working vPCs on them already.  The Meraki switch is not sending any LACP packets to the Nexus switches despite documentation saying it should.  How do you enable LACP on the MS390s? ... View more

I run in to this issue every so often, would really like to be alerted when it happens.   Any update on this? ... View more

I have wiresharks gathered on MS350 switches running MS12.27 that show this is not true.  MCAST will continue from the initial address and cause the port to send out both streams until the first stream times out.   This is consistent with Fast-Leave / Immediate-Leave not being enabled or correctly implemented.   In a Crestron NVX system you can turn the stream bandwidth down from 950Mbps to 450Mbps to get around this limitation assuming you are happy with the reduced video quality. ... View more

@MRCUR wrote: @Mosquitar wrote: Hi,   Did you ever get this issue resolved? If so, what was the fix as we are experiencing issues with a topology similar to yours.   Thanks Unfortunately not. I had to reopen the support case today as the issue (likely with DNS) is still occurring and causing instability for the 425 stack. The school year ended before we were able to determine a root cause last year so hopefully it can be found this time around.  The remaining issue is being caused by malformed DNS packets through the app X-VPN - https://xvpn.io/. The individual packets are significantly larger than would be expected for a DNS response and are possibly all being sent to the MS425 CPU to process for DNS inspection.    We've put in place ACL's on the 425 stack temporarily to block all DNS traffic that does not go to or come from our internal DNS servers. MS engineering is looking into the issue.  ... View more

Firmware version on both switches? ... View more

I would recommend engaging Meraki Support for investigation. If there is an open case, would you mind sharing the case number in a private message? ... View more

Hi @Kapil   Great question, when I moved VLAN 120 to the Meraki side I disabled Multicast Routing on my integration vlan 1201. This was the RP vlan, I never changed it over to VLAN 120.   So, I just did that and it seems to work. I feel kind of stupid with this oversight. ... View more

We had this same issue with a MS-120-48 port. There weren't any reported issues, but we swapped out a few cables and the errors were still showing up. Meraki ended up sending us a replacement and that device has been error free.  ... View more

I configured the meraki switch stacks to never be root for the network and published vlan 1 across all trunked uplinks - the meraki stacks all acknowledge the cisco switches as root for the network now and there has not been a designated >  root  root > designated event since I made the changes at 5am this morning - the event logs from the previous few days indicate a STP event several times per day so that looks promising. I'll reconnect the port channel from my other bldg in the near future to verify that problem has gone away also.  ... View more

Thank you to everyone for being so active in the Meraki Community.     We have identified the issue which has been causing MS22, MS42, MS220 and MS320 switches to require a physical reboot during an upgrade.  The issue is present on switches currently running MS 9.0 and above.  We hope to rectify this issue and provide a fix shortly.    In the interim, we have discovered a reboot of the switch via dashboard prior to performing an upgrade will prevent the switch from becoming unreachable.   As always, if you have any further questions/concern, please do not hesitate to reach out to our Cisco Meraki Support Team. ... View more