Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
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.0.0 HF3, 12.0.0 HF4
Fixed In:
13.0.0, 12.1.1 HF2, 12.1.1 HF1, 12.1.0 HF2
Opened: Jun 14, 2016 Severity: 2-Critical
After a network partition is resolved, the BIG-IP high availability subsystem may select a different device to handle traffic than the external network.
Traffic will be interrupted since the upstream network is sending traffic to a device that won't process it.
If the external network does not respond to GARP (Gratuitous ARP) messages to direct IP traffic to the correct device after an Active/Active condition is resolved, then it may continue to send traffic to a device that is now in Standby mode.
The administrator might be able to manually run a script or command to redirect traffic to the correct device that is hosting the virtual service.
When a network partition is resolved, and an Active/Active high availability pair chooses a single Active node, it now invokes a script that can be used to automatically notify the external network infrastructure of the new location for the virtual service. This new script is located in /config/failover/tgrefresh, and is invoked in addition to the transmission of GARP messages.