Last Modified: Oct 14, 2024
Affected Product(s):
BIG-IP All
Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7
Fixed In:
15.0.0, 14.1.2.8
Opened: Nov 01, 2018 Severity: 3-Major
At runtime, the HiGig MAC recovery mechanism might be triggered due to FCS errors. Normally, the FCS recovery mechanism corrects the issue. However, if the blade does not recover, the mechanism runs continuously, preventing correct blade operation.
The blade remains in the Inoperative state and cannot pass traffic.
The issue might be related to the traffic pattern the blade is processing.
Manually reboot the blade.
The blade now reboots if FCS recovery is not able to fix the link. The reboot can be disabled using the db variable: tmm.hsb.hgmfcsresetaction