Dynamic Balancing is stuck at the initialization state

Support Center > Search Results > SecureKnowledge Details

Technical Level

Solution ID	sk179573
Technical Level
Product	VSX
Version	R80.40
Date Created	22-Jun-2022
Last Modified	26-Jul-2022

Symptoms

Dynamic Balancing is stuck at the initialization state.

The "[Expert@HostName]# dynamic_balancing -p" command shows:

"Dynamic Balancing is currently Initializing"
A reboot does not fix the issue.
The "dynamic_split -r" command does not fix the issue.

The $FWDIR/conf/dynamic_split.com file contains:

ALPHA=10
EMERGENCY_CPU_HANDLING_THRESHOLD=40
LOG_LEVEL=0
STD_DIV_MULTIPLAYER=1
DEFAULT_BOOT_STATUS=1
VERBOSE_DEBUG=0
STATE_VRIFICATION_FAILURE_DETECTED=0
MACHINE_CONFIG_OK=1
OFF_BY_DEFAULT_ON_VSX=0
INITIALIZATION=1

The dsd.elg file contains:

Up and Running
configurable param INTERVAL set to default value (3000)
configurable param MONITOR_INTERVAL set to default value (60000)
configurable param VERIFY_INTERVAL set to default value (100)
configurable param MONITOR_MODE set to default value (0)
configurable param BLADE_AWERE_MODE set to default value (0)
configurable param CLUSTER_MODE set to default value (1)
configurable param AUTOMATION_MODE set to default value (0)
value of current is_vsx doesn't match the value in ds_state file
Creating new recovery file
ds_init: This is a cluster env. The daemon will attempt to sync split decisions depending on cluster mode and state.
ds_sync_init: initialized. Cluster instance ID is 1.
ds_set_signals: Setting signals
fwk cores num different than default split on first run (current:56 default:68)
ds_delete_recovery_file: Deleting recovery file
ds_delete_recovery_file: could not delete recovery file
ds_init_mappings: could not read initial fwks to cpus maps
ds_init_mappings failed
ds_init failed

Cause

You configured manual affinity.

When Dynamic Balancing starts, the affinity must be the default affinity.

Solution

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