I’m sure that there are many times a network admin is not sure of the changes that he is making and he does not know whether the changes will disconnect him or not.
there is a handy command in cisco: shutdown in n minutes
with this command if you lose your access due to recent changes, the system could reload with startup-config after some minutes and you have access to system again.
there is no handy command in ROS to do this simply. I use some kind of script to do this. but that is far away from a handy command.
a command could be there to restore a saved configuration in n minutes to avoid loss of access remotely.
I’m sure that everyone are agree to add this simple but handy feature to ROS.
I hope everyone vote for it…
Use safe mode, which doesn’t commit changes to disk until you leave safe mode (by default all changes to the running config are persisted to the startup config, in safe mode that does not take place). If the session that invoked safe mode interrupt abnormally changes are rolled back - so if you screw up routing or the firewall you’re taken care of. You can of course also schedule reloads just like in IOS.
So what you want already exists.
By the way, if you want to look at the best way to handle this look at JunOS. You can have scheduled rollbacks, and config changes are transactional. Rebooting to get back old configuration is not something you would want to do on a high profile router.
hmmm… just dreaming: is it possible to use Safe Mode in API? I still don’t loose a hope about creating dynamic address-list entries, so delaying writes for weeks would be some kind of workaround =)