Configuring a PSD with a Single Routing Engine

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 OS command-line interface (CLI):
   cli commandstarting Junos OS CLIroot@% cliroot@>
4. Enter Junos OS configuration mode:
   configure commandentering Junos OS configuration modecli> configure[edit]root#
5. Configure the name of the routing platform (the routing platform hostname). We do not recommend spaces in the routing platform name. However, if the name does include spaces, enclose the entire name in quotation marks ("  ").
   [edit]root# set system host-name host-name
6. Configure the routing platform’s domain name:
   [edit]root# set system domain-name domain-name
7. Configure the IP addresses and prefix lengths for one or both of the router management Ethernet interfaces (fxp0 and fxp1) on each Routing Engine.
   [edit]root# set interfaces fxp0 unit 0 family inet address address/prefix-length

   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.

8. 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.

9. 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
10. 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-passwordNew password: type passwordRetype 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
11. Commit the configuration, which activates the configuration on the routing platform:
    [edit]root# commit

    After committing the configuration, you see the newly configured hostname appear after the username in the prompt; for example, user@host#.

    Junos OS defaults are now set on the routing platform.

    If you want to configure additional Junos OS properties at this time, remain in the CLI configuration mode and add the necessary configuration statements. For more information about how to configure additional properties, see the Junos System Basics Configuration Guide. You will need to commit your configuration changes to activate them on the routing platform.

12. Exit from the Junos OS configuration mode.
    [edit]root@host-name# exitroot@host-name>
13. Issue the request system snapshot command to back up the configuration to the /altconfig file system on the hard drive.

    If you do not issue the request system snapshot command, the configuration on the alternate boot device will be out of sync with the configuration on the primary boot device. 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 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 the 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.