Last Modified: Oct 06, 2020
Affected Product:
See more info
BIG-IP VE
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.10, 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.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, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.1.0, 12.1.0 HF1
Fixed In:
13.0.0, 12.1.1 HF2, 12.1.1 HF1, 12.1.0 HF2, 12.0.0 HF4, 11.6.1 HF2, 11.5.4 HF3
Opened: Jun 01, 2016
Severity: 3-Major
Some of the floating object's IPs might not be reattached to the instance acting as the new active device.
Potential traffic disruption. Some of the floating object's IPs might not be reattached to the instance acting as the new active device.
AWS deployments where there are multiple coincidences for the provided IP address (corresponding to other Amazon VPCs in the same Availability Zone containing unrelated instances but having the same IP address as the BIG-IP's floating IP address.
Do not have AWS deployments with multiple VPCs sharing the same IP address as the BIG-IP's floating IP address.
Failover now narrows network description by filtering with VPC id.