The install guide calls out mounting vertically/upright position.    "NOTE - It is important to ensure that the sensor is oriented in the upright position for PM2.5 sampling to accurately collect data."   I've only seen mounting height and coverage area numbers specifically for vape detection scenarios with the MT14. https://documentation.meraki.com/MT/MT_General_Articles/MT14_High_Sampling_Mode#Installation_Best_Practise_for_Vape_Detection ... View more

Think of the Switch mgmt IPs just like any client. They just need to be on a VLAN that can NAT out through your firewall to reach the internet/dashboard. Typical best practice is to use dedicated mgmt VLANs/subnets for infrastructure devices like Switches, AP, Cameras, etc. But they literally can be on any VLAN/subnet on your LAN as long as they can reach the internet.   For example in my network I use a unique VLAN for Switches, APs, Cameras. The mgmt VLAN for Switches is the native VLAN on my trunk ports. This allows the switch to grab a DHCP IP from the switch mgmt VLAN and this VLAN has proper firewall rules in place for it to talk to dashboard. ... View more

Looks like you got it sorted yes? ... View more

I have a 75 running 18.2, but it's not my main fw so my use/testing on it's definitely limited. Hoping to see a beta version bump very soon though 🤞 ... View more

Hmm. I've been on every release of 18.2 beta on my MX95 without issue. My MSFT teams use is limited though compared to Webex. ... View more

A SSID tunnel should be considered the same as an AutoVPN (site to site) tunnel and therefore the same sizing guidelines would apply. ... View more

If you upgrade to MX 18.2 firmware it adds a Live Firewall Logging tool https://documentation.meraki.com/MX/Firewall_and_Traffic_Shaping/Firewall_Logging ... View more

What model MX do you have? ... View more

That's not what anyone is suggesting. Distributed Layer 3 roaming is meant for when a SSID is configured to use AP tags mapped to VLANs. For example, per building or per floor subnets that will have clients roaming between them.   Having a SSID configured for L3 roaming but only mapped to one VLAN doesn't do anything. Clients are only ever on the single VLAN mapped to that SSID.   https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practice_Design_-_MR_Wireless/Wireless_Layer_3_Roaming_Best_Practices#Distributed_Layer_3_Roaming   And with that said that was just an observation I made of your config. That would not be a reason clients cannot ping each other.   At this point I'd recommend you open a Support case and do some real time troubleshooting with a Meraki engineer. ... View more

They're all bridged mode/L3 roaming. Which by the way isn't a valid or needed config as each SSID only maps to a single VLAN.   L3 with one VLAN doesn't do anything. ... View more

Can you give a specific example of a source and destination IP that cannot ping each other? 6.0.0.0/8 IPs are going to cause you issues. I can tell you that much. ... View more

Can you ping all your networks that aren't 6.x.x.x IPs?   ... View more

I see you have lots of SSIDs, VLANs/subnets. What specific VLAN is this issue occurring on? ... View more

MR will come later ... View more

Are you able to login now? I'm thinking yes based on your screenshot. When logged in go to your email in the upper right, click My profile, and on that page you should be able to disable 2FA, save, then re-enable 2FA to get a new QR code.     Just noticed you said it's enabled at your Org level. It does seem to then remove the off function as I noted at the user level. My thought would be disable it Org wide, then disable your own 2FA, set it back up, then enable at Org level again.   Or maybe run it by Support to see if there's another way I'm unaware of.  ... View more

Do the MXs have a direct link between them? If yes, when switch 1 was down was traffic still flowing from switch 1 or 2 > MX 2 > MX 1 > internet? ... View more

Is the 3550 maybe using a L3 routed port config? Meraki switches don't support routed ports today and instead you'd define a L3 interface on the switch and then place the switch port into said VLAN.   When you created the first VLAN on the MS425 it would have required a next hop IP which would in turn create a default route out from the switch. Is that next hop reachable? And, does the next hop know how to get back to the Meraki switch VLAN(s)? ... View more

We don't offer nor test/certify any antennas besides the ones the MX67C come with. That said they are removable and are RP-SMA connectors. So, with a compatible connector and as short of a cable as possible it might work. You would have to test it yourself. ... View more

In that case I'd recommend you open a Support case ... View more

Did you review the LAN port mapping to ensure the config still aligns properly? The LAN port numbering is different between a MX64 and MX85.   https://documentation.meraki.com/MX/Other_Topics/MX_Cold_Swap_Replacing_an_Existing_MX_with_a_Different_MX#Port_Mapping_for_different_MX_models  ... View more

The document covering what @GIdenJoe mentioned above https://documentation.meraki.com/MR/Radio_Settings/MR_Regulatory_Domains ... View more

I think this is now addressed in 18.107.6    "Corrected an issue that resulted in AutoVPN tunnels briefly dropping and re-establishing after configuration or WAN connectivity change if 1) the MX was configured in high availability (HA) mode and 2) both AutoVPN peers were running MX 18" ... View more

Appears to be a UI issue with the new "Design System" view of dashboard. I don't use that so my menu formatting is different/classic style. I'd recommend tossing a case into Support to report it. ... View more

Anytime you're out of compliance/over subscribed it should invoke a 30 day grace period. Again, I'd talk through it with your Meraki Account Team first. ... View more