Technical Documentation

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 System Basics Configuration Guide

Entering Configuration Mode

Verify that the network device is powered on.
Log in as the root user. There is no password.
```
Amnesiac <ttyd0>
   login: root
```
Start the CLI.
root@% cliroot>
Enter configuration mode.
root> configure Entering configuration mode.[edit]root#

Configuring User Accounts and Passwords

For information about using an encrypted password or an SSH public key string (DSA or RSA), see the Junos OS System Basics Configuration Guide .

Add a password to the root administration user account. Enter a clear-text password.
[edit]root# set system root-authentication plain-text-passwordNew password: password Retype new password: password

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

Set the user account class to super-user.

[edit]
root@# set system login user user-name class super-user

Configuring System Attributes

For more information on configuring the backup routing and static routes, see the Junos OS System Basics Configuration Guide .

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

[edit]root@host# set system host-name host-name

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:

user-name@host-name>

Configure the IP address of the DNS server.

[edit]
root# set system name-server address

Configure the router’s domain name.
[edit]root@# set system domain-name domain-name

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.

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

[edit]root@# set interfaces em0 unit 0 family inet address address/prefix-length

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.
```
[edit]
root# set system backup-router address
```
(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.
```
[edit]
root# set routing-options static route remote-subnet next-hop destination-IP retain no-readvertise
```
Configure the telnet service at the [edit system services] hierarchy level.
```
[edit]
set system services telnet
```

Committing the Configuration

For a chassis with two Routing Engines, commit the configuration changes to both Routing Engines. When you issue the 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.

Display the configuration to verify that it is correct.

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;
        }
    }
}

Commit the configuration to activate it. 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 hostname
```
Optionally, configure additional properties by adding the necessary configuration statements. Then commit the changes to activate them.
[edit]root@host# commit synchronize

Exit configuration mode.

[edit]
roo@hostt# exit
Exiting configuration mode
   
root>

Choose Country

North America

Europe

Asia Pacific