What is configuration rollback Best Practice

[AndrewAllen]

I am trying to set up some corporate guidelines around this. at present, I think there are three ways I could rollback a configuration to an earlier version

[UL]
[LI]Have an earlier version offline that I send to the router's flash and then reboot[/LI]
[LI]Could simply do a copy start runn if the running config had fewer statements then the start.[/LI]
[LI]Could build an offline config with explicit "no" commands, copy to start then reboot[/LI]
[LI]Could enter "no" commands followed by correct commands (if needed) line by line in config mode.[/LI]
[/UL]

Which of these (or other approaches) would this community and/or Cisco deem as a "Best Practice". Each one obviously brings its own impacts and caveats.

Thanks!

Andy Ford
Uplogix, Inc.
Austin

 

[lgarner]

I use a combination of 1 and 2. I have copies of the running-config downloaded periodically, so after changing it I'll have the old and new.

I also don't write to the startup-config until the new running-config proves itself to be stable and correct; that way, a simple "reload" will bring back the original.

 

[baddos]

copy running-config flash:mybackupconfig.txt

Then make your changes...

If need to rollback, then....

copy flash:mybackupconfig.txt running-config

 

[AdmanOK]

I agree with lgarner... never write your config until you have confirmed that everything is working. If you are dealing with a router than you cannot easily get physical access to (for example if it's on the other side of the country) then run a 'reload in 30' before you make any changes. That way if something goes wrong and you lose your connection to the site it will reboot and have the old configuration in 30 minutes. If all goes well with the changes you make you can either save before the thirty minutes is up or cancel the reboot. Either way you know that you won't be offline for more than half an hour. I also dump a copy of the configuration of to a TFTP on my machine before I make any changes.