Configuring the JUNOS Software the First Time on a Router with a Single Routing Engine

To configure the software for the first time, follow these steps:

1. Connect a terminal or laptop computer to the routing platform through the console port—a serial port on the front of the routing platform. Only console access to the routing platform is enabled by default.
2. Power on the routing platform and wait for it to boot.

   The JUNOS software boots automatically. The boot process is complete when you see the login: prompt on the console.

3. Log in as the user 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@#.

4. Start the JUNOS software command-line interface (CLI):

   root@# cli

   root@>

5. Enter JUNOS software configuration mode:

   cli> configure

   [edit]

   root@#

6. 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 hostname

7. Configure the routing platform’s domain name:

   [edit]

   root@# set system domain-name domain-name

8. Configure the IP address and prefix length for the router management Ethernet interface, fxp0. fxp0 is an Ethernet management interface that provides a separate out-of-band management network for the router.

   [edit]

   root@# set interfaces fxp0 unit 0 family inet address address/prefix-length

9. Configure the IP address of a backup or default routing platform. This device is called the backup router, because it is used only while the routing protocol process is not running. Choose a router that is directly connected to the local routing platform by way of the management interface. The routing platform uses this backup router only when it is booting and only or when the JUNOS routing software (the routing protocol process, rpd) is not running.

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

   [edit]

   root@# set system backup-router address

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

11. Set the root password, entering either a clear-text password that the system will encrypt, a password that is already encrypted, or an SSH public key string. For more information about passwords, see Specifying Plain-Text Passwords.

    Choose one of the following:

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

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

       [edit]

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

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

       [edit]

       root@# set system root-authentication ssh-rsa key

12. 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-rsa "public-key";

    ssh-dsa "public-key";

    }

    name-server {

    address;

    }

    interfaces {

    fxp0 {

    unit 0 {

    family inet {

    address address ;

    }

    }

    }

    }

    }

13. 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 software defaults are now set on the routing platform.

    If you want to configure additional JUNOS software 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 Configuring Software Properties and System Management. You will need to commit your configuration changes to activate them on the routing platform.

14. Exit from the CLI configuration mode.

    [edit]

    root@ hostname# exit

    root@hostname>

15. Back up the configuration on the hard drive.

    After you have installed the software on the routing platform, committed the configuration, and are satisfied that the new configuration is successfully running, you should issue the request system snapshot command to back up the new software to the /altconfig file system. 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 CompactFlash card, 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.

Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice.