About ww

ww

https://documentation.meraki.com/General_Administration/Monitoring_and_Reporting/Meraki_Device_Reporting_-_Syslog%2C_SNMP%2C_and_API#SNMP_Configuration

ww

Api == meraki account The connection is https.

ww

Mr32 can not run 27 it will stay on 26.x If you look at a Mr33 it should be on 27.x

ww

You can check it at you mx Sd-wan & traffic shaping > Active-Active AutoVPN

ww

In case you use mx auto vpn, you can choose to not run active vpn on wan2 .

ww

Depending on your rf profile setting you may have to edit it there.

ww

Claim your order. Go to the org >inventory. Select a device, and add it to the mx network. If that does not work just create a New network. Then go the org overview page. Select both networks and press combine https://community.meraki.com/t5/Dashboard-Administration/Combining-Network-Types/m-p/116548#M4338

ww

Can you show the trunk config of 9500 Trunk config of meraki trunk port Management config of the switch By no native vlan you mean you are using native vlan 1?

ww

What did you set as management vlan at switch> switch settings? What did you set at the switch itself on the management vlan field? What the native vlan of the 9500?

ww

I would try reboot 1 ap to see if that ap obeys the settings after reboot. Ofc you could also log a meraki case

ww

@TLoperDenverIT Thats only for http(s) traffic

ww

There is a mac whitelist on the switchport settings. You can edit that if you know the mac address of the client https://developer.cisco.com/meraki/api-v1/#!update-device-switch-port macAllowList

ww

https://community.meraki.com/t5/Security-SD-WAN/Client-VPN-and-AMP/td-p/97568 @KarstenI tested this

ww

Lots of people asking for 1Gbit. So there is the mx75. Looks like a few models need to go eos

ww

You are sure you edited the profile assigned to the ap? Did you wait a few hours?

ww

I dont know about the ms390 But all other meraki switches/devices are using (even when stacked) a unique ip for management to the cloud. Its recommended that the switches get a ip on native vlan of the upstream router/device

ww

You can not mix different mx licenses in the same organization

ww

Can you also verify the dhcp/bootp packets from a capture on the client itself. (In dont trust meraki switch packet captures)

ww

Can you check the wireless profile assigned to your meraki ap's. In would try this: Disable band steering. Disable client balancing 5ghz channel set to 20Mhz ax disabled

ww

If wan1 is disconnected, instantly. If it still has a link it depends, but schould be within 300 seconds. https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practice_Design_-_MX_Security_and_SD-WAN/Meraki_SD-WAN#Failover_Times

ww

Just create the vlan and ip on the mx. And turn of dhcp for that vlan. Then put it on the trunk to a switch. Exclude mx ip from your dhcp server

ww

There is no real downside. In case you have only 50 devices active, but the scope is 90%full, you could also first look to decrease the dhcp leasetime f.e. if its on 1 day you can put it 8 hours In case you really have 200+ active devices i would make it a /23 and combine it with a fw upgrade.

ww

Do you have a firewall somewhere that allowed the meraki ip + port 7351? If possible check that fw logging what happens to the session

ww

Only one ap has this message or both?

ww

For example. A mr46 is best on the ceiling. Mr46e could be a good choice for wall mount

ww

Community Record

Badges