- Products
- Learn
- Local User Groups
- Partners
- More
MVP 2026: Submissions
Are Now Open!
What's New in R82.10?
Watch NowOverlap in Security Validation
Help us to understand your needs better
CheckMates Go:
Maestro Madness
Hi,
I ran into the following issue, and I simply can't explain it to myself.
After cluster upgrade to R81.20 I started having ACTIVE(!) and DOWN for the cluster members; reason for the state change: Mismatch in the number of CoreXL FW instances (Event Code CLUS-113900)
Now.. the two appliances are in fact identical Dell servers; the only way for me to clear this cluster error was with cpconfig and modifying the CoreXL cores on one of the cluster members, to match the second;
Oddly enough, cpconfig on both cluster members didn't show the same number of available CPUs for CoreXL, and I was forced to drop to 2 CPUs for CoreXL on one of the members.
How and why would R81.20 lead to such behavior, given that the cluster has functioned properly and without any issues on previous Gaia version?
Any thoughts?
BR,
Daniel
different BIOS settings perhaps?
BIOS settings ? What are you speaking about ? Please supply a reference.
For how many CPUs/Cores is the license valid ? You can choose 2 / 4 / 8 / 32...
That's an aspect I didn't think about, will need to check once I get access to the environment.
One of the cluster members was running with 2 CPU cores available for CoreXL, without any possibility to edit that in cpconfig; the second one was running with 3 CPU cores and luckily it was possible for me to change that to 2 CPUs for CoreXL;; cpconfig menu for activating/modifying the CoreXL cores was available for performing modifications, compared to the first cluster member where I didn't have those options.
But why would a Gaia R81.20 upgrade change those settings, given that the R81.10 before it was in perfectly-funtioning state on both servers?
3 FW cores would be 1 SND and a total of 4 cores. I would check the licenses and their core numbers as well as the CPU hardware. Maybe there is a difference once ironed out using cpconfig that poped up as cores were distributed automatically after upgrade ?
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 12 | |
| 10 | |
| 9 | |
| 8 | |
| 6 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 1 |
Tue 16 Dec 2025 @ 05:00 PM (CET)
Under the Hood: CloudGuard Network Security for Oracle Cloud - Config and Autoscaling!Thu 18 Dec 2025 @ 10:00 AM (CET)
Cloud Architect Series - Building a Hybrid Mesh Security Strategy across cloudsTue 16 Dec 2025 @ 05:00 PM (CET)
Under the Hood: CloudGuard Network Security for Oracle Cloud - Config and Autoscaling!Thu 18 Dec 2025 @ 10:00 AM (CET)
Cloud Architect Series - Building a Hybrid Mesh Security Strategy across cloudsAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY