Supported Platforms
Related Documentation
- MX Series
- Bulk Configuration of VLANs and Bridge Domains
- Example: Configuring Multiple Bridge Domains with a VLAN ID List
- Additional Information
- Ethernet Networking Feature Guide for MX Series Routers
Example: Configuring VLAN Translation with a VLAN ID List
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 vlan-rewrite statement at the [edit interfaces interface-name unit unit-number] hierarchy level. You must also include the family bridge statement at the same level because VLAN translation 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 following example translates incoming trunk packets from VLAN identifier 200 to 500 and 201 to 501 (other valid VLAN identifiers are not affected):
 | Note: This example also translates frame VLANs from 500 to 200 and 501 to 201 on egress. |
Related Documentation
- MX Series
- Bulk Configuration of VLANs and Bridge Domains
- Example: Configuring Multiple Bridge Domains with a VLAN ID List
- Additional Information
- Ethernet Networking Feature Guide for MX Series Routers
Published: 2013-08-27
Supported Platforms
Related Documentation
- MX Series
- Bulk Configuration of VLANs and Bridge Domains
- Example: Configuring Multiple Bridge Domains with a VLAN ID List
- Additional Information
- Ethernet Networking Feature Guide for MX Series Routers
