Bug ID 1077785: STP errors messages reported in platform.log when global STP is enabled but STP parameters are not configured in interfaces

Last Modified: Apr 28, 2025

Affected Product(s):
F5OS Velos(all modules)

Fixed In:
F5OS-A 1.1.0

Opened: Feb 02, 2022

Severity: 3-Major

Symptoms

The VELOS platform.log contains numerous STP error messages: appliance-1 stpd[1]: priority="Err" version=1.0 msgid=0x6102000000000018 msg="Failed to write to cdb" FIELD="Adv Stp Interface name" ERRNO=8 ERRNOSTR="badly formatted or nonexistent path". appliance-1 stpd[1]: priority="Err" version=1.0 msgid=0x6102000000000018 msg="Failed to write to cdb" FIELD="Adv Stp Interface port-num" ERRNO=8 ERRNOSTR="badly formatted or nonexistent path". appliance-1 stpd[1]: priority="Err" version=1.0 msgid=0x6102000000000018 msg="Failed to write to cdb" FIELD="Adv Stp Interface port-state" ERRNO=8

Impact

VELOS platform.log size will grow at rate of 2MB per minute.

Conditions

The following is the correct sequence of STP configuration. appliance-1(config)# stp global config enabled-protocol RSTP appliance-1(config)# stp rstp interfaces interface 1.0 config cost 100;top appliance-1(config)# stp interfaces interface 1.0 config edge-port EDGE_AUTO link-type P2P ; appliance-1(config-interface-1.0)# exit appliance-1(config)# commit; If the command "stp rstp interfaces interface 1.0 config cost 100;top" is not run, the log messages will occur.

Workaround

To stop these messages, configure the following: stp rstp interfaces interface 1.0 config cost 100;top

Fix Information

Multiple STP errors messages are no longer logged when not needed.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips