[Contents] [Prev] [Next] [Index] [Report an Error]

Routing Matrix CLI Specifics

The CLI has specific components for managing a routing matrix. The following sections provide key examples to assist you in understanding how managing the routing matrix can differ from managing a standalone T640 routing node:

Routing Matrix Overview

A routing matrix is a multichassis architecture composed of one TX Matrix platform, to which you can connect from one to four T640 routing nodes, as shown in Figure 2. Each component has two Routing Engines.


Figure 2: Routing Matrix


A TX Matrix platform is also referred to as a switch-card chassis (SCC). The CLI uses scc to refer to the TX Matrix platform. A T640 routing node in a routing matrix is also referred to as a line-card chassis (LCC). The CLI uses lcc to refer to a specific T640 routing node. LCCs are assigned numbers, 0 through 3, depending on the hardware setup and how they are connected to the TX Matrix platform. For more information, see the TX Matrix Platform Hardware Guide.

CLI Options for Selecting Routing Matrix Components

From the CLI, you can view the routing matrix as a single router with many Flexible PIC Concentrators (FPCs) and Physical Interface Cards (PICs). For example, you can view a list of all hardware components in the routing matrix, view alarms for the entire routing matrix, view interfaces on all T640 routing nodes, and so on.

When you issue operational mode commands on the TX Matrix platform, CLI command options allow you to apply the command to a component of the routing matrix rather than to the routing matrix as a whole:

The following example displays information for the TX Matrix and all of its T640 routing nodes:

user@host> show version

scc-re0:

--------------------------------------------------------------------------

Hostname: scc

Model: TX Matrix

JUNOS Base OS boot [7.0-20040630.0]

JUNOS Base OS Software Suite [7.0-20040629.0]

JUNOS Kernel Software Suite [7.0-20040630.0]

JUNOS Packet Forwarding Engine Support (T-Series) [7.0-20040630.0]

JUNOS Routing Software Suite [7.0-20040630.0]

JUNOS Online Documentation [7.0-20040630.0]

JUNOS Crypto Software Suite [7.0-20040630.0]



lcc0-re0:

--------------------------------------------------------------------------

Hostname: lcc0

Model: t640

JUNOS Base OS boot [7.0-20040630.0]

JUNOS Base OS Software Suite [7.0-20040629.0]

JUNOS Kernel Software Suite [7.0-20040630.0]

JUNOS Packet Forwarding Engine Support (T-Series) [7.0-20040630.0]

JUNOS Routing Software Suite [7.0-20040630.0]

JUNOS Online Documentation [7.0-20040630.0]

JUNOS Crypto Software Suite [7.0-20040630.0]

JUNOS Support Tools Package [7.0-20040630.0]



lcc1-re0:

--------------------------------------------------------------------------

Hostname: lcc1

Model: t640

JUNOS Base OS boot [7.0-20040630.0]

JUNOS Base OS Software Suite [7.0-20040629.0]

JUNOS Kernel Software Suite [7.0-20040630.0]

JUNOS Packet Forwarding Engine Support (T-Series) [7.0-20040630.0]

JUNOS Routing Software Suite [7.0-20040630.0]

JUNOS Online Documentation [7.0-20040630.0]

JUNOS Crypto Software Suite [7.0-20040630.0]

JUNOS Support Tools Package [7.0-20040630.0]

The following example displays information for all routing nodes:

user@host> show version all-lcc

lcc0-re0:

--------------------------------------------------------------------------

Hostname: lcc0

Model: t640

JUNOS Base OS boot [7.0-20040630.0]

JUNOS Base OS Software Suite [7.0-20040629.0]

JUNOS Kernel Software Suite [7.0-20040630.0]

JUNOS Packet Forwarding Engine Support (T-Series) [7.0-20040630.0]

JUNOS Routing Software Suite [7.0-20040630.0]

JUNOS Online Documentation [7.0-20040630.0]

JUNOS Crypto Software Suite [7.0-20040630.0]

JUNOS Support Tools Package [7.0-20040630.0]



lcc1-re0:

--------------------------------------------------------------------------

Hostname: lcc1

Model: t640

JUNOS Base OS boot [7.0-20040630.0]

JUNOS Base OS Software Suite [7.0-20040629.0]

JUNOS Kernel Software Suite [7.0-20040630.0]

JUNOS Packet Forwarding Engine Support (T-Series) [7.0-20040630.0]

JUNOS Routing Software Suite [7.0-20040630.0]

JUNOS Online Documentation [7.0-20040630.0]

JUNOS Crypto Software Suite [7.0-20040630.0]

JUNOS Support Tools Package [7.0-20040630.0]

The following example displays information for a specific routing node:

user@host> show version lcc 0

lcc0-re0:

--------------------------------------------------------------------------

Hostname: lcc0

Model: t640

JUNOS Base OS boot [7.0-20040630.0]

JUNOS Base OS Software Suite [7.0-20040629.0]

