Bug ID 1347825: Traffic group becomes active on more than one BIG-IP after a long uptime and long HA disconnection time

Last Modified: Jun 25, 2024

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

Known Affected Versions:
14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,,,,,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6,, 15.1.7, 15.1.8,,, 15.1.9,, 15.1.10,,,, 16.1.0, 16.1.1, 16.1.2,,, 16.1.3,,,,,, 16.1.4,,,, 17.0.0,,, 17.1.0,,,, 17.1.1,,,

Opened: Sep 01, 2023

Severity: 3-Major


Traffic-groups become active/active after a long uptime interval and the HA connection is disconnected for longer than 30 seconds. Note: Uptime required to encounter this issue is dependent on the number of traffic groups: the more traffic groups, the shorter the uptime. For example: -- For 4 traffic groups, the interval is ~621 days. -- For 7 traffic groups, the interval is ~355 days. -- For 15 traffic groups, the interval is ~165 days.


Outage due to traffic-group members being active on both systems at the same time.


-- Two or more BIG-IP systems defined in a device group for sync/failover. -- There is one or more traffic groups configured. -- The BIG-IP systems have a long uptime. -- The BIG-IP systems lose their HA connection for more than 30 seconds. -- The issue is more likely to occur when the watchdog daemon sod uptime, normally the same as system uptime, is above (6.8 years / number of traffic groups ).


There is no workaround. Either all the BIG-IP units need to be rebooted on a regular interval, or the BIG-IP units need to be rebooted before they are disconnected from each other for a long time.

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips