Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation

Solutions

Featured solutions AI Campus and branch Data center WAN Security Service provider Cloud operator Industries
Campus and Branch

Welcome to the NOW Way to Wi-Fi

Take your networking performance to new heights with a modern, cloud-native, AI-Native architecture. Only Juniper can help you unleash the full potential of Wi-Fi 7 with our AI-Native platform for innovation.
Prepare for liftoff
Business intelligence analyst dashboard on virtual screen. Big data Graphs Charts.

AI Data Center Networking

Juniper’s AI data center solution is a quick way to deploy high performing AI training and inference networks that are the most flexible to design and easiest to manage with limited IT resources.
Find out more
Enterprise AI-Native Networking

Enterprise AI‑Native Routing

Juniper's Ai-Native routing solution delivers robust 400GbE and 800GbE capabilities for unmatched performance, reliability, and sustainability at scale.
Explore enterprise routing
Zero trust security

Ops4AI Lab

Visit our lab in Sunnyvale, CA and see our AI data center solution for yourself. You can try out your own model’s functionality and performance, too.
Visit the lab
Enterprise AI-Native Networking

Enterprise AI‑Native Routing

Juniper's Ai-Native routing solution delivers robust 400GbE and 800GbE capabilities for unmatched performance, reliability, and sustainability at scale.
Explore enterprise routing
Higher Education

Shaping Student Experiences: The NOW Way to Build Higher Education Networks

Join Juniper Networks CIO Sharon Mandell and a virtual summit of C-level IT leaders from prestigious institutions as they discuss ongoing efforts to support digital transformation.
Register to attend
Hand on tablet with healthcare overlay of graphics

Security in healthcare

In this IDC Spotlight report, discover how AI networking can automate and strengthen a healthcare ecosystem to defeat criminals and prevent loss. 
Gain insights into ecosystem security
Retail

The Future of In-Store Technologies

Join us for an enlightening webinar with Kevin McCartan, Senior IT Service Delivery Engineer at Musgrave; retail guru Jack Stratten of Insider Trends; and Christian Gilby, Director of Product Marketing at Juniper Networks, as they discuss the future of in-store technologies.
Reserve my spot

Products

Wireless access Wired access SD-WAN / SASE Routing and switching Security Mist AI™ Management software Network operating system Blueprint for AI-Native Acceleration Optics
  • Operations
ACX7020 router

Juniper ACX7020 Cloud Metro Access Router

Legacy networks simply cannot meet the demands of today’s rapidly evolving metro landscape. Unlock a new generation of highly scalable architectures and automated operations with the Juniper ACX7020. 
Learn more
EX4000 Ethernet Switch

Next-gen AI-Native EX4000 line of switches

Lack of AI innovation from your current networking vendor slowing you down? Embrace Juniper’s cloud-native, AI-Native access switches that support every level and layer, across nearly every deployment.
Discover how
The Q and AI text with an image of Bob Friday and Kedar Dhuru.

The Q&AI Podcast

Delivering practical solutions and enriching discussions, this podcast series is a vital resource for those seeking an in-depth exploration of AI's transformative potential.
Catch the latest episode

Services

Services
Services AI Care

Juniper AI Care Services Revolutionize Your Service Experience

Our industry-first AI-Native services couple AIOps with our deep expertise across the full network life cycle. You can move from reactive response to proactive insight and action.
Explore AI Care Services
Services AI Data Center

Juniper AI Data Center Deployment Services Optimize Your AI Model Runs

We use our expertise and validated designs to help design, deploy, validate and tune networks, including GPUs and storage, to get the most from your AI infrastructure operation.
Learn about AI Data Center Deployment Services

Partners

Partners

Support and Documentation

Support and Documentation

Learn

About Juniper Training Events The Feed Resources Technology learning topics Thought leadership and insights
Audience raising hands up while businessman is speaking in training at the office.

Juniper certification and training news

See the latest
Ringing of the bell

All global events

See the latest
AI-native-now

AI-Native NOW event series

Register now
Juniper's Christina Hendrix at the head of a conference table. With the text "The NOW Way to Network" overlayed, with "NOW" emphasizing the "O" in green color.

The NOW Way to Network

Watch the video series
AI Native Now

Executive insights

Dive deep with leading experts and thought leaders on all the topics that matter most to your business, from AI to network security to driving rapid, relevant transformation for your business.
Learn more
A keynote speaker giving a presentation at a conference. There are dozens of people sitting around them. The presentation is displayed via projector on all the walls in the room.

Leadership voices

Juniper Networks’ leaders operate on the front lines of creating the network of the future. Take a look around to see what’s on their minds.
Watch now
Bob Friday and Jessica Garrison speaking

Bob Friday Talks

Join Bob as he ventures into all the knowns -- and -- unknowns -- of AI.
Catch the latest episode
Documentation
Menu
License Guide
Quick Starts
Validated Designs
Explore Pathfinder Apps
CLI Explorer
Feature Explorer
Hardware Compatibility Tool
Port Checker
Browse All
Collapse

Pathfinder Apps

All

By Software

By Hardware

Learn More
Pathfinder HomeCLI ExplorerCompliance AdvisorFeature ExplorerHardware Compatibility ToolJunos XML API ExplorerJunos YANG Data Model ExplorerPort CheckerPower CalculatorSNMP MIB ExplorerSystem Log Explorer
CLI ExplorerFeature ExplorerJunos XML API ExplorerJunos YANG Data Model ExplorerSNMP MIB ExplorerSystem Log Explorer
Compliance AdvisorFeature ExplorerHardware Compatibility ToolPort CheckerPower Calculator
Home Documentation Junos OS Junos CLI Reference CLI Reference S

Junos CLI Reference

keyboard_arrow_up
close
keyboard_arrow_left
Junos CLI Reference
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
ON THIS PAGE
keyboard_arrow_right

show chassis cluster information

date_range 17-Oct-24
arrow_backward
arrow_forward

Syntax

content_copy zoom_out_map
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.

Table 1: show chassis cluster information Output Fields

Field Name

Field Description

Node

Node (device) in the chassis cluster (node0 or node1).

Redundancy mode

Displays configured data plane mode for the cluster.

  • active-active—Primary and secondary nodes in active mode.

  • active-backup—Primary in active, secondary in backup mode.

Redundancy Group Information

  • Redundancy Group—ID number (0 - 255) of a redundancy group in the cluster.

  • Current State—State of the redundancy group: primary, secondary, hold, or secondary-hold.

  • Weight—Relative importance of the redundancy group.

  • Time—Time when the redundancy group changed the state.

  • From—State of the redundancy group before the change.

  • To—State of the redundancy group after the change.

  • Reason—Reason for the change of state of the redundancy group.

Chassis cluster LED information

  • Current LED color—Current color state of the LED.

  • Last LED change reason—Reason for change of state of the LED.

Sample Output

show chassis cluster information detail

content_copy zoom_out_map
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)

content_copy zoom_out_map
user@host> show chassis cluster information

The following output is specific to monitoring abnormal (unhealthy) case.

content_copy zoom_out_map
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)

content_copy zoom_out_map
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.

Related Documentation

arrow_backward PREVIOUS show chassis cluster ethernet-switching status
NEXT arrow_forward show chassis cluster information configuration-synchronization
footer-navigation

© 1999 - 2025 Juniper Networks, Inc. All rights reserved.

Scroll to top