I know as a network engineer we always have to do configuration changes in our day to day work however a miss-configuration may lead to access loss or communication loss. To overcome this situation, we have a builtin utility within configuration Commit called Commit Confirmed which enables us with an option to rollback the configuration changes if we do not confirm them with another Commit within a set time limit.
So if we made a wrong/miss configuration and got kicked out of the system we are not stuck with it; system will rollback to its original configuration state and we will be able to log back in.
Example:
In this example we will configure a loopback 1 on the router R1 and test the configuration commit with 1 minute to rollback if we do not confirm.
Topology:
Router R1:
Show interface brief showing the loopback interfaces:
Router R1 configured for Loopback 1 with commit confirmed in 1 minute with show error to display the error message when we do not confirm
Router R1 status after configuration change:
Step1: Checking the logging for the commit ( showing the commit for the initial configuration change)
Step2: Checking interface status after commit ( showing the new interface Loopback 1 available after change)
Step3: Checking the commit ( showing the configuration change we made to test the scenario)
Step4: Checking the logging after 1 minute (showing the new system commit to rollback the configuration)
Step5: Checking the commit after 1 minute (showing the new commit by system to rollback configuration of Loopback 1 interface since we never confirmed)
Step6: Checking interface status after 1 minute (showing the Loopback 1 no longer available)
Note: If we see the configuration was correct and everything works fine you can just type commit within the time limit (1 minute per our above example) we specified initially and the changes will be made permanent.
Happy Networking !!!!!