Users Guide

This feature allows the user to disable path cost re-calculation on link flap events. If disabled, the path cost of the lag
is calculated based on the below formula LAG speed = speed of a single member * number of configured member ports
(irrespective of its oper status).
Path cost changes only for the user event [addition/removal of channel-member]. Path cost is calculated based on the number
of configured ports.
Dynamic path cost disable functionality is supported for VLT port channel.
Debug facilities
Use the debug spanning-tree bpdu command to monitor and verify that the MST configuration is communicating as
configured. To ensure all necessary parameters match — region name, region version, and VLAN to instance mapping, examine
your individual devices. Use the show spanning-tree mst command to view the MST configuration, or use the show
running-configuration command to view the overall MST configuration.
MST flags for
communication
received from
the same region
The MST routers are located in the same region. If the debug logs indicate that packets are coming from
a Different Region, one of the key parameters does not match.
MST region name
and revision
The configured name and revisions must be identical among all devices. If the region name is blank, a
name was configured on one device and was not configured or was configured differently on another —
spelling and capitalization count.
MST instances Verify the VLAN-to-MST instance mapping using the show commands. If you see extra MST instances
in the Sending or Received logs, an additional MST instance was configured on one router but not the
others.
● View BPDUs in EXEC mode.
debug spanning-tree bpdu
● View MST-triggered topology change messages in EXEC mode.
debug spanning-tree events
View MST configuration
OS10# show spanning-tree mst configuration
Region Name: force10
Revision: 100
MSTI VID
0 1,31-4093
1 2-10
2 11-20
3 21-30
EdgePort
EdgePort allows the interface to forward traffic approximately 30 seconds sooner as it skips the Blocking and Learning states.
CAUTION:
Configure EdgePort only on links connecting to an end station. EdgePort can cause loops if you
enable it on an interface connected to a network. Edge ports do not receive BPDUs.
NOTE: Whenever a port becomes a designated port, it will start a timer called the edge delay while timer (hello-time + 1/2
* hello-time); if the hello-time is set to 2 seconds, the edge delay while timer is 3 seconds. If BPDUs are not received for 3
seconds, then the port is declared as oper edge on the fly and is moved to forwarding state.
OS10 supports auto edge feature . If the port does not receive BPDU for the hello-time + one second interval then it places the
port into auto edge mode.
If the edge port receives any BPDU, it looses the edge port property.
Layer 2
599