Print Download PDF Send Feedback

Previous

Next

Upgrading ClusterXL High Availability Using Connectivity Upgrade

Before you upgrade:

Make sure that the cluster has 2 members, one of which is Active and the other is Standby.

To check the cluster member status:

On each cluster member, run: cphaprob state

To upgrade the cluster:

  1. Upgrade the Standby cluster member.

    Reboot the Standby cluster member after the upgrade.

  2. In SmartConsole:
    1. Open the cluster object.
    2. In the General Properties window, change the Cluster version to the upgraded version.
    3. Click Install Policy.
    4. In the Install Policy window, go to Installation Mode > Install on each selected gateway independently section and make sure to clear the checkbox For Gateway Clusters install on all the members, if it fails do not install at all.
    5. Install the Access Policy on the cluster object.

    Note - The policy successfully installs on the upgraded cluster member and fails to install on the Active cluster member. This is expected. Ignore the warning.

  3. On the Active cluster member, run: cphaprob state

    Make sure the status is Active or Active Attention. Record the IP address of the Sync interface and the Member ID of the cluster member.

  4. On the upgraded cluster member, run: cphaprob state

    Make sure the status is Ready.

  5. On the upgraded cluster member, configure dynamic routing.

    For BGP, you must configure graceful restart, for BGP routes to remain after failover.

  6. On the upgraded cluster member, run: cphacu start [no_dr]

    If dynamic routing synchronization is not required, use the no_dr option.

    The Connectivity Upgrade runs, and shows this message when it finishes: Connectivity upgrade status: Ready for Failover

  7. On the upgraded cluster member, run: cphacu state

    Make sure that the Active cluster member handles the traffic.

  8. On the Active cluster member, run these commands:
    1. cphaprob state

      Make sure the local member is in Active or Active Attention state, and the upgraded member is in Down state.

    2. fwaccel off -a

      Turns off fwaccel on all Virtual Systems, so that the delayed connections are synchronized to the upgraded cluster member that is now in Ready state.

    3. cpstop

      The connections fail over to the upgraded cluster member.

  9. On the upgraded cluster member, run: cphaprob state

    Make sure that it is now in the Active state.

  10. On the upgraded cluster member, run: cphacu stat

    Make sure it handles the traffic.

  11. Upgrade the former Active cluster member.

    Make sure to reboot it, after the upgrade finishes.

  12. In SmartConsole, install Access Policy on this cluster object.

After the cluster upgrade is complete, the Cluster Control Protocol (CCP) run in the broadcast mode. To return it to the multicast mode, on all cluster members, run (this configuration survives reboot): cphaconf set_ccp multicast