Support Center > Search Results > SecureKnowledge Details
Graceful failover with CoreXL mismatch after a CoreXL license upgrade Technical Level
Symptoms
  • cphaprob stat shows 'Active / Down' on one member and 'Ready' on the other member after attaching a new license to one of the cluster members, followed by a reboot.
  • Error: "Ready state reason: another member was detected with a lower number of CoreXL instances".
  • Running fw ctl affinity -l -v -a on both members shows a different number of CPUs listed at the bottom (e.g. "The current license only permits using CPU 0").
Cause

For clustering to correctly synchronize the connection table to the secondary member, the gateways should have the same number of cores. After attaching a new license with a different number of cores, rebooting the device will automatically adjust the number of cores used by the appliance.


Solution
Note: To view this solution you need to Sign In .