Example: Configuring a Layer 2 VPN Routing Instance on a VLAN-Bundled Logical Interface
The following configuration shows that the single-tag
logical interface ge-1/0/5.0 bundles a list of VLAN IDs,
and the logical interface ge-1/1/1.0 supports IPv4 traffic
using IP address 10.30.1.130 and can participate in an MPLS path.
[edit interfaces]
ge-1/0/5 {
vlan-tagging;
encapsulation extended-vlan-ccc;
unit 0 { # VLAN-bundled logical interface
vlan-id-list [513 516 520-525];
}
}
ge-1/1/1 {
unit 0 {
family inet {
address 10.30.1.1/30;
}
family mpls;
}
}
The following configuration shows the type of traffic supported on the Layer 2 VPN routing instance:
[edit protocols]
rsvp {
interface all;
interface lo0.0;
}
mpls {
label-switched-path lsp {
to 10.255.69.128;
}
interface all;
}
bgp {
group g1 {
type internal;
local-address 10.255.69.96;
family l2vpn {
signaling;
}
neighbor 10.255.69.128;
}
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface lo0.0;
interface ge-1/1/1.0;
}
}
The following configuration shows that the VLAN-bundled logical interface is the interface over which VPN traffic travels to the CE router and handles traffic for a CCC to which the VPN connects.
[edit routing-instances]
red {
instance-type l2vpn;
interface ge-1/0/5.0; # VLAN-bundled logical interface
route-distinguisher 10.255.69.96:100;
vrf-target target:1:1;
protocols {
l2vpn {
encapsulation-type ethernet; # For single-tag VLAN logical interface
site CE_ultima {
site-identifier 1;
interface ge-1/0/5.0;
}
}
}
}
Because the VLAN-bundled logical interface supports single-tag frames, Ethernet is the Layer 2 protocol used to encapsulate incoming traffic. Although the connection spans multiple VLANs, the VLANs are bundled and therefore can be encapsulated as a single VLAN.
However, with Ethernet encapsulation, the circuit signal processing does not check that the VLAN ID list is the same at both ends of the CCC connection.