Bug ID 446828: SOD service still sends failover messages to peers after removing the unicast address configuration.

Last Modified: Apr 10, 2019

Bug Tracker

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

Known Affected Versions:
11.4.1, 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.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

Fixed In:
12.0.0

Opened: Jan 30, 2014
Severity: 3-Major

Symptoms

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.

Impact

The device will stay on the active/standby/standby state even after we delete the Unicast/Multicast configuration.

Conditions

If we delete this Unicast/Multicast configuration, the devices still be active/standby/standby status. But it should be in active/active/active state.

Workaround

Do "bigstart restart sod" after removal of the unicast address.

Fix Information

Unknown.

Behavior Change