Configuration of p2mp L2 VPN with over provisioning

The following configuration demonstrates a point to multipoint L2 VPN that connects to two remote sites, with over provisioning configured for two additional sites. The local site is represented by the site-identifier and each remote site is sequentially assigned a site-id in the order that the attachment circuit interfaces are configured within the VPN.

The remote site allocation avoids additional local site configuration so the sequential allocation is not duplicated. This process happens with the remote sites, which always begin the allocation from 1 and miss out their local site whilst allocating sub interfaces to site ids.

Additional interfaces representing other sites in the VPN are over provisioned in preparation for the deployment of those sites which are configured with the respective ordered site-ids. If all interfaces are ordered correctly the over provisioning will work and sites and interfaces will be allocated correctly.

routing-instances vpn-a {
     instance-type l2vpn;
     interface ge-0/0/0.512;
     interface ge-0/0/0.513;
     interface ge-0/0/0.514;
     interface ge-0/0/0.515;
     route-distinguisher 172.25.0.1:100;
     vrf-target target:65001:100;
     protocols {
          l2vpn {
               encapsulation-type ethernet-vlan;
               site CE-A {
                    site-identifier 1;
                    interface ge-0/0/0.512;
                    interface ge-0/0/0.513;
                    interface ge-0/0/0.514;
                    interface ge-0/0/0.515;
                    }
               }
          }
     }
}
The configuration below shows how the site 2 would be configured to connect the logical .512 circuit back to site 1.
routing-instances vpn-a {
     instance-type l2vpn;
     interface ge-0/0/0.512;
     route-distinguisher 172.25.0.2:100;
     vrf-target target:65001:100;
     protocols {
          l2vpn {
               encapsulation-type ethernet-vlan;
               site CE-B {
                    site-identifier 2;
                    interface ge-0/0/0.512;
                    }
               }
          }
     }
}

The interface must be configured with vlan-ccc encapsulation at both the physical and logical levels. When using CCC encapsulation VLAN ids must be above 512 to support this encapsulation type for L2 VPN.

interfaces {
ge-0/0/1.10 {
vlan-tagging;
encapsulation vlan-ccc;
unit 10 {
encapsulation vlan-ccc;
vlan-id 10;
family inet {
address {
10.100.0.1/30;
}
}
}
}
}

routing-instances {
L2VPN_A     {
instance-type l2vpn;
interface ge-0/0/1.10;
vrf-target target:65001:100;
protocols {
l2vpn {
encapsulation-type vlan-ccc;
site-name CE_A {
site-identifier 1;
interface ge-0/0/1.10;
}
}
}
}
}