Last Modified: Aug 19, 2026
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
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.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, 12.0.0, 12.0.0 hf1, 12.0.0 hf2, 12.0.0 hf3, 12.0.0 hf4, 12.1.0, 12.1.0 hf1, 12.1.0 hf2, 12.1.1, 12.1.1 hf1, 12.1.1 hf2, 12.1.2, 12.1.2 hf1, 12.1.2 hf2, 13.0.0, 13.0.0 hf1, 13.0.0 hf2, 13.0.0 hf3
Fixed In:
13.1.0, 13.0.1, 12.1.3, 11.6.2, 11.5.6
Opened: Feb 15, 2017 Severity: 3-Major Related Article:
K42751321
Traffic-groups become active/active for 30 seconds after a long uptime interval. 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 ~1242 days. -- For 7 traffic groups, the interval is ~710 days. -- For 15 traffic groups, the interval is ~331 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.
There is no workaround. The only option is to reboot all the BIG-IP units in the device group on a regular interval. The interval is directly dependent on the number of traffic groups.
Traffic groups no longer becomes active on more than one BIG-IP system in a device group after a long uptime interval.