WAN uplink shutdown

guitb
Getting noticed

WAN uplink shutdown

In the event of an intentional shutdown of both Meraki MX WAN interfaces, leading to a loss of cloud connectivity, are there any automatic security mechanisms to revert to the previous configuration and restore the connection?

 

If not, what steps are needed to resolve this?

6 Replies 6
alemabrahao
Kind of a big deal

Meraki MX devices do not have automatic security mechanisms to revert to the previous configuration and restore the connection if both WAN interfaces are intentionally shut down.

 

For good practice, it is best to have a pair of MXs in HA.

If an intentional shutdown is performed manually, there is not much you can do other than access the MX locally and reactivate the interfaces.

To prevent this from happening, only those who really need access can do so.

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.
guitb
Getting noticed

How do you locally access the meraki MX?

alemabrahao
Kind of a big deal

Via Device Local Status Page.

 

https://documentation.meraki.com/General_Administration/Tools_and_Troubleshooting/Using_the_Cisco_Me...

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.
DarrenOC
Kind of a big deal
Kind of a big deal

@guitb , never tried it.  You would think the system would alert you to the dangers of doing so like the warning you get when configuring an uplink on the switches.

Darren OConnor | doconnor@resalire.co.uk
https://www.linkedin.com/in/darrenoconnor/

I'm not an employee of Cisco/Meraki. My posts are based on Meraki best practice and what has worked for me in the field.
Samir771
Meraki Employee
Meraki Employee
alemabrahao
Kind of a big deal

Unfortunately if you disable the interface manually the information in the document does not apply.

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.
Get notified when there are additional replies to this discussion.