Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Configuring Junos OS for the First Time on a Device with Dual Routing Engines

1. Go to Configuring Junos OS for the First Time on a Router or Switch with a Single Routing Engine and follow Step 1 through Step 5 to initially configure the backup Routing Engine.

2. Create the configuration group re0. The re0 group is a special group designator that is only used by RE0 in a redundant routing platform.
   [edit]root@host# set groups re0
3. Navigate to the groups re0 level of the configuration hierarchy.
   [edit]root@host# edit groups re0
4. Specify the router hostname.
   [edit groups re0]root@host# set system host-name host-name

   Note: The hostname specified in the router configuration is not used by the DNS server to resolve to the correct IP address. This hostname is used to display the name of the Routing Engine in the CLI. For example, the hostname appears at the command-line prompt when the user is logged in to the CLI: user-name@host-name>

   Note: Before you begin Step 5, see Supported Routing Engines by Chassis to find the management Ethernet interface that you should use to perform this configuration.

5. Configure the IP address and prefix length for the router management Ethernet interface. The management Ethernet interface provides a separate out-of-band management network for the router.
   • For routers that use management Ethernet interface fxp0:
     [edit groups]root@host# set interfaces fxp0 unit 0 family inet address address/prefix-length
   • For routers that use management Ethernet interface em0:
     [edit groups]root@host# set interfaces em0 unit 0 family inet address address/prefix-length

     To use em0 as an out-of-band management Ethernet interface, you must configure its logical port, em0.0, with a valid IP address.

6. Set the loopback interface address for the re0 configuration group:
   [edit groups]root@host# set re0 interfaces lo0 unit 0 family inet address address/prefix-length
7. Return to the top level of the hierarchy.
   [edit groups re0]root@host# top
8. Create the configuration group re1.
   [edit]root@host# set groups re1
9. Navigate to the groups re1 level of the configuration hierarchy.
   [edit]root@host# edit groups re1
10. Specify the router hostname.
    [edit groups re1]root@host# set system host-name host-name

    Note: Before you begin Step 11, see Supported Routing Engines by Chassis to find the management Ethernet interface that you should use to perform this configuration.

11. Configure the IP address and prefix length for the router management Ethernet interface.
    • For routers that use management Ethernet interface fxp0:
      [edit groups]root@host# set interfaces fxp0 unit 0 family inet address address/prefix-length
    • For routers that use management Ethernet interface em0:
      [edit groups]root@host# set interfaces em0 unit 0 family inet address address/prefix-length

      To use em0 as an out-of-band management Ethernet interface, you must configure its logical port, em0.0, with a valid IP address.

12. Set the loopback interface address for re1 configuration group:
    [edit groups]root@host# set re1 interfaces lo0 unit 0 family inet address address/prefix-length
13. Return to the top level of the hierarchy.
    [edit groups re0]root@host# top
14. Configure the apply-groups statement to reproduce the configuration group information to the main part of the configuration and to specify the group application order.
    [edit]root@host# set apply-groups [ re0 re1 ]
15. Configure Routing Engine redundancy:
    [edit]root@host# set chassis redundancy routing-engine 0 masterroot@host# set chassis redundancy routing-engine 1 backup
16. Save the configuration change on both Routing Engines:
    [edit]user@host> commit synchronize

1. Configure the IP address of the DNS server.
   [edit ]root@host# set system name-server address
2. Configure the router domain name:
   [edit ]root@host# set system domain-name domain-name
3. Configure the IP address of a backup or default router. A backup router is used only while the routing protocol process is not running. Choose a router that is directly connected to the local router by way of the management interface. The router uses this backup router only when it is booting and or when the Junos routing software (the routing protocol process, rpd) is not running. For more information, see Configuring a Backup Router.

   For routers with two Routing Engines, the backup Routing Engine, RE1, uses the backup router as a default gateway after the router boots. This enables you to access the backup Routing Engine. (RE0 is the default master Routing Engine.)

   Note: The backup router Routing Engine does not support more than 16 destinations. If you configure more than 16 destinations on the backup Routing Engine, the Junos OS ignores any destination addresses after the sixteenth address and displays a commit-time warning message to this effect.

   [edit]root@host# set system backup-router address
4. Set the root password by choosing one of the following:
   1. To enter a clear-text password, use the following command:
      [edit]root@host# set system root-authentication plain-text-passwordNew password: type passwordRetype new password: retype password
   2. To enter a password that is already encrypted, use the following command:
      [edit]root@host# set system root-authentication encrypted-password encrypted-password
   3. To enter an SSH public key, use the following command:
      [edit]root@host# set system root-authentication ssh-rsa key
5. Optionally, display the configuration statements:
   [edit]root@ show

   system {host-name hostname;domain-name domain.name;backup-router address;root-authentication {(encrypted-password "password" | public-key);ssh-dsa "public-key";ssh-ecdsa "public-key";ssh-rsa "public-key";}name-server {address;}interfaces {fxp0 {unit 0 {family inet {address address ;}}}}}

   On routers that use management Ethernet interface em0, you will see em0 in place of fxp0 in the show command output.

6. After you have installed the new software and are satisfied that it is successfully running, issue the request system snapshot command to back up the new software on both master and backup Routing Engines.
   {master}user@host> request system snapshot

   The root file system is backed up to /altroot, and /config is 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.

   Note: After you issue the request system snapshot command, you cannot return to the previous version of the software, because the running copy and backup copy of the software are identical.

For information about creating configuration groups, see CLI User Guide.

For information about configuring high availability features for redundant Routing Engine systems and the re0 group, see Junos OS High Availability Configuration Guide.