JUNOS Kernel Software Suite [7.0-20040630.0]

JUNOS Packet Forwarding Engine Support (T-Series) [7.0-20040630.0]

JUNOS Routing Software Suite [7.0-20040630.0]

JUNOS Online Documentation [7.0-20040630.0]

JUNOS Crypto Software Suite [7.0-20040630.0]

JUNOS Support Tools Package [7.0-20040630.0]

The following example displays information for the TX Matrix platform only:

user@host> show version scc

Hostname: scc

Model: TX Matrix

JUNOS Base OS boot [7.0-20040630.0]

JUNOS Base OS Software Suite [7.0-20040629.0]

JUNOS Kernel Software Suite [7.0-20040630.0]

JUNOS Packet Forwarding Engine Support (T-Series) [7.0-20040630.0]

JUNOS Routing Software Suite [7.0-20040630.0]

JUNOS Online Documentation [7.0-20040630.0]

JUNOS Crypto Software Suite [7.0-20040630.0]

Using FPC Numbers in Routing Matrix CLI Commands

A standalone T640 routing node can be configured with up to eight FPCs (numbered 0 through 7). Because a routing matrix can have up to four T640 routing nodes, and each T640 routing node has up to eight FPCs, the routing matrix can have up to 32 FPCs (0 through 31).

Table 9 shows the correspondence between the FPC hardware slot numbers in the T640 routing nodes and the FPC assignments recognized by the JUNOS software for a routing matrix.


Table 9: FPC Correspondence Between T640 Routing Nodes and the Routing Matrix
T640 Routing Node
T640 FPC Range
Routing Matrix FPC Range

LCC 0

0-7

0-7

LCC 1

0-7

8-15

LCC 2

0-7

16-23

LCC 3

0-7

24-31

You can specify the FPC slot number in operational mode chassis commands in two ways:

This is the recommended method. The show command output also lists information in this way, sorted first by LCC number and then by FPC slot 0 through 7.

For example, the following commands have the same result, but the first is the recommended usage:

user@host> request chassis fpc lcc 1 slot 1 offline
user@host> request chassis fpc slot 9 offline

General Operational Tasks

Operational mode commands that you issue on the TX Matrix master Routing Engine are distributed to all master Routing Engines on the T640 routing nodes in the routing matrix. Commands that you issue on the TX Matrix backup Routing Engine are distributed to all backup Routing Engines on the T640 routing nodes in the routing matrix.

More information is provided in the following sections:

Upgrading Software on a Routing Matrix

By default, when you upgrade software on the TX Matrix platform, the new image is pushed down to the master Routing Engines of the connected T640 routing nodes.

Once installation on the TX Matrix platform is complete, a reboot issued on the TX Matrix platform causes the new software to be activated on the master Routing Engines of the TX Matrix platform and all connected T640 routing nodes.

Managing Backup Routing Engines

To manage the backup Routing Engines on all components (for example, to upgrade JUNOS software on backup routing engines), you must log in to the TX Matrix backup Routing Engine.

Halting and Rebooting Routing Matrix Components

A reboot issued on the TX Matrix platform reboots the T640 routing node master Routing Engines. You can halt the TX Matrix platform or a specific T640 routing node within a routing matrix. However, halting both Routing Engines on a TX Matrix platform halts both Routing Engines on all the connected T640 routing nodes.

Bringing Routing Nodes Offline or Online

You can bring offline or online a specific T640 routing node within a routing matrix:

user@host> request chassis lcc ?

Possible completions:

  offline              Take LCC offline

  online               Bring LCC online

  slot                 LCC Slot (0..3)

Managing Files on Routing Engines

You can manage files on all Routing Engines. For example, you can copy a file from the TX Matrix master Routing Engine to a T640 routing node Routing Engine.

user@host> file list



/var/home/user/:

.ssh/

fred.txt



user@host> file copy fred.txt lcc0:fred.txt



user@host> file list lcc0:

lcc0-master:

--------------------------------------------------------------------------



/var/home/user/:

.ssh/

fred.txt

Displaying Logs on Any Routing Engine

You can display logs on any Routing Engines from the TX Matrix platform:

user@host> show log lcc0:messages

lcc0-master:

--------------------------------------------------------------------------

Aug 19 17:17:23  lcc0 mgd[7099]: UI_LOAD_EVENT: User 'user' is performing a 
'rollback'

Aug 19 17:17:24  lcc0 mgd[7099]: UI_LOAD_EVENT: User 'user' is performing a 
'load update'

Aug 19 17:17:25  lcc0 mgd[7099]: UI_COMMIT: User 'user' performed commit: no 
comment

Checking the Status of T640 Routing Nodes

Check the status of the T640 routing nodes with the following command:

user@host> show chassis lccs

Slot  State              Uptime

0     Online             39 minutes, 16 seconds

1     Online             39 minutes, 16 seconds

2     Empty

3     Empty


[Contents] [Prev] [Next] [Index] [Report an Error]