Spanning-Tree Protocols User Guide - Juniper

2y ago
25 Views
2 Downloads
1.62 MB
485 Pages
Last View : 27d ago
Last Download : 3m ago
Upload by : Louie Bolen
Transcription

Spanning-Tree Protocols User GuidePublished2021-12-10

iiJuniper Networks, Inc.1133 Innovation WaySunnyvale, California 94089USA408-745-2000www.juniper.netJuniper Networks, the Juniper Networks logo, Juniper, and Junos are registered trademarks of Juniper Networks, Inc.in the United States and other countries. All other trademarks, service marks, registered marks, or registered servicemarks are the property of their respective owners.Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the rightto change, modify, transfer, or otherwise revise this publication without notice.Spanning-Tree Protocols User GuideCopyright 2021 Juniper Networks, Inc. All rights reserved.The information in this document is current as of the date on the title page.YEAR 2000 NOTICEJuniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-relatedlimitations through the year 2038. However, the NTP application is known to have some difficulty in the year 2036.END USER LICENSE AGREEMENTThe Juniper Networks product that is the subject of this technical documentation consists of (or is intended for usewith) Juniper Networks software. Use of such software is subject to the terms and conditions of the End User LicenseAgreement ("EULA") posted at https://support.juniper.net/support/eula/. By downloading, installing or using suchsoftware, you agree to the terms and conditions of that EULA.

iiiTable of ContentsAbout This Guide xii1OverviewSpanning-Tree Protocol Overview 2How Spanning Tree Protocols Work 2Choosing a Spanning Tree Protocol 62Spanning-Tree Instances and InterfacesSpanning Tree Instances and Interfaces 18Understanding Spanning-Tree Instance Interfaces 18Configuring a Virtual Switch Routing Instance on MX Series Routers 20Configuring a Spanning-Tree Instance Interface as an Edge Port for Faster Convergence 213Configuring Spanning-Tree ProtocolsConfiguring STP Protocol 23Understanding STP 23Understanding System Identifiers for Bridges in STP or RSTP Instances 25Configuring STP on EX Series Switches (CLI Procedure) 25Configuring RSTP Protocol 26Understanding RSTP 27Configuring Rapid Spanning Tree Protocol 28Configuring RSTP on EX Series Switches (CLI Procedure) 31Example: Configuring Faster Convergence and Network Stability on ELS Switches with RSTP 32Requirements 33Overview and Topology 33Configuring RSTP and Nonstop Bridging on Switch 1 36Configuring RSTP and Nonstop Bridging on Switch 2 41Configuring RSTP and Nonstop Bridging on Switch 3 46Configuring RSTP and Nonstop Bridging on Switch 4 51

ivVerification 55Example: Faster Convergence and Improved Network Stability with RSTP on EX SeriesSwitches 59Requirements 59Overview and Topology 60Configuring RSTP and Nonstop Bridging on Switch 1 63Configuring RSTP and Nonstop Bridging on Switch 2 68Configuring RSTP and Nonstop Bridging on Switch 3 73Configuring RSTP and Nonstop Bridging on Switch 4 78Verification 82Forcing RSTP or VSTP to Run as IEEE 802.1D STP (CLI Procedure) 86Configuring MSTP Protocol 87Understanding MSTP 87Configuring MSTP on Switches 91Configuring Multiple Spanning Tree Protocol 95Configuring MSTP Instances on a Physical Interface 98Example: Configuring Network Regions for VLANs with MSTP on Switches 101Requirements 101Overview and Topology 102Configuring MSTP on Switch 1 105Configuring MSTP on Switch 2 110Configuring MSTP on Switch 3 115Configuring MSTP on Switch 4 120Verification 124Disabling MSTP 133Configuring VSTP Protocol 134Understanding VSTP 135Global and Specific VSTP Configurations for Switches 136Example: Configuring VSTP on a Trunk Port with Tagged Traffic 141Requirements 141Overview 141

vConfiguration 142Verification 154Reverting to RSTP or VSTP from Forced IEEE 802.1D STP 1574BPDU Protection for Spanning-Tree ProtocolsBPDU Protection for Spanning-Tree Protocols 160Understanding BPDU Protection for Spanning-Tree Instance Interfaces 160Understanding BPDU Protection for STP, RSTP, and MSTP 162Configuring BPDU Protection for Individual Spanning-Tree Instance Interfaces 164Understanding BPDUs Used for Exchanging Information Among Bridges 165BPDU Protection on All Edge Ports of the Bridge 166Understanding BPDU Protection for EVPN-VXLAN 166Configuring BPDU Protection on Switch Spanning Tree Interfaces 169Configuring BPDU Protection on ACX Router, EX Switch and MX Router Edge Ports 171Configuring BPDU protection For Edge Interfaces 172Configuring BPDU for Interface Protection With Port Shutdown Mode 174Configuring BPDU for Interface Protection With BPDU Drop Mode 175Example: Configuring BPDU Protection on Interfaces to Prevent STP Miscalculations 178Requirements 178Overview 179Configuration 179Verification 181Example: Configuring BPDU Protection on MX Edge Interfaces to Prevent STP Miscalculations 185Requirements 185Overview 186Configuration 188Verification 189Example: Configuring BPDU Protection on Edge Interfaces to Prevent STP Miscalculations 192Requirements 192

viOverview 193Configuration 193Verification 195Example: Configuring BPDU Protection on Switch Edge Interfaces With ELS to Prevent STPMiscalculations 197Requirements 197Overview and Topology 198Configuration 200Verification 201Example: Configuring BPDU Protection on Edge Interfaces to Prevent STP Miscalculations onnon-ELS EX Series Switches 204Requirements 204Overview and Topology 205Configuration 207Verification 208Example: Configuring BPDU Protection on Interfaces to Prevent STP Miscalculations on EXSeries Switches 210Requirements 211Overview and Topology 212Configuration 214Verification 215Example: Blocking BPDUs on Aggregated Ethernet Interface for 600 Seconds 217Example: Configuring BPDU Protection on Interfaces to Prevent STP Miscalculations on EXSeries Switches 218Requirements 219Overview and Topology 219Configuration 222Verification 2255Loop Protection for Spanning-Tree ProtocolsLoop Protection for Spanning-Tree Protocols 229Understanding Loop Protection for Spanning-Tree Instance Interfaces 229Eliminating Bridge Loops in Ethernet LANs with Spanning Tree Protocol 231Example: Enabling Loop Protection for Spanning-Tree Protocols 240

viiConfiguring Loop Protection for a Spanning-Tree Instance Interface 240Example: Configuring Loop Protection to Prevent Interfaces from Transitioning from Blocking toForwarding in a Spanning Tree on non-ELS EX Series Switches 242Requirements 242Overview and Topology 243Configuration 245Verification 246Example: Configuring Loop Protection to Prevent Interfaces from Transitioning from Blocking toForwarding in a Spanning Tree on EX Series Switches With ELS 248Requirements 249Overview and Topology 249Configuration 251Verification 2526Root Protection for VPLS Multihome EnvironmentsRoot Protection for VPLS Multihome Environments 256Understanding VPLS Multihoming 256Understanding Bridge Priority for Election of Root Bridge and Designated Bridge 261Understanding Root Protection for Spanning-Tree Instance Interfaces in a Layer 2 SwitchedNetwork 261Example: Configuring VPLS Root Topology Change Actions 263Enabling Root Protection for a Spanning-Tree Instance Interface 263Configuring VPLS Root Protection Topology Change Actions to Control Individual VLANSpanning-Tree Behavior 264Example: Configuring Root Protection to Enforce Root Bridge Placement in Spanning Trees onnon-ELS EX Series Switches 266Requirements 266Overview and Topology 266Configuration 269Verification 270Example: Configuring Root Protection to Enforce Root Bridge Placement in Spanning Trees onEX Series Switches With ELS 273Requirements 273

viiiOverview and Topology 274Configuration 276Verification 2777Monitoring and TroubleshootingMonitoring and Troubleshooting Spanning Tree Protocols 282Monitoring Spanning Tree Protocols on Switches 282Checking the Status of Spanning-Tree Instance Interfaces 286Understanding Spanning-Tree Protocol Trace Options 286Configuring Tracing Spanning-Tree Operations 287Example: Tracing Spanning-Tree Protocol Operations 289Unblocking a Switch Interface That Receives BPDUs in Error (CLI Procedure) 290Unblocking an Interface on non-ELS EX Series Switches That Receives BPDUs in Error (CLIProcedure) 291Clearing the Blocked Status of a Spanning-Tree Instance Interface 291Checking for a MAC Rewrite Error Condition Blocking a Spanning-Tree Instance Interface 292Clearing a MAC Rewrite Error Condition Blocking a Spanning-Tree Instance Interface 292Clearing a MAC Rewrite Error on an Interface with Layer 2 Protocol Tunneling 293Understanding Forward Delay Before Ports Transition to Forwarding State 2948Configuration Statementsaccess-trunk 297arp-on-stp 298backup-bridge-priority 300block (Spanning Trees) 302bpdu-destination-mac-address (Spanning Tree) 303bpdu-block 305bpdu-block-on-edge 307bridge-priority 310

ixconfiguration-name 312cost 314disable 317disable-timeout 319drop (BPDU Block) 322edge 324enable-all-ifl 326extended-system-id 328force-version (IEEE 802.1D STP) 329forward-delay 331hello-time 333interface (BPDU Blocking) 336interface (Spanning Tree) 338layer2-control 341log (Spanning Trees) 344mac-rewrite 345max-age 347max-hops 350mode 352msti 355mstp 358no-root-port 362priority (Protocols STP) 364priority-hold-time 367protocol 368

xprotocols (STP Type) 372revision-level 374rstp 376shutdown (BPDU Block) 381stp 382system-id 385traceoptions (Spanning Tree) 387vlan (MSTP) 392vlan (VSTP) 395vlan-group 398vpls-flush-on-topology-change 400vstp 4019Operational Commandsclear error bpdu interface 409clear error mac-rewrite 411clear ethernet-switching bpdu-error interface 413clear spanning-tree protocol-migration 414clear spanning-tree statistics 416clear spanning-tree statistics bridge 418clear spanning-tree stp-buffer 420show bridge mac-table 421show mac-rewrite interface 429show spanning-tree bridge 432show spanning-tree interface 440show spanning-tree mstp configuration 453

xishow spanning-tree statistics 457show spanning-tree statistics bridge 460show spanning-tree statistics interface 462show spanning-tree statistics message-queues 465show spanning-tree stp-buffer see-all 467

xiiAbout This GuideSpanning-tree protocols on routers and switches address provide link redundancy while simultaneouslypreventing undesirable loops.

1CHAPTEROverviewSpanning-Tree Protocol Overview 2

2Spanning-Tree Protocol OverviewIN THIS SECTIONHow Spanning Tree Protocols Work 2Choosing a Spanning Tree Protocol 6How Spanning Tree Protocols WorkIN THIS SECTIONBenefits of Using Spanning Tree Protocols 3Spanning Tree Protocols Help Prevent Broadcast Storms 3Port Roles Determine Participation in the Spanning Tree 3Port States Determine How a Port Processes a Frame 4Edge Ports Connect to Devices That Cannot Be Part of a Spanning Tree 4BPDUs Maintain the Spanning-Tree 4When a Root Bridge Fails 5Devices Must Relearn MAC Addresses After a Link Failure 5Ethernet networks are susceptible to broadcast storms if loops are introduced. However, an Ethernetnetwork needs to include loops because they provide redundant paths in case of a link failure. Spanningtree protocols address both of these issues because they provide link redundancy while simultaneouslypreventing undesirable loops.Juniper Networks devices provide Layer 2 loop prevention through Spanning Tree Protocol (STP), RapidSpanning Tree Protocol (RSTP), Multiple Spanning Tree Protocol (MSTP), and VLAN Spanning TreeProtocol (VSTP). RSTP is the default spanning-tree protocol for preventing loops on Ethernet networks.This topic describes:

3Benefits of Using Spanning Tree ProtocolsSpanning Tree protocols have the following benefits: Provide link redundancy while simultaneously preventing undesirable loops Prevent Broadcast Storms Connects to devices that are not STP-capable, such as PCs, servers, routers, or hubs that are notconnected to other switches, by using edge portsSpanning Tree Protocols Help Prevent Broadcast StormsSpanning-tree protocols intelligently avoid loops in a network by creating a tree topology (spanning tree)of the entire bridged network with only one available path between the tree root and a leaf. All otherpaths are forced into a standby state. The tree root is a switch within the network elected by the STA(spanning-tree algorithm) to use when computing the best path between bridges throughout thenetwork and the root bridge. Frames travel through the network to their destination–a leaf such as anend-user PC–along branches. A tree branch is a network segment, or link, between bridges. Switchesthat forward frames through an STP spanning tree are called designated bridges.NOTE: If you are using Junos OS for EX Series and QFX Series switches with support for theEnhanced Layer 2 Software (ELS) configuration style, you can force the original IEEE 802.1DSpanning Tree Protocol (STP) version to run in place of RSTP or VSTP by setting "force-version"on page 329.Port Roles Determine Participation in the Spanning TreeEach port has both a role and a state. A port’s role determines how it participates in the spanning tree.The five port roles used in RSTP are: Root port—The port closest to the root bridge (has the lowest path cost from a bridge). This is theonly port that receives frames from and forwards frames to the root bridge. Designated port—The port that forwards traffic away from the root bridge toward a leaf. Adesignated bridge has one designated port for every link connection it serves. A root bridge forwardsframes from all of its ports, which serve as designated ports. Alternate port—A port that provides an alternate path toward the root bridge if the root port failsand is placed in the discarding state. This port is not part of the active spanning tree, but if the rootport fails, the alternate port immediately takes over.

4 Backup port—A port that provides a backup path toward the leaves of the spanning tree if adesignated port fails and is placed in the discarding state. A backup port can exist only where two ormore bridge ports connect to the same LAN for which the bridge serves as the designated bridge. Abackup port for a designated port immediately takes over if the port fails. Disabled port—The port is not part of the active spanning tree.Port States Determine How a Port Processes a FrameEach port has both a state and a role. A port’s state determines how it processes a frame. RSTP placeseach port of a designated bridge in one of three states: Discarding—The port discards all BPDUs. A port in this state discards all frames it receives and doesnot learn MAC addresses. Learning—The port prepares to forward traffic by examining received frames for location informationin order to build its MAC address table. Forwarding—The port filters and forwards frames. A port in the forwarding state is part of the activespanning tree.Edge Ports Connect to Devices That Cannot Be Part of a Spanning TreeSpanning Tree also defines the concept of an edge port, which is a designated port that connects todevices that are not STP-capable, such as PCs, servers, routers, or hubs that are not connected to otherswitches. Because edge ports connect directly to end stations, they cannot create network loops andcan transition to the forwarding state immediately. You can manually configure edge ports, and a switchcan also detect edge ports by noting the absence of communication from the end stations.The edge ports themselves do send BPDUs to the spanning tree. If you have a good understanding ofthe implications on your network and want to modify RSTP on the edge port interface.BPDUs Maintain the Spanning-TreeSpanning-tree protocols use frames called bridge protocol data units (BPDUs) to create and maintain thespanning tree. A BPDU frame is a message sent from one switch to another to communicate informationabout itself, such as its bridge ID, root path costs, and port MAC addresses. The initial exchange ofBPDUs between switches determines the root bridge. Simultaneously, BPDUs are used to communicatethe cost of each link between branch devices, which is based upon port speed or user configuration.RSTP uses this path cost to determine the ideal route for data frames to travel from one leaf to anotherleaf and then blocks all other routes. If an edge port receives a BPDU, it automatically transitions to aregular RSTP port.

