• Downloads
• Configuring a PSD with Redundant Routing Engines    

• Related Topics
• Configuring an RSD and Creating PSDs
• Configuring a PSD with a Single Routing Engine

Configuring a PSD with Redundant Routing Engines

To initially configure a PSD with redundant Routing Engines:

1. Connect to the console port on the Routing Engine that is assigned to the PSD you want to configure.
2. At the login prompt on the console, log in with the username root.

   Initially, the root user account requires no password. You can see that you are the root user, because the prompt on the routing platform shows the username root@%.

3. Start the JUNOS Software command-line interface (CLI):

   cli commandstarting JUNOS CLI

   root@% cli

   root@>

4. Enter JUNOS Software configuration mode:

   configure commandentering JUNOS Software configuration mode

   cli> configure

   [edit]

   root#

5. Configure a hostname and the IP addresses and prefix lengths for one or both of the router management Ethernet interfaces (fxp0 and fxp1) on each Routing Engine.

   If both interfaces are configured (for JCS switch module redundancy), we recommend that the IP address for each interface be on a separate subnet. The fxp0 interface connects to port 6 on the JCS switch module in bay 1, whereas the fxp1 interface connects to port 6 on the JCS switch module in bay 2.

   [edit]

   root# edit groups

   [edit groups]

   root# set re0 system host-name router1

   root# set re0 interfaces fxp0 unit 0 family inet address 10.10.10.1/24

   root# set re1 system host-name router2

   root# set re1 interfaces fxp0 unit 0 family inet address 10.10.10.2/24

   root# set re0 system host-name router1

   root# set re0 interfaces fxp1 unit 0 family inet address 10.20.20.1/24

   root# set re1 system host-name router2

   root# set re1 interfaces fxp1 unit 0 family inet address 10.20.20.2/24

6. Configure the routing platform’s domain name:

   [edit]

   root# set system domain-name domain-name

7. Set the loopback interface address for each Routing Engine.

   [edit groups]

   root# set re0 interfaces lo0 unit 0 family inet address 2.2.2.1/32

   root# set re1 interfaces lo0 unit 0 family inet address 2.2.2.2/32

8. Issue the apply-groups statement to reproduce the configuration group information to the main part of the configuration.

   [edit groups]

   root# top

   [edit]

   root# set apply-groups [re0 re1]

9. Configure Routing Engine redundancy:

   [edit]

   root# set chassis redundancy routing-engine 0 master

   root# set chassis redundancy routing-engine 1 backup

   root# set chassis redundancy routing-engine graceful-switchover

10. Save the configuration change on both Routing Engines:

    [edit]

    root# commit synchronize

11. Configure the IP address of a backup or default routing platform.

    [edit]

    root# set system backup-router address

    Choose a router that is directly connected to the local routing platform by way of the management interface.

12. Configure the IP address of a DNS server. The routing platform uses the DNS name server to translate hostnames into IP addresses.

    [edit]

    root# set system name-server address

13. Set the root password, entering a clear-text password that the system will encrypt, a password that is already encrypted, or an SSH public key string.

    Choose one of the following:

    • To enter a clear-text password, use the following command:

      [edit]

      root# set system root-authentication plain-text-password

      New password: type password

      Retype new password: retype password

    • To enter a password that is already encrypted, use the following command:

      [edit]

      root# set system root-authentication encrypted-password encrypted-password

    • To enter an SSH public key, use the following command:

      [edit]

      root# set system root-authentication ssh-rsa key

14. 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 routing platform’s flash disk, and the /altroot and /altconfig file systems are on the routing platform’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.

Note: The logout-on-disconnect statement at the [edit system ports console] hierarchy level is not supported for Routing Engines on the JCS1200 platform. When the cable is unplugged from the Routing Engine, the user is not logged out of the console session.