Rescue Configuration
A rescue configuration is the known working configuration. If the active configuration is corrupted, the device automatically loads the rescue configuration file as the active configuration.
Creating and Returning to a Rescue Configuration
A rescue configuration allows you to define a known working
configuration or a configuration with a known state for recovery, if necessary. This
alleviates the necessity of having to remember the rollback number with the
rollback
command. The rescue configuration rolls back the
device to a known configuration, or can serve as a last resort if your device
configuration and the backup configuration files become damaged beyond repair.
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
To return to the rescue configuration, use the rollback rescue
configuration mode command. To commit the rescue configuration, thereby activating
it, use the commit
command.
[edit]
user@host# rollback rescue
load complete
If the rescue configuration does not exist, or if the rescue configuration is not
a complete, viable configuration, then the rollback
command
fails, an error message appears, and the current configuration remains
active.
To delete an existing rescue configuration, issue the request system
configuration rescue delete
command:
user@host> request system configuration rescue delete
user@host>
We recommend setting the rescue configuration. This enables the device to
automatically load the rescue configuration file as the active configuration if
for any reason the current active configuration fails. A minor alarm
Rescue configuration is not set
is raised if you do not set
the rescue configuration using the request system configuration rescue
save
command.