Bug ID 474149: SOD posts error message: Config digest module error: Traffic group device not found

Last Modified: Mar 17, 2021

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS(all modules)

Known Affected Versions:
11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4

Fixed In:
12.1.0

Opened: Aug 01, 2014
Severity: 3-Major
Related AskF5 Article:
K83100432

Symptoms

SOD posts error message: Config digest module error: Traffic group device not found.

Impact

This issue may cause the HA failover next-active device selection to fall back to the static (IP-based) selection algorithm. As a result, your DSC group with more than 2 devices, selects a device other than the intended device to take over services.

Conditions

In a failover device group, if a peer device (non self device) has gone through a management IP address change, SOD fails to clean up the old IP address from its internal storage, so the system subsequently and incorrectly behaves as if there is a 'configuration data inconsistent' error.

Workaround

To workaround this issue, you can perform configSync to propagate the new management IP peer, and then restart the sod process. To restart sod, at the command line run the following command: bigstart restart sod

Fix Information

In this release, if the peer device (non self device) has gone through the management IP address change, the system correctly removes the old IP address from its internal storage.

Behavior Change