Juniper Networks
Log in
|
How to Buy
|
Contact Us
|
United States (Change)
Choose Country
Close

Choose Country

North America

  • United States

Europe

  • Deutschland - Germany
  • España - Spain
  • France
  • Italia - Italy
  • Россия - Russia
  • United Kingdom

Asia Pacific

  • Asean Region (Vietnam, Indonesia, Singapore, Malaysia)
  • Australia
  • 中国 - China
  • India
  • 日本 - Japan
  • 대한민국 - Korea
  • 台灣 - Taiwan
Solutions
Products & Services
Company
Partners
Support
Education
Community
Security Intelligence Center

Technical Documentation

Technical Documentation
 
CLI Explorer New
 
Content Explorer New
 
Documentation Help New
 
Enterprise MIBs
 
EOL Documentation
 
Feature Explorer Login required New
 
Glossary
 
Portable Libraries
 
Home > Support > Technical Documentation > Junos OS > Example Step: Configuring Spanning Tree Protocols
Print
Rate and give feedback:  Feedback Received. Thank You!
Rate and give feedback: 
Close
This document helped resolve my issue.  Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  
E-mail: 
Submitting...
 

Related Documentation

  • MX Series
  • Layer 2 Features for a Bridging Environment
  • Example Roadmap: Configuring a Basic Bridge Domain Environment
  • Example Step: Configuring Interfaces and VLAN Tags
  • Example Step: Configuring Bridge Domains
  • Example Step: Configuring Integrated Bridging and Routing
  • Additional Information
  • Ethernet Networking
 

Example Step: Configuring Spanning Tree Protocols

Configure the Spanning Tree Protocol on all three routers. This is necessary to avoid the potential bridging loop formed by the triangular architecture of the routers. MSTP is configured on the three routers so the set of VLANs has an independent, loop-free topology. The Layer 2 traffic can be load-shared over 65 independent paths (64 Multiple Spanning Tree Instances [MSTIs] and one Common and Internal Spanning Tree [CIST]), each spanning a set of VLANs. The configuration names, revision level, and VLAN-to-MSTI mapping must match in order to utilize the load-sharing capabilities of MSTP (otherwise, each router will be in a different region).

To configure the Spanning Tree Protocol on all three routers:

  1. Configure MSTP on Router 1:

    [edit]
    protocols {mstp {configuration-name mstp-for-R1-2-3; # The names must match to be in the same regionrevision-level 3; # The revision levels must matchbridge-priority 0; # This bridge acts as root bridge for VLAN 100 and 200interface ae1;interface ae2;msti 1 {vlan100; # This VLAN corresponds to MSTP instance 1}msti 2 {vlan200; # This VLAN corresponds to MSTP instance 2}}}
  2. Configure MSTP on Router 2:

    [edit]
    protocols {mstp {configuration-name mstp-for-R1-2-3; # The names must match to be in the same regionrevision-level 3; # The revision levels must matchinterface ae1;interface ae3;msti 1 {vlan100; # This VLAN corresponds to MSTP instance 1bridge-priority 4096; # This bridge acts as VLAN 100 designated bridge on                              # the R2-R3 segment}msti 2 {vlan200; # This VLAN corresponds to MSTP instance 2}}}
  3. Configure MSTP on Router 3:

    [edit]
    protocols {mstp {configuration-name mstp-for-R1-2-3; # The names must match to be in the same regionrevision-level 3; # The revision levels must matchinterface ae2;interface ae3;msti 1 {vlan100; # This VLAN corresponds to MSTP instance 1}msti 2 {vlan200; # This VLAN corresponds to MSTP instance 2bridge-priority 4096; # This bridge acts as VLAN 200 designated bridge on                              # the R2-R3 segment}}}

As a result of this configuration, VLAN 100 and VLAN 200 share physical links, but have different designated ports, root ports, and alternate ports on the three different routers. The designated, root, and alternate ports for the two VLANs on the three routers are shown in Figure 1.

Figure 1: Designated, Root, and Alternate Ports

Designated, Root, and Alternate
Ports
 

Related Documentation

  • MX Series
  • Layer 2 Features for a Bridging Environment
  • Example Roadmap: Configuring a Basic Bridge Domain Environment
  • Example Step: Configuring Interfaces and VLAN Tags
  • Example Step: Configuring Bridge Domains
  • Example Step: Configuring Integrated Bridging and Routing
  • Additional Information
  • Ethernet Networking
 

Published: 2013-02-13

 
  • About Juniper
  • Investor Relations
  • Press Releases
  • Newsletters
  • Juniper Offices
  • Green Networking
  • Resources
  • How to Buy
  • Partner Locator
  • Image Library
  • Visio Templates
  • Security Center
  • Community
  • Forums
  • Blogs
  • Junos Central
  • Social Media
  • Developers
  • Support
  • Technical Documentation
  • Knowledge Base (KB)
  • Software Downloads
  • Product Licensing
  • Contact Support
Site Map / RSS Feeds / Careers / Accessibility / Feedback / Privacy & Policy / Legal Notices
Copyright© 1999-2013 Juniper Networks, Inc. All rights reserved.
Help
|
My Account
|
Log Out