Multi-Version Cluster Upgrade Procedure - Gateway Mode

Note - The procedure below is for ClusterXL and VRRP Cluster. For VSX Cluster, see Multi-Version Cluster Upgrade Procedure - VSX Mode.

Important - Before you upgrade a Cluster:

Step

Instructions

1

Back up your current configuration (see Backing Up and Restoring).

2

See Upgrade Options and Prerequisites.

3

Upgrade the Management Server and Log Servers.

4

See Planning a Cluster Upgrade.

5

Schedule a full maintenance window to make sure you can make all the custom configurations again after the upgrade.

Note - MVC supports Cluster Members with different Gaia kernel editions (R80.40 64-bit and R77.30 / R80.10 32-bit).

The procedure described below is based on an example cluster with three Cluster Members M1, M2 and M3.

However, you can use it for clusters that consist of two or more.

Action plan:

  1. In SmartConsole, change the cluster object version to R80.40.

  2. On the Cluster Member M3:

    1. Upgrade to R80.40

      Note - If you perform a Clean Install of R80.40, then you must establish SIC in SmartConsole with this Cluster Member and install Access Control Policy on it

    2. Enable the MVC

  3. In SmartConsole, install the Access Control Policy on the Cluster Member M3.

  4. On the next Cluster Member M2:

    1. Upgrade to R80.40

      Note - If you perform a Clean Install of R80.40, then you must establish SIC in SmartConsole with this Cluster Member and install Access Control Policy on it

    2. Enable the MVC

  5. In SmartConsole, install the Access Control Policy on the Cluster Member M3 and M2.

  6. On the remaining Cluster Member M1:

    • Upgrade to R80.40

      Note - If you perform a Clean Install of R80.40, then you must establish SIC in SmartConsole with this Cluster Member

  7. In SmartConsole, install the Access Control Policy and the Threat Prevention Policy on the Cluster object.

Procedure: