Hi @_Val_ apologize for the confusion. So let me try again to hopefully ask my question a bit better .
Lets use Primary FW = A and Backup = B
So I lifted B to R80.20 first and then I turn off new member as per
https://dl3.checkpoint.com/paid/7b/7b22658ee3d35d95632c544190065733/CP_Cluster_ConnectivityUpgrade_B... (Page15-17)
Step 8/9/10/13 (11 and 12 excluded since only 2 member in my cluster).
Now when I come to start upgrading FW A let's say 2 scenarios
scenario A
I have to increase the volume or lets say update CPUSE or something else due to which I need to reboot it before actually upgrading to 88.20. So when this comes back up will it take the role or being Active ? As per the original persons post seems like since this is lower version it will take it ? yeah ?
Scenario B
If I only have to do one reboot and that would be for 88.20 upgrade, then as soon as it comes online , will it automatically take the role of being Active and kick out FW B from being Active? Or will it wait until in the above link we complete step 16 (page 18) when we Install the Access Control Policy ? As in the document it says in step 17 the one will be active it does not say which one will be active .
Basically I am trying here to control that FW A does not become active until I see the upgrade has properly completely and then I make FW A as active by restarting CP service on FW B.
I hope I am able to explain this well. Sorry about the confusion 🙂