sk182004 - "Dynamic Balancing is currently Initializing" status does not change on Security Gateway

"Dynamic Balancing is currently Initializing" status does not change on Security Gateway

Product: CoreXL

Version: R80.40 (EOS), R81 (EOS), R81.10 (EOS), R81.20

Last Modified: 2024-11-26

Symptoms

After an upgrade, when the Security Gateway is running in the User Space Firewall mode (USFW), the output of the "dynamic_balancing -p" command shows "Dynamic Balancing is currently Initializing".
The output of the "fw ctl multik stat" command shows that all CoreXL instances are affined to all CPU cores.

Example:

[Expert@GW:0]# fw ctl multik stat
ID  | Active  | CPU    | Connections | Peak
  -----------------------------------------------
0   | Yes     | all    |           0 |       33
1   | Yes     | all    |           0 |        2
2   | Yes     | all    |           0 |        2
3   | Yes     | all    |           0 |        2
4   | Yes     | all    |           0 |        2
... ... ...

The output of the "cpprod_util fwisusermode" command shows "1". Meaning, the Security Gateway is running in the User Space Firewall mode (USFW).
The output of the "cpprod_util fwisusfw" command shows "0". Meaning, the Security Gateway is not running in the User Space Firewall mode (USFW), but in the Kernel Space Firewall mode (KSFW).

Cause

Incorrect value of the fwisusfw parameter. The value is set to 0, while it must be set to 1.

Solution

This problem was fixed. The fix is included in:

Check Point R82
Jumbo Hotfix Accumulator for R81.20 starting from Take 89
Jumbo Hotfix Accumulator for R81.10 starting from Take 170
Jumbo Hotfix Accumulator for R81 starting from Take 106

If you choose not to upgrade, Check Point can supply a Hotfix. Contact Check Point Support to get a Hotfix for this issue.

A Support Engineer will make sure the Hotfix is compatible with your environment before providing the Hotfix.

For faster resolution and verification, please collect CPinfo files from the Security Management Server and Security Gateways involved in the case.

Hotfix installation instructions:

Refer to sk168597 - How to install a Hotfix.

NOTE

This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.

Article Properties

Access Level: General

Status: Approved by TAC

Date Created: 2024-02-07

Last Modified: 2024-11-26