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

Download Software
Research a Problem Login required
Case Management Login required
Contract & Product Management Login required
Technical Documentation
Documentation Archive
Enterprise MIBs
File Format Help
Glossary
Portable Libraries
End-of-Life Products
Contact Support
Guidelines and Policies
Security Resources
Home > Support > Technical Documentation > Junos OS > Example: Configuring Multiple Bridge Domains with a VLAN ID List
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
  • Bulk Configuration of VLANs and Bridge Domains
  • Example: Configuring VLAN Translation with a VLAN ID List
  • Additional Information
  • Ethernet Networking
 

Example: Configuring Multiple Bridge Domains with a VLAN ID List

To configure multiple bridge domains with one statement, include the vlan-id-list statement at the [edit bridge-domains] hierarchy level.

The following example automatically configures 4093 bridge domains named sales-vlan-2 through sales-vlan-4094:

[edit]bridge-domains {sales { # This is the prefixvlan-id-list [ 2–4096 ]; # These are the numbers}}

You can configure these bridge domains in a virtual switch routing instance. However, if a VLAN identifier is already part of a VLAN identifier list in a bridge domain under a routing instance, then you cannot configure an explicit bridge domain with that VLAN identifier. In other words. there can be no overlap between a VLAN identifier list and another VLAN identifier configuration.

The following example removes the VLAN identifier 5 from the original VLAN list (vlan-id-list [ 1–10 ]) and configures the bridge domain explicitly:

[edit routing-instance rtg-inst-10]instance-type virtual-switch;interface ge-7/3/0.0;bridge-domains {bd-vlan–5 {vlan-id 5;}bd {vlan-id [ 1–4 6–10 ];}}

If a VLAN identifier is already part of a VLAN identifier list in a bridge domain under a routing instance, then you must delete the VLAN identifier from the list before you can configure an explicit or “regular” bridge domain. Also, the explicit bridge domain will not perform properly unless it has the same name as the bridge domain in the VLAN identifier list.

In other words, if sales-vlan-100 was part of a bridge domain VLAN list and you wish to configure it explicitly, you must use the same naming convention:

[edit]bridge-domains {sales-vlan-100 { # You must use this name explicitlyvlan-id 100;}}

The following limitations apply to automatic bridge domain configuration:

  • Only one vlan-id-list statement is allowed in a routing instance.
  • Bridge options are not supported with the vlan-id-list statement.
  • Only trunk interfaces are supported.
  • There is no support for integrated routing and bridging (IRB).

You display the status and other parameters for automatic bridge domains configured with the vlan-id-list statement using the same show l2-learning instance command as used for individually configured bridge domains.

 

Related Documentation

  • MX Series
  • Bulk Configuration of VLANs and Bridge Domains
  • Example: Configuring VLAN Translation with a VLAN ID List
  • Additional Information
  • Ethernet Networking
 

Published: 2011-11-01

 
  • About Juniper
  • The New Network
  • Investor Relations
  • Press Releases
  • Newsletters
  • Juniper Offices
  • Resources
  • How to Buy
  • Partner Locator
  • Image Library
  • Visio Templates
  • Security Center
  • Community
  • Forums
  • Blogs
  • Junos Central
  • Social Media
  • 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-2012 Juniper Networks, Inc. All rights reserved.
Help
|
My Account
|
Log Out