Bug ID 536475: As more virtual addresses are added to the BIG-IP running in AWS, the network failover time increases.

Last Modified: Apr 28, 2025

Affected Product(s):
BIG-IP MA-VE(all modules)

Known Affected Versions:
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, 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, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6

Fixed In:
13.0.0

Opened: Jul 29, 2015

Severity: 3-Major

Symptoms

As more virtual addresses are added to the BIG-IP running in AWS, the network failover time increases.

Impact

Network failover time degrades as the number of virtual addresses increases.

Conditions

Same region failover in AWS.

Workaround

None.

Fix Information

Failover time for BIG-IPs that have multiple virtual addresses on the same interface has been improved. Failover time mostly depends now on the number of the interfaces with floating objects (and only slightly depends on the number of floating objects). This significantly improves the failover duration for configurations which were previously showing the longest duration.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips