Bug ID 930825: System should reboot (rather than restart services) when it sees a large number of HSB XLMAC errors

Last Modified: Feb 19, 2021

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS(all modules)

Known Affected Versions:
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.4,, 12.1.5,,, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 16.0.0,, 16.0.1

Opened: Jul 24, 2020
Severity: 3-Major


The following symptoms may be seen when the HSB is experiencing a large number of XLMAC errors and is unable to recover from the errors. After attempting XLMAC recovery fails, the current behavior is to failover to the peer unit and go-offline and down links. This can be seen the TMM logs: -- notice The number of the HSB XLMAC recovery operation 11 or fcs failover count 0 reached threshold 11 on bus: 3. -- notice HA failover action is triggered due to XLMAC/FCS errors on HSB1 on bus 3. -- notice HSBE2 1 disable XLMAC TX/RX at runtime. -- notice HA failover action is cleared. Followed by a failover event.


The BIG-IP system fails over.


It is unknown under what conditions the XLMAC errors occur.


Modify the default high availability (HA) action for the switchboard-failsafe to reboot instead of go offline and down links.

Fix Information


Behavior Change