I anticipate getting a wide variety of answers to this question...and I am sure they will all be excellent. I am going to have to spend a great deal of time soon modifing configs on some Nex 5020's (4.1) we have. I do not have the luxury of the "checkpoint-rollback" function safety net. Aside from copying off the running config to an tftp server and bringing it back in when flames come out of the switch....what other ways are there to backout of a config error (fatfinger...wrong cli command...etc). I do like the "verify" function, but , unfortunately it will only warn me of typos and consistency (not if I meant to type "vlan add" not "add vlan") which we all know will cause havoc if not used correctly.. What I am looking for is a method(s) to get back to a stable state after a "ooops I meant vlan add not add vlan".
You can also negate using a shceduled reload and instead use the Cisco archive rollback feature
config archive path flash:backup exit
sh archive configure replace flash:backup-0 time 10 ( if not verified within 10 minutes router will revert your changes back WITHOUT reloading your router)
Make some changes you to:
conf t default inter fa0/0 default inter fa0/1
sh archive config differences
configure revert timer xxx( if you wish to extend the timed rollback further)
( ONLY if you happy with your changes) - ##THIS JUST STOPS THE ROLLBACK IT DOES NOT SAVE THE RUNNING CONFIG## -If not applied, then the specified time limit reached a rollback to the exisitng running config prior to changes will be initiated.
Please don't forget to rate any posts that have been helpful.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...