Last Modified: Feb 28, 2025
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4
Fixed In:
17.5.0, 17.1.2
Opened: Feb 14, 2023 Severity: 3-Major
There are cases where FCS errors occur between the switch and HSB. This can be observed in the snmp_dot3_stat stats table, following is an example: name fcs_errors ---- ---------- 10.1 19729052
Networking traffic can be impacted when this condition occurs.
This requires a BIG-IP iSeries platform that has a switch and HSB.
The device needs to be rebooted in order to clear the FCS errors.
The improvement adds the ability to trigger a High Availability (HA) action when FCS errors are detected on the switch <-> HSB interfaces on iSeries platforms. This is disabled by default but can be enabled with DB variables. There are three DB variables that control this feature: sys db bcm56xxd.hgmfcsthreshold { value "0" } bcm56xxd.hgmfcsthreshold = 0 indicates the feature is disabled. Otherwise, it is the number of FCS errors per second that need to occur before the nic_failsafe HA event is triggered. sys db bcm56xxd.hgmfcsrebootaction { value "enable" } bcm56xxd.hgmfcsrebootaction = enable triggers a nic_failsafe reboot. If this variable is set to disable, then go-offline-downlinks is triggered if the FCS threshold is exceeded. sys db bcm56xxd.hgmfcsnumpolls { value "5" } This controls the number of consecutive poll loops FCS errors have to occur before triggering the HA event. Each poll loop is one second, so the default is 5 seconds.