Redundant Host Subsystems in a Routing Matrix with a TX Matrix Plus Router

• In a TX Matrix Plus router, the independent control planes are connected by two physical links between the two 10-Gigabit Ethernet ports on their respective Routing Engines. The primary link to the remote Routing Engine is at the ixgbe0 internal 10-Gigabit Ethernet interface. The alternate link to the remote Routing Engine is at the ixgbe1 internal 10-Gigabit Ethernet interface. If one of the two links between the host subsystems fails, both Routing Engines can use the other link for IP communication.
• In a T1600 router in a routing matrix, the independent control planes are connected by two physical links between the Gigabit Ethernet ports on their respective Routing Engines. The primary link to the remote Routing Engine is at the bcm0 internal Ethernet interface. The alternate link to the remote Routing Engine is at the em1 internal Ethernet interface. If one of the two links between the host subsystems fails, both Routing Engines can use the other link for IP communication.

Two Routing Engines provide redundancy and graceful Routing Engine switchover (GRES) capabilities.

Note: If GRES is configured, the CLI command prompt indicates Routing Engine mastership ({master} or {backup}) and physical slot number (-re0 or -re1). For example, the following CLI prompt indicates that you are logged in to the master Routing Engine in slot RE0 of the router with hostname mylcc3: {master} user@mylcc3-re0> The following CLI prompt indicates that you are logged in to the backup Routing Engine in slot RE1 of the router with hostname mylcc3: {backup} user@mylcc3-re1>