Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP (all modules)
Known Affected Versions:
11.2.0, 11.3.0, 11.4.0, 11.4.1, 11.5.1, 11.5.1 HF1, 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.1 HF10, 11.5.1 HF11, 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.5.10, 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
Fixed In:
12.0.0
Opened: Jan 30, 2014 Severity: 3-Major
When the SOD service ignores the removal of the unicast address configuration, it keeps sending failover messages to its peers. Therefore all devices would maintain their current failover states. But the operator expects all devices in stand alone state for lack of the peer to peer of communication.
The device will stay on the active/standby/standby state even after we delete the Unicast/Multicast configuration.
If we delete this Unicast/Multicast configuration, the devices still be active/standby/standby status. But it should be in active/active/active state.
Do "bigstart restart sod" after removal of the unicast address.
Unknown.