Initially Configuring the T320 Router

The T320 Core Router is shipped with the Junos OS preinstalled and ready to be configured when the router is powered on. There are three copies of the software: one on a CompactFlash card (if installed) in the Routing Engine, one on the hard disk in the Routing Engine, and one on a PC card or USB device that can be inserted into the slot in the Routing Engine faceplate.

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.

1. Entering Configuration Mode

2. Configuring User Accounts and Passwords

3. Configuring System Attributes

4. Committing the Configuration

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 the backup router 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 Ethernet interface.
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

1. Display the configuration to verify that it is correct.
2. Commit the configuration to activate it on the router.
3. Optionally, configure additional properties by adding the necessary configuration statements. Then commit the changes to activate them on the router.
4. When you have finished configuring the router, exit configuration mode.