Bug ID 475728: BCM56xxd might restart due to parity errors

Last Modified: Jun 13, 2019

Bug Tracker

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

Known Affected Versions:
11.0.0, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4

Fixed In:
12.0.0

Opened: Aug 15, 2014
Severity: 2-Critical
Related AskF5 Article:
K17306

Symptoms

The TMOS daemon bcm56xxd may restart due to parity errors.

Impact

bcm56xxd re-initializes the internal switch, which might briefly affect data traffic. The system might report memory parity errors in different tables within bcm56xxd by posting log messages similar to the following: info bcm56xxd[8127]: 012c0016:6: unit 0 L2_ENTRY_ONLY entry 120673 parity error. -- info bcm56xxd[8127]: 012c0012:6: Exiting on parity errors. -- notice mcpd[7108]: 01070406:5: Removed publication with publisher id BCM56xxPublisher. -- info bcm56xxd: 012c0013:6: BCM56xxd starting. debug=0, foreground=1, packet=1, bcm_debug=0x7, soc_debug=0x0 The following types of messages may be logged if a parity error is detected by the broadcom chip in an area that is not used by user data. These type of errors will not trigger a driver restart, and are not user impacting, however they can generate a large number of log entries. F5 recommend rebooting the device to clear this state 012c0016:6: unit 0 FP_TCAM entry 1127 TCAM parity error 012c0016:6: unit 0 SER parity failure without valid count soc_xgs3_mem_dma: EGR_SERVICE_COUNTER_TABLE_X.epipe0 failed(NAK)

Conditions

Under rare conditions, the bcm56xxd process may restart due to parity errors. This issue only affects the following hardware platforms: BIG-IP 6900 (D104) BIG-IP 8900 (D106) BIG-IP 8950 (D107) BIG-IP 11000 (E101) BIG-IP 11050 (E102) BIG-IP 5000 series (C109) BIG-IP 7000 series (D110) BIG-IP 10000s/10050s/10200v/10250v (D113) VIPRION blade B2100 (A109) VIPRION blade B2150 (A113) VIPRION blade B2250 (A112) VIPRION blade B4100 (A100) VIPRION blade B4200 (A107) VIPRION blade B4300 (A108) VIPRION blade B4340N (A110) Note: The bcm56xxd process is the switch driver daemon for the BIG-IP system.

Workaround

None.

Fix Information

TMOS has been updated to prevent the daemon bcm56xxd from restarting due to parity errors.

Behavior Change