I suggest you open a support case. ... View more

You should be using a Disconnect, not a CoA. In the web login configuration, you can increase the login delay to accommodate for the network change. ... View more

Take a look at this.   https://status.meraki.net/ ... View more

If it works like the MX Group Policies when authenticating via AD, it won't work, what will count are the policies for the last user who connected to the machine via RDS. ... View more

I suggest you open a support case or a new discussion on Meraki community. ... View more

Another thing, usually when it is not available in the dashboard, is probably something that should be requested from Meraki to enable. You can also call support instead of waiting for a response. ... View more

What is you switch model?   Reminder: MS17 is available to all Meraki Switches, except for MS390 and Catalyst 9300-M.   ... View more

Hi check it out.   Cloud CLI for Cloud-Native IOS XE - Cisco Meraki Documentation ... View more

Do you have full admin rights in the organization? If so, I suggest opening a support case. ... View more

You can replace without any problems. ... View more

Here is the point.   Solved: DHCP updates are not applied to MX when calling `appliance/singleLan` endpo... - The Meraki Community ... View more

Just to confirm, you are using this API, right? https://developer.cisco.com/meraki/api-v1/update-network-appliance-vlan/ ... View more

I forgot to specify that in this case it does not work for single LAN. ... View more

I suggest you contact Meraki via phone or via support case. ... View more

The Meraki API does not support updating DHCP options for the MX. ... View more

I totally agree, it's high time they gave us this possibility. ... View more

As mentioned, to retain logs for longer you need to send the information to a Syslog server. ... View more

When the primary MX's LAN connection drops, the failover behavior can be influenced by several factors, including VRRP heartbeats and the configuration of the LAN ports. Typically, VRRP heartbeats are used to monitor the health of the primary MX, and if these heartbeats are not received by the standby MX, it should trigger a failover. Some recomendations: Ensure VRRP monitoring is enabled and functioning correctly. This will help in detecting LAN failures more promptly. If possible, establish a direct link between the primary and standby MXs to improve failover detection and response times.   MX Warm Spare - High-Availability Pair - Cisco Meraki Documentation Routed HA Failover Behavior - Cisco Meraki Documentation ... View more

Oh, the guest is a user like any other, so the data retention time will be the same as for your corporate users. Could you explain better what you need? ... View more

It depends, what exactly do you need? Here is a list of log retention periods and other information. Dashboard Data Availability - Cisco Meraki Documentation ... View more

Network or organization? If you are looking for a network, you will find everything you need in the link below.   https://documentation.meraki.com/General_Administration/Inventory_and_Devices/Adding_and_Removing_Devices_from_Dashboard_Networks ... View more

Check it out.   https://community.meraki.com/t5/Security-SD-WAN/Service-Notice-Unexpected-MX-reboots/m-p/269394 ... View more

It is not a good practice, I personally have seen some problems happen, so avoid it. ... View more