Bug ID 1632925: Sod does not update the value for sys DB failover.crcvalues

Last Modified: Dec 10, 2024

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2

Opened: Aug 23, 2024

Severity: 3-Major

Symptoms

- The Traffic Groups GUI on a device in a device group reports the following even if the traffic group is in sync: “The traffic group configuration on this device does not match with other devices. Sync the Configuration between devices.” - Traffic group CRC values are consistent among peer devices when dumping the sod registers into /var/log/sodlog using the command /bin/cmd_sod get info. - Restarting sod does not change the DB var failover.crcvalues from 'disagree' to 'agree'.

Impact

The GUI displays the incorrect message in contrast to the actual state of the traffic group.

Conditions

The DBVAR failover.crcvalues was previously set to disagree before the sod restart.

Workaround

-- Ensure that the traffic groups are in sync and the peers agree on the CRC values. -- Manually set the db var failover.crcvalues to 'agree' on the affected device. The commands would be: tmsh modify sys db failover.crcvalues value agree tmsh save sys config

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips