Support Center > Search Results > SecureKnowledge Details
Upgrade VSX Cluster from R77 / R77.10 to R77.20 / R77.30, or from R77.20 to R77.30, using in-place upgrade Technical Level
Solution

Refer to the main sk97552 (VSX Reconfigure and Upgrade Matrix to R77.10 / R77.20 / R77.30).

 

When to use this procedure

  • Upgrading VSX cluster members from R77 to R77.10 / R77.20 / R77.30 (using in-place upgrade).
  • Upgrading VSX cluster members from R77.10 to R77.20 / R77.30 (using in-place upgrade).
  • Upgrading VSX cluster members from R77.20 to R77.30 (using in-place upgrade).

 

Part 1 - Upgrade of Security Management Server / Multi-Domain Security Management Server

  1. Backup the involved machines at the same time:

    • Security Management Server / Multi-Domain Security Management Server
    • All VSX cluster members

    Note: Refer to "Related Documentation" section below - "How to Backup".

  2. If required, upgrade your Security Management Server / Multi-Domain Security Management Server to the desired version before collecting the backup.

    R77.20 / R77.30 Security Gateways (in Gateway mode and in VSX mode) can be managed by the following Security Management Servers / Multi-Domain Security Management Servers:

    Note: Only features relevant to the version installed on the Security Management Servers / Multi-Domain Security Management Server will be available in SmartDashboard and in 'vsx_util' command.
    Examples:
    • You will not be able to upgrade the VSX cluster configuration from R77 to R77.20, if you manage it with R77 Security Management server.
    • You will not be able to use Mobile Access Blade on VSX R77.20, if you manage it with R76 Security Management server.
    • You will not be able to use Multi Bridge capability on R77.30, if you manage it with prior version to R77.30 Security Management server.

 

Part 2 - Upgrade of VSX Cluster

The following references are used in the procedure below:

  • Last upgraded - denotes last member to be upgraded (in HA cluster, this should be the Active member).
  • First upgraded - denotes first member to be upgraded and reconfigured.

Procedure:

  1. Upgrade the configuration of the VSX Cluster object to R77.20 / R77.30 version on the Security Management Server / Main Domain Management Server.

    Note: If you do not want new R77.20 / R77.30 features on the VSX Cluster, then skip this step (proceed to Step 2 below).

    Run the 'vsx_util upgrade' command and follow on screen instructions.
    Select your VSX Cluster and then select the R77.20 / R77.30 version.

    Important Note: On Management Server R77.20 and lower, when 'vsx_util upgrade' operation completes, user is prompted to reconfigure the VSX machines. User must refuse - select "no" - and proceed to Step 2 below.


  2. Stop Check Point services on the first upgraded VSX cluster member:

    [Expert@HostName:0]# cpstop

    Note: In VSX Load Sharing (VSLS) cluster, this will cause a fail-over.

  3. Perform in-place upgrade from R77 to R77.20 / R77.30, or from R77.10 to R77.20 / R77.30, or from R77.20 to R77.30, on the first upgraded cluster member.

    • For upgrade requirements:

      Refer to Release Notes (R77.20, R77.30) - Chapter 'Installation and Upgrade' - section 'Required Disk Space on Gaia'
    • For upgrade instructions:

      Refer to Release Notes (R77.20) - Chapter 'Installation and Upgrade' - section 'Upgrading with Legacy CLI'
      Refer to Release Notes (R77.30) - Chapter 'Installation and Upgrade' - section 'Upgrading'

    In addition, refer to sk101975: Jumbo Hotfix Accumulator for R77.20 - section "How to upgrade to R77.30".

  4. On the first upgraded VSX cluster member, verify that this cluster member is ready for fail-over:

    • All Virtual Systems must be up with the correct policy (this may take few minutes):

      [Expert@HostName:0]# vsx stat -v

    • The state of the cluster member must be 'Ready':

      [Expert@HostName:0]# cphaprob state


  5. To upgrade to R77.30, you can use the Connectivity Upgrade (CU) method at this point (optional).

    If you upgrade to R77.20, or using Optimal Service Upgrade (OSU) method, proceed to the next step.

    Note: Refer to sk107042 (ClusterXL upgrade methods and paths).

  6. Stop Check Point services on the last upgraded VSX cluster member (the one still running on old VSX version):

    [Expert@HostName:0]# cpstop

    Note: This will cause a fail-over, and the first upgraded VSX cluster member will become Active.

  7. Perform in-place upgrade from R77 to R77.20 / R77.30, or from R77.10 to R77.20 / R77.30, or from R77.20 to R77.30 on the last upgraded cluster member.

    • For upgrade requirements:

      Refer to Release Notes (R77.10, R77.20, R77.30) - Chapter 'Installation and Upgrade' - section 'Required Disk Space on Gaia'
    • For upgrade instructions:

      Refer to Release Notes (R77.10, R77.20) - Chapter 'Installation and Upgrade' - section 'Upgrading with Legacy CLI'
      Refer to Release Notes (R77.30) - Chapter 'Installation and Upgrade' - section 'Upgrading'

    In addition, refer to sk101975: Jumbo Hotfix Accumulator for R77.20 - section "How to upgrade to R77.30".

  8. Follow the instructions in sk101465 to enable Mobile Access Push Notifications on the upgraded R77.20 / R77.30 Virtual Systems.

 

Related Documentation

Show / Hide documentation

Documents:

 

Solutions:

 

How to Backup:

Give us Feedback
Please rate this document
[1=Worst,5=Best]
Comment