Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Copying a Configuration File from One Routing Engine to the Other

    You can use either the console port or the management Ethernet port to establish connectivity between the two Routing Engines. You can then copy or use FTP to transfer the configuration from the master to the backup, and load the file and commit it in the normal way.

    To connect to the other Routing Engine using the management Ethernet port, issue the following command:

    user@host> request routing-engine login (other-routing-engine | re0 | re1)

    On a TX Matrix router, to make connections to the other Routing Engine using the management Ethernet port, issue the following command:

    user@host> request routing-engine login (backup | lcc number | master | other-routing-engine | re0 | re1)

    For more information about the request routing-engine login command, see the CLI Explorer.

    To copy a configuration file from one Routing Engine to the other, issue the file copy command:

    user@host> file copy source destination

    In this case, source is the name of the configuration file. These files are stored in the directory /config. The active configuration is /config/juniper.conf, and older configurations are in /config/juniper.conf {1...9}. The destination is a file on the other Routing Engine.

    The following example copies a configuration file from Routing Engine 0 to Routing Engine 1:

    user@host> file copy /config/juniper.conf re1:/var/tmp/copied-juniper.conf

    The following example copies a configuration file from Routing Engine 0 to Routing Engine 1 on a TX Matrix router:

    user@host> file copy /config/juniper.conf scc-re1:/var/tmp/copied-juniper.conf

    To load the configuration file, enter the load replace command at the [edit] hierarchy level:

    user@host> load replace /var/tmp/copied-juniper.conf

    Caution: Make sure you change any IP addresses specified in the management Ethernet interface configuration on Routing Engine 0 to addresses appropriate for Routing Engine 1.

    Modified: 2014-09-19