Multi-Version Cluster Limitations

Specific limitations apply to Multi-Version Cluster.

General limitations in Multi-Version Cluster configuration

• The Multi-Version Cluster (MVC) upgrade does not support the replacement of the hardware (replacing the entire cluster member).

  The MVC upgrade supports only multi-version software.

• While the cluster contains Cluster Members that run different software versions (Multi-Version Cluster), it is not supported to change specific settings of the cluster object in SmartConsole.

  • You cannot change the cluster mode.

    For example, from High Availability to Load Sharing.

  • In the High Availability mode, you cannot change the recovery mode.

    For example, from Maintain current active Cluster Member to Switch to higher priority Cluster Member.

  • You cannot change the cluster topology.

    Do not add, remove, or edit settings of cluster interfaces (IP addresses, Network Objectives, and so on).

    In a VSX Cluster object, do not add, remove, or edit static routes.

  Note - You can change these settings either before or after you upgrade all the Cluster Members.

• While the cluster contains Cluster Members that run different software versions (Multi-Version Cluster), you must install the policy two times.

• Multi-Version Cluster (MVC) does not support Cluster Members with Dynamically Assigned IP Addresses (DAIP).

  Procedure

  Important - In a VSX Cluster, it is possible to install policy only on the upgradedVSX Cluster Members that run R80.40. After you change the version of the VSX Cluster object to R80.40, the Management Server does not let you change it to the previous version.

  1. Make the required changes in the Access Control or Threat Prevention policy.

  2. In SmartConsole, change the version of the cluster object to R80.40:

     On the General Properties page > in the Platform section > in the Version field, select R80.40 > click OK.

  3. Install policy on the upgradedCluster Members that run R80.40:

     1. In the Policy field, select the applicable policy.

     2. In the Install Mode section, select these two options:

        • Select Install on each selected gateway independently.

        • Clear For gateway clusters, if installation on a cluster member fails, do not install on that cluster.

     3. Click Install.

        The Policy installation:

        • Succeeds on the upgradedR80.40Cluster Members.

        • Fails on the oldCluster Members with a warning. Ignore this warning.

  4. In SmartConsole, change the version of the cluster object to the previous version:

     On the General Properties page > in the Platform section > in the Version field, select the previous version > click OK.

  5. Install policy on the oldCluster Members that run the previous version:

     1. In the Policy field, select the applicable policy.

     2. In the Install Mode section, select these two options:

        • Select Install on each selected gateway independently.

        • Clear For gateway clusters, if installation on a cluster member fails, do not install on that cluster.

     3. Click Install.

        The Policy installation:

        • Succeeds on the oldCluster Members.

        • Fails on the upgradedR80.40Cluster Members with a warning. Ignore this warning.