Introduction to Configuring Layer 2 VPNs
To configure Layer 2 virtual private network (VPN) functionality, you must enable Layer 2 VPN support on the provider edge (PE) router. You must also configure PE routers to distribute routing information to the other PE routers in the VPN and configure the circuits between the PE routers and the customer edge (CE) routers.
Each Layer 2 VPN is configured under a routing instance
of type l2vpn. An l2vpn routing instance can
transparently carry Layer 3 traffic across the service provider’s
network. As with other routing instances, all logical interfaces belonging
to a Layer 2 VPN routing instance are listed under that instance.
The configuration of the CE routers is not relevant to the service provider. The CE routers need to provide only appropriate Layer 2 circuits (with appropriate circuit identifiers, such as data-link connection identifier [DLCI], virtual path identifier/virtual channel identifier [VPI/VCI], or virtual LAN [VLAN] ID) to send traffic to the PE router.
To configure Layer 2 VPNs, include the following statements:
On the EX9200 switches, replace encapsulation-type with the encapsulation statement.
description text; instance-type l2vpn; interface interface-name; route-distinguisher (as-number:id| ip-address:id); vrf-export [ policy-names ]; vrf-import [ policy-names ]; vrf-target { community; import community-name; export community-name; } protocols { l2vpn { (control-word | no-control-word); encapsulation-type type; site site-name { interface interface-name { description text; remote-site-id remote-site-id; } site-identifier identifier; site-preference preference-value { backup; primary; } } traceoptions { file filename <files number> <size size> <world-readable | no-world-readable>; flag flag <flag-modifier> <disable>; } } }
You can include these statements at the following hierarchy levels:
[edit routing-instances routing-instance-name][edit logical-systems logical-system-name routing-instances routing-instance-name]
For Layer 2 VPNs, only some of the statements in the [edit routing-instances] hierarchy are valid. For the full
hierarchy, see Junos OS Routing Protocols
Library.
In addition to these statements, you must configure MPLS label-switched paths (LSPs) between the PE routers, IBGP sessions between the PE routers, and an interior gateway protocol (IGP) on the PE and provider (P) routers. You must also configure the statements that are required for all types of VPN configuration.
By default, Layer 2 VPNs are disabled.
Many of the configuration procedures for Layer 2 VPNs are identical to the procedures for Layer 3 VPNs and virtual private LAN service (VPLS).