Supported Platforms
TX Matrix Plus Router and T1600 Router Configuration Overview
This topic provides an overview of configuring the TX Matrix Plus router and T1600 routers.
- TX Matrix Plus Router and T1600 Router-Based Routing Matrix Overview
- Running Different Junos OS Releases on the TX Matrix Plus Router and T1600 Routers
- TX Matrix Plus Router Software Upgrades and Reinstallation
- TX Matrix Plus Router Rebooting Process
- TX Matrix Plus Router Routing Engine Rebooting Sequence
- TX Matrix Plus Router Management Ethernet Interfaces
- TX Matrix Plus Router Internal Ethernet Interfaces
- Routing Matrix-Based T1600 Router Internal Ethernet Interfaces
- Committing Configurations on the TX Matrix Plus Router
- Routing Matrix Configuration Groups
- Routing Matrix System Log Messages
TX Matrix Plus Router and T1600 Router-Based Routing Matrix Overview
A routing matrix based on a TX Matrix Plus router is a multichassis architecture that consists of a TX Matrix Plus router and from one to four T1600 routers. From the perspective of the user interface, the routing matrix appears as a single router. The TX Matrix Plus router (or switch-fabric chassis (SFC)) controls all the T1600 routers (or line-card chassis (LCC)) in the routing matrix, as shown in Figure 1.
Figure 1: Routing Matrix Composed of a TX Matrix Plus Router and Four T1600 Routers
You configure and manage the TX Matrix Plus router and its T1600 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 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 router:
These messages appear because any configuration you commit on a T1600 router is not propagated to the TX Matrix Plus router or other T1600 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 Routers
On a routing matrix composed of a TX Matrix Plus router and T1600 routers, if you elect to run different Junos OS Releases on the TX Matrix Plus router and T1600 Routing Engines, a change in Routing Engine mastership can cause one or all T1600 routers to be logically disconnected from the TX Matrix Plus router.
 | Note: All the master 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 T1600 routers. Software installed on a primary TX Matrix Plus router is distributed to all connected primary T1600 routers and the backup is distributed to all connected backup routers.
TX Matrix Plus Router Rebooting Process
When you reboot the TX Matrix Plus router master Routing Engine, all the master Routing Engines in the connected T1600 routers reboot. In addition, you can selectively reboot the master Routing Engine or any of the connected T1600 routers.
TX Matrix Plus Router Routing Engine Rebooting Sequence
The Routing Engines on the TX Matrix Plus router (or switch-fabric chassis) and T1600 routers (or line-card chassis) in the routing matrix boot from the storage media in this order: the USB device (if present), the CompactFlash 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 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.
|
|
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 host subsystem. For each host subsystem in the router, the 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 Router Internal Ethernet Interfaces
On a T1600 router configured in a routing matrix, the Routing Engine (RE-TXP-LCC) and Control Board (LCC-CB) function as a unit, or host subsystem. For each host subsystem in the router, the 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 routers configured in a routing matrix, see the Junos® OS Network Interfaces.
Committing Configurations on the TX Matrix Plus Router
In a routing matrix composed of a TX Matrix Plus router and T1600 routers, all configuration must be performed on the TX Matrix Plus router. Any configuration you commit on a T1600 router is not propagated to the TX Matrix Plus router or other T1600 routers. Only configuration changes you commit on the TX Matrix Plus router are propagated to all T1600 routers. A commit on a TX Matrix Plus router overrides any changes you commit on a T1600 router.
If you issue the commit command, you commit the configuration to all the master 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 TX Matrix Plus router. |
If you issue the commit synchronize command on the TX Matrix Plus router, you commit the configuration to all the master 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 router: lcc n-re0 and lcc n-re1. n identifies a T1600 router from 0 through 3.
Routing Matrix System Log Messages
You configure the T1600 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 the TX Matrix Plus router or the T1600 routers, see Configuring System Logging for a TX Matrix Plus Router.
