Bug ID 1235161: Modification of STP path cost with value 0 on appliance/chassis does not work as expected

Last Modified: May 29, 2024

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

Fixed In:
F5OS-C 1.6.0, F5OS-A 1.7.0

Opened: Feb 06, 2023

Severity: 3-Major

Symptoms

User is allowed to set path cost as 0 but it does participate in port role selection. > Port role is dependent on path cost; port with lesser path cost becomes root. > In the current issue, though port has a lesser value of path cost (0), it is not becoming root.

Impact

Interface with path-cost as 0 does not become root or it does not restrict user to set path cost value as 0.

Conditions

STP is enabled on F5OS enabled platforms and > Path cost of any of the interface is set to some number > One of the interface has default value or value 0.

Workaround

Don not keep path-cost value as 0.

Fix Information

> Default value of path-cost is modified to 1. > Range of the path-cost is updated, it starts from 1 instead of 0.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips