Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation

show chassis cluster ethernet-switching status

Syntax

show chassis cluster ethernet-switching status

Release Information

Command introduced in Junos OS Release 11.1.

Description

Display the Ethernet switching status of the chassis cluster.

Required Privilege Level

view

List of Sample Output

show chassis cluster ethernet-switching status

Output Fields

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

Table 1: show chassis cluster ethernet-switching status Output Fields

Field Name

Field Description

Cluster ID

ID number (1-255) of a cluster. Setting a cluster ID to 0 is equivalent to disabling a cluster. More than 16 cluster IDs will work only if the fabric and control link interfaces are connected back-to-back.

Note: If you create a cluster with cluster IDs greater than 16, and then decide to roll back to a previous release image that does not support extended cluster IDs, the system comes up as standalone.

Note: If you have a cluster set up and running with an earlier release of Junos OS, you can upgrade to Junos OS Release 12.1X45-D10 and re-create a cluster with cluster IDs greater than 16. However, if for any reason you decide to revert to the previous version of Junos OS that did not support extended cluster IDs, the system comes up with standalone devices after you reboot.

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 mastership.

Manual failover

  • Yes: If mastership is set manually through the CLI.
  • No: Mastership is not set manually through the CLI.

Sample Output

show chassis cluster ethernet-switching status

user@host> show chassis cluster ethernet-switching status
Cluster ID: 10
Node                  Priority          Status    Preempt  Manual failover

Redundancy group: 0 , Failover count: 1
    node0                   1           primary        no       no
    node1                   0           lost           n/a      n/a

Switch fabric link statistics:
    Probe state : DOWN
    Probes sent: 8145
    Probes received: 8013
    Probe recv errors: 0
    Probe send errors: 0

Published: 2013-11-11

Supported Platforms

Published: 2013-11-11