To verify the chassis cluster configuration, perform the following tasks:
Purpose
Display chassis cluster verification options.
Action
From the CLI, enter the show chassis cluster ? command:
{primary:node1}user@host> show chassis cluster ?Possible completions: interfaces Display chassis-cluster interfaces statistics Display chassis-cluster traffic statistics status Display chassis-cluster status
What it Means
The output shows a list of all chassis cluster verification parameters. Verify the following information:
Purpose
Display information about chassis cluster interfaces.
Action
From the CLI, enter the show chassis cluster interfaces command:
{primary:node1}user@host> show chassis cluster interfacesControl link 0 name: em0
Redundant-ethernet Information:
Name Status Redundancy-group
reth0 Up 1
Interface Monitoring:
Interface Weight Status Redundancy-group
ge-6/0/0 200 Up 1
{primary:node1}user@host> show chassis cluster interfacesControl link 0 name: em0
Control link 1 name: em1
Redundant-ethernet Information:
Name Status Redundancy-group
reth0 Up 1
Interface Monitoring:
Interface Weight Status Redundancy-group
ge-6/0/0 200 Up 1
What it Means
The first output shows the state of fxp1, the control link between the nodes, and provides information about the link state; it also shows the state of the fabric interface between the nodes and provides information about traffic on that link. The second output shows this information for a chassis cluster that uses dual control links (SRX5000 and SRX3000 lines only).
Purpose
Display information about chassis cluster services and interfaces.
Action
From the CLI, enter the show chassis cluster statistics command:
{primary:node1}user@host> show chassis cluster statistics
Control link statistics:
Control link 0:
Heartbeat packets sent: 798
Heartbeat packets received: 784
Fabric link statistics:
Probes sent: 793
Probes received: 0
Services Synchronized:
Service name RTOs sent RTOs received
Translation context 0 0
Incoming NAT 0 0
Resource manager 0 0
Session create 0 0
Session close 0 0
Session change 0 0
Gate create 0 0
Session ageout refresh requests 0 0
Session ageout refresh replies 0 0
IPSec VPN 0 0
Firewall user authentication 0 0
MGCP ALG 0 0
H323 ALG 0 0
SIP ALG 0 0
SCCP ALG 0 0
PPTP ALG 0 0
RTSP ALG 0 0
{primary:node1}user@host> show chassis cluster statistics
Control link statistics:
Control link 0:
Heartbeat packets sent: 258689
Heartbeat packets received: 258684
Control link 1:
Heartbeat packets sent: 258689
Heartbeat packets received: 258684
Fabric link statistics:
Probes sent: 258681
Probes received: 258681
Services Synchronized:
Service name RTOs sent RTOs received
Translation context 0 0
Incoming NAT 0 0
Resource manager 0 0
Session create 1 0
Session close 1 0
Session change 0 0
Gate create 0 0
Session ageout refresh requests 0 0
Session ageout refresh replies 0 0
IPSec VPN 0 0
Firewall user authentication 0 0
MGCP ALG 0 0
H323 ALG 0 0
SIP ALG 0 0
SCCP ALG 0 0
PPTP ALG 0 0
RPC ALG 0 0
RTSP ALG 0 0
RAS ALG 0 0
MAC address learning 0 0
GPRS GTP 0 0
{primary:node1}user@host> show chassis cluster statistics
Control link statistics:
Control link 0:
Heartbeat packets sent: 82371
Heartbeat packets received: 82321
Control link 1:
Heartbeat packets sent: 0
Heartbeat packets received: 0What it Means
The first output shows the control link statistics (heartbeats sent and received), the fabric link statistics (probes sent and received), and the number of RTOs sent and received for services. The second output shows these statistics for a chassis cluster that uses dual control links (SRX5000 and SRX3000 lines only). The output for the SRX5000 and SRX3000 lines will always show control link 0 and control link 1 statistics, even though only one control link is active or working, as shown in the third (partial) output.
Purpose
Clear displayed information about chassis cluster services and interfaces.
Action
From the CLI, enter the clear chassis cluster statistics command:
{primary:node1}user@host> clear chassis cluster statisticsCleared control-plane statistics Cleared data-plane statistics
Purpose
Display chassis cluster control-plane statistics.
Action
From the CLI, enter the show chassis cluster control-plane statistics command:
{primary:node1}user@host> show chassis cluster control-plane statistics
Control link statistics:
Control link 0:
Heartbeat packets sent: 124
Heartbeat packets received: 125
Fabric link statistics:
Probes sent: 124
Probes received: 125{primary:node1}user@host> show chassis cluster control-plane statistics
Control link statistics:
Control link 0:
Heartbeat packets sent: 258698
Heartbeat packets received: 258693
Control link 1:
Heartbeat packets sent: 258698
Heartbeat packets received: 258693
Fabric link statistics:
Probes sent: 258690
Probes received: 258690
What it Means
The first output shows the control link statistics (heartbeats sent and received) and the fabric link statistics (probes sent and received). The second output shows these statistics for a chassis cluster that uses dual control links (SRX5000 and SRX3000 lines only).
Purpose
Clear displayed chassis cluster control plane statistics.
Action
From the CLI, enter the clear chassis cluster control—plane statistics command:
{primary:node1}user@host> clear chassis cluster control—plane statisticsCleared control-plane statistics
Purpose
Display chassis cluster data plane statistics.
Action
From the CLI, enter the show chassis cluster data-plane statistics command:
{primary:node1}user@host> show chassis cluster data-plane statistics
Services Synchronized:
Service name RTOs sent RTOs received
Translation context 0 0
Incoming NAT 0 0
Resource manager 0 0
Session create 0 0
Session close 0 0
Session change 0 0
Gate create 0 0
Session ageout refresh requests 0 0
Session ageout refresh replies 0 0
IPSec VPN 0 0
Firewall user authentication 0 0
MGCP ALG 0 0
H323 ALG 0 0
SIP ALG 0 0
SCCP ALG 0 0
PPTP ALG 0 0
RTSP ALG 0 0What it Means
The output shows the number of RTOs sent and received for services.
Purpose
Clear displayed chassis cluster data plane statistics.
Action
From the CLI, enter the clear chassis cluster data-plane statistics command:
{primary:node1}user@host> clear chassis cluster data-plane statisticsCleared data-plane statistics
Purpose
Display the failover status of a chassis cluster.
Action
From the CLI, enter the show chassis cluster status command:
{primary:node1}user@host> show chassis cluster statusCluster 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
{primary:node1}user@host> show chassis cluster statusCluster 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{primary:node1}user@host> show chassis cluster statusCluster 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
What it Means
The three outputs show the failover status of the chassis cluster in addition to information about the chassis cluster redundancy groups. The second output shows node 1 as lost, meaning that node 1 lost contact with node 0 through the control link. Loss of contact is most likely to occur when both nodes are in a cluster and due to a control link failure, one node cannot exchange heartbeats, or when the other node is rebooted. The third output shows node 1 as unavailable, meaning that node 0 is not aware of node 1 in the cluster. That is, node 0 has not received a single heartbeat over the control link from node 1 since node 1 booted up. Unavailability is most likely to occur when one node boots up before the other node, or if only one node is present in the cluster.
Purpose
Clear the failover status of a chassis cluster.
Action
From the CLI, enter the clear chassis cluster failover-count command:
{primary:node1}user@host> clear chassis cluster failover-countCleared failover-count for all redundancy-groups
Purpose
Display the failover status of a chassis cluster redundancy group.
Action
From the CLI, enter the show chassis cluster status redundancy-group command:
{primary:node1}user@host> show chassis cluster status redundancy-group 2Cluster 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
What it Means
The output shows state and priority of both nodes in a cluster and indicates whether the primary has been preempted or whether there has been a manual failover.