5When the network is in a steady state, the spanning tree converges when the spanning-tree algorithm(STA) identifies both the root and designated bridges and all ports are in either a forwarding or blockingstate. To maintain the tree, the root bridge continues to send BPDUs at a hello time interval (default 2seconds). These BPDUs continue to communicate the current tree topology. When a port receives ahello BPDU, it compares the information to that already stored for the receiving port. One of threeactions takes place when a switch receives a BPDU: If the BPDU data matches the existing entry in the MAC address table, the port resets a timer calledmax age to zero and then forwards a new BPDU with the current active topology information to thenext port in the spanning tree. If the topology in the BPDU has been changed, the information is updated in the MAC address table,max age is again set to zero, and a new BPDU is forwarded with the current active topologyinformation to the next port in the spanning tree. When a port does not receive a BPDU for three hello times, it reacts one of two ways. If the port isthe root port, a complete rework of the spanning tree occurs—see When an RSTP Root Bridge Fails.If the bridge is any non-root bridge, RSTP detects that the connected device cannot send BPDUs andconverts that port to an edge port.When a Root Bridge FailsWhen a link to the root port goes down, a flag called a topology change notification (TCN) is added tothe BPDU. When this BPDU reaches the next port in the VLAN, the MAC address table is flushed andthe BPDU is sent to the next bridge. Eventually, all ports in the VLAN have flushed their MAC addresstables. Then, RSTP configures a new root port.After a root port or a designated port fails, the alternate or backup port takes over after an exchange ofBPDUs called the proposal-agreement handshake. RSTP propagates this handshake over point-to-pointlinks, which are dedicated links between two network nodes, or switches, that connect one port toanother. If a local port becomes a new root or designated port, it negotiates a rapid transition with thereceiving port on the nearest neighboring switch by using the proposal-agreement handshake to ensurea loop-free topology.Devices Must Relearn MAC Addresses After a Link FailureBecause a link failure causes all associated ports to flush their MAC address table, the network might beslower as it floods to relearn the MAC addresses. There is a way to speed up this relearning process.During TCN propagation, the Layer 2 forwarding table of switches is flushed, resulting in a flood of datapackets. The Address Resolution Protocol (ARP) feature causes the switch to proactively send ARPrequests for IP addresses in the ARP cache (present because of Layer 3 VLAN interface). With ARP onSTP enabled, as the reply comes through, the switches builds up the Layer 2 forwarding table, thuslimiting the flooding later. Enabling ARP on STP is most useful to prevent excessive flooding in largeLayer 2 networks using RVIs.

6NOTE: The ARP feature is not available on Junos OS for EX Series switches with support for theEnhanced Layer 2 Software (ELS) configuration style.SEE ALSOUnderstanding STP 23Understanding MSTP 87Understanding RSTP 27Example: Faster Convergence and Improved Network Stability with RSTP on EX Series Switches 59Example: Configuring Faster Convergence and Network Stability on ELS Switches with RSTP 32Configuring RSTP on EX Series Switches (CLI Procedure) 31Choosing a Spanning Tree ProtocolIN THIS SECTIONComparison of Spanning Tree Features 6Switch and Router Spanning Tree Support and Limitations 12When selecting a spanning-tree protocol, consider two basic questions: What STP features do I need? What switch or router will be used?Comparison of Spanning Tree FeaturesTable 1 on page 7 describes differences between spanning-tree protocols STP, RSTP, MSTP and VSTP.

7Table 1: Selecting a Spanning-Tree ProtocolProtocolAdvantagesDisadvantagesRSTP Rapid Spanning Tree Protocol is the default switch STP and RSTP are limitedconfiguration and is recommended for most networkconfigurations because it converges more quickly than STPafter a failure. Voice and video work better with RSTP than they do withSTP. RSTP is backward compatible with STP; therefore, switchesdo not all have to run RSTP. RSTP supports more ports than MSTP or VSTP. On MX and ACX routers, you can configure RSTP, MSTP, andVSTP instance interfaces as edge ports.to a single instance onany physical interface.Use the set rstpinterface statement toconfigure interfacesparticipating in the RSTPinstance. RSTP does not work with802.1D 1998 bridges.Use STP instead—see"Forcing RSTP or VSTPto Run as IEEE 802.1DSTP (CLI Procedure)" onpage 86 RSTP is notrecommended formultiple VLAN networksbecause it is not VLANaware—as a result, allVLANs within a LANshare the same spanningtree. This limits thenumber of forwardingpaths for data traffic. UseMSTP instead.TIP: Use the set rstp interface configuration statement to indicate which logical interfaces participate in RSTP.See.TIP: If RSTP has been forced to run as the original STP version, you can revert back to RSTP by "Reverting toRSTP or VSTP from Forced IEEE 802.1D STP" on page 157.

8Table 1: Selecting a Spanning-Tree Protocol (Continued)ProtocolAdvantagesDisadvantagesSTP Spanning Tree Protocol works with 802.1D 1998 bridges. STP and RSTP are limited RSTP is backward compatible with STP; therefore, you canto a single instance onany physical interface.run RSTP on some switches and STP on others with 802.1D1998 bridges.Use the set stpinterface statement toconfigure interfacesparticipating in the RSTPinstance. STP is slower than RSTP. STP is not recommendedfor multiple VLANnetworks because it isnot VLAN-aware—as aresult, all VLANs within aLAN share the samespanning-tree. This limitsthe number offorwarding paths for datatraffic. Use MSTPinstead. Although STP providesbasic loop preventionfunctionality, it does notprovide fast networkconvergence when thereare topology changes.The STP process todetermine network statetransitions is slower thanthe RSTP processbecause it is timer-based.RSTP converges fasterbecause it uses ahandshake mechanismbased on point-to-pointlinks instead of thetimer-based processused by STP.

9Table 1: Selecting a Spanning-Tree Protocol (Continued)ProtocolAdvantagesDisadvantages Edge ports are notsupported when theoriginal IEEE 802.1D STPis configured. If youspecify edge at the [editprotocols stp] hierarchylevel, the softwareignores the option.TIP: Use the set stp interface statement to configure interfaces to participate in the STP instance. See"Configuring STP on EX Series Switches (CLI Procedure)" on page 25.MSTP Multiple Spanning Tree Protocol works with most VLANs. MSTP supports multiple instances on a single physicalinterface. On MX and ACX routers, you can configure RSTP, MSTP, andVSTP instance interfaces as edge ports. Some protocols requirecompatibility notprovided by MSTP. In thiscase, use VSTP. MSTP supports a limitednumber of ports. AnMSTP region supports upto 64 MSTIs with eachinstance supporting from1 through 4094 VLANs MSTP uses more CPUthan RSTP and does notconverge as fast as RSTP.TIP: Use the set mstp interface configuration statement to indicate which logical interfaces participate in MSTP.See "Configuring MSTP on Switches" on page 91.

10Table 1: Selecting a Spanning-Tree Protocol (Continued)ProtocolAdvantagesDisadvantagesVSTP VSTP works with VLANs that require device compatibility. With VSTP, there can beEnable VSTP on all VLANs that could receive VSTP bridgeprotocol data units (BPDUs).only one STP instanceper VLAN, where MSTPlets you combinemultiple VLANs in oneinstance. VSTP and RSTP are the only spanning-tree protocols that canbe configured concurrently on a switch. For VSTP, interfaces can be configured at the global level or atthe VLAN level. Interfaces configured at the global VSTP levelwill be enabled for all the configured VLANs. If an interface isconfigured at both the global and VLAN levels, theconfiguration at the VLAN level overrides the globalconfiguration. On MX and ACX routers, you can configure RSTP, MSTP, andVSTP instance interfaces as edge ports. VSTP supports a limitednumber of portscompared to RSTP. You can configure VSTPfor a maximum of 509VLANs. However, havinga large number of VSTPand RSTP instances cancause continuouschanges in the topology.As a performanceworkaround, reduce thenumber of VSTPinstances to fewer than190. Using the same VLAN forRSTP and VSTP is notsupported. For example,if you are configuring aVLAN under VSTP,configuring RSTP with aninterface that containsthe same VLAN is notsupported. If you configure VSTPand RSTP at the sametime and the switch hasmore than 253 VLANs,VSTP is configured onlyfor the first 253 VLANs.For the remaining

