show chassis cluster status

ID number (1-15) of a cluster is applicable for releases upto Junos OS Release 12.1X45-D10. ID number (1-255) is applicable for Releases 12.1X45-D10 and later. Setting a cluster ID to 0 is equivalent to disabling a cluster.

You can create up to 128 redundancy groups in the chassis cluster.

Node (device) in the chassis cluster (node0 or node1).

Assigned priority for the redundancy group on that node.

State of the redundancy group (Primary, Secondary, Lost, or Unavailable).

• Primary—Redundancy group is active and passing traffic.

• Secondary—Redundancy group is passive and not passing traffic.

• Lost—Node loses contact with the other node through the control link. Most likely to occur when both nodes are in a cluster and there is a control link failure, one node cannot exchange heartbeats, or when the other node is rebooted.

• Unavailable—Node has not received a single heartbeat over the control link from the other node since the other node booted up. Most likely to occur when one node boots up before the other node, or if only one node is present in the cluster.

• Yes: Primary state can be preempted based on priority.

• No: Change in priority will not preempt the primary state.

• Yes: Primary state is set manually through the CLI with the request chassis cluster failover node or request chassis cluster failover redundancy-group command. This overrides Priority and Preempt.

• No: Primary state is not set manually through the CLI.

• None: Cluster working properly.

• Monitor Failure code: Cluster is not working properly and the respective failure code is displayed.