show virtual-chassis heartbeat (MX Series Virtual Chassis)

membern

Member ID of the Virtual Chassis member router for which output is displayed.

Local

IP address of the local member router that forms the heartbeat connection.

Remote

IP address of the remote member router that forms the heartbeat connection.

State

State of the heartbeat connection:

• Alive—Primary Routing Engine in the specified member router is connected and has received a heartbeat response message.

• Connected—Primary Routing Engine in the specified member router is connected and awaiting a heartbeat response message.

• Conn-Pending—Primary Routing Engine in the specified member router is connecting to the other member router.

• Detected—Primary Routing Engine in the specified member router has successfully exchanged a heartbeat connection message with the other member router when an adjacency disruption or split occurs in the Virtual Chassis. The Detected state persists until the heartbeat connection is reset, or until the Virtual Chassis forms again and a primary router (protocol primary) and backup router (protocol backup) are elected.

• Idle—Heartbeat connection is enabled but not yet connected.

• Inactive—Heartbeat connection is not active. To activate the connection, you must configure the heartbeat address and, optionally, the heartbeat timeout value.

Time

Date and time, in the format yyyy-mm-dd hh:mm:ss, of the last connection state change. If you have cleared or never collected timestamps, this field displays Never and the time interval displays 0 (zero).

Heartbeat Statistics

Detailed statistics for the heartbeat connection:

• Heartbeats sent—Number of heartbeat request messages sent.

• Heartbeats received—Number of heartbeat response messages received.

• Heartbeats lost/missed—Calculated difference between Heartbeats sent value and Heartbeats received value.

• Last time sent—Date and time, in the format yyyy-mm-dd hh:mm:ss, and time since, in the format (hh:mm:ss ago), the last heartbeat request message was sent. If you have cleared or never collected timestamps, this field displays Never and the time interval displays 0 (zero).

• Last time received—Date and time, in the format yyyy-mm-dd hh:mm:ss, and time since, in the format (hh:mm:ss ago), the last heartbeat request response message was received. If you have cleared or never collected timestamps, this field displays Never and the time interval displays 0 (zero).

• Maximum latency—Maximum number of seconds that elapse on the local member router between transmission of a heartbeat request message and receipt of a heartbeat response message.

• Minimum latency—Minimum number of seconds that elapse on the local member router between transmission of a heartbeat request message and receipt of a heartbeat response message.