Loading...
Loading...
During the ClusterXL upgrade to R82, the output of the " cphaprob state " command shows: The column " State " shows " ACTIVE(!) " for the upgraded ClusterXL Member The row " Active PNOTEs " shows " COREXL " The row " Reason for state change " shows " Mismatch in the number of CoreXL FW instances has been detected " Example output: Cluster Mode: High Availability (Active Up) with IGMP Membership ID Unique Address Assigned Load State Name 1 192.168.2.1 0% STANDBY MemberA 2 (local) 192.168.2.2 100% ACTIVE(!) MemberB Active PNOTEs: COREXL Last member state change event: Event Code: CLUS-113905 State change: STANDBY -> ACTIVE(!) Reason for state change: Mismatch in the number of CoreXL FW instances has been detected Event time: XXX
If a ClusterXL Member has 20 or more CPU cores and it runs the version R81.20 (or lower) in the User Space Firewall mode (USFW, see sk167052 ), then CoreXL automatically assigns one dedicated CPU core to the FWD daemon. Starting in R82, this design was changed - CoreXL does not assign one dedicated CPU core to the FWD daemon automatically anymore. This means: Before the upgrade to R82 (or higher), such a ClusterXL Member has: ["X" CoreXL instances, Firewall and SND] + [1 CoreXL SND instance for FWD daemon] After the upgrade to R82 (or higher), such a ClusterXL Member has: ["X+1" CoreXL instances, Firewall and SND] As a result, the ClusterXL mechanism shows the message about the mismatch in the number of CoreXL Firewall instances.
Gaia
Click on a version to see all relevant bugs
Check Point Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.