Meraki

Talhaturkdogan

Can you tell us workaround?

jimmyt234

Sounds like you just need to make sure your device is kept online for >30 minutes after an upgrade for it to be "safe"? 😕

Suresh_stp

Hi, Do we have API endpoint for configuring source based routes and Non-Meraki VPN peers ? As we are in the migration of MX Devices, wanted to config via Python script using Meraki API's

EricCZ

Many thanks for your sharing guys. Just to let you know that without you we wouldn't be us 😉

rhbirkelund

Using Option 43 with FOM, you wouldn't have to use Meraki or API at all... The AP determines the regulatory domain itself, using the buildin GPS, or Proximity.

rhbirkelund

The Local LAN rule is always set to Deny on the first SSID. On all other SSIDs it's Allow.

GreenMan

You can't do it yourself... from the document that Alex linked: Everything is ready Once everything is confirmed to be set up and you are ready for the migration, initiate a migration from Meraki mode to DNA mode by raising a case with Meraki support.

Wade_Carroll

That was it! Not sure it caused any issues but it was annoying to look at. Thanks, I've turned off meshing and the 'overlapping' channels (SSIDs) went away. Thanks everyone for the suggestions

jrhop

Yeah we can get the 9162 for £400, but like you say its getting on now, released 2022 I believe. But I think they still sell WiFi 6 APs, released in 2019/2020.

srajiwate

how it works means because of what it act as DNS resolver ?

NetEngJH

I've removed the switches from the network and back to inventory, and back into the network. This removed all the switchport configurations and moved them all back to trunks. I've also changed from using static IP for management IP back to DHCP. Still to same problem. This is actually a pair of switches and the last thing that changed was creating them into a stack. I have also tried remove the stack config, physically removing the stack cables and factory resetting each switch individually, then try to form the stack again. Still the same problem. Support are in the process of issuing an RMA.

alemabrahao

Check this, it will help you. https://documentation.meraki.com/General_Administration/Inventory_and_Devices/Using_the_Organization_Inventory#Unclaiming_Devices

PhilipDAth

This is the layer 3 WiFi design guide. https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practice_Design_-_MR_Wireless/Wireless_Layer_3_Roaming_Best_Practices

cmr

That's what you should see. If you have another non 6e/7 Asp in the same network the WPA3 client should connect to the 5GHz on that AP and when roaming should step up to 6GHz. I've got this reliably working with CW9163E/CW9166I APs. Before you say the 9163 is a 6GHz AP, it isn't in the UK, or pretty much any of the world other than the US...

gagan239

Thanks for the replies. Meraki Access manager looks interesting.

rhbirkelund

From the top of a quick google search, you could refer to https://www.mdpi.com/2071-1050/14/18/11744 You'll have to review the credibility of the article, yourself. There's also https://www.everythingrf.com/community/what-is-the-impact-of-rain-on-rf-signal-propagation which usually are on point.

McWireless

Yea thinking this might be the case as it seems the support ticket is slowly arriving at the same conclusion.

alemabrahao

Are the devices you want to connect to the wireless network tagged appropriately in Systems Manager? Have you configured the SSID for EAP-TLS authentication?

PhilipDAth · ‎Mar 12 2025

You have me thinking. What about if you configure SAML (you can use Entra ID)? You would use your SAML credentials and SAML MFA, and then the SAML access token would be stored for as long as your SAML provider permits, and you can use biometric authentication on your phone. A heavy solution for the problem, but it is an option for you. And if you are heavily regulated, this is likely to tick additional boxes.

Ryan_Miles · ‎Mar 12 2025

@MartinLL thanks for testing and confirming. Our documentation mentions three permissions and the first one in my screenshot isn't part of that. Not even sure how that one got in my tenant config. I've since removed it and aligned to only what's mentioned in our doc. Also removed my screenshot as to not confuse matters. And I'm using the free Entra tier as well 👍

michalc · ‎Mar 12 2025

Just to clarify - this seems to be related to your very specific client eGauge Core WiFi (EG4215) and so far we are unable to replicate the issue in our lab. We have not heard from any other clients on a similar issue. The product specialist is still reviewing the case and you'll receive an update once we have one through the support ticket.

CarolineS · ‎Mar 11 2025

Moderator note: Marking Jaideep's reply as the solution, as it seems to be the definitive answer (at least for now!)

MauroF · ‎Mar 10 2025

Not really. First of all we authenticate via AAD DS in Azure which sync with EntraID. So there is integration from this point of view. But what i just said...is thanks to a different MX (mx68). I cannot do the same with a MX68W.

cmr · ‎Mar 6 2025

Totally agree with @PhilipDAth here. Meraki firmware is updated somewhat more frequently than some legacy vendors. If you need really need approval for specific versions, you should schedule the upgrade when you make the request, as you can do this for several weeks in the future. If it isn't approved the you can cancel or delay it.

rhbirkelund · ‎Mar 5 2025

Odd limitation though. 😄 Small-Form Factor Pluggable (SFP) and Stacking Accessories Change: Added "***Note: The number of Network Module ports are limited when C9300X-NM-8Y are used with the C9300X-48HXN models. Only 6 of the 8 ports will be available on a C9300X-48HXN switch."

About rhbirkelund

rhbirkelund

Community Record

Badges