So, you’re making a change to your router in Siberia and you commit the cardinal sin of changing something that cuts your connectivity off from the router. Now what do you do? More importantly, who is getting sent to Siberia to power off/on the router and how long will it take them to get there? All questions you should be thinking about when making changes to remote Cisco devices! In this video tutorial I cover two (2) distinct and effective approaches on how to avoid and mitigate your downtime in this exact scenario. We see how the ‘reload in’ option can be leveraged and then compare and contrast this to using the Cisco ‘archive’ feature set so that we can ‘revert’ or ‘rollback’ auto-magically to a previously archived configuration. Finally, we examine the log option under the archive feature so that we can gather invaluable forensic information on exactly who was running what command and when on your device! Enjoy!
Link to remote change procedures using the archive utility: