Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Initially Configuring the T1600 Router

 

The T1600 Core Router is shipped with Junos OS preinstalled and ready to be configured when the T1600 router is powered on. These procedures connect a router to the network but do not enable it to forward traffic. For complete information about enabling the router to forward traffic, including examples, see the Junos OS configuration guides.

You configure the router by issuing Junos OS command-line interface (CLI) commands, either on a console device attached to the CONSOLE port on the CIP, or over a telnet connection to a network connected to the ETHERNET port on the CIP.

Note

These procedures enable you to use the ETHERNET management port. For the initial configuration, use a device attached to the CONSOLE port on the CIP.

For more information about the commands in this procedure see the Junos OS Administration Library.

  1. Preparing to Configure the T1600 Router

  2. Entering Configuration Mode

  3. Configuring User Accounts and Passwords

  4. Configuring System Attributes

  5. Committing the Configuration

Preparing to Configure the T1600 Router

Gather the following information before configuring the router:

  • Name the router will use on the network

  • Domain name the router will use

  • IP address and prefix length information for the Ethernet interface

  • IP address of a default router

  • IP address of a DNS server

  • Password for the root user

Entering Configuration Mode

  1. Verify that the network device is powered on.
  2. Log in as the root user. There is no password.
  3. Start the CLI.
  4. Enter configuration mode.

Configuring User Accounts and Passwords

For information about using an encrypted password or an SSH public key string (DSA or RSA), see Configuring the Root Password and authentication (Login).

  1. Add a password to the root administration user account. Enter a cleartext password.
  2. Create a management console user account.
  3. Set the user account class to super-user.

Configuring System Attributes

For more information on configuring the backup routing and static routes, see the Junos OS Administration Library.

  1. Configure the name of the router. If the name includes spaces, enclose the name in quotation marks (“ ”).
    Note

    The DNS server does not use the hostname 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 shows on the command-line prompt when the user is logged on to the CLI:

  2. Configure the IP address of the DNS server.
  3. Configure the router’s domain name.
  4. Configure the IP address and prefix length for the router’s management Ethernet interface.Note

    The RE-C1800 Routing Engine (RE-DUO-1800) does not support the fxp0 interface or the fxp1 and fxp2 internal Ethernet interfaces. Use the em0 interface for the RE-C1800 Routing Engine, and fxp0 interface for all other Routing Engines supported for the router.

  5. Configure the IP address of a backup routing engine. The backup routing engine is used while the local router is booting and if the routing process fails to start. After the routing process starts, the backup routing engine address is removed from the local routing and forwarding tables.
  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 must add a static route to that subnet within the routing table.
  7. Configure the telnet service at the [edit system services] hierarchy level.

Committing the Configuration

For a chassis with two Routing Engines, commit the configuration changes to both Routing Engines. When you issue the commit synchronize command, the configuration is shared between both Routing Engines and committed on both Routing Engines simultaneously. For a chassis with only one Routing Engine, use the commit command instead of the commit synchronize command.

  1. Display the configuration to verify that it is correct.
  2. Commit the configuration to activate it, and synchronize the configuration. The commit synchronize command commits this new configuration on both Routing Engines simultaneously.

    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:

  3. (Optional) Configure additional properties by adding the necessary configuration statements. Then commit the changes to activate them.
  4. Exit configuration mode.