SRX

 View Only

IMPORTANT MODERATION NOTICE

This community is currently under full moderation, meaning  all posts will be reviewed before appearing in the community. Please expect a brief delay—there is no need to post multiple times. If your post is rejected, you'll receive an email outlining the reason(s). We've implemented full moderation to control spam. Thank you for your patience and participation.



  • 1.  SRX-5800 manual chassis cluster switch over is not happening

    Posted 03-12-2022 05:59
    Manual chassis cluster switcover is not happening in SRX-5800 and getting error shown below.

    "Manual failover is not permitted as readiness check failed redundancy-group 1 on node1 priority is 0 Use 'force' option at the end to ignore this check"

    Please provide a solution to switch over


  • 2.  RE: SRX-5800 manual chassis cluster switch over is not happening

     
    Posted 03-12-2022 20:09
    What troubleshooting have you done? The error message is pretty clear. This is the first google hit for "redundancy-group 1 on node1 priority is 0":

    [SRX] Troubleshooting Priority 0 issue on Redundancy Groups with both nodes of a Chassis Cluster.



  • 3.  RE: SRX-5800 manual chassis cluster switch over is not happening

    Posted 03-14-2022 05:40
    Our FPC card showing multiple error.We have given  Card jack in  jack out.But error persists.

    Redundancy group: 1 , Failover count: 3
    node0 50 primary yes no None
    node1 0 secondary yes no IF CS FL


  • 4.  RE: SRX-5800 manual chassis cluster switch over is not happening

    Posted 03-12-2022 20:09
    Hi Prasanth,

    The error indicates that node1 is in unhealthy state because of some monitoring failure and hence the priority is 0. You may check output of below commands to understand the root cause.

    show chassis alarms
    show system core-dumps
    show chassis fpc pic-status
    show chassis cluster status
    show chassis cluster interfaces
    show chassis cluster information detail
    show log messages (look for any alarm/error etc when the issue reported)

    Thanks,
    Nellikka