Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TX Matrix Plus Router Configuration Overview

 

This topic provides an overview of configuring the TX Matrix Plus router and its connected routers.

TX Matrix Plus Router and Router-Based Routing Matrix Overview

A routing matrix based on a Juniper Networks TX Matrix Plus Router is a multichassis architecture composed of one TX Matrix Plus router and one of the following line-card chassis (LCC) configurations:

  • TXP-T1600 configuration—Supports up to four interconnected Juniper Networks T1600 Core Routers.

  • TXP-T1600-3D configuration—Supports up to eight interconnected Juniper Networks T1600 Core Routers.

  • TXP-4000-3D configuration—Supports up to four interconnected Juniper Networks T4000 Core Routers.

  • TXP-Mixed-LCC-3D configuration—Supports the following combinations of T1600 and T4000 routers:

    • Six T1600 routers and one T4000 router

    • Four T1600 routers and two T4000 routers

    • Two T1600 routers and three T4000 routers

Note

The TXP-T1600-3D, TXP-T4000-3D, and TXP-Mixed-LCC-3D configurations use 3D SIBs (TXP-F13-3D and TXP-F2S-3D SIBs on the switch-fabric chassis or the SFC and TXP-LCC-3D SIB on the LCCs). For more details on the hardware components used in the routing matrix with TX Matrix Plus Router, see the TX Matrix Plus Router Hardware Guide.

From the perspective of the user interface, the routing matrix appears as a single router. The TX Matrix Plus router controls all the T1600 or T4000 routers in the routing matrix.

You configure and manage the TX Matrix Plus router and its T1600 or T4000 routers in the routing matrix through the CLI on the TX Matrix Plus router. This means that the configuration file on the TX Matrix Plus router is used for the entire routing matrix.

Because all configuration, troubleshooting, and monitoring are performed through the TX Matrix Plus router, we do not recommend accessing its T1600 or T4000 routers directly (through the console port or management Ethernet interface [em0]). If you do, the following messages appear when you first start the CLI through a T1600 or T4000 router:

These messages appear because any configuration you commit on a T1600 or a T4000 router is not propagated to the TX Matrix Plus router or other T1600 or T4000 routers in the routing matrix. For details, see Committing Configurations on the TX Matrix Plus Router.

Running Different Junos OS Releases on the TX Matrix Plus Router and T1600 or T4000 Routers

On a routing matrix composed of a TX Matrix Plus router and T1600 or T4000 routers, if you elect to run different Junos OS Releases on the TX Matrix Plus router and T1600 or T4000 Routing Engines, a change in Routing Engine primary role can cause one or all T1600 or T4000 routers to be logically disconnected from the TX Matrix Plus router.

Note

All the primary Routing Engines on the routing matrix must use the same Junos OS version. For information about hardware and software requirements, see the TX Matrix Plus Router Hardware Guide.

TX Matrix Plus Router Software Upgrades and Reinstallation

By default, when you upgrade or reinstall software on the TX Matrix Plus router, the new software image is distributed to the connected routers.

TX Matrix Plus Router Rebooting Process

When you reboot the primary Routing Engine of TX Matrix Plus router, all the primary Routing Engines in the connected routers reboot. In addition, you can selectively reboot the primary Routing Engine or any of the connected routers.

TX Matrix Plus Router Routing Engine Rebooting Sequence

The Routing Engines on the TX Matrix Plus router and T1600 or T4000 routers in the routing matrix boot from the storage media in this order: the USB device (if present), the Compact Flash card (if present), the disk (if present) in slot 1, and then the LAN.

TX Matrix Plus Router Management Ethernet Interfaces

The management Ethernet interface used for the TX Matrix Plus router and the T1600 or T4000 routers in a routing matrix is em0. This interface provides an out-of-band method for connecting to the routers in the routing matrix. The Junos OS automatically creates the router’s management Ethernet interface, em0. To use em0 as a management port, you must configure its logical port, em0.0, with a valid IP address.

Note
  • The Routing Engines in the TX Matrix Plus router and in the T1600 or T4000 routers configured in a routing matrix do not support the management Ethernet interface fxp0 or the internal Ethernet interfaces fxp1 or fxp2.

  • Automated scripts that have been developed for standalone routers (T1600 routers not configured in a routing matrix) might contain references to the fxp0, fxp1, or fxp2 interfaces. Before reusing the scripts on T1600 routers in a routing matrix, edit any command lines that reference the T1600 router management Ethernet interface fxp0 by replacing “fxp0” with “em0”.

TX Matrix Plus Router Internal Ethernet Interfaces

On a TX Matrix Plus router, the Routing Engine (RE-TXP-SFC) and Control Board (TXP-CB) function as a unit, or a host subsystem. For each host subsystem in the router, Junos OS automatically creates two internal Ethernet interfaces, ixgbe0 and ixgbe1, for the two 10-Gigabit Ethernet ports on the Routing Engine.

Routing Matrix-Based T1600 or T4000 Router Internal Ethernet Interfaces

On a T1600 or a T4000 router configured in a routing matrix, the Routing Engine (RE-TXP-LCC) and Control Board (LCC-CB) function as a unit, or a host subsystem. For each host subsystem in the router, Junos OS automatically creates two internal Ethernet interfaces, bcm0 and em1, for the two Gigabit Ethernet ports on the Routing Engine.

For more information about the management Ethernet interface and internal Ethernet interfaces on a TX Matrix Plus router and T1600 or T4000 LCCs configured in a routing matrix, see Junos OS Network Interfaces Library for Routing Devices.

Committing Configurations on the TX Matrix Plus Router

In a routing matrix composed of a TX Matrix Plus router and T1600 or T4000 routers, all configuration must be performed on the TX Matrix Plus router. Any configuration you commit on a T1600 or a T4000 router is not propagated to the TX Matrix Plus router or other T1600 or T4000 routers. Only configuration changes you commit on the TX Matrix Plus router are propagated to all routers. A commit operation on the a TX Matrix Plus router overrides any changes you commit on a T1600 or a T4000 router.

If you issue the commit command, you commit the configuration to all the primary Routing Engines in the routing matrix.

Note

If a commit operation fails on any node, then the commit operation is not completed for the entire routing matrix.

If you issue the commit synchronize command on the TX Matrix Plus router, you commit the configuration to all the primary and backup Routing Engines in the routing matrix.

Routing Matrix Configuration Groups

For routers that include two Routing Engines, you can specify two special group names—re0 and re1. These two special group names apply to the Routing Engines in slots 0 and 1 of the TX Matrix Plus router. In addition, the routing matrix supports group names for the Routing Engines for each T1600 or T4000 router: lcc n-re0 and lcc n-re1. n identifies a T1600 or T4000 router depending on the LCC configuration.

Routing Matrix System Log Messages

You configure the T1600 or T4000 routers to forward their system log messages to the TX Matrix Plus router at the [edit system syslog host sfc0-master] hierarchy level. For information about how to configure system log messages on a routing matrix based on a TX Matrix Plus router and T1600 or T4000 LCCs, see Configuring System Logging for a TX Matrix Plus Router.