Figure 286: Tx Matrix And Tx Matrix Plus Router Redundant Host - Juniper M Series Monitoring And Troubleshooting Manual

Hide thumbs Also See for M Series:

Table of Contents

M Series and T Series Routers Monitoring and Troubleshooting Guide

Documentation

Routing Engine, Host Module, and Host Subsystem Redundancy Connections

Figure 286: TX Matrix and TX Matrix Plus Router Redundant Host

It is important to understand how a redundant Routing Engine, redundant host module,

or redundant subsystem communicates with its active counterparts to avoid severing

the connection used for communication. Severing the connection can potentially trigger

a failover protection.

For example, the M160 router active host module (the Routing Engine and the MCS) has

the running configuration on it and communicates with the MCS, which in turn

communicates with the Flexible PIC Concentrator (FPC) and the Switching and

Forwarding Modules (SFMs). The host modules send keepalive messages to each other,

checking the operating state. Each host module issues keepalive responses, letting the

other host module know that it is up and operating. If keepalive responses are not returned

to the standby host module (response times will vary depending upon the time settings

specified in the

set chassis redundancy keepalive-time

module can become the active host module.

You also can configure failover on the router to switch mastership if a critical process

fails. If a critical process on the active host module terminates, the standby host module

routing becomes the active host module. You can configure processes for which this

TX Matrix Plus

statement), the standby host