Technical Documentation
Related Documentation
- MX Series
- Packet Flow Through a Bridged Network with Normalized VLANs
- Configuring a Normalized VLAN for Translation or Tagging
- Configuring Learning Domains for VLAN IDs Bound to Logical Interfaces
- Example: Configuring a Provider Bridge Network with Normalized VLAN Tags
- Example: Configuring a Provider VPLS Network with Normalized VLAN Tags
- Example: Configuring One VPLS Instance for Several VLANs
- Additional Information
- Ethernet Networking
VLANs Within a Bridge Domain or VPLS Instance
A packet received on a physical port is only accepted for processing if the VLAN tags of the received packet match the VLAN tags associated with one of the logical interfaces configured on the physical port. The VLAN tags of the received packet are translated only if they are different than the normalized VLAN tags. For the translation case, the VLAN identifier tags specify the normalized VLAN. For this case, the terms “learn VLAN” and “normalized VLAN” can be used interchangeably.
You can specify the normalized VLAN using one of the following conditions:
- The VLAN identifier is determined explicitly by configuration
- The VLAN identifier is specified as “none,” meaning the VLAN tags are not translated or generated
- The inner and outer VLAN identifier tags are both determined explicitly by configuration
Related Documentation
- MX Series
- Packet Flow Through a Bridged Network with Normalized VLANs
- Configuring a Normalized VLAN for Translation or Tagging
- Configuring Learning Domains for VLAN IDs Bound to Logical Interfaces
- Example: Configuring a Provider Bridge Network with Normalized VLAN Tags
- Example: Configuring a Provider VPLS Network with Normalized VLAN Tags
- Example: Configuring One VPLS Instance for Several VLANs
- Additional Information
- Ethernet Networking
Published: 2011-11-01
Copyright© 1999-2012 Juniper Networks, Inc. All rights reserved.
