Difficult to diagnose without looking at your Dashboard setup - Id say this is one for Meraki Support - and I'd definitely call in on the phone, rather than just raising via the Dashboard. Do you have the built-in 'Best for VoIP' performance class configured anywhere relevant to this traffic? ... View more

Have you tried deploying a second WiFi profile, for an SSID that is normally not advertised, that you can enable if you ever lose touch via the primary profile? ... View more

Basically as yet this is lacking significant highlighted customer demand so, to RyGuy's point, I'd really recommend getting in touch with your Meraki account team, with details of your business needs here. ... View more

OK - that is the Network-wide > clients page, right?   And the Meraki device on that Network is an MX?  My guess would be that maybe they don't generate any interesting traffic otherwise. While many / most devices would probably appear as a client in the Dashboard if they are routing traffic through the MX, a switch - particularly one not setup for management - is not a client in the same way as a PC, a smartphone etc.   Have you tried running packet captures on the LAN side of the MX, filtered for the switch MAC, to see what traffic (if any) it is generating? ... View more

CBS 250 cannot be monitored or managed by the Meraki Dashboard, so I'm not sure what you're indicating here.   Can you provide a screenshot or two? ... View more

Is the device associating to SSID    'M-F'  ?   How is it getting the Pre Shared Key? With the setup you have, if you want to prevent association, you need to keep the key private.   Without the key, the client won't be able to access the SSID ... View more

Yeah - I'm not sure why this has been called out here either.   As you say, it was previously the case anyway. No news on having UI flexiblity for this, at this stage, unfortunately - customers ask for a lot of different features, particularly for MX.    Fitting them all in and making them work together is a challenge.  If it's particularly pressing for you, I suggest contacting your Meraki account team and explaining the business case, so they can add weight to the official request. ... View more

Fixed...   Thanks for highlighting  🙂 ... View more

I'd be interested to understand your use case as, for MX-protected branches, Secure Connect is used primarily to provide secure Internet Access (hence the default route).   If you provide your Spoke MX with any more specific route though, that will be preferred over the SC default route.   So if you have a tunnel to a Hub in a traditional DC, which is advertising some routes for the services they host (typically from within RFC1918), that traffic would use the direct tunnel, not go via SC - but your Internet traffic would still flow via SC. You can also perform local breakout at the MX (full-tunnel exclusion), if you wish:   https://documentation.meraki.com/MX/Site-to-site_VPN/VPN_Full-Tunnel_Exclusion_(Application_and_IP%2F%2FURL_Based_Local_Internet_Breakout) ... View more

Si está utilizando el proceso de Prueba Gratuita de Meraki aquí, la licencia que se incluye no afecta la fecha de Terminación Conjunta, si solicita la prueba en una Organización existente. Si desea utilizar las funciones de AutoVPN para interconectar dispositivos MX, como ha descubierto, necesitará tener esos MX (y cualquier unidad VMX o Z4) en la misma organización, para las capacidades SD-WAN que proporciona. ... View more

Basically you'd look to use the API to PUT them back again...   The scripts that are out there, to enable the process of extracting the setup usually have accompanying script(s) to upload them, if needed. ... View more

Just to be clear - it doesn't say 'unspecified radio' - this event is being seen across two radios;   2.4 GHz (radio 0 [channel = 1]) and 5 GHz (radio 1 [channel = 36]) The reason is unspecified. I would check whether those client devices of yours support WPA3.  This technology is usually associated with 6 GHz W-Fi 6E and later - and require specific client side support.   My guess - based purely on the radios mentioned here - is that the Meraki APs may not support 6 GHz either. ... View more

You need to raise a case with Meraki Support.   My guess is that the standby MX is trying and failing to upgrade its firmware - or something along those lines.   Support should be able to dig further.  Suggest calling on the phone - it'll likely save a bunch of time. ... View more

I suggest you talk with your preferred Cisco partner - they should be able to provide you quotes specific to your situation. ... View more

The markings on the MR76 AP are correct: 2 antenna posts are dedicated to 2.4 GHz only.  The other two posts; to 5 GHz only.  You need to ensure the same coverage cell for each radio, so if you have (for example) an ANT-25 and an ANT-27 then, because they are both dual-band antennas, you could use each antenna on either radio, but you must connect both pigtails of an antenna to the same radio.  Do not split them one to 2.4 & the other to 5. ... View more

That's what you asked for...    🙂 Did you follow the link? ... View more

Pretty sure this is referring to SAML login and is expected behaviour.   The listed accounts have been used historically to access the dashboard, so will still be visible there, even though they've been deleted at the IdP end.   While they are listed, they will not be able to login. I believe such associations can be removed by toggling the enable / disable on that SSO. ... View more

Did you raise a case with Meraki Support?   Pcaps are the way to go, as recommended above, but Support can help you along the way ... View more

You'll want to use DHCP Option 43, with the appropriate Hex Option: Custom, Code: 43, Type: Hex,  Value: 01:04:00:00:00:02   As per https://community.meraki.com/t5/Security-SD-WAN/DHCP-Option-43-and-Sub-option/m-p/47435 ... View more

Not really - it's being subbed for Subscription Licensing, which I think most customers will ultimately find to be a much better balance between the 'all or nothing' approach of Co-termination and the 'micro-manage everything' of PDL.    https://documentation.meraki.com/General_Administration/Licensing/Subscription_-_Licensing_Overview Depending on your geo, it should be available to move to from Co-term at renewal time. ... View more

So...   chances are this is not a permitted 'conversion' from a Support perspective.  If you contact the Meraki account team, they may be able to reflect any residual value of the Z1 license in the pricing for the Z4 license. ... View more

Yes - it would have been like-for-like - unless there was no inventory left of Z1 (which I'd say is quite likely, given the age of Z1), in which case the nearest available equivalent model would be provided (probably Z3) and an appropriate license 'conversion' would be applied by Support.   If I could recommend;   you've made a few assumptions about how things might work - you'd have been better off checking;   initially with Support;   they have strict practices they have to follow.  They don't have any choice.   Secondly with the Meraki account team - if a new purchase was required.  As it's then a commercial discussion, they have a few more levers at their disposal. ... View more

For an all-Cisco solution incorporating MX, you might want to consider pairing it with Umbrella DNS protection but, as per your mention of cost;   Umbrella is an extra and Advanced Security licensing the same (though I can't imagine, in that environment, you'd really want the basic Enterprise MX license). https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Manually_Integrating_Cisco_Umbrella_with_Meraki_Networks https://docs.umbrella.com/deployment-umbrella/docs/the-activity-search-report   ... View more