Hi Guys, here is what ended up practically solving the issue for us. But it is more of an art than a formula since different Switches (MS390 vs MS125) ended up with different settings. 1. Port Isolation - Enabled 2. Link Negotiation - 1 GB Fixed to the MR30H 3. Flood unknown multicast traffic: try Enable / Disable and see if helps.   A firmware upgrade was important since Meraki added Multicast Queuing. Let me know if this helps.       ... View more

I have tried today it is working fine. you can use Cisco GLCT to Uplink ports. ... View more

If your inner traffic is not tagged, your outer traffic will not be tagged to. Please make a capture on the final switch right before the packet enters the LAN interface of the MX. Or make sure you have rules in place to tag the packets at the MX. ... View more

As for today, Meraki still do not have feature to this. We still tweaking from the netscaler. ... View more

@CameronMoody ? ... View more

@Raj66 wrote: Hi @NolanHerring , As @PhilipDAth already mentioned, this can be  bypassed by adding a backend feature by Meraki support. Please open a case and explain your situation and support will take care of the rest.   Cheers!   Raj @PhilipDAth  and @Raj66    Support enabled this and now it works !! Woohoo thank goodness you guys said something lol ... View more

Hi   Sorry to stir the pot, but please remember that the Meraki High/Normal/Low priority settings are not what most people expect when they read Priority, but more like a bandwidth control...   See this: https://documentation.meraki.com/MX/Firewall_and_Traffic_Shaping/Using_Packet_Prioritization_on_a_Traffic_Shaping_Rule   ... View more