show chassis cluster status

Syntax

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

Release Information

Command modified in Release 9.2 of Junos OS. Output changed to support dual control ports in Release 10.0 of Junos OS.

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 Topics

redundancy-group

clear chassis cluster failover-count

request chassis cluster failover node

request chassis cluster failover reset

List of Sample Output

show chassis cluster status
show chassis cluster status redundancy-group 2
show chassis cluster status
show chassis cluster status

Output Fields

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

Table 15: show chassis cluster status Output Fields

Field Name

Field Description

Cluster ID

ID number (1-15) of a cluster.

Redundancy-Group

ID number (1-255) 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.

Sample Output

show chassis cluster status

user@host> show chassis cluster status 
Cluster ID: 3 
   Node name               Priority    Status    Preempt  Manual failover
	Redundancy-group: 0, Failover count: 1
    node0                   254         primary   no       no
    node1                   2           secondary no       no
	Redundancy-group: 1, Failover count: 1    
    node0                   254         primary   no       no
    node1                   1           secondary no       no

Sample Output

show chassis cluster status redundancy-group 2

user@host> show chassis cluster status redundancy-group 2 
Cluster ID: 14 
   Node name          Priority    Status    Preempt  Manual failover
	Redundancy-Group: 2, Failover count: 1
    node0              50          secondary no       no  
    node1              100         primary   no       no

Sample Output

show chassis cluster status

user@host> show chassis cluster status 
Cluster ID: 15
Node                  Priority          Status    Preempt  Manual failover
Redundancy group: 0 , Failover count: 5
    node0                   200         primary        no       no
    node1                   0           lost           n/a      n/a
Redundancy group: 1 , Failover count: 41
    node0                   101         primary        no       no
    node1                   0           lost           n/a      n/a

Sample Output

show chassis cluster status

user@host> show chassis cluster status 
Cluster ID: 15
Node                  Priority          Status    Preempt  Manual failover
Redundancy group: 0 , Failover count: 5
    node0                   200         primary        no       no
    node1                   0           unavailable    n/a      n/a
Redundancy group: 1 , Failover count: 41
    node0                   101         primary        no       no
    node1                   0           unavailable    n/a      n/a
Copyright© 1999-2010 Juniper Networks, Inc. All rights reserved.