Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Configuring a Normalized VLAN for Translation or Tagging

    This topic provides configuration and operational information to help you manipulate virtual local area networks (VLANs) within a bridge domain or a virtual private LAN service (VPLS) instance. The VPLS configuration is not covered in this topic. For more information about configuring Ethernet pseudowires as part of VPLS, see the Junos OS.

    Note: This topic is not intended as a troubleshooting guide. However, you can use it with a broader troubleshooting strategy to identify Juniper Networks MX Series 3D Universal Edge Router network problems.

    The manipulation of VLANs within a bridge domain or a VPLS instance can be done in several ways:

    • By using the vlan-map statements at the [edit interfaces] hierarchy level. This chapter does not use vlan-map. For more information about VLAN maps, see the Junos OS Network Interfaces Library for Routing Devices.
    • By using vlan-id statements within a bridge domain or VPLS instance hierarchy. This method is used in the configuration in this chapter.

    The vlan-id and vlan-tags statements under the bridge domain or VPLS routing instance are used to:

    • Translate (normalize) received VLAN tags, or
    • Implicitly create multiple learning domains, each with a “learn” VLAN.

    The use of a VLAN map or a normalized VLAN is optional.

    Note: You cannot use vlan-map when configuring a normalized VLAN.

    This section discusses the following topics:

    Implicit VLAN Translation to a Normalized VLAN

    The VLAN tags of a received packet are compared with the normalized VLAN tags specified with either the vlan-id or vlan-tags statements. If the VLAN tags of the received packet are different from the normalized VLAN tags, then appropriate VLAN tag operations (such as push-push, pop-pop, pop-swap, swap-swap, swap, and others) are implicitly made to convert the received VLAN tags to the normalized VLAN tags. For more information about these operations, see the Junos OS Routing Protocols Library.

    Then, the source MAC address of a received packet is learned based on the normalized VLAN configuration.

    For output packets, if the VLAN tags associated with an egress logical interface do not match the normalized VLAN tags within the packet, then appropriate VLAN tag operations (such as push-push, pop-pop, pop-swap, swap-swap, swap, and others) are implicitly made to convert the normalized VLAN tags to the VLAN tags for the egress logical interface. For more information about these operations, see the Junos OS Routing Protocols Library.

    Sending Tagged or Untagged Packets over VPLS Virtual Interfaces

    If the packets sent over the VPLS virtual interfaces (vt- or lsi- interfaces) need to be tagged by the normalized VLAN, use one of the following configuration statements:

    • vlan-id vlan-number—Tags all packets sent over the VPLS virtual interface with the configured vlan-number. For an example of this configuration, see Example: Configuring One VPLS Instance for Several VLANs.
    • vlan-tags outer outer-vlan-number inner inner-vlan-number—Tags all packets sent over the VPLS virtual interfaces with the specified inner and outer VLAN tags.

    If the incoming VLAN tags identifying a Layer 2 logical interface are removed when packets are sent over VPLS virtual interfaces, use the vlan-id none statement.

    Note: Even when the vlan-id none statement is configured, the packets can still contain other customer VLAN tags.

    Configuring a Normalized VLAN

    The following factors are important when configuring a normalized VLAN:

    • Use either the vlan-id vlan-number statement (to tag all packets with one normalized VLAN tag) or the vlan-tags outer outer-vlan-number inner inner-vlan-number statement (to tag all packets with the normalized outer and inner VLAN tags) if you want to tag packets sent onto the VPLS pseudowires.
    • Use the vlan-id none statement to remove the incoming VLAN tags identifying a Layer 2 logical interface when packets are sent over VPLS pseudowires. This statement is also used to configure shared VLAN learning.

      Note: The outgoing packets can still contain customer VLAN tags.

    • If integrated routing and bridging (IRB) is configured for a bridge domain or a VPLS routing instance, then you must configure a normalized VLAN using one of the following statements:

      • vlan-id vlan-number
      • vlan-id none
      • vlan-tags outer outer-vlan-number inner inner-vlan-number
    • Use the vlan-id all statement to configure bridging for several VLANS with minimal amount of configuration and switch resources. For an example of this configuration, see Example: Configuring One VPLS Instance for Several VLANs.

    Modified: 2017-09-13