Supported Platforms
TX Matrix Router and T640 Router Configuration Overview
This topic provides an overview of configuring the TX Matrix router and T640 routers.
- TX Matrix Router and T640 Router-Based Routing Matrix Overview
- Running Different Junos OS Releases on the TX Matrix Router and T640 Routers
- TX Matrix Router Software Upgrades and Reinstallation
- TX Matrix Router Rebooting Process
- Committing Configurations on the TX Matrix Router
- TX Matrix and T640 Router Configuration Groups
- Routing Matrix System Log Messages
TX Matrix Router and T640 Router-Based Routing Matrix Overview
A routing matrix is a multichassis architecture that consists of a TX Matrix router and from one to four T640 routers. From the perspective of the user interface, the routing matrix appears as a single router. The TX Matrix router controls all the T640 routers in the routing matrix, as shown in Figure 1.
Figure 1: Routing Matrix Composed of a TX Matrix Router and Four T640 Routers
You configure and manage the TX Matrix router and its T640 routers in the routing matrix through the CLI on the TX Matrix router. This means that the configuration file on the TX Matrix router is used for the entire routing matrix.
Because all configuration, troubleshooting, and monitoring are performed through the TX Matrix router, we do not recommend accessing its T640 routers directly (through the console port or management Ethernet [fxp0]). If you do, the following messages appear when you first start the CLI through a T640 router:
These messages appear because any configuration you commit on a T640 router is not propagated to the TX Matrix router or other T640 routers in the routing matrix. For details, see Committing Configurations on the TX Matrix Router.
Running Different Junos OS Releases on the TX Matrix Router and T640 Routers
On a routing matrix, if you elect to run different Junos OS Releases on the TX Matrix router and T640 Routing Engines, a change in Routing Engine mastership can cause one or all T640 routers to be logically disconnected from the TX Matrix router.
 | Note: The routing matrix supports Release 7.0 and later versions of the Junos OS. All the master Routing Engines on the routing matrix must use the same software version. For information about hardware and software requirements, see the TX Matrix Router Hardware Guide. |
TX Matrix Router Software Upgrades and Reinstallation
By default, when you upgrade or reinstall software on the TX Matrix router, the new software image is distributed to the connected T640 routers. Software installed on a primary TX Matrix router is distributed to all connected primary T640 routers and the backup is distributed to all connected backup routers.
TX Matrix Router Rebooting Process
When you reboot the TX Matrix router master Routing Engine, all the master Routing Engines in the connected T640 routers reboot. In addition, you can selectively reboot the master Routing Engine or any of the connected T640 routers.
Committing Configurations on the TX Matrix Router
In a routing matrix composed of a TX Matrix router and T640 routers, all configuration must be performed on the TX Matrix router. Any configuration you commit on a T640 router is not propagated to the TX Matrix router or other T640 routers. Only configuration changes you commit on the TX Matrix router are propagated to all T640 routers. A commit on a TX Matrix router overrides any changes you commit on a T640 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 router. |
If you issue the commit synchronize command on the TX Matrix router, you commit the configuration to all the master and backup Routing Engines in the routing matrix.
TX Matrix and T640 Router 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 router. In addition, the routing matrix supports group names for the Routing Engines for each T640 router: lcc n-re0 and lcc n-re1. n identifies a T640 router from 0 through 3.
Routing Matrix System Log Messages
You configure the T640 routers to forward their system log messages to the TX Matrix router at the [edit system syslog host scc-master] hierarchy level. For information about how to configure system log messages in a routing matrix, see Junos OS System Log Configuration Overview and Configuring System Logging for a TX Matrix Router.
