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:
Reboot the Standby cluster member after the upgrade.
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.
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.
cphaprob state
Make sure the status is Ready.
For BGP, you must configure graceful restart, for BGP routes to remain after failover.
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
cphacu state
Make sure that the Active cluster member handles the traffic.
cphaprob state
Make sure the local member is in Active or Active Attention state, and the upgraded member is in Down state.
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.
cpstop
The connections fail over to the upgraded cluster member.
cphaprob state
Make sure that it is now in the Active state.
cphacu stat
Make sure it handles the traffic.
Make sure to reboot it, after the upgrade finishes.
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