Performing the Initial Software Configuration for the TX Matrix Plus Router

These procedures connect a TX Matrix Plus 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 TX Matrix Plus router by issuing Junos OS command-line interface (CLI) commands, either on a console device attached to the CONSOLE port on the TXP-CB, or over a telnet connection to a network connected to the ETHERNET port on the TXP-CB.

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 TXP-CB.

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.

   Amnesiac <ttyd0>
      login: root

3. Start the CLI.
   root@% cliroot>
4. 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 .

1. 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
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

Configuring System Attributes

1. Configure the name of the router. If the name includes spaces, enclose the name in quotation marks (“ ”).
   [edit]root@# 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>

2. Configure the IP address of the DNS server.

   [edit]
   root# set system name-server address

3. Configure the TX Matrix Plus router’s domain name.
   [edit]root@# set system domain-name domain-name
4. Configure the IP address and prefix length for the TX Matrix Plus router’s management Ethernet interface.
   [edit]root@# set interfaces em0 unit 0 family inet address address/prefix-length
5. For routers with two Routing Engines, 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

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.

   [edit]
   root# set routing-options static route remote-subnet next-hop destination-IP retain no-readvertise

7. Configure the telnet service at the [edit system services] hierarchy level.

   [edit]
   set system services telnet

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

Committing the Configuration

1. Display the configuration to verify that it is correct.
   [edit]root@# showsystem {host-name host-name;domain-name domain-name;backup-router address;root-authentication {authentication-method (password | public-key);}name-server {address;}}interfaces {em0 {unit 0 {family inet {address address/prefix-length;}}}}
2. Commit the configuration to activate it.
   [edit]root@# commit
3. Optionally, configure additional properties by adding the necessary configuration statements. Then commit the changes to activate them.
   [edit]root@host# commit
4. When you have finished the configuration, exit configuration mode.
   [edit]root@host# exitroot@host>