Rescue Configuration on the Juniper Junos device

Another important thing that I wish to explain to you in this chapter is the “Rescue configuration”.

It is important always to have a “rescue configuration” which is a good version of your router configuration that you keep it saved in case something wrong went to your router or your active configuration, this way you can recall the rescue and it will be loaded to the active configuration.

Let’s save the rescue configuration taking a copy of the current active configuration of the router:

Maher@R1> request system configuration rescue save

To see where the file of the rescue configuration has been save, you need to do the following command:

Maher@R1> file list /config/

error: Stat failed: /config/..

/config/:

db_ext

db_ext-

juniper.conf.1.gz

juniper.conf.2.gz

juniper.conf.3.gz

juniper.conf.gz

juniper.conf.md5

rescue.conf.gz

usage.db

vchassis/

Maher@R1>

You can see that the rescue configuration has been saved in the config folder under the name of rescue.conf.gz

There is a way that you can test if the rescue configuration is on a good state and doesn’t have any error so you know that you have saved a good copy of the configuration. For this, you need to be logged in as a root so you can do the test. I logged in as a root and let me show you how this can be done:

root@R1> test configuration /config/rescue.conf.gz

configuration check succeeds

root@R1>

It looks great 😊

Now say that you have done some changes on the router configuration, then you decided that you want to rollback to the rescue configuration, this would be possible as the following:

root@R1# rollback rescue

load complete

[edit]

root@R1# commit

commit complete

[edit]

root@R1#

And finally, if you have decided to delete the rescue configuration file, you can do it as the following:

root@R1> request system configuration rescue delete

root@R1>

Let’s check if the file has been deleted under the config folder:

root@R1> file list /config/

/config/:

db_ext

db_ext-

juniper.conf.1.gz

juniper.conf.2.gz

juniper.conf.3.gz

juniper.conf.gz

juniper.conf.md5

usage.db

vchassis/

root@R1>

Yes indeed, I don’t see it anymore 😊

This is all what I wanted to show you in this lesson, hope you enjoyed it and see you in the upcoming one.

Course Content

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *


The reCAPTCHA verification period has expired. Please reload the page.

About