You have just upgraded your Load Sharing gateway cluster (both members) from NGX R65 to
R77. cphaprob stat shows:
Cluster Mode: New High Availability (Active Up)
Member Unique Address Assigned Load State
1 (local) 172.16.185.21 100% Active
2 172.16.185.22 0% Ready
Which of the following is NOT a possible cause of this?
A.
Member 1 is at a lower version than member 2
B.
You have not run cpconfig on member 2 yet.
C.
You have a different number of cores defined for CoreXL between the two members
D.
Member 1 has CoreXL disabled and member 2 does not
C
According to sk42096
There are several possible reasons :
There are cluster members with a lower software version on this subnet / VLAN.
The number of CoreXL FireWall instances on cluster members is different.
The ID numbers of CoreXL FireWall instances and handling CPU core numbers on cluster members are different.
On Gaia OS – Linux kernels on cluster members are different (32-bit vs 64-bit).
On Gaia OS – Cluster member runs in VSX mode, while other members run in Gateway mode.
The question hsa the word NOT in it
W/c in this case it is B
All the other options ARE actual/reasonable/listed reasons hihi 🙂
The question is “which of the following is NOT a possible cause”.
Answer B, You have not run cpconfig on member 2 yet because is NOT a possible cause.
It’s B. Running cpconfig means nothing; what you do in that menu is what matters.
Assuming they mean you haven’t “Enable Cluster membership” then it wouldn’t even show up in this list to begin with.
Ready state means it’s failover capable, but there are inconsistencies between the members. You typically see this during cluster upgrades.
B. You have not run cpconfig on member 2 yet.