Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
11.5.4, 11.5.4 HF1, 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, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4
Fixed In:
12.1.0, 11.6.1, 11.5.4 HF2
Opened: Nov 03, 2015 Severity: 3-Major
When a device is in a failover group, sod logs the state change messages indicating the reachability of other devices in the group. For example: Nov 2 11:34:54 BIGIP-1 notice sod[5716]: 010c007f:5: Receiving status updates from peer device /Common/BIGIP-3.localdomain (10.145.192.5) (Online). Nov 2 11:31:19 BIGIP-1 notice sod[5716]: 010c007f:5: Receiving status updates from peer device /Common/BIGIP-3.localdomain (10.145.192.5) (Offline). Nov 2 11:31:43 BIGIP-1 notice sod[5716]: 010c007e:5: Not receiving status updates from peer device /Common/BIGIP-3.localdomain (10.145.192.5) (Disconnected). If a reachable device is removed from the failover group, no "Disconnected" message is issued, so the last reported status will be inaccurate. When a device is part of a trust, sod logs messages indicating what unicast addresses it is monitoring on remote devices: Nov 2 11:34:29 BIGIP-1 info sod[5716]: 010c007a:6: Added unicast failover address 10.145.192.5 port 1026 for device /Common/BIGIP-3.localdomain. If devices are removed from the trust, sod does not log a message that those unicast addresses are no longer in use.
Inaccurate state reporting.
When a device is removed from a failover device group, or removed from a device trust.
None
When a device is removed from a failover device group, it is now reported as "Disconnected". When a device is removed from the device trust, sod on the other devices correctly reports that the unicast addresses belonging to the other devices have been deleted.