Cloud Managed Networks

Finding that there is a default configuration saved as a checkpoint and when the switch loses connection it will cycle through our start-up configuration checkpoints and end at the default. So once it comes back online, it is on the last checkpoint which is the default configuration. 

I am going to proceed with removing the default configuration checkpoint. 

Before deleting anything I'd check what the reverted switches actually booted from, because AOS-CX doesn't walk through checkpoints on boot. A switch comes up on startup-config; if startup was never written it comes up default, and that's the pattern you're describing.

On one that reverted, run show checkpoint list and checkpoint diff startup-config running-config, and check whether checkpoint auto was ever set, since that's the one thing that rolls a config back on its own. My read is the ones that lost config had a Central push that landed in running but never made it to startup. Sort that and the checkpoint cleanup becomes housekeeping rather than the fix.

Finding that there is a default configuration saved as a checkpoint and when the switch loses connection it will cycle through our start-up configuration checkpoints and end at the default. So once it comes back online, it is on the last checkpoint which is the default configuration. 

I am going to proceed with removing the default configuration checkpoint. 

Most switches are plugged into a UPS and do not actually lose power so I am thinking its using auto to get a config in attempt to reestablish connection to Central. Am I understanding that correctly? Once the switch loses connection to Aruba Central does it proceed to go through these checkpoints until it can reach central again? I have weekly backups via ansible so I don't need a long list of checkpoints on the device. I am thinking that I would only need a few checkpoints on the switch and refer back to the backups if I need to get older config changes. I would still like to have auto setup options so if I break a configuration I have a timeline of when it will revert back to a known good config. 

Start-up config is the same as the running config on this device here:

Before deleting anything I'd check what the reverted switches actually booted from, because AOS-CX doesn't walk through checkpoints on boot. A switch comes up on startup-config; if startup was never written it comes up default, and that's the pattern you're describing.

On one that reverted, run show checkpoint list and checkpoint diff startup-config running-config, and check whether checkpoint auto was ever set, since that's the one thing that rolls a config back on its own. My read is the ones that lost config had a Central push that landed in running but never made it to startup. Sort that and the checkpoint cleanup becomes housekeeping rather than the fix.

Finding that there is a default configuration saved as a checkpoint and when the switch loses connection it will cycle through our start-up configuration checkpoints and end at the default. So once it comes back online, it is on the last checkpoint which is the default configuration. 

I am going to proceed with removing the default configuration checkpoint.