Meraki

Ryan_Miles · ‎May 10 2023

Maybe give API a try. This call pulls the entire org inventory and includes the address field. Keep in mind this is for devices deployed (configured) in networks. If the serials just reside in the inventory, but are not bound to a network this call doesn't show them.

Ryan_Miles · ‎May 10 2023

MR32 is not a supported gateway for MTs https://documentation.meraki.com/MT/MT_Installation_Guides/MT10_Installation_Guide_-_Temperature_and_Humidity#List_of_Compatible_Gateways:

Ryan_Miles · ‎May 9 2023

Sounds like a browser issue or a bug. I've done both of the things you've mentioned plenty of times with no problem. I'd suggest a Support case so they can look into what's going on.

Ryan_Miles · ‎May 5 2023

You might want to check out Oberon's options. You can filter by Vendor and model to see what's compatible.

Ryan_Miles · ‎Apr 29 2023

This is how Meraki switches have always worked. Internet issues aside if you configure a static IP that is not valid the switch will revert to DHCP in order to try to get an IP and connect to dashboard. Being that Meraki devices are cloud managed there are multiple failsafe routines to ensure it can find a way to dashboard. Also, if you give it some time the device should revert to using it's static if that's a valid config. It shouldn't need a reboot.

Ryan_Miles · ‎Apr 27 2023

Do you perhaps know what switch they are wired back to and if yes look up the MAC table?

Ryan_Miles · ‎Apr 27 2023

Open a Support case

Ryan_Miles · ‎Apr 26 2023

I think your best option at this point is to open a Support ticket with Meraki and they can help troubleshoot the issue with you.

Ryan_Miles · ‎Apr 26 2023

Do you have the same cellular carrier at all sites or various carriers? Typically AutoVPN not working on cellular is due to CGNAT. In the US I almost never have issues with Verizon or T-Mobile. However, ATT almost never works unless you get a static IP and special APN from ATT.

Ryan_Miles · ‎Apr 26 2023

Keep in mind when you land private WAN on a MX WAN port and then do AutoVPN traffic isn't being NAT'd. It's L3 routed traffic inside a VPN.

Ryan_Miles · ‎Apr 26 2023

Many customers do this by landing the private WAN connection on a MX WAN port. You then have AutpVPN tunnels over both links. So, you no longer require static routes. Routing is handled by AutoVPN and what networks are marked for VPN. On the SD-WAN/traffic shaping page you can create rules for which WAN path to take. In this configuration internet bound traffic can take the private WAN path through HQ as you described.

Ryan_Miles · ‎Apr 19 2023

The bottom of this doc explains exactly what you're describing

Ryan_Miles · ‎Apr 18 2023

You have to delete them manually under the port config or perhaps with an API endpoint https://developer.cisco.com/meraki/api-latest/#!update-device-switch-port

Ryan_Miles · ‎Apr 17 2023

VLAN tagging can be left disabled at the SSID level. The VLAN tag in the IPSK GP will still work.

Ryan_Miles · ‎Apr 15 2023

Looks like it's resolved now

Ryan_Miles · ‎Apr 12 2023

The various causes of this error are being fixed. A number of fixes already went out over the past month that resolved many of these events. It's important folks report this into Support so any remaining issues around this can be resolved.

Ryan_Miles · ‎Apr 12 2023

You'll need to open a Support case and they can help you with this one.

Ryan_Miles · ‎Apr 10 2023

Try disabling magnetic design on Early Access Page and try again. Also, you should open a Support case so they have this error reported.

Ryan_Miles · ‎Apr 10 2023

Right. You have config issues. The one switch showing green has trunks set to 181 native. The alerting switches are all set as native 1. You need to fix the mismatch.

Ryan_Miles · ‎Apr 10 2023

You have native VLAN mismatch issues. Your Meraki switches (except for one) are configured as trunk, native 1, allow all. The upstream 3750 appears to be native 181?

Ryan_Miles · ‎Apr 6 2023

The mgmt IP doesn't affect any port level configs or client traffic

Ryan_Miles · ‎Apr 6 2023

On the page Switching > Configure > Switch Settings configure the mgmt VLAN as 181

Ryan_Miles · ‎Apr 6 2023

https://documentation.meraki.com/MR/MR_Installation_Guides/CW9162_Installation_Guide#LED_Indicators_and_Run_Dark_Mode

Ryan_Miles · ‎Apr 4 2023

For your second question, yes, the CW9166-MR supports the Meraki MT Sensors

Ryan_Miles · ‎Apr 4 2023

You can go the MX LAN PoE port route. Just be aware the MX will then detect the MG as a rogue DHCP server and if that alert if enabled you'll get an email. I've not tried reserving the entire DHCP scope and creating a fixed assignment just for the MX WAN port on the MG to see if that prevents the DHCP warning. Or, reserve the entire scope and statically address MX WAN 2.

About Ryan_Miles

Ryan_Miles

Ryan Miles

Community Record

Badges