Bug ID 694947: bcm56xxd restart causes error logs from stpd, lldpd and lacpd.

Last Modified: May 01, 2019

Bug Tracker

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

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.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5

Fixed In:
14.0.0

Opened: Nov 16, 2017
Severity: 3-Major

Symptoms

When bcm56xxd restarts as a result of an interface bundling change, other daemons (lldpd, stpd, lacpd) lose connectivity for the duration of the restart. This loss of connectivity results in the following errors being logged: -- err stpd[11965]: 01290003:3: HalmsgTerminalImpl_::sendMessage() Unable to send to any BCM56XXD address -- err stpd[11965]: 01280012:3: HAL packet request sendMessage failed (slot 0) -- err lacpd[10147]: 01290003:3: HalmsgTerminalImpl_::sendMessage() Unable to send to any BCM56XXD address -- err lacpd[10147]: 01160005:3: HalMsgHandler.cpp:125 - HAL send PDU request failed -- lldpd[11052]: 01290003:3: HalmsgTerminalImpl_::sendMessage() Unable to send to any BCM56XXD address -- err lldpd[11052]: 01570004:3: HAL send PDU request failed

Impact

Restart of bcm56xxd, which also results in restart of other daemons and logging of error messages to LTM log. Traffic disrupted while daemons restart.

Conditions

Enabling or disabling bundling on 40 GB interface.

Workaround

None.

Fix Information

Enabling or disabling bundling on 40 GB interface now presents a message similar to the following: Are you sure? Y/N (changing the interface bundling will restart bcm56xxd, cause loss of connectivity to other daemons and impact traffic).

Behavior Change