show chassis cluster information
Syntax
show chassis cluster information
Description
Display chassis cluster messages. The messages indicate each node's health condition and details of the monitored failure.
Required Privilege Level
view
Output Fields
Table 1 lists the output fields for the show chassis cluster information
command. Output fields are listed in the approximate order in which they appear.
Field Name |
Field Description |
---|---|
|
Node (device) in the chassis cluster ( |
|
Displays configured data plane mode for the cluster.
|
|
|
|
|
Sample Output
show chassis cluster information detail
user@host> show chassis cluster information detail node0: -------------------------------------------------------------------------- Redundancy mode: Configured mode: active-active Operational mode: active-active Cluster configuration: Heartbeat interval: 1000 ms Heartbeat threshold: 3 Control link recovery: Disabled Fabric link down timeout: 66 sec Node health information: Local node health: Healthy Remote node health: Not healthy Redundancy group: 0, Threshold: 255, Monitoring failures: none Events: Oct 16 21:44:50.783 : hold->secondary, reason: Hold timer expired Oct 16 21:45:41.587 : secondary->primary, reason: Better priority (200/1) Redundancy group: 1, Threshold: 255, Monitoring failures: none Events: Oct 16 21:44:50.784 : hold->secondary, reason: Hold timer expired Oct 16 21:45:41.599 : secondary->primary, reason: Remote yield (0/0) Control link statistics: Control link 0: Heartbeat packets sent: 35917 Heartbeat packets received: 35372 Heartbeat packet errors: 0 Duplicate heartbeat packets received: 0 Control link 1: Heartbeat packets sent: 35917 Heartbeat packets received: 0 Heartbeat packet errors: 0 Duplicate heartbeat packets received: 0 Control recovery packet count: 3 Sequence number of last heartbeat packet sent: 35917 Sequence number of last heartbeat packet received: 32962 Fabric link statistics: Child link 0 Probes sent: 68081 Probes received: 3385 Child link 1 Probes sent: 0 Probes received: 0 Chassis cluster LED information: Current LED color: Green Last LED change reason: No failures Cold Synchronization: Status: Cold synchronization completed for: FPC 0 PIC 0, FPC 0 PIC 1 Cold synchronization failed for: N/A Cold synchronization not known for: N/A Current Monitoring Weight: 0 Progress: CS Prereq 2 of 2 SPUs completed 1. if_state sync 2 SPUs completed 2. fabric link 2 SPUs completed 3. policy data sync 2 SPUs completed 4. cp ready 2 SPUs completed 5. VPN data sync 2 SPUs completed 6. IPID data sync 2 SPUs completed 7. All SPU ready 2 SPUs completed 8. AppID ready 2 SPUs completed 9. Tunnel Sess ready 2 SPUs completed CS RTO sync 2 of 2 SPUs completed CS Postreq 2 of 2 SPUs completed Statistics: Number of cold synchronization completed: 2 Number of cold synchronization failed: 0 PFE Cold-Sync complete Cold-Sync failed ---------------------------------------------------------------- FPC 0 PIC 0 1 0 FPC 0 PIC 1 1 1 Events: Oct 16 21:53:24.430 : Cold sync for PFE FPC 0 PIC 0 is Pre-req check in process Oct 16 21:53:35.272 : Cold sync for PFE FPC 0 PIC 1 is Pre-req check in process Oct 16 21:55:46.983 : Cold sync for PFE FPC 0 PIC 0 is RTO sync in process Oct 16 21:56:06.077 : Cold sync for PFE FPC 0 PIC 0 is Completed Oct 16 22:01:27.414 : Cold sync for PFE FPC 0 PIC 1 is Not complete Oct 16 22:03:38.712 : Cold sync for PFE FPC 0 PIC 1 is RTO sync in process Oct 16 22:05:48.502 : Cold sync for PFE FPC 0 PIC 1 is Completed Loopback Information: PIC Name Loopback Nexthop Mbuf ------------------------------------------------- FPC 0 PIC 0 Success Success Success FPC 0 PIC 1 Success Success Success SPU monitoring: Status: Active Current monitoring weight: 0 PIC Name State ----------------------------- FPC 0 PIC 0 SPC3 cp-flow combo PIC Up FPC 0 PIC 1 SPC3 flow PIC Up Statistics: SPU up count: 2 NPC up count: 0 SPU down count: 0 NPC down count: 0 Chassis info processing error count: 0 Events: Oct 16 21:50:33.960 : ioc4 PIC Up in slot FPC 3 PIC 0 Oct 16 21:50:46.888 : ioc4 PIC Up in slot FPC 3 PIC 1 Oct 16 21:51:00.356 : ioc3 PIC Up in slot FPC 2 PIC 0 Oct 16 21:51:00.427 : ioc3 PIC Up in slot FPC 2 PIC 1 Oct 16 21:53:24.430 : SPC3 cp-flow combo PIC in slot FPC 0 PIC 0 Oct 16 21:53:35.272 : SPC3 flow PIC Up in slot FPC 0 PIC 1 Interface monitoring: Statistics: Monitored interface failure count: 0 Fabric monitoring: Status: Fabric Monitoring: Enabled Activation status: Suspended by local node and other node Fabric Status reported by data plane: Down JSRPD internal fabric status: Up Fabric link events: Oct 16 22:58:05.026 : Child xe-15/0/7 of fab1 is down Oct 16 22:58:05.027 : Child xe-15/0/7 of fab1 is up Oct 16 22:58:18.817 : Child xe-15/0/7 of fab1 is down Oct 16 22:58:25.266 : Fabric link fab0 is up Oct 16 22:58:25.267 : Child xe-3/0/7 of fab0 is up Oct 16 22:58:25.470 : Fabric link fab1 is up Oct 16 22:58:25.471 : Child xe-15/0/7 of fab1 is up Oct 16 22:59:12.120 : Fabric link down, link status timer Oct 17 00:35:22.682 : Child xe-3/0/7 of fab0 is up Oct 17 00:35:24.348 : Child xe-15/0/7 of fab1 is up Control link status: Up Server information: Server status : Connected Server connected to 130.32.0.1/48579 Client information: Client status : Inactive Client connected to None Hardware monitoring: Status: Activation status: Enabled Redundancy group 0 failover for hardware faults: Enabled Hardware redundancy group 0 errors: 0 Hardware redundancy group 1 errors: 0 Hardware monitoring events: Oct 17 00:35:06.509 : hw-mon errors notified RG-0 errors:0 RG-1 errors:0 Schedule monitoring: Status: Activation status: Disabled Schedule slip detected: None Timer ignored: No Statistics: Total slip detected count: 0 Longest slip duration: 0(s) Configuration Synchronization: Status: Activation status: Enabled Last sync operation: Auto-Sync Last sync result: Not needed Last sync mgd messages: Events: Oct 16 21:45:41.599 : Auto-Sync: Not needed. Cold Synchronization Progress: CS Prereq 2 of 2 SPUs completed 1. if_state sync 2 SPUs completed 2. fabric link 2 SPUs completed 3. policy data sync 2 SPUs completed 4. cp ready 2 SPUs completed 5. VPN data sync 2 SPUs completed 6. IPID data sync 2 SPUs completed 7. All SPU ready 2 SPUs completed 8. AppID ready 2 SPUs completed 9. Tunnel Sess ready 2 SPUs completed CS RTO sync 2 of 2 SPUs completed CS Postreq 2 of 2 SPUs completed ISSU events: System currently in ISSU Window and ISSU state is 80 Oct 16 21:50:21.708 : node0: Exiting ISSU window, issu_state: 32 Oct 16 21:50:21.709 : node0: Exited ISSU, issu_state: 0 Oct 16 22:08:29.645 : node0: Entered ISSU window, issu_state: 32 Oct 16 22:08:29.645 : node0: Initiating ISSU, issu_state: 48 Command history: Oct 16 21:50:21.709 : Invoked ISSU abort on node0 Oct 16 22:08:29.645 : Invoked ISSU on node0 node1: -------------------------------------------------------------------------- Redundancy mode: Configured mode: active-active Operational mode: active-active Cluster configuration: Heartbeat interval: 1000 ms Heartbeat threshold: 3 Control link recovery: Disabled Fabric link down timeout: 66 sec Node health information: Local node health: Not healthy Remote node health: Healthy Redundancy group: 0, Threshold: 255, Monitoring failures: none Events: Oct 16 22:34:12.282 : hold->secondary, reason: Hold timer expired Redundancy group: 1, Threshold: -765, Monitoring failures: spu-monitoring, cold-sync-monitoring, hardware-monitoring Events: Oct 16 22:34:12.282 : hold->secondary, reason: Hold timer expired Control link statistics: Control link 0: Heartbeat packets sent: 32962 Heartbeat packets received: 32987 Heartbeat packet errors: 0 Duplicate heartbeat packets received: 0 Control link 1: Heartbeat packets sent: 32962 Heartbeat packets received: 0 Heartbeat packet errors: 0 Duplicate heartbeat packets received: 0 Control recovery packet count: 3 Sequence number of last heartbeat packet sent: 32962 Sequence number of last heartbeat packet received: 35917 Fabric link statistics: Child link 0 Probes sent: 0 Probes received: 0 Child link 1 Probes sent: 0 Probes received: 0 Chassis cluster LED information: Current LED color: Amber Last LED change reason: Monitored objects are down 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 0 of 2 SPUs completed 1. if_state sync 0 SPUs completed 2. fabric link 0 SPUs completed 3. policy data sync 0 SPUs completed 4. cp ready 0 SPUs completed 5. VPN data sync 0 SPUs completed 6. IPID data sync 0 SPUs completed 7. All SPU ready 0 SPUs completed 8. AppID ready 0 SPUs completed 9. Tunnel Sess ready 0 SPUs completed CS RTO sync 0 of 2 SPUs completed CS Postreq 0 of 2 SPUs completed Statistics: Number of cold synchronization completed: 0 Number of cold synchronization failed: 0 SPU monitoring: Status: Active Current monitoring weight: 510 Statistics: SPU up count: 0 NPC up count: 0 SPU down count: 2 NPC down count: 0 Chassis info processing error count: 0 Events: Oct 16 22:41:06.095 : ioc4 PIC Up in slot FPC 3 PIC 0 Oct 16 22:41:18.374 : ioc4 PIC Up in slot FPC 3 PIC 1 Oct 16 22:53:50.425 : PIC empty in slot FPC 3 PIC 0 Oct 16 22:53:50.426 : PIC empty in slot FPC 3 PIC 1 Oct 16 22:54:05.600 : PIC empty in slot FPC 2 PIC 0 Oct 16 22:54:05.600 : PIC empty in slot FPC 2 PIC 1 Oct 16 22:58:04.973 : ioc4 PIC Up in slot FPC 3 PIC 0 Oct 16 22:58:17.586 : ioc4 PIC Up in slot FPC 3 PIC 1 Oct 16 23:01:18.754 : ioc3 PIC Up in slot FPC 2 PIC 0 Oct 16 23:01:21.937 : ioc3 PIC Up in slot FPC 2 PIC 1 Interface monitoring: Statistics: Monitored interface failure count: 0 Fabric monitoring: Status: Fabric Monitoring: Enabled Activation status: Suspended by local node and other node Fabric Status reported by data plane: Down JSRPD internal fabric status: Down Fabric link events: Oct 16 22:58:25.270 : Child xe-3/0/7 of fab0 is up Oct 16 22:58:25.474 : Fabric link fab1 is up Oct 16 22:58:25.474 : Fabric link fab1 is up Oct 16 22:58:25.475 : Child xe-15/0/7 of fab1 is up Oct 16 23:10:46.812 : Fabric monitoring is suspended due to HWMON failure Oct 16 23:10:46.813 : Fabric monitoring is suspended due to HWMON failure Oct 17 00:35:22.685 : Child xe-3/0/7 of fab0 is up Oct 17 00:35:24.352 : Child xe-15/0/7 of fab1 is up Oct 17 01:15:06.691 : Fabric monitoring is suspended due to HWMON failure Oct 17 01:15:06.692 : Fabric monitoring is suspended due to HWMON failure Control link status: Up Server information: Server status : Inactive Server connected to None Client information: Client status : Connected Client connected to 129.32.0.1/32245 Control link heartbeat and jitter events: Oct 16 22:32:12.278 : Missed heartbeats, between 0-2912 Oct 16 22:32:12.661 : Missed heartbeats, between 2937-2957 Hardware monitoring: Status: Activation status: Enabled Redundancy group 0 failover for hardware faults: Enabled Hardware redundancy group 0 errors: 0 Hardware redundancy group 1 errors: 1 Hardware monitoring events: Oct 16 22:53:26.686 : hw-mon errors notified RG-0 errors:0 RG-1 errors:1 Oct 16 22:53:26.852 : hw-mon errors notified RG-0 errors:0 RG-1 errors:1 Oct 16 22:53:31.774 : hw-mon errors notified RG-0 errors:0 RG-1 errors:1 Oct 16 23:10:46.812 : hw-mon errors notified RG-0 errors:0 RG-1 errors:1 Oct 16 23:10:46.813 : hw-mon errors notified RG-0 errors:0 RG-1 errors:1 Oct 17 00:35:06.690 : hw-mon errors notified RG-0 errors:0 RG-1 errors:0 Oct 17 01:15:06.691 : hw-mon errors notified RG-0 errors:0 RG-1 errors:1 Oct 17 01:15:06.692 : hw-mon errors notified RG-0 errors:0 RG-1 errors:1 Schedule monitoring: Status: Activation status: Disabled Schedule slip detected: None Timer ignored: No Statistics: Total slip detected count: 0 Longest slip duration: 0(s) Configuration Synchronization: Status: Activation status: Enabled Last sync operation: NO OP Last sync result: Not performed Last sync mgd messages: Cold Synchronization Progress: CS Prereq 0 of 2 SPUs completed 1. if_state sync 0 SPUs completed 2. fabric link 0 SPUs completed 3. policy data sync 0 SPUs completed 4. cp ready 0 SPUs completed 5. VPN data sync 0 SPUs completed 6. IPID data sync 0 SPUs completed 7. All SPU ready 0 SPUs completed 8. AppID ready 0 SPUs completed 9. Tunnel Sess ready 0 SPUs completed CS RTO sync 0 of 2 SPUs completed CS Postreq 0 of 2 SPUs completed ISSU events: System currently in ISSU Window and ISSU state is 64
Sample Output
show chassis cluster information (Monitoring Abnormal Case)
user@host> show chassis cluster information
The following output is specific to monitoring abnormal (unhealthy) case.
node0: -------------------------------------------------------------------------- Redundancy Group Information: Redundancy Group 0 , Current State: secondary, Weight: 255 Time From To Reason Apr 1 11:07:38 hold secondary Hold timer expired Apr 1 11:07:41 secondary primary Only node present Apr 1 11:29:20 primary secondary-hold Manual failover Apr 1 11:34:20 secondary-hold secondary Ready to become secondary Redundancy Group 1 , Current State: primary, Weight: 0 Time From To Reason Apr 1 11:07:38 hold secondary Hold timer expired Apr 1 11:07:41 secondary primary Only node present Redundancy Group 2 , Current State: primary, Weight: 255 Time From To Reason Apr 1 11:07:38 hold secondary Hold timer expired Apr 1 11:07:41 secondary primary Only node present Chassis cluster LED information: Current LED color: Amber Last LED change reason: Monitored objects are down Failure Information: IP Monitoring Failure Information: Redundancy Group 1, Monitoring Status: Failed IP Address Status Reason 10.1.1.1 Unreachable redundancy-group state unknown node1: -------------------------------------------------------------------------- Redundancy Group Information: Redundancy Group 0 , Current State: primary, Weight: 255 Time From To Reason Apr 1 11:08:40 hold secondary Hold timer expired Apr 1 11:29:20 secondary primary Remote is in secondary hold Redundancy Group 1 , Current State: secondary, Weight: 0 Time From To Reason Apr 1 11:08:40 hold secondary Hold timer expired Redundancy Group 2 , Current State: secondary, Weight: 255 Time From To Reason Apr 1 11:08:40 hold secondary Hold timer expired Chassis cluster LED information: Current LED color: Amber Last LED change reason: Monitored objects are down Failure Information: IP Monitoring Failure Information: Redundancy Group 1, Monitoring Status: Failed IP Address Status Reason 10.1.1.1 Unreachable redundancy-group state unknown
Sample Output
show chassis cluster information (Preempt Delay Timer)
user@host> show chassis cluster information node0: -------------------------------------------------------------------------- Redundancy Group Information: Redundancy Group 0 , Current State: secondary, Weight: 255 Time From To Reason Aug 4 12:30:02 hold secondary Hold timer expired Aug 4 12:30:05 secondary primary Only node present Aug 4 14:19:58 primary secondary-hold Manual failover Aug 4 14:24:58 secondary-hold secondary Ready to become secondary Redundancy Group 1 , Current State: secondary, Weight: 255 Time From To Reason Aug 4 14:07:57 secondary primary Remote is in secondary hold Aug 4 14:20:23 primary secondary-hold Monitor failed: IF Aug 4 14:20:24 secondary-hold secondary Ready to become secondary Aug 4 14:20:54 secondary primary Remote is in secondary hold Aug 4 14:21:30 primary secondary-hold Monitor failed: IF Aug 4 14:21:31 secondary-hold secondary Ready to become secondary Chassis cluster LED information: Current LED color: Green Last LED change reason: No failures node1: -------------------------------------------------------------------------- Redundancy Group Information: Redundancy Group 0 , Current State: primary, Weight: 255 Time From To Reason Aug 4 12:33:47 hold secondary Hold timer expired Aug 4 14:19:57 secondary primary Remote is in secondary hold Redundancy Group 1 , Current State: primary, Weight: 255 Time From To Reason Aug 4 14:07:56 secondary-hold secondary Ready to become secondary Aug 4 14:20:22 secondary primary Remote is in secondary hold Aug 4 14:20:37 primary primary-preempt-hold Preempt (99/101) Aug 4 14:20:52 primary-preempt-hold secondary-hold Primary preempt hold timer e Aug 4 14:20:53 secondary-hold secondary Ready to become secondary Aug 4 14:21:28 secondary primary Remote yield (99/0) Chassis cluster LED information: Current LED color: Green Last LED change reason: No failures
Release Information
Command introduced in Junos OS Release 12.1X47-D10.
The Redundancy mode
option is introduced in Junos OS Release
24.4R1.