Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 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, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2
Fixed In:
12.1.0
Opened: Sep 14, 2015 Severity: 3-Major
When assigning/changing Load Factors on traffic groups, an increased Load factor did not always result in a traffic group 'next active' being reassigned to a more lightly-loaded device.
Changes to the Load Factor appears to be ignored for some traffic groups when assigning the next-active location.
This affects only traffic groups using the Load Aware failover method. HA Order and HA Groups are not affected. The problem only exists in Device Service Clusters with three or more devices in the failover device group.
None.
The evaluation of load factors is now performed consistently, so that changing the HA Load Factor results in reassignment of the next-active device, if appropriate.
Assignment of traffic groups to devices using the HA Load Factor failover method did not produce predictable results. Once all devices in the Device Service Cluster are upgraded to the new version, the assigned loads will be distributed more evenly.