Juniper TX MATRIX, Hardware Manual, Page: 178 / 396

•
If the
on-loss-of-keepalives
statement is included at the
[edit chassis redundancy failure]
hierarchy level, consider the following:
• If you or a host subsystem initiates a change in mastership to the backup Routing
Engine in the TX Matrix router, the master Routing Engines in the T640 routers detect
a software release mismatch with the new master Routing Engine in the TX Matrix
router and switch mastership to their backup Routing Engines.
• If you attempt to initiate a change in mastership to a backup Routing Engine in a
T640 router, the new master Routing Engine in the T640 router detects a software
release mismatch with the master Routing Engine in the TX Matrix router and
relinquishes mastership to the original master Routing Engine. (Routing Engine
mastership in the TX Matrix router does not switch in this case.)
•
If a host subsystem initiates a change in mastership to a backup Routing Engine in
a T640 router because the master Routing Engine has failed, the T640 router is
logically disconnected from the TX Matrix router. To reconnect the T640 router,
initiate a change in mastership to the backup Routing Engine in the TX Matrix router,
or replace the failed Routing Engine in the T640 router and switch mastership to it.
(The replacement Routing Engine must be running the same software release as
the master Routing Engine in the TX Matrix router.)
• If the
on-loss-of-keepalives
statement is not included at the
[edit chassis redundancy
failure] hierarchy level, consider the following:
• If you initiate a change in mastership to the backup Routing Engine in the TX Matrix
router, all T640 routers are logically disconnected from the TX Matrix router. To
reconnect the T640 routers, switch mastership of all master Routing Engines in the
T640 routers to their backup Routing Engines.
• If you initiate a change in mastership to a backup Routing Engine in a T640 router,
the T640 router is logically disconnected from the TX Matrix router. To reconnect
the T640 router, switch mastership of the new master Routing Engine in the T640
router back to the original master Routing Engine.
If you run the same Junos OS release on all master and backup Routing Engines in the
routing matrix, a change in mastership to any backup Routing Engine in the routing matrix
does not cause a change in mastership in any other chassis in the routing matrix.
Configuration Groups
Configuration groups allow you to create a group containing configuration statements
(by including the
groups statement) and to direct the inheritance of that group's
statements in the rest of the configuration. The configuration groups offer a simple way
to establish hostnames, management interfaces, and default routes. You can also 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 TX Matrix router
supports group names for the Routing Engines in each T640 router in the following
formats:
lcc lcc-number -re0
Copyright © 2010, Juniper Networks, Inc. 146
TX Matrix Hardware Guide