Rescue and Recovery of Configuration File (Junos OS)

To save a current device configuration as a rescue configuration file:

1. Edit the configuration file on the device to reflect the base configuration you wish to use.

2. In the CLI operational mode, save this edited base configuration as the rescue configuration file:

   content_copy zoom_out_map

   user@host> request system configuration rescue save

   The rescue configuration file is automatically saved under /config directory as rescue.conf.gz.

You can verify that the syntax of a configuration file is correct and check for commit check errors by using the test configuration filename command.

To verify if a rescue configuration file is correct:

This task is optional but recommended.

To copy the rescue configuration to a remote server:

Your rescue configuration is probably not exactly the configuration you want or need on your system. Therefore, you will want to examine the failures that occurred when you tried to activate the current configuration and make corrective actions.

To correct the failed configuration:

Not all platforms run Junos OS with updated FreeBSD. Those that do not or are releases earlier than Junos OS Release 16.1, do not have the automatic recovery mode. You will need to rollback to rescue configuration manually to bring the device back to normal running mode.

To roll back to the rescue configuration:

To delete an existing rescue configuration:

To copy the saved configuration to the router:

1. Log in to the console as root. There is no password.

   content_copy zoom_out_map

   Escape character is '^]'. 
   [Enter]
   router (ttyd0)
      
   login: root
   Password: [Enter]

   Initially, access to the router is limited to the console port after a recovery installation. Access through the management ports and interfaces is set in the configuration. For information about accessing the router through the console port, see the administration guide for your particular router.

2. Start the CLI:

   content_copy zoom_out_map

   # cli

3. Copy the configuration file on the remote server to the router’s /var/tmp directory:

   content_copy zoom_out_map

   root@host> ftp remote-server
   user: username
   password: password
   ftp> bin
   Type set to I.
   ftp> get /path/file
   ftp> bye
   Goodbye.

Once the saved configuration file is copied to the router, you load and commit the file:

1. Start the CLI configuration mode.

   content_copy zoom_out_map

   user@host> configure
   Entering configuration mode
       
   [edit]
   user@host# 

2. Load the file into the current configuration. You should override the existing file.

   content_copy zoom_out_map

   user@host# 
   load override /var/tmp/filename
   load complete

3. Commit the file.

   content_copy zoom_out_map

   user@host# commit
   commit complete

4. Exit the CLI configuration mode.

   content_copy zoom_out_map

   user@host# exit
   user@host>

5. Back up Junos OS.

   After you have installed the software on the router, committed the configuration, and are satisfied that the new configuration is successfully running, issue the request system snapshot command to back up the new software to the /altconfig file system. If you do not issue the request system snapshot command, the configuration on the alternate boot drive will be out of sync with the configuration on the primary boot drive.

   The request system snapshot command causes the root file system to be backed up to /altroot, and /config to be backed up to /altconfig. The root and /config file systems are on the router’s CompactFlash card, and the /altroot and /altconfig file systems are on the router’s hard disk or solid-state drive (SSD).