Bulk Administration Of Layer 2 Features On Mx Series Routers; Bulk Configuration Of Vlans And Bridge Domains; Example: Configuring Vlan Translation With A Vlan Id List - Juniper JUNOS OS 10.4 Manual

CHAPTER 5
Bulk Administration of Layer 2 Features
on MX Series Routers

Bulk Configuration of VLANs and Bridge Domains

Related
Documentation

Example: Configuring VLAN Translation with a VLAN ID List

Copyright © 2012, Juniper Networks, Inc.
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
In some cases, service providers must deal with 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
bridge domain will have the form
by the configuration statement.
Ethernet Networking
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
In many cases, the VLAN identifiers on the frames of an interface's packets are not exactly
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
statement at the
[edit interfaces interface-name unit unit-number]
must also include the
family bridge
is only supported on trunk interfaces. The reverse translation takes place on egress. In
other words, if VLAN 200 is translated to 500 on ingress, VLAN 500 is translated to VLAN
200 on egress.
. The prefix and number are supplied
prefix-vlan-number
statement at the same level because VLAN translation
vlan-rewrite
hierarchy level. You
59