Bug ID 479115: stpd tries to use bcm56xxd before it has started which results in error messages in ltm log

Last Modified: Apr 10, 2019

Bug Tracker

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

Known Affected Versions:
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: Sep 12, 2014
Severity: 3-Major

Symptoms

There is a race condition when the daemons startup where stpd is coming up before bcm56xxd. The stpd daemon tries to use bcm56xxd before it has started. You see the following in /var/log/ltm: err stpd[8241]: 01290003:3: HalmsgTerminalImpl_::sendMessage() Unable to send to any BCM56XXD address

Impact

Several error messages appear in the ltm log: Feb 9 15:06:23 localhost err stpd[9390]: 01290003:3: HalmsgTerminalImpl_::sendMessage() Unable to send to any BCM56XXD address Feb 9 15:06:23 localhost err stpd[9390]: 01280012:3: HAL packet request sendMessage failed (slot 0)

Conditions

Affects switch based platforms that use bcm56xxd.

Workaround

None

Fix Information

The startup of stpd daemon is now dependent on bcm56xxd being in the running state.

Behavior Change