11Table 1: Selecting a Spanning-Tree Protocol (Continued)ProtocolAdvantagesDisadvantagesVLANs, only RSTP isconfigured. When you configureVSTP with the setprotocol vstp vlan vlanid interface interfacename command, the VLANnamed default isexcluded. You mustmanually configure aVLAN with the namedefault to run VSTP.TIP: When using VSTP, we recommend that you enable VSTP on all VLANs that can receive VSTP bridge protocoldata units (BPDUs).TIP: When you configure VSTP with the set protocol vstp vlan all command, VLAN ID 1 is not set; it is excludedso that the configuration is compatible with Cisco PVST . If you want VLAN ID 1 to be included in the VSTPconfiguration on your switch, you must set it separately with the set protocol vstp vlan 1 command. For moreinformation, see Knowledge Base articles KB15138 and KB18291 at https://kb.juniper.net/InfoCenter/indexTIP: The maximum number of VLANs supported by VSTP on a switch depends upon whether you are using JunosOS for EX Series and QFX Series switches with support for the Enhanced Layer 2 Software (ELS) configurationstyle or Junos OS that does not support ELS.You can use Juniper Networks switches with VSTP and Cisco switches with PVST and Rapid-PVST in the samenetwork. Cisco supports a proprietary Per-VLAN Spanning Tree (PVST) protocol, which maintains a separatespanning tree instance per each VLAN. One Spanning Tree per VLAN allows fine grain load balancing but requiresmore BPDU CPU processing as the number of VLANs increases. PVST runs on Cisco proprietary ISL trunks whichis not supported by Juniper. Juniper switches only inter-operate with PVST and Rapid-PVST .TIP: Spanning-tree protocols all generate their own BPDUs. User bridge applications running ona PC can also generate BPDUs. If these BPDUs are picked up by STP applications running on theswitch, they can trigger STP miscalculations, and those miscalculations can lead to networkoutages. See Configuring BPDU Protection on Spanning Tree Interfaces.

12NOTE: If you are configuring an interface for any spanning tree protocol (STP, MSTP, RSTP, andVSTP), the interface all, vlan all, and vlan-group options are not available when you configure aninterface with the flexible-vlan-tagging family option.Switch and Router Spanning Tree Support and LimitationsNot all switches and routers support the exact same features and configurations. Known differences arelisted in Table 2 on page 12.Table 2: Spanning Tree Hardware ConsiderationsRouter or SwitchConsiderationsMX Series RoutersOnly MX Series routers can use the virtual-switch routing instance typeto isolate a LAN segment with its spanning-tree instance and toseparate its VLAN ID space. See "Configuring a Virtual Switch RoutingInstance on MX Series Routers" on page 20Tracing and global tracing are available on ACX and MX routers with theglobal "traceoptions" on page 387 statement—see "UnderstandingSpanning-Tree Protocol Trace Options" on page 286.Beginning with Release 14.1R1, these STP log enhancements aresupported on MX Series routers: Logging of information in the internal ring buffer about events likeSpanning Tree (such as STP, MSTP, RSTP, or VSTP) interface role orstate change without having to configure STP traceoptions. Capturing information as to what triggered the spanning-tree role orstate change.On MX and ACX routers, you can configure RSTP, MSTP, and VSTPinstance interfaces as edge ports for faster convergence than theoriginal STP version. Edge ports transition directly to the forwardingstate, and so the protocol does not need to wait for BPDUs to bereceived on edge ports.On an MX Series router running RSTP or MSTP in a provider network,you can enable provider bridge participation in the RSTP or MSTPinstance—see Understanding Provider Bridge Participation in RSTP orMSTP Instances.

13Table 2: Spanning Tree Hardware Considerations (Continued)Router or SwitchConsiderationsTIP: For 802.1ad provider bridge networks (stacked VLANs) on MX Series and M Series routers, single-taggedaccess ports and double-tagged trunk ports can co-exist in a single spanning tree context. In this mode, the VLANSpanning Tree Protocol (VSTP) can send and receive untagged Rapid Spanning Tree Protocol (RSTP) bridgeprotocol data units (BPDUs) on Gigabit Ethernet (ge), 10 -Gigabit Ethernet (xe), and ag

Sep 20, 2021 · Forcing RSTP or VSTP to Run as IEEE 802.1D STP \(CLI Procedure\) 89. Configuring MSTP Protocol. 90. Understanding MSTP. 90. Configuring MSTP on Switches. 94. Configuring Multiple Spanning Tree Protocol. 98. Configuring MSTP Instances on a Physical Interface. 102. Example: Configuring Network Regions for VLANs with MSTP on Switches . 104 .

Related Documents:

STP - Spanning Tree Protocol VLAN - Virtual Local Area Network Supported Spanning Tree Protocols Arista switches use Multiple Spanning Tree Protocol (MSTP/802.1s) by default. However, they also support Rapid Spanning Tree Protocol (RSTP/802.1w), as well as Rapid Per-VLAN Spanning Tree (Rapid-PVST) for vendor interoperability.File Size: 2MBPage Count: 36

Spanning Tree Protocol (STP) Page 6 Spanning Tree Protocols: STP, RSTP, and MSTP Spanning Tree Protocol (STP) STP uses the process described in Table 1 on page 4, to avoid loops. STP port states In STP mode, each switch port can be in one of five spanning tree states, and one of two

Spanning tree protocol ent ities transmit and receive BPDUs (Clause 14) to convey parameters used by RSTP and MSTP to calculate CST, CIST, and MSTI spanning trees. BPDUs also convey parameters that all the spanning tree protocols use to interoperate with

Civic Style - Marker Symbols Ü Star 4 û Street Light 1 ú Street Light 2 ý Tag g Taxi Æb Train Station Þ Tree 1 òñðTree 2 õôóTree 3 Ý Tree 4 d Truck ëWreck Tree, Columnar Tree, Columnar Trunk Tree, Columnar Crown @ Tree, Vase-Shaped A Tree, Vase-Shaped Trunk B Tree, Vase-Shaped Crown C Tree, Conical D Tree, Conical Trunk E Tree, Conical Crown F Tree, Globe-Shaped G Tree, Globe .

MSTP Multiple Spanning Tree Protocol PEP Provider edge port RSTP Rapid Spanning Tree Protocol SEFOS Sun Ethernet Fabric Operating System SST Single spanning tree STI Spanning tree instance S-VLAN Service VLAN TC Topology change VLAN Virtual

Fundamental Spanning-Tree Concepts The first important choice to make in the design of a data center network is the spanning-tree choice. It is beyond the scope of this document to describe the spanning-tree algorithms in detail. At the time of

STP –Spanning Tree Protocol indigoo.com Contents 1. Goal of STP: Loop-free topology for Ethernet networks 2. STP standards overview 3. IEEE 802.1D STP protocol 4. IEEE 802.1w RSTP Rapid STP 5. IEEE 802.1Q CST Common Spanning Tree 6. Cisco PVST and PVRST 7. IEEE 802.1s MST Multiple Spanning Tree Protocol 8. STP Pros and Cons

L2Switch2 (Catalyst 2960) 92 L3Switch1 (Catalyst 3560/3650/3750) 94 L2Switch1 (Catalyst 2960) 95 CHAPTER 11 Spanning Tree Protocol 97 Spanning Tree Protocol Definition 97 Enabling Spanning Tree Protocol 98 Changing the Spanning-Tree Mode 99 BPDU Guard (3650/9xxx Series) 99 Configuring th