Reference Guide
Example (Dynamic)
OS10# show mac address-table dynamic
VlanId Mac Address Type Interface
1 90:b1:1c:f4:a6:8f dynamic ethernet1/1/3
Example (Ethernet)
OS10# show mac address-table interface ethernet 1/1/3
VlanId Mac Address Type Interface
1 66:38:3a:62:31:3a dynamic ethernet1/1/3
Supported Releases 10.2.0E or later
Multiple spanning-tree protocol
MST is a RSTP-based spanning-tree variation that improves on per-VLAN RPVST+. You can congure MST instances and map multiple
VLANs to one spanning-tree instance to reduce the total number of required instances. RPVST+ allows a spanning-tree instance for each
VLAN. This 1:1 approach is not suitable if you have multiple VLANs — each spanning-tree instance costs bandwidth and processing
resources.
The MST protocol is compatible with RSTP and RPVST+. When you enable MST, all ports in Layer 2 mode participate in MST. Keep in mind
that OS10 only supports one MST region.
Load balancing can be achieved using the MST protocol. When three VLANs are mapped to two MSTIs, VLAN 100 trac takes a dierent
path than VLAN 200 and 300 trac.
Conguring MST is a four-step process:
1 Enable MST, if the current running STP version is not MST.
2 (Optional) Map the VLANs to dierent instances to achieve load balancing.
3 Ensure the same region name is congured in all the bridges running MST.
4 (Optional) Congure the revision number.
Congure MST protocol
When you enable MST globally, all L2 physical, port-channel, and VLAN interfaces are automatically assigned to MST instance (MSTI) zero
(0). Within an MSTI, only one path from any one bridge to another is enabled for forwarding.
1 Enable MST in CONFIGURATION mode.
spanning-tree mode mst
2 Save the conguration.
do commit
Layer 2
137