Filter
Top Products
CHAPTER 5
Bulk Administration of Layer 2 Features
on MX Series Routers
•
Bulk Configuration of VLANs and Bridge Domains on page 59
•
Example: Configuring VLAN Translation with a VLAN ID List on page 59
•
Example: Configuring Multiple Bridge Domains with a VLAN ID List on page 60
Bulk Configuration of VLANs and Bridge Domains
In some cases, serviceproviders must dealwith thousands of bridge domains on a single
switch. By default the router does not create more than one bridge domain. The
configuration of even several hundred bridge domains one at a time can be a burden.
However, you can configure multiple bridge domains with only one statement. Each
bridgedomain will have the form prefix-vlan-number.Theprefix andnumber are supplied
by the configuration statement.
Related
Documentation
MX Series Ethernet Services Routers Solutions Page•
• Example: Configuring VLAN Translation with a VLAN ID List on page 59
• Example: Configuring Multiple Bridge Domains with a VLAN ID List on page 60
Example: Configuring VLAN Translation with a VLAN ID List
In many cases,the VLAN identifiers onthe framesof an interface’spacketsare notexactly
correct. VLAN translation, or VLAN rewrite, allows you to configure bidirectional VLAN
identifier translation with a list on frames arriving on and leaving from a logical interface.
This lets you use unique VLAN identifiers internally and maintain legacy VLAN identifiers
on logical interfaces.
To perform VLAN translation on the packets on a trunk interface, insert the vlan-rewrite
statement at the [edit interfaces interface-name unit unit-number] hierarchy level. You
mustalso includethe familybridgestatement atthe samelevelbecauseVLAN translation
is only supported on trunk interfaces. The reverse translation takes place on egress. In
other words, ifVLAN 200 istranslatedto500 oningress, VLAN500 istranslatedto VLAN
200 on egress.
59Copyright © 2010, Juniper Networks, Inc.