Troubleshooting the Logical Disconnection of a T1600 Router from the TX Matrix Plus Router

Problem

• A host subsystem initiates a change in mastership to a backup Routing Engine in a T1600 router because the master Routing Engine has failed.
• You initiate a change in mastership to a backup Routing Engine in a T1600 router and the on-loss-of-keepalives statement is not included at the [edit chassis redundancy failure] hierarchy level.

You initiate a change in mastership to the backup Routing Engine in the TX Matrix Plus router and the on-loss-of-keepalives statement is not included at the [edit chassis redundancy failure] hierarchy level—All T1600 routers are logically disconnected from the TX Matrix Plus router.

Solution

• Initiate a change in mastership to the backup Routing Engine in the TX Matrix Plus router.
• Replace the failed Routing Engine in the T1600 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 Plus router. See the T1600 Core Router Hardware Guide .

Switch mastership of all master Routing Engines in the T1600 routers to their backup Routing Engines.

Switch mastership of the new master Routing Engine in the T1600 router back to the original master Routing Engine.