Connectivity Guide

Table Of Contents
EdgePort Forward traffic
EdgePort allows the interface to forward traffic approximately 30 seconds sooner as it skips the Blocking and Learning states.
The spanning-tree bpduguard enable command causes the interface hardware to shut down when it receives a BPDU.
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.
When you implement BPDU guard, although the interface is placed in the Error Disabled state when receiving the BPDU, the
physical interface remains in the Up state. The hardware discards regular network traffic after a BPDU violation. BPDUs forward
to the CPU, where they are discarded as well.
Enable EdgePort on an interface in INTERFACE mode.
spanning-tree port type edge
Configure EdgePort
OS10(conf-if-eth1/1/4)# spanning-tree port type edge
View interface status
OS10# show spanning-tree interface ethernet 1/1/4
ethernet1/1/4 of MSTI 0 is designated Forwarding
Edge port:yes port guard :none (default)
Link type is point-to-point (auto)
Boundary: YES bpdu filter :disable bpdu guard :disable bpduguard shutdown-on-
violation :disable RootGuard: disable LoopGuard disable
Bpdus (MRecords) sent 610, received 5
Interface Designated
Name PortID Prio Cost Sts Cost Bridge ID PortID
--------------------------------------------------------------------------
ethernet1/1/4 128.272 128 500 FWD 0 32768 90b1.1cf4.a911 128.272
==========================================================================
Spanning-tree extensions
STP extensions provide a means to ensure efficient network convergence by securely enforcing the active network topology.
OS10 supports BPDU filtering, BPDU guard, root guard, and loop guard STP extensions.
BPDU filtering
Protects the network from unexpected flooding of BPDUs from an erroneous device. Enabling BPDU
Filtering instructs the hardware to drop BPDUs and prevents flooding from reaching the CPU. BPDU
filtering is enabled by default on Edge ports. All BPDUs received on the Edge port drops. If you explicitly
configure BPDU filtering on a port, that port drops all BPDUs it receives.
BPDU guard Blocks the L2 bridged ports and LAG ports connected to end hosts and servers from receiving any
BPDUs. When you enable BPDU guard, it places a bridge or LAG port in the Error_Disable or Blocking
state if the port receives any BPDU frames. In a LAG, all member ports, including new members are
placed in the Blocking state. The network traffic drops but the port continues to forward BPDUs to the
CPU that are later dropped. To prevent further reception of BPDUs, configure a port to shut down using
the shutdown command. The port can only resume operation from the Shutdown state after manual
intervention.
Root guard Avoids bridging loops and preserves the root bridge position during network transitions. STP selects the
root bridge with the lowest priority value. During network transitions, another bridge with a lower priority
may attempt to become the root bridge and cause unpredictable network behavior. To avoid such an
attempt and preserve the position of the root bridge, configure the spanning-tree guard root
command. Root guard is enabled on ports that are designated ports. The root guard configuration applies
to all VLANs configured on the port.
Loop guard Prevents L2 forwarding loops caused by a cable or interface hardware failure. When a hardware failure
occurs, a participating spanning tree link becomes unidirectional and a port stops receiving BPDUs. When
a blocked port stops receiving BPDUs, it transitions to a Forwarding state causing spanning tree loops in
the network. Enable loop guard on a port that transitions to the Loop-Inconsistent state until it receives
BPDUs using the spanning-tree guard loop command. After BPDUs are received, the port moves
310 Layer 2