Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
Edward_Waithaka
Participant
Participant

Check Point VSX Cluster - Virtual Systems down after upgrade from R80.20 to R81.10

We recently upgraded a VSX VSLS cluster from R80.20 to R81.10 HF55 and the VSs are now reported as DOWN due to FWD pnote (FWD on Active VSX cluster member VSs are in Terminated state T).

Only one VS is in Active/Standby state while the rest are Active/Down.

Anyone faced such an issue recently?

See sample output.

Cluster name: CP-Cluster

Virtual Devices Status on each Cluster Member
=============================================

 ID    | Weight| CP-G| CP-G
       |       | W-1       | W-2
       |       | [local]   |
-------+-------+-----------+-----------
 2     | 10    | DOWN      | ACTIVE
 6     | 10    | ACTIVE(!) | DOWN
 7     | 10    | DOWN      | ACTIVE(!)
 8     | 10    | DOWN      | ACTIVE(!)
 9     | 10    | DOWN      | ACTIVE(!)
 10    | 10    | STANDBY   | ACTIVE
---------------+-----------+-----------
 Active        | 1         | 5
 Weight        | 10        | 50
 Weight (%)    | 16        | 84

Legend:  Init - Initializing, Active! - Active Attention
         Down! - ClusterXL Inactive or Virtual System is Down

0 Kudos
33 Replies
Ilya_Yusupov
Employee
Employee

@genisis__ ,

 

can you please share with me your case number and i will review and contact the TAC engineer.

 

Thanks,

Ilya 

0 Kudos
genisis__
Leader Leader
Leader

sent

0 Kudos
laurent_ragon
Participant

HI,

Do you get any solution from TAC?

we get a simulary problem during an VSX upgrade from R80.20 to R81.10. At the moment we have a cluster in mvc mode, one FW is in R80.20 and the other in R81.10 with 4 VS.

the FW in R81.10 was the Active FW, and we get a crash for one VS (spike_cpu detect high load cpu on every fwk of one VS).

for the FW in R80.20, the VS is Active mode and for the FW in R81.10, the VS is in Ready mode wherase the MVC is on!

thanks

0 Kudos
genisis__
Leader Leader
Leader

What Jumbo are you running?  We are running JHFA79 with specific private fixes ontop.

I believe the following are included in the private fix:

PRHF-25611

PRHF-25610

PRHF-25597

PRHF-25607

PRHF-25594

Now JHFA81 is recommended, you may find some of the above have been integrated.  I would suggest contacting TAC and confirming if the above bugs have been integrated, and if not for them to provide a private fix for you to go on-top of JHFA81 (or JHFA79), keep in mind you may not be facing the exact same issues.

Also I found doing a clean install of R81.10 a better option then just upgrading.

0 Kudos

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    Tue 23 Apr 2024 @ 11:00 AM (EDT)

    East US: What's New in R82

    Thu 25 Apr 2024 @ 11:00 AM (SGT)

    APAC: CPX 2024 Recap

    Tue 30 Apr 2024 @ 03:00 PM (CDT)

    EMEA: CPX 2024 Recap

    Thu 02 May 2024 @ 11:00 AM (SGT)

    APAC: What's new in R82

    Tue 23 Apr 2024 @ 11:00 AM (EDT)

    East US: What's New in R82

    Thu 25 Apr 2024 @ 11:00 AM (SGT)

    APAC: CPX 2024 Recap

    Tue 30 Apr 2024 @ 03:00 PM (CDT)

    EMEA: CPX 2024 Recap

    Thu 02 May 2024 @ 11:00 AM (SGT)

    APAC: What's new in R82
    CheckMates Events