Hi All,
Below is the plan I am going to follow to upgrade Clerapass cluster from 6.10.8 to 6.11.9.
I decided to start upgrade from existing Subscriber first so 6.10.8 and 6.11 will be running in parallel, which help me to validate config side by side.
Regarding step 6, which backup config should be imported into new Publisher (ex-Subscriber)? I tried both options in the lab and it seems importing backup config from ex-Subscriber to new Publisher took much less time and more smoothly.
in addition, I don't believe DB cert needs to be imported into new Publisher / Subscriber as this self-assigned cert can be generated by new versions of CPPM automatically.
Not sure if anyone has had success upgrade procedure and willing to share. Thanks
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
1) 2 CPPM appliances (One Publisher, one Subscriber) with existing version 6.10.8
2) Removes subscriber IP from VIP and drop Subscriber from Cluster
3) install 6.11.1 image onto this node (ex-subscriber) and apply 6.11.9 update afterwards
4) Check FIPS mode and set correct time zone and NTP
5) Import Access license to this node
6) Restore backup config of existing Subscriber ( or Publisher) to this node, so it will become new Publish but with ex-subscriber IP address
7) Import all backup certificates, such as HTTPS cert, Radius cert
8) Not sure if self-assigned DB cert is necessarily required to be imported as the new one generated by 6.11 also should work ?
9) Move VIP to this new Publisher and test all WiFi authentication to make sure it works as expected on the new Publisher
10) install 6.11.1 image onto ex-Publisher and apply 6.11.9 update afterward
11) Check FIPS mode and set correct time zone and NTP
12) Import Access license to this node
13) Import all backup certificates, such as HTTPS cert, Radius cert
14) No need to restore backup config to this node
15) Join this ex-Publisher to Cluster as new Subscriber