The values for interface PVST+ parameters are given in the output of the
show spanning-tree pvst
command, as previously shown.
Configuring an EdgePort
The EdgePort feature enables interfaces to begin forwarding traffic approximately 30 seconds sooner.
In this mode an interface forwards frames by default until it receives a BPDU that indicates that it should behave otherwise; it does not go
through the Learning and Listening states. The
bpduguard shutdown-on-violation
option causes the interface hardware to be
shut down when it receives a BPDU. When you only implement
bpduguard
, although the interface is placed in an Error Disabled state
when receiving the BPDU, the physical interface remains up and spanning-tree drops packets in the hardware after a BPDU violation.
BPDUs are dropped in the software after receiving the BPDU violation.
This feature is the same as PortFast mode in spanning tree.
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.
To enable EdgePort on an interface, use the following command.
•
Enable EdgePort on an interface.
INTERFACE mode
spanning-tree pvst edge-port [bpduguard | shutdown-on-violation]
The EdgePort status of each interface is given in the output of the
show spanning-tree pvst
command, as previously shown.
Dell Networking OS Behavior
: Regarding the
bpduguard shutdown-on-violation
command behavior:
•
If the interface to be shut down is a port channel, all the member ports are disabled in the hardware.
•
When you add a physical port to a port channel already in an Error Disable state, the new member port is also disabled in the hardware.
•
When you remove a physical port from a port channel in an Error Disable state, the Error Disabled state is cleared on this physical port
(the physical port is enabled in the hardware).
•
You can clear the Error Disabled state with any of the following methods:
•
Perform a
shutdown
command on the interface.
•
Disable the
shutdown-on-violation
command on the interface (the
no spanning-tree stp-id portfast
[bpduguard | [shutdown-on-violation]]
command).
•
Disable spanning tree on the interface (the
no spanning-tree
command in INTERFACE mode).
•
Disabling global spanning tree (the
no spanning-tree
command in CONFIGURATION mode).
PVST+ in Multi-Vendor Networks
Some non-Dell Networking systems which have hybrid ports participating in PVST+ transmit two kinds of BPDUs: an 802.1D BPDU and an
untagged PVST+ BPDU.
Dell Networking systems do not expect PVST+ BPDU (tagged or untagged) on an untagged port. If this situation occurs, Dell Networking
OS places the port in an Error-Disable state. This behavior might result in the network not converging. To prevent Dell Networking OS from
executing this action, use the
no spanning-tree pvst err-disable cause invalid-pvst-bpdu
command. After you
configure this command, if the port receives a PVST+ BPDU, the BPDU is dropped and the port remains operational.
Enabling PVST+ Extend System ID
In the following example, ports P1 and P2 are untagged members of different VLANs. These ports are untagged because the hub is VLAN
unaware. There is no data loop in this scenario; however, you can employ PVST+ to avoid potential misconfigurations.
If you enable PVST+ on the Dell Networking switch in this network, P1 and P2 receive BPDUs from each other. Ordinarily, the Bridge ID in
the frame matches the Root ID, a loop is detected, and the rules of convergence require that P2 move to blocking state because it has the
lowest port ID.
To keep both ports in a Forwarding state, use extend system ID. Extend system ID augments the bridge ID with a VLAN ID to differentiate
BPDUs on each VLAN so that PVST+ does not detect a loop and both ports can remain in a Forwarding state.
726
Per-VLAN Spanning Tree Plus (PVST+)
Содержание S4048T-ON
Страница 1: ...Dell Configuration Guide for the S4048 ON System 9 11 2 1 ...
Страница 148: ...Figure 10 BFD Three Way Handshake State Changes 148 Bidirectional Forwarding Detection BFD ...
Страница 251: ...Dell Control Plane Policing CoPP 251 ...
Страница 363: ... RPM Synchronization GARP VLAN Registration Protocol GVRP 363 ...
Страница 511: ...Figure 64 Inspecting the LAG Configuration Link Aggregation Control Protocol LACP 511 ...
Страница 512: ...Figure 65 Inspecting Configuration of LAG 10 on ALPHA 512 Link Aggregation Control Protocol LACP ...
Страница 515: ...Figure 67 Inspecting a LAG Port on BRAVO Using the show interface Command Link Aggregation Control Protocol LACP 515 ...
Страница 516: ...Figure 68 Inspecting LAG 10 Using the show interfaces port channel Command 516 Link Aggregation Control Protocol LACP ...
Страница 558: ...Figure 84 Configuring Interfaces for MSDP 558 Multicast Source Discovery Protocol MSDP ...
Страница 559: ...Figure 85 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 559 ...
Страница 560: ...Figure 86 Configuring PIM in Multiple Routing Domains 560 Multicast Source Discovery Protocol MSDP ...
Страница 564: ...Figure 88 MSDP Default Peer Scenario 2 564 Multicast Source Discovery Protocol MSDP ...
Страница 565: ...Figure 89 MSDP Default Peer Scenario 3 Multicast Source Discovery Protocol MSDP 565 ...
Страница 729: ...protocol spanning tree pvst no disable vlan 300 bridge priority 4096 Per VLAN Spanning Tree Plus PVST 729 ...
Страница 841: ...Figure 115 Single and Double Tag TPID Match Service Provider Bridging 841 ...
Страница 842: ...Figure 116 Single and Double Tag First byte TPID Match 842 Service Provider Bridging ...