Bug ID 584545: Failure to stabilize internal HiGig link will not trigger failover event

Last Modified: May 29, 2024

Affected Product(s):
BIG-IP LTM(all modules)

Known Affected Versions:
12.1.1, 12.1.2, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
13.1.0, 12.1.3

Opened: Mar 31, 2016

Severity: 3-Major


The internal HiGig interface potentially and repeatedly report FCS errors or does not become stable in rare cases.


Device is left in a state where it cannot receive or pass traffic or have frame checksum errors.


The internal HiGig interfaces experiences FCS or XLMAC link failures.



Fix Information

HA failover mechanism is now activated when internal HSB ports on critical data path are consistently unstable.

Behavior Change

There is a condition in which failures happen on the internal HiGig interfaces on the critical packet path between the HSB and the Broadcom switch, causing traffic interruption. Such failures can be inferred by HSB XLMAC instability or by observing increasing FCS errors. When these HSB XLMAC failures happened in the past, TMOS initiated a recovery mechanism by resetting the HSB MAC interface. However, if the failure persisted even after repeated recovery attempts, TMOS triggered a high availability (HA) failover event to prevent prolonged traffic disruption. The failover triggering condition is set as either the consecutive recovery attempts or consecutive FCS failure events that reach a configurable preset limit. After the HA failover was triggered, the original active unit will still keep trying to recover, and will mark itself ready if the failure condition is no longer observed. The XLMAC reset was existing behavior. The new behavior also applies to FCS failure events.

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips