Technical Documentation

Creating a New Configuration on a Single Routing Engine

To create a new base configuration on a single Routing Engine:

Log In to the Router Console

To log in to the router’s console interface and open the CLI in configuration mode:

  1. Verify the router is powered on.
  2. Log in through the console port as root.
    Amnesiac <ttyd0>

    login: root

    Note: From the factory, the root administration user account is not associated with a password. However, you must add a password to the root administration account before you can successfully commit a configuration.

  3. Start the CLI, which initially opens in operational mode. Note the command prompt ends with > in the CLI operational mode.
    root@% cli
    root>
  4. Enter the CLI configuration mode. Note the command prompt ends with # in the CLI configuration mode.
    root> configure
    [edit]
    root#

Configure Administration User Accounts

Set the root administration user account password. You also need to set up one or more administration user accounts. These administration user accounts are used to log in to the router through the management console. To configure administration user accounts:

  1. Add a password to the root (superuser) administration user account.
    [edit]
    root# set system root-authentication plain-text-password
    New password: password
    Retype new password: password
  2. Create a management console user account.
    [edit]
    root# set system login user user-name authentication plain-text-password
    New Password: password
    Retype new password: password
  3. Set the user account class to super-user.
    [edit]
    root# set system login user user-name class super-user

Add the Management Console to the Network

To add the management console to the network:

  1. Specify the router hostname.

    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, this hostname appears on the command line prompt when the user is logged in to the CLI:

    user-name@host-name>
    [edit]
    root# set system host-name host-name
  2. Configure the IP address of the DNS server.
    [edit]
    root# set system name-server address
  3. Configure the router domain name.
    [edit]
    root# set system domain-name domain-name
  4. Configure the IP address and prefix length for the router Ethernet interface.
    • For all routers except the TX Matrix Plus router and T1600 routers in a routing matrix:
      [edit]root@# set interfaces fxp0 unit 0 family inet address address/prefix-length
    • For TX Matrix Plus and T1600 routers in a routing matrix only:
      [edit]root@# 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.

    • For a T1600 standalone router (not connected to a TX Matrix Plus router and not in a routing matrix):
      [edit]root@# set interfaces fxp0 unit 0 family inet address address/prefix-length
  5. Configure the IP address of a backup router. The backup router is used while the local router is booting and if the routing process fails to start. Once the routing process starts, the backup router address is removed from the local routing and forwarding tables. For more information on the backup router, see the JUNOS System Basics Configuration Guide.
    [edit]
    root# set system backup-router address
  6. (Optional) Configure the static routes to remote subnets with access to the management port. Access to the management port is limited to the local subnet. To access the management port from a remote subnet, you need to add a static route to that subnet within the routing table. For more information on static routes, see the JUNOS System Basics Configuration Guide.
    [edit]
    root# set routing-options static route remote-subnet next-hop destination-IP retain no-readvertise
  7. Configure telnet service at the [edit system services] hierarchy level.
    [edit]
    root# set system services telnet

Commit Changes

Now that you have completed your changes to the configuration file, commit the configuration changes.

  1. Before committing the configuration, you can review your changes to the configuration with the show command.
    root# show
    ## Last changed: 2008-08-27 22:30:42 UTC version 9.3B1.5; system { host-name tp8; domain-name subnet.juniper.net; backup-router 192.168.71.254; root-authentication { encrypted-password "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx."; ## SECRET-DATA } name-server { 192.168.5.68; 172.17.28.101; } login { user regress { class super-user; authentication { encrypted-password "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"; ## SECRET-DATA } } } services { telnet; } syslog { user * { any emergency; } file messages { any notice; authorization info; } file interactive-commands { interactive-commands any; } } } interfaces { fxp0 { unit 0 { family inet { address 192.128.69.205/21; } } } } routing-options { static { route 172.16.0.0/12 { next-hop 192.168.71.254; retain; no-readvertise; } route 192.168.0.0/16 { next-hop 192.168.71.254; retain; no-readvertise; } } }

    On a TX Matrix Plus router, the management Ethernet interface is em0 and not fxp0. Therefore, when you issue the show command in the configuration mode, the configuration statements would be:

    [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 {em0 {unit 0 {family inet {address address ;}}}}}
  2. Commit the configuration.
    [edit]
    root# commit
    commit complete

    Note: If you receive an error message after you issue the commit statement, you can review the configuration using the show command to find the errors in your configuration. You can delete incorrect entries using the delete command. For example, to delete a hostname from the configuration, issue the following statement:

    [edit]
    root# delete system host-name host-name
  3. Exit configuration mode.
    [edit]
    root# exit
    Exiting configuration mode

    root>

Published: 2010-04-28