Meraki

Ryan_Miles

Here's a practical example of what @GreenMan mentioned using the License Calculator Your current state expiring 2025.10.02 If you were to "Add" a MX84 with a 7 year license it would bump the entire Org to 2026.04.18 adding a little over 6 months to the entire Org. You could of course accomplish this in many different ways using different model licenses and durations. My example is just a basic one.

Ryan_Miles

You really shouldn't post your Meraki serials or MACs in any public forum. Both can be claimed by anyone. Also, if you intend to sell the gear it needs to be unclaimed from any Org so the purchaser can claim it.

Ryan_Miles

I submitted that feedback to the Doc team. Thanks @RWelch

Ryan_Miles

https://documentation.meraki.com/General_Administration/Service_Providers_-_SPs/Service_Provider_Dashboard_Roles Note: This feature is only available to Service Providers and must be enabled by Meraki Support.

Ryan_Miles

Interesting idea. Maybe even something that could merged into an existing series like the unboxed podcast.

Ryan_Miles

What are the LAN port settings of the MXs? You don't want to have them set as drop untagged traffic. That will results in loops due to STP running on the untagged VLAN. Practical example of a spoke I have. Diagram and failover animations here. MX has VLANs: 10, 20, 30, 31, 32, 50. VLAN 30 is the mgmt VLAN for the switches and also what I use as the native VLAN. So, MX LAN ports are trunks, native 30, allow 10, 20, 30, 31, 32, 50. Switches ports are the same exact config - trunks, native 30, allow 10, 20, 30, 31, 32, 50. As for MS side STP options. This doc covers the use case for each option. My personally, I wouldn't use any guard mode for the switchports connected to the MX LAN ports.

Ryan_Miles

Partner = who you purchase from

Ryan_Miles

https://documentation.meraki.com/General_Administration/Licensing/Subscription_-_Licensing_Changes_Cloud_Managed#How_To_Submit_A_Change_Request

Ryan_Miles

A couple of quick things. In order to use Auto VPN & SD-WAN the MXs need to all be in the same Org. And Networks can only have one MX config (single MX or HA pair). So, one Org is pretty much a must. As is separate Networks for each location/MX. Subscriptions are applied at the Network level. So that will meet your requirement of per site costs.

Ryan_Miles

Yep, L3 is part of the basic ENT license https://documentation.meraki.com/MS/MS_Overview_and_Specifications/Catalyst_9300X-M_Datasheet#Features

Ryan_Miles

Not so far, no.

Ryan_Miles

Client roaming is decided by the client not by the AP. And the roaming behavior is dictated by how the vendor of the client has programmed it. It's not driven by time (on the client nor the infrastructure). https://documentation.meraki.com/MR/Wi-Fi_Basics_and_Best_Practices/Client_roaming_and_connectivity_decisions_explained

Ryan_Miles

Just trying to make sure we're talking about the same alerts. The one mentioned by @pjc is the new Org level alerts page. When you hover on the info bubble in the status column it mentions email and webhook. That doesn't mean (as far I as understand - I could be wrong) that alerts wouldn't still be shown on the Org alerts page.

Ryan_Miles

SMS isn't an option on that page?

Ryan_Miles

Getting alerted via email, webhook, both or you mean the alerts are just listed in dashboard under the alerts page or elsewhere?

Ryan_Miles

The IW9167 is not supported in dashboard today.

Ryan_Miles

The word "firewall" is missing from path in your script.

Ryan_Miles

Serials can be claimed in multiple Orgs. As @PhilipDAth mentioned above you need to also add the serial to a network to make sure it's not already in use elsewhere.

Ryan_Miles

Motion alerts in rain, heavy fog/mist, dust, bugs, etc can be tricky to deal with. The main approach to reducing the false alerts is adjusting the sensitivity of the motion alerts through the available controls (duration, sensitivity, area of interest, alert of people only). Another deployment practice that can help is to use an external IR panel instead of the onboard IR lights. This is especially helpful on the MV52 which I find to be the most sensitive to rain drops, snow, mist, bugs, etc. For on demand searches I find the people and vehicles filters in Vision Portal do a pretty good job cutting out many of the false positives. I hope we see more refinement with motion alerts in general.

Ryan_Miles

So you're talking about manual motion search? I'm not following.

Ryan_Miles

? https://documentation.meraki.com/MV/Advanced_Configuration/Motion_Alerts#Configuring_Areas_of_Interest

Ryan_Miles

I rarely (can't actually recall an actual time) I've seen in which band steering needs to be disabled. I typically only see things like 11r, 11w, or client balancing impacting legacy/poor performing clients.

Ryan_Miles

Claim them and find out. If it works, then unclaim and sell. If you can't claim then they're claimed elsewhere and unless the admin from that Org unclaims them there's nothing you can do.

Ryan_Miles

This thread gives a bit more guidance. I too cannot access it without requesting access.

Ryan_Miles

Workaround at the moment is when the page loads the "old" version click the ESC key to stop the page loading. Then you should be able to navigate around the tabs and between APs. If you have the device health tab don't click that or it will launch the "new" version and break the page again.

About Ryan_Miles

Ryan_Miles

Ryan Miles

Community Record

Badges