Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary
Navigation

show chassis cluster status

Syntax

show chassis cluster status <redundancy-group group-number >

Release Information

Command modified in Junos OS Release 9.2. Support for dual control ports added in Junos OS Release 10.0. Support for monitoring failures added in Junos OS Release 12.1X47-D10.

Description

Display the failover status of a chassis cluster.

Options

  • none—Display the status of all redundancy groups in the chassis cluster.
  • redundancy-group group-number —(Optional) Display the status of the specified redundancy group.

Required Privilege Level

view

 

Related Documentation

 

List of Sample Output

show chassis cluster status
show chassis cluster status redundancy-group 1

Output Fields

Table 1 lists the output fields for the show chassis cluster status command. Output fields are listed in the approximate order in which they appear.

Table 1: show chassis cluster status Output Fields

Field Name

Field Description

Cluster ID

ID number (1-15) of a cluster is applicable for releases upto 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.

Redundancy-Group

ID number (1-128) of a redundancy group in the chassis cluster.

Node name

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

Priority

Assigned priority for the redundancy group on that node.

Status

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 due to 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.

Preempt

  • Yes: Mastership can be preempted based on priority.
  • No: Change in priority will not preempt the mastership.

Manual failover

  • Yes: If the Mastership 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: Mastership is not set manually through the CLI.

Monitor-failures

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

Sample Output

Displays chassis cluster status with all redundancy groups.

show chassis cluster status

user@host> show chassis cluster status 
Monitor Failure codes:
		CS  Cold Sync monitoring        FL  Fabric Connection monitoring
    GR  GRES monitoring             HW  Hardware monitoring
    IF  Interface monitoring        IP  IP monitoring
    LB  Loopback monitoring         MB  Mbuf monitoring
    NH  Nexthop monitoring          NP  NPC monitoring
    SP  SPU monitoring              SM  Schedule monitoring
    CF  Config Sync monitoring

Cluster ID: 1
Node   Priority Status         Preempt Manual   Monitor-failures

Redundancy group: 0 , Failover count: 1
node0  200      primary        no      no       None
node1  1        secondary      no      no       None

Redundancy group: 1 , Failover count: 1
node0  101      primary        no      no       None
node1  1        secondary      no      no       None

Sample Output

Displays chassis cluster status with redundancy group 1 only.

show chassis cluster status redundancy-group 1

user@host> show chassis cluster status redundancy-group 1 
Monitor Failure codes:
    CS  Cold Sync monitoring        FL  Fabric Connection monitoring
    GR  GRES monitoring             HW  Hardware monitoring
    IF  Interface monitoring        IP  IP monitoring
    LB  Loopback monitoring         MB  Mbuf monitoring
    NH  Nexthop monitoring          NP  NPC monitoring
    SP  SPU monitoring              SM  Schedule monitoring
    CF  Config Sync monitoring

Cluster ID: 1
Node   Priority Status         Preempt Manual   Monitor-failures

Redundancy group: 1 , Failover count: 1
node0  101      primary        no      no       None
node1  1        secondary      no      no       None

Published: 2015-02-27

Previous Page Next Page