Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Announcement: Try the Ask AI chatbot for answers to your technical questions about Juniper products and solutions.

close
header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Ethernet Switching User Guide
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Configuring a Layer 2 VPN Routing Instance on a VLAN-Bundled Logical Interface

date_range 20-Dec-24

This topic describes how to configure a Layer 2 VPN routing instance on a logical interface bound to a list of VLAN IDs.

Configuring a VLAN-Bundled Logical Interface to Support a Layer 2 VPN Routing Instance

To configure a VLAN-bundled logical interface, specify the list of VLAN IDs by including the vlan-id-list statement or the vlan-tags statement on a provider edge (PE) router:

content_copy zoom_out_map
interfaces {
    ethernet-interface-name {
        vlan-tagging; # Support single- or dual-tag logical interfaces 
        flexible-vlan-tagging; # Support mixed tagging
        encapsulation (extended-vlan-ccc | flexible-ethernet-services);
        unit logical-unit-number {
            vlan-id-list [vlan-id vlan-idvlan-id]; # For single-tag
            vlan-tags outer <tpid.>vlan-id inner-list [vlan-id vlan-idvlan-id]; # For dual-tag
        }
        . . .
    }
}

You can include the statements at the following hierarchy levels:

  • [edit]

  • [edit logical-systems logical-system-name]

Specifying the Interface Over Which VPN Traffic Travels to the CE Router

To configure a Layer 2 VPN routing instance on a PE router, include the instance-type statement and specify the value l2vpn. To specify an interface connected to the router, include the interface statement and specify the VLAN-bundled logical interface:

content_copy zoom_out_map
instance-type l2vpn;
interface logical-interface-name;

You can include the statements at the following hierarchy levels:

  • [edit routing-instances routing-instance-name]

  • [edit logical-systems logical-system-name routing-instances routing-instance-name]

Specifying the Interface to Handle Traffic for a CCC

To configure the VLAN-bundled logical interface as the interface to handle traffic for a circuit connected to the Layer 2 VPN routing instance, include the following statements:

content_copy zoom_out_map
protocols {
    l2vpn {
        (control-word | no-control-word);
        encapsulation-type (ethernet | ethernet-vlan); 
        site site-name {
            site-identifier identifier;
            interface logical-interface-name { # VLAN-bundled logical interface
                . . . interface-options . . .
            }
        }
    }
}

You can include the statements at the same hierarchy level at which you include the instance-type l2vpn and interface logical-interface-name statements:

  • [edit routing-instances routing-instance-name]

  • [edit logical-systems logical-system-name routing-instances routing-instance-name]

To enable a Layer 2 VPN routing instance on a PE router, include the l2vpn statement. For more information, see the Junos OS VPNs Library for Routing Devices.

The encapsulation-type statement specifies the Layer 2 protocol used for traffic from the customer edge (CE) router. If the Layer 2 VPN routing instance is being connected to a single-tag Layer 2 circuit, specify ethernet as the encapsulation type. If the Layer 2 VPN routing instance is being connected to a dual-tag Layer 2 circuit, specify ethernet-vlan as the encapsulation type.

To specify the interface to handle traffic for a circuit connected to the Layer 2 VPN routing instance, include the interface statement and specify the VLAN-bundled logical interface.

footer-navigation