Meraki

Mon19

The core switch is obtaining its management IP via DHCP instead of the previously statically assigned

alemabrahao

Probably when you make the change, it can't communicate with the Meraki cloud again, so the configuration is rolled back, which is the expected behavior.

How are you making this change?

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.

RWelch

You can check Organization > Monitor > Change Log for any recent changes to the switch's management interface - not sure if you were wanting to find out the "why" part of the equation or what caused this to occur.

This normally happens when there have been manual configuration changes (e.g., an admin set the switch to use DHCP for management), or a configuration rollback, or firmware upgrade or device reboot that did not regain the static IP setting.

Assigning a Static IP Address

If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.

Meraki

Community

Meraki core switch fallback from Static IP to DHCP

Meraki core switch fallback from Static IP to DHCP