show chassis high-availability information
Syntax
show chassis high-availability information
Description
Display details of the Multinode High Availability status on your security device including health status of the peer node.
Required Privilege Level
view
Output Fields
Table 1 lists
the output fields for the show chassis high-availability information command. Output fields are listed in the approximate order in which
they appear.
Field Name |
Field Description |
|---|---|
|
|
Node failure codes are:
|
|
|
|
Local-domain-info |
ICL Local-IP—IP address of ICL in the local domain |
|
|
|
Local node IDL BFD & CS info
(States from domain id 1 node id 1) |
Local node status details that includes:
|
Peer node ICL BFD & CS info
(States from domain id 1 node id 2) |
Peer node status details that includes:
|
Peer node IDL BFD & CS info
(States from domain id 1 node id 2) |
|
HA Hardware Upgrade
Events |
Message on additional SPC3 installation status. |
Packet Statistics |
Health and activity of connections between the nodes such as counts of failed packet transmissions or receptions, exchanged protocol messages. |
HA Peer Conn
events |
Status of the Bidirectional Forwarding Detection (BFD) connection between the nodes. |
Cold
Synchronization |
Status of cold synchronization that includes status (cold sync tasks are pending or completed), progress (lists the steps involved), statistics (counters for completed or failed cold sync attempts) , and events (logs the actual cold sync operations, including flowd sync and any RTO sync) |
SPU Monitoring |
Display the services processing unit (SPU) monitoring status and statistics. It displays activation status and counters that report how many processing components are currently detected as up/down. |
Loopback
Information |
Provides link health between nodes in a chassis cluster. |
|
|
Hardware monitoring errors. Displays activation status and control and data plane errors. |
|
|
|
|
|
|
|
|
|
Sample Output
- show chassis high-availability information
- show chassis high-availability information detail
- show chassis high-availability information (Junos OS 23.4R1)
- show chassis high-availability information (Four-Node MNHA)
- show chassis high-availability information (Four-Node MNHA)
show chassis high-availability information
user@host> show chassis high-availability information
Node failure codes:
HW Hardware monitoring LB Loopback monitoring
MB Mbuf monitoring SP SPU monitoring
CS Cold Sync monitoring SU Software Upgrade
Node Status: ONLINE
Local-id: 2
Local-IP: 10.22.0.2
HA Peer Information:
Peer Id: 1 IP address: 10.22.0.1 Interface: ge-0/0/2.0
Routing Instance: default
Encrypted: YES Conn State: DOWN
Cold Sync Status: IN PROGRESS
Services Redundancy Group: 0
Current State: ONLINE
Peer Information:
Peer Id: 1
SRG failure event codes:
BF BFD monitoring
IP IP monitoring
IF Interface monitoring
CP Control Plane monitoring
Services Redundancy Group: 1
Deployment Type: ROUTING
Status: ACTIVE
Activeness Priority: 1
Preemption: DISABLED
Process Packet In Backup State: NO
Control Plane State: READY
System Integrity Check: N/A
Failure Events: NONE
Peer Information:
Peer Id: 1
Status : BACKUP
Health Status: HEALTHY
Failover Readiness: READY
show chassis high-availability information detail
user@host> show chassis high-availability information detail
Node level Information:
Node Status: ONLINE
Local-id: 2
Local-IP: 10.22.0.2
HA Peer Information:
Peer-ID: 1 IP address: 10.22.0.1 Interface: ge-0/0/2.0
Routing Instance: default
Encrypted: YES Conn State: UP
Cold Sync Status: COMPLETE
Internal Interface: st0.16000
Internal Local-IP: 180.100.1.2
Internal Peer-IP: 180.100.1.1
Internal Routing-instance: __juniper_private1__
Packet Statistics:
Receive Error : 0 Send Error : 0
Packet-type Sent Received
SRG Status Msg 9 8
SRG Status Ack 8 7
Attribute Msg 3 2
Attribute Ack 2 2
HA Peer Conn events:
Dec 11 22:22:18.696 : HA Peer 180.100.1.1 BFD conn came up
Dec 11 22:22:25.269 : HA Peer 180.100.1.1 BFD conn went down
Dec 11 22:22:31.619 : HA Peer 180.100.1.1 BFD conn came up
Cold Synchronization:
Status:
Cold synchronization completed for: N/A
Cold synchronization failed for: N/A
Cold synchronization not known for: N/A
Current Monitoring Weight: 0
Progress:
CS Prereq 1 of 1 SPUs completed
1. if_state sync 1 SPUs completed
2. ha peer conn 1 SPUs completed
3. policy data sync 1 SPUs completed
4. cp ready 1 SPUs completed
5. VPN data sync 1 SPUs completed
6. IPID data sync 1 SPUs completed
7. All SPU ready 1 SPUs completed
8. AppID ready 1 SPUs completed
9. Tunnel Sess ready 1 SPUs completed
CS RTO sync 1 of 1 SPUs completed
CS Postreq 1 of 1 SPUs completed
Statistics:
Number of cold synchronization completed: 0
Number of cold synchronization failed: 0
Events:
Dec 11 22:22:23.870 : Cold sync for PFE is Post-req check in process
Dec 11 22:22:24.872 : Cold sync for PFE is Completed
Dec 11 22:22:37.293 : Cold sync for PFE is Post-req check in process
Dec 11 22:22:38.291 : Cold sync for PFE is Completed
SPU monitoring:
Status: Enabled
Current monitoring weight: 0
Statistics:
SPU up count: 1
NPC up count: 0
SPU down count: 0
NPC down count: 0
Chassis info processing error count: 0
Loopback Information:
PIC Name Loopback Nexthop Mbuf
-------------------------------------------------
Success Success Success
Hardware monitoring:
Status:
Activation status: Enabled
Ctrl Plane Hardware errors: 0
Data Plane Hardware errors: 0
SRGS Information:
Services Redundancy Group: 1
Deployment Type: ROUTING
Status: BACKUP
Activeness Priority: 1
Hold Timer: 1
Services: [ IPSEC ]
Process Packet In Backup State: NO
Control Plane State: READY
System Integrity Check: COMPLETE
Peer Information:
Failure Events: NONE
Peer Id: 1
Last Advertised HA Status: ACTIVE
Last Advertised Health Status: HEALTHY
Failover Readiness: N/A
Signal Route Info:
Active Signal Route:
IP: 10.39.1.1
Routing Instance: default
Status: NOT INSTALLED
Backup Signal Route:
IP: 10.39.1.2
Routing Instance: default
Status: INSTALLED
Split-brain Prevention Probe Info:
DST-IP: 10.111.0.1
SRC-IP: 10.11.0.1
Routing Instance: default
Status: NOT RUNNING
Result: N/A Reason: N/A
SRG State Change Events:
Dec 11 22:21:36.379 : SRG[1] state UNKNOWN -> HOLD, Reason: State machine start
Dec 11 22:23:28.889 : SRG[1] state HOLD -> ACTIVE, Reason: Peer state Backup adv received
Dec 11 22:23:31.152 : SRG[1] state ACTIVE -> BACKUP, Reason: HA state preemption
BFD Monitoring:
Status: UNKNOWN
SRC-IP: 10.5.0.1 DST-IP: 10.5.0.2
Routing Instance: default
Type: SINGLE-HOP
IFL Name: ge-0/0/3.0
State: INSTALLED
Interface Monitoring:
Status: UP
IF Name: ge-0/0/4 State: Up
IF Name: ge-0/0/3 State: Up
show chassis high-availability information (Junos OS 23.4R1)
user@host> show chassis high-availability information
Node failure codes:
HW Hardware monitoring LB Loopback monitoring
MB Mbuf monitoring SP SPU monitoring
CS Cold Sync monitoring SU Software Upgrade
Node Status: ONLINE
Local-id: 1
Local-IP: 10.22.0.1
Local Forwarding IP: 100.1.1.1
HA Peer Information:
Peer Id: 2 IP address: 10.22.0.2 Interface: ge-0/0/2.0
Routing Instance: default
Encrypted: YES Conn State: UP
Configured BFD Detection Time: 5 * 400ms
Cold Sync Status: COMPLETE
Peer Forwarding IP: 200.1.1.1 Interface: lo0.0
Peer ICD Conn State: UP
Services Redundancy Group: 0
Current State: ONLINE
Peer Information:
Peer Id: 2
SRG failure event codes:
BF BFD monitoring
IP IP monitoring
IF Interface monitoring
CP Control Plane monitoring
Services Redundancy Group: 1
Deployment Type: ROUTING
Status: ACTIVE
Activeness Priority: 200
Preemption: ENABLED
Process Packet In Backup State: NO
Control Plane State: READY
System Integrity Check: N/A
Failure Events: NONE
Peer Information:
Peer Id: 2
Status : BACKUP
Health Status: HEALTHY
Failover Readiness: READYshow chassis high-availability information (Four-Node MNHA)
user@host> show chassis high-availability information
root@srx# run show chassis high-availability information Node failure codes:
HW Hardware monitoring LB Loopback monitoring
MB Mbuf monitoring SP SPU monitoring
CS Cold Sync monitoring SU Software Upgrade
Node Status: ONLINE
Local-domain-id: 2
Local-id: 1
Local-domain-info:
ICL Local-IP: 22.0.0.1
HA ICL Peer Information:
Peer Id: 2 IP address: 22.0.0.2 Interface: xe-1/0/7.0
Routing Instance: default
Encrypted: YES Conn State: UP
Configured BFD Detection Time: 3 * 500ms
Cold Sync Status: COMPLETE
Peer-domain-info:
Peer-domain-id: 1
IDL Local-IP: 23.0.0.2
HA IDL Peer Information:
Peer Id: 1 IP address: 23.0.0.1 Interface: xe-1/0/6.0
Routing Instance: default
Encrypted: YES Conn State: DOWN
Configured BFD Detection Time: 3 * 500ms
Cold Sync Status: IN PROGRESS
Services Redundancy Group: 0
Current State: ONLINE
Peer Information:
Peer Id: 2
Peer Domain Id: 1
Peer Id: 1
show chassis high-availability information (Four-Node MNHA)
user@host> show chassis high-availability information details
Node level Information:
Node Status: ONLINE
Local-domain-id: 1
Local-id: 2
Local-domain-info:
ICL Local-IP: 2200::2
HA ICL Peer Information:
Peer Domain ID: 1
Peer-ID: 1 IP address: 2200::1 Interface: xe-1/1/7.0
Routing Instance: default
Encrypted: YES Conn State: UP
Cold Sync Status: IN PROGRESS
Local node IDL BFD & CS info (States from domain id 1 node id 2):
Domain id: 2
Peer id: 2
IDL Conn State: UP
Cold Sync Status: IN PROGRESS
Peer node ICL BFD & CS info (States from domain id 1 node id 1):
ICL Conn State: UP
Cold Sync Status: COMPLETE
Peer node IDL BFD & CS info (States from domain id 1 node id 1):
Domain id: 2
Peer id: 2
IDL Conn State: UP
Cold Sync Status: COMPLETE HA ICL Peer Information:
Internal Interface: st0.16017
Internal Local-IP: 180.17.18.18
Internal Peer-IP: 180.17.18.17
Internal Routing-instance: __juniper_private1__
Packet Statistics:
Receive Error : 0 Send Error : 0
Packet-type Sent Received
SRG Status Msg 0 0
SRG Status Ack 0 0
Attribute Msg 3 2
Attribute Ack 2 2
SRG Ctx Msg 5 3
SRG Ctx Ack 3 4
Pkt Req 3 2
Pkt Req Ack 2 2
HA Peer Conn events:
Nov 23 11:52:44.814 : HA Peer 180.17.18.17 BFD conn came up
Nov 23 12:09:55.601 : HA Peer 180.17.18.17 BFD conn went down
Nov 23 12:10:19.447 : HA Peer 180.17.18.17 BFD conn came up
Cold Synchronization:
Status:
Cold synchronization completed for: N/A
Cold synchronization failed for: N/A
Cold synchronization not known for: N/A
Current Monitoring Weight: 255
Progress:
CS Prereq 1 of 1 SPUs completed
1. if_state sync 1 SPUs completed
2. ha peer conn 1 SPUs completed
3. policy data sync 1 SPUs completed
4. cp ready 1 SPUs completed
5. VPN data sync 1 SPUs completed
6. IPID data sync 1 SPUs completed
7. All SPU ready 1 SPUs completed
8. AppID ready 1 SPUs completed
9. Tunnel Sess ready 1 SPUs completed
CS RTO sync 1 of 1 SPUs completed
CS Postreq 1 of 1 SPUs completed
Statistics:
Number of cold synchronization completed: 0
Number of cold synchronization failed: 0
Events:
Nov 23 11:55:49.146 : Cold sync for PFE flowd is Post-req check in process
Nov 23 11:55:50.149 : Cold sync for PFE flowd is Completed
Nov 23 11:56:30.521 : Cold sync for PFE flowd is Post-req check in process
Nov 23 11:56:31.522 : Cold sync for PFE flowd is Completed
Nov 23 11:57:56.105 : Cold sync for PFE flowd is Post-req check in process
Nov 23 11:57:57.108 : Cold sync for PFE flowd is Completed
Nov 23 11:57:58.213 : Cold sync for PFE flowd is RTO sync in process
Nov 23 11:58:37.856 : Cold sync for PFE flowd is Post-req check in process
Nov 23 11:58:38.858 : Cold sync for PFE flowd is Completed
Nov 23 12:10:30.700 : Cold sync for PFE flowd is RTO sync in process
SPU monitoring:
Status: Enabled
Current monitoring weight: 0
Statistics:
SPU up count: 1
NPC up count: 0
SPU down count: 0
NPC down count: 0
Chassis info processing error count: 0
Loopback Information:
PIC Name Loopback Nexthop Mbuf
-------------------------------------------------
flowd Success Success Success
Hardware monitoring:
Status:
Activation status: Enabled
Ctrl Plane Hardware errors: 0
Data Plane Hardware errors: 0
Services Redundancy Group: 0
Current State: ONLINE
Peer Information:
Peer Id: 1
Peer Domain Id: 2
Peer Id: 2
Peer-domain-info:
Peer-domain-id: 2
HA IDL Peer Information:
Peer Domain ID: 2
Peer-ID: 2 IP address: 2400::2 Interface: xe-1/1/1.0
Routing Instance: default
Encrypted: YES Conn State: UP
Peer node ICL BFD & CS info (States from domain id 2 node id 2):
ICL Conn State: UP
Cold Sync Status: COMPLETE
Peer node IDL BFD & CS info (States from domain id 2 node id 2):
Domain id: 1
Peer id: 2
IDL Conn State: UP
Cold Sync Status: COMPLETE
HA IDL Peer Information:
Internal Interface: st0.16034
Internal Local-IP: 180.18.34.18
Internal Peer-IP: 180.18.34.34
Internal Routing-instance: __juniper_private1__
Packet Statistics:
Receive Error : 0 Send Error : 0
Packet-type Sent Received
SRG Status Msg 0 0
SRG Status Ack 0 0
Attribute Msg 4 3
Attribute Ack 3 3
SRG Ctx Msg 8 3
SRG Ctx Ack 3 7
Pkt Req 3 3
Pkt Req Ack 3 3
HA Peer Conn events:
Nov 23 11:52:36.249 : HA Peer 180.18.34.34 BFD conn came up
Nov 23 11:52:43.812 : HA Peer 180.18.34.34 BFD conn went down
Nov 23 11:52:48.611 : HA Peer 180.18.34.34 BFD conn came up
Nov 23 12:09:55.703 : HA Peer 180.18.34.34 BFD conn went down
Nov 23 12:10:09.694 : HA Peer 180.18.34.34 BFD conn came up Cold Synchronization:
Status:
Cold synchronization completed for: N/A
Cold synchronization failed for: N/A
Cold synchronization not known for: N/A
Current Monitoring Weight: 255
Progress:
CS Prereq 1 of 1 SPUs completed
1. if_state sync 1 SPUs completed
2. ha peer conn 1 SPUs completed
3. policy data sync 1 SPUs completed
4. cp ready 1 SPUs completed
5. VPN data sync 1 SPUs completed
6. IPID data sync 1 SPUs completed
7. All SPU ready 1 SPUs completed
8. AppID ready 1 SPUs completed
9. Tunnel Sess ready 1 SPUs completed
CS RTO sync 1 of 1 SPUs completed
CS Postreq 1 of 1 SPUs completed
Statistics:
Number of cold synchronization completed: 0
Number of cold synchronization failed: 0
Events:
Nov 23 11:55:49.146 : Cold sync for PFE flowd is Post-req check in process
Nov 23 11:55:50.149 : Cold sync for PFE flowd is Completed
Nov 23 11:56:30.521 : Cold sync for PFE flowd is Post-req check in process
Nov 23 11:56:31.522 : Cold sync for PFE flowd is Completed
Nov 23 11:57:56.105 : Cold sync for PFE flowd is Post-req check in process
Nov 23 11:57:57.108 : Cold sync for PFE flowd is Completed
Nov 23 11:57:58.213 : Cold sync for PFE flowd is RTO sync in process
Nov 23 11:58:37.856 : Cold sync for PFE flowd is Post-req check in process
Nov 23 11:58:38.858 : Cold sync for PFE flowd is Completed
Nov 23 12:10:30.700 : Cold sync for PFE flowd is RTO sync in process
SPU monitoring:
Status: Enabled
Current monitoring weight: 0
Statistics:
SPU up count: 1
NPC up count: 0
SPU down count: 0
NPC down count: 0
Chassis info processing error count: 0
Loopback Information:
PIC Name Loopback Nexthop Mbuf
-------------------------------------------------
flowd Success Success Success
Hardware monitoring:
Status:
Activation status: Enabled
Ctrl Plane Hardware errors: 0
Data Plane Hardware errors: 0
Services Redundancy Group: 0
Current State: ONLINE
Peer Information:
Peer Id: 1
Peer Domain Id: 2
Peer Id: 2
Release Information
Command introduced in Junos OS Release 20.4R1.