Owners Manual

NOTE: OpenSwitch OPX does not support RSTP, MSTP, and RPVST in a Linux bridge due to a Linux kernel limitation. STP is not
supported on a bridge which has multiple member interfaces with dierent VLAN IDs.
See YANG model reference in the OpenSwitch OPX Developers Guide for more information on the dell-open-stp.yang model for the
supported STP parameters.
Linux STP does not support the concept of spanning-tree groups. In Linux, you can enable spanning tree independently in each bridge
instance. OpenSwitch OPX treats STP enabled in a bridge instance as a separate spanning-tree group for each VLAN. If a Linux bridge
contains only untagged ports, the software does not support STP on the bridge.
1 Create a VLAN in the Linux bridge (see VLAN bridging).
2 Enable STP on the bridge, then view the conguration.
$ brctl stp br100 on
$ brctl show br100
bridge name bridge id STP enabled interfaces
br100 8000.90b11cf4a918 yes e101-001-0.100
$ brctl showstp br100
br100
bridge id 8000.90b11cf4a918
designated root 8000.90b11cf4a918
root port 0 path cost 0
max age 20.00 bridge max age 20.00
hello time 2.00 bridge hello time 2.00
forward delay 15.00 bridge forward delay 15.00
ageing time 300.00
hello timer 0.00 tcn timer 0.00
topology change timer 0.00 gc timer 0.00
flags
e101-001-0.100 (1)
port id 8001 state disabled
designated root 8000.90b11cf4a918 path cost 100
designated bridge 8000.90b11cf4a918 message age timer 0.00
designated port 8001 forward delay timer 0.00
designated cost 0 hold timer 0.00
flags
Disable STP on bridge
$ brctl stp br100 off
View bridge conguration
$ brctl show br100
bridge name bridge id STP enabled interfaces
br100 8000.90b11cf4a918 no e101-001-0.100
When you enable STP on a bridge which has tagged VLAN interfaces, OpenSwitch OPX creates a new spanning-tree group and associates
the VLAN ID of the bridge with the newly created spanning-tree group. When you delete a bridge from the Linux kernel, the corresponding
NPU spanning-tree group is deleted.
12
Layer 2 bridging