Creating and Returning to a Rescue Configuration

If a user accidently commits a configuration that denies management access to the router, you must either connect a console to the router or invoke a rescue configuration. Using a rescue configuration is the recommended method.

A rescue configuration is one that you know allows management access to the router. You save a rescue configuration for recovery purposes — in case it is necessary to restore a valid, nondefault configuration. Once you have created a rescue configuration, you can return to it at any time.

To save the most recently committed configuration as the rescue configuration so that you can return to it at any time, issue the request system configuration rescue save command:

user@host> request system configuration rescue save

user@host>

To return to the rescue configuration, use the rollback rescue configuration mode command:

[edit]

user@host# rollback rescue

load complete

To activate the rescue configuration that you have loaded, use the commit command:

[edit]

user@host# rollback rescue

load complete

[edit]

user@host# commit

To save the most recently committed configuration as the rescue configuration so that you can return to it at any time using either the rollback command, issue the request system configuration rescue save command:

user@host> request system configuration rescue save

user@host>

To delete an existing rescue configuration, issue the request system configuration rescue delete command:

user@host> request system configuration rescue delete

user@host>

For more information about the request system configuration rescue delete and request system configuration rescue save commands, see the JUNOS System Basics and Services Command Reference.