[an error occurred while processing this directive][an error occurred while processing this directive]

Creating a New Configuration with Redundant Routing Engines

To create a new base configuration on a router with redundant Routing Engines:

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

Set Up Routing Engine Configuration Groups

In a router with two Routing Engines, one configuration should be shared between both Routing Engines. This ensures that both Routing Engine configurations are identical. Within this configuration, create two Routing Engine groups, one for each Routing Engine. Within these groups, you specify the Routing Engine–specific parameters.

For more information about creating configuration groups, see JUNOS® Software CLI User Guide.

For more information about the initial configuration for redundant Routing Engine systems and the re0 group, see JUNOS® Software High Availability Configuration Guide.

  1. 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# set groups re0
  2. Navigate to the groups re0 level of the configuration hierarchy.

    [edit]
    root# edit groups re0
  3. Specify the router hostname.
    [edit groups re0]
    root# 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>
  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. Return to the top level of the hierarchy.

    [edit groups re0]
    root# top
  6. Create the configuration group re1.

    [edit]
    root# set groups re1
  7. Navigate to the groups re1 level of the configuration hierarchy.

    [edit]
    root# edit groups re1
  8. Specify the router hostname.
    [edit groups re1]
    root# set system host-name host-name
  9. 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
  10. Return to the top level of the hierarchy.

    [edit groups re0]
    root# top
  11. Specify the group application order.

    [edit]root# set apply-groups [ re0 re1 ]

Complete the Management Console Configuration

To configure the global management console parameters.

  1. Configure the IP address of the DNS server.
    [edit]
    root# set system name-server address
  2. Configure the router domain name.
    [edit]
    root# set system domain-name domain-name
  3. 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 about the backup router, see the JUNOS System Basics Configuration Guide.
    [edit]
    root# set system backup-router address
  4. (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 about 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
  5. Configure telnet service at the [edit system services] hierarchy level.
    [edit]
    root# set system services telnet

Commit and Synchronize Changes

Commit the configuration changes. When you issue the synchronize command, the configuration is shared between both Routing Engines and committed on both Routing Engines simultaneously.

  1. Before committing the configuration, you can review the configuration entries using the show command.
    root# show
    ## Last changed: 2008-10-17 18:32:25 UTC version 9.1R1.8; groups { re0 { system { host-name spice-re0; } interfaces { fxp0 { unit 0 { family inet { address 192.168.69.155/21; } } } } } re1 { system { host-name spice-re1; } interfaces { fxp0 { unit 0 { family inet { address 192.168.70.72/21; } } } } } global; } apply-groups [ re0 re1 ]; system { domain-name englab.juniper.net; backup-router 192.168.71.254; root-authentication { encrypted-password "xxxxxxxxxxx"; ## SECRET-DATA } name-server { 192.168.1.1; } login { user regress { uid 2001; class super-user; authentication { encrypted-password "xxxxxxxxxxx"; ## SECRET-DATA } } } services { telnet; } syslog { user * { any emergency; } file messages { any notice; authorization info; } file interactive-commands { interactive-commands any; } } } routing-options { static { /* corporate office */ route 172.16.0.0/12 { next-hop 192.168.71.254; retain; no-readvertise; } } }
  2. Commit and synchronize the configuration. The commit synchronize command commits this new configuration on both Routing Engines simultaneously.
    [edit]
    root# commit synchronize
    re0:
    configuration check succeeds
    re1:
    commit complete
    re0:
    commit complete

    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 command:

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

    root>

Published: 2010-04-28

[an error occurred while processing this directive]