Connecting to a Routing Matrix with a TX Matrix Plus Router

On a routing matrix with a TX Matrix Plus router, you can perform management and service operations on the routing matrix through a Junos OS command-line interface (CLI) session with the TX Matrix Plus router.

Best Practice: We recommend that you access a routing matrix by connecting to the master Routing Engine on the TX Matrix Plus router. Under normal operating conditions, you do not need to access or configure the T1600 routers directly.

Accessing a Routing Engine by Direct Console Connection to a Serial Port

For an in-band connection to a Routing Engine in the routing matrix, you can attach one or more management console or auxiliary devices to the appropriate serial ports on a Routing Engine in a routing matrix. On a TX Matrix Plus router, the CONSOLE or AUXILIARY serial ports are located on each control board (TXP-CB). On a T1600 router in a routing matrix, the CONSOLE or AUXILIARY serial ports are located on the Connector Interface Panel (CIP). For more information, see the TX Matrix Plus Router Hardware Guide 

Accessing a Routing Engine by Telnet Access to a Management Ethernet Port

For an out-of-band management connection to a Routing Engine in a routing matrix, you can establish a Telnet session over the network connection to that Routing Engine. On a TX Matrix Plus router, the ETHERNET port is located on each TXP-CB. On a T1600 router in a routing matrix, the ETHERNET port is located on the CIP.

For a TX Matrix Plus router and for T1600 routers in a routing matrix, the CLI syntax for operational commands and configuration statements refers to the ETHERNET management port as the em0 management Ethernet interface. To use em0 as a management port, you must configure its logical port, em0.0, with a valid IP address. For more information, see the Junos OS Network Interfaces Configuration Guide.

Accessing a Routing Engine by Logging In from the CLI of Another Routing Engine

After you are logged in to one Routing Engine in a routing matrix, you can issue the request routing-engine login command to connect to another Routing Engine in the routing matrix. For example:

{master}
user@hostA-re0> request routing-engine login ?
Possible completions:
  backup               Log in to backup RE
  lcc                  Log in to specific LCC (0..3)
  master               Log in to master RE
  other-routing-engine  Log in to the other Routing Engine
  re0                  Log in to RE0
  re1                  Log in to RE1
  sfc                  Log in to SFC (0..0)

{master}
user@hostA-re0> request routing-engine login sfc 0 ?
Possible completions:
  backup               Log in to backup RE
  master               Log in to master RE
  re0                  Log in to RE0
  re1                  Log in to RE1

{master}
user@hostA-re0> request routing-engine login lcc 3 ?
Possible completions:
  backup               Log in to backup RE
  master               Log in to master RE
  re0                  Log in to RE0
  re1                  Log in to RE1

{master}
user@hostA-re0> request routing-engine login lcc 3 backup re1

--- JUNOS 1.1-11111111.1 built 1111-11-11 11:11:11 UTC
% cli
{backup}
user@hostB-re1> 

Connecting to a Backup Routing Engine on the TX Matrix Plus Router

To manage the backup Routing Engines on all routers in the routing matrix (for example, to upgrade Junos OS), we recommend that you connect to the backup Routing Engine of the TX Matrix Plus router.

Note: If you access a Routing Engine on a T1600 router, the following warning displays: user@host> request routing-engine login lcc 0 re0 --- JUNOS 9.6I built 2009-07-13 8:13:04 UTC % cli warning: This chassis is a Line Card Chassis (LCC) in a multichassis system. warning: Use of interactive commands should be limited to debugging. warning: Normal CLI access is provided by the Switch Fabric Chassis (SFC). warning: Please logout and log into the SFC to use CLI.