See this on our MR36s running 30.7.1 as well and no changes on our side and no way all the cables are bad for all the APs reporting the issue. Tried shut/no-shut and hardcoding to 1000 but neither worked.  APs com back up at 100Mbps.    No way all of us, all of the sudden, have bad cabling, it is surely an issue with the AP firmware.     Doesn't seem to be an issue for our MR56s.     GigabitEthernet1/0/26 is up, line protocol is up (connected) Hardware is Gigabit Ethernet, address is b44c.90c4.7a9a (bia b44c.90c4.7a9a) Description: Meraki AP-M36 MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec) Full-duplex, 100Mb/s, media type is 10/100/1000BaseTX       ... View more

Update to all this, it seems OSX clients won't tag ZOOM traffic over a Meraki SSID, but the AP will tag that traffic once it sees it.  I assume this is due to fast lane on OSX but I really don't have any way to confirm that.  Can you disable fast lane via Meraki?    At the end of the day we have it working mostly for what we want and these are the traffic shaping rules we ended up with.  We see the tags from the client or the wired side of the AP if the client isn't tagging it.       ... View more

@GIdenJoe    These are the default rules you are referring to?  If so have you had good results using them? I can set ZOOM to use whatever I want and can go as far as to match those default rules.       ... View more

The reason I did is because 56/CS7 is what Cisco recommended and ZOOM defaults to.  I am not seeing the right tags from the client connected to the AP when it reaches the firewall.  So it’s either all traffic is being tagged as CS7 or none of it.  Versus outside the office where my voice and video are being tagged correctly.   I can change CS7 to something else once I have this working correctly.   ... View more

Yeah so that is from my house, so the only rules applying there are ZOOM marking them which it is doing.  In the office doing a packet capture from the firewall for wireless clients I don't see any tags or I see all (CS7) 56 which is just odd.  So I figured Meraki must be doing something nefarious because on the backbone we are just trusting the tags and prioritizing traffic based on them.     Below is from the firewall for a wireless client at the office and all their traffic towards the internet. You can see all this users traffic is tagged as CS7 and we see the complete opposite from other users with 0 tags whatsoever.       I wanted to be sure that if Meraki does see those tags it doesn't limit bandwidth to them.  So that is where the traffic shaping rules came into play and how to best ensure we had them configured correctly.  When checking all the moving parts we are seeing odd behavior and not sure what is causing it.      Make a long story short we are tagging traffic from ZOOM and we aren't seeing those tags applied correctly to wireless clients.  We know those clients can send/receive those tags because we see them outside the office, why inside the office we don't see the same behavior is the unknown.     Do you know if I specify a localsubnet on a rule will Meraki tag all packets on that subnet that match the ports I have defined on that same rule?  Its just not clear on what exactly those definitions are doing.    Let me see if I can decipher what wired office clients are doing.       ... View more

I have no MX, I have PAN firewalls at the office.   At home, outside of my network and sans Meraki I get the correct tags via my ZOOM client installed via the MSI file.  I want the same behavior in the office but again something is not translating.  Sometimes clients get all CS7 (56) and sometimes they get none at all.  All of them share the same wireless/core/firewall which is prioritizing traffic, but why some get tagged with 1 tag and others get no tags is the problem I am having.  And since this is only deployed on our wireless I am looking at the APs as part of the problem.     But traffic that is tagged is being influenced and given priority, I can see that.     ZOOM admin console: Packet capture from my home office, so the only influence here is ZOOM sending DSCP tags 56 and 40 to my client and vice versa so I know ZOOM can tag its traffic correctly on both windows and OSX.         What I don't fully understand is the correlation of ZOOM sending tags and Meraki honoring them if seen, adding them if not seen and or stripping them?         ... View more

Good point, so to be clear, we have ZOOM configured to push DSCP tags but our windows clients aren't honoring them along with some OSX clients in the office.   So to get around that we are trying to enforce them via Meraki as well as no bandwidth limits for traffic matching those DSCP markings.  But what does it matter if ZOOM is enforcing them and as well as Meraki? I mean if the tag is there no harm no foul, if it isn't then Meraki should apply it right?  ... View more

I am NOT specifying destination ZOOM CIDRs in the shaping rules in Meraki.  Are you saying don't specify 443/80 on the traffic shaping rules?  The only place I am specifying them on the firewall and I have to in order to be sure the FW is only prioritizing traffic to and from those specific IPs.     On my PAN FW We are matching ports/destination IPs and DSCP tags to prioritize traffic so what I am trying to accomplish is to ensure the tags we are prioritizing are being sent from ZOOM, honored/applied if not already by Meraki and then prioritized accordingly.  ... View more

Yeah man, we have done all that.  I am more focused on the Meraki side as to what is the best way to enforce/apply those tags on the AP/wireless side.   ... View more

Great thanks all! ... View more