Hi,
An update to the previous discussions.
Both solutions provided are working and valid configurations.
Below is sample config for 2 PEs:
PE1:
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
unit 192 {
encapsulation vlan-ccc;
vlan-id 192;
}
unit 193 {
encapsulation vlan-ccc;
vlan-id 193;
}
[edit]
root@PE1# show routing-instances L2VPN
instance-type l2vpn;
interface ge-0/0/5.192;
interface ge-0/0/5.193;
route-distinguisher 192.168.0.1:192;
vrf-target target:65001:192;
protocols {
l2vpn {
encapsulation-type ethernet-vlan;
site PE1 {
site-identifier 1;
interface ge-0/0/5.192 {
remote-site-id 3;
}
}
site PE1-1 {
site-identifier 2;
interface ge-0/0/5.193 {
remote-site-id 4;
}
}
}
}
-- VLAN Bundled interface solution:
root@PE1# show interfaces ge-0/0/6
vlan-tagging;
encapsulation extended-vlan-ccc;
unit 0 {
vlan-id-list 192-193;
}
[edit]
root@PE1# show routing-instances L2VPN-2
instance-type l2vpn;
interface ge-0/0/6.0;
route-distinguisher 192.168.0.1:195;
vrf-target target:65001:195;
protocols {
l2vpn {
encapsulation-type ethernet;
site CE2 {
site-identifier 2;
interface ge-0/0/6.0;
}
}
}
PE2:
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
unit 192 {
encapsulation vlan-ccc;
vlan-id 192;
}
unit 193 {
encapsulation vlan-ccc;
vlan-id 193;
}
[edit]
root@PE2# show routing-instances L2VPN
instance-type l2vpn;
interface ge-0/0/5.192;
interface ge-0/0/5.193;
route-distinguisher 192.168.0.2:192;
vrf-target target:65001:192;
protocols {
l2vpn {
encapsulation-type ethernet-vlan;
site PE2 {
site-identifier 3;
interface ge-0/0/5.192 {
remote-site-id 1;
}
}
site PE2-1 {
site-identifier 4;
interface ge-0/0/5.193 {
remote-site-id 2;
}
}
}
}
--- VLAN Bundled interface solution:
root@PE2# show interfaces ge-0/0/6
vlan-tagging;
encapsulation extended-vlan-ccc;
unit 0 {
vlan-id-list 192-193;
}
[edit]
root@PE2# show routing-instances L2VPN-2
instance-type l2vpn;
interface ge-0/0/6.0;
route-distinguisher 192.168.0.2:195;
vrf-target target:65001:195;
protocols {
l2vpn {
encapsulation-type ethernet;
site CE1 {
site-identifier 1;
interface ge-0/0/6.0;
}
}
}
Results:
Instance: L2VPN
Local site: PE2 (3)
connection-site Type St Time last up # Up trans
PE2-1 (4) loc OR
1 rmt Up Aug 2 08:00:31 2016 1
Remote PE: 192.168.0.1, Negotiated control-word: Yes (Null)
Incoming label: 800000, Outgoing label: 800000
Local interface: ge-0/0/5.192, Status: Up, Encapsulation: VLAN
2 rmt OR
Local site: PE2-1 (4)
connection-site Type St Time last up # Up trans
PE2 (3) loc OR
1 rmt CN
2 rmt Up Aug 2 08:00:31 2016 1
Remote PE: 192.168.0.1, Negotiated control-word: Yes (Null)
Incoming label: 800003, Outgoing label: 800003
Local interface: ge-0/0/5.193, Status: Up, Encapsulation: VLAN
Instance: L2VPN-2
Local site: CE1 (1)
connection-site Type St Time last up # Up trans
2 rmt Up Aug 2 08:12:22 2016 1
Remote PE: 192.168.0.1, Negotiated control-word: Yes (Null)
Incoming label: 800013, Outgoing label: 800008
Local interface: ge-0/0/6.0, Status: Up, Encapsulation: ETHERNET
________________________________________________________________________________________________
I know that L2VPN is a point-to-point connection, however, what I miss here is the endpoints of the P2P L2VPN. For example, will the site referenced under the [protocol l2vpn] stanza is the endpoint? or, the individiual interface under the site itself?
My topology is I have 1 Hub and 2x Spokes, for every spoke the hub will have 2 VLAN interfaces (one for data traffic and the other one is for voice).
So, I would ideally imagine that I need 4x VLAN interfaces under Site1 (HUB) and 2x VLAN interfaces under Site2 (Spoke1) and 2x VLAN interfaces under Site3 (Spoke3).
Is this the correct analogy?
_________________________________________________________________________________________________
For BGP L2VPNS, the endpoint is discovered from the vrf:targets [route-target extended community] which is what enables auto-discovery through advertisement of L2VPN NLRIs.
For your scenario, you could be using only 2 vlans in a hub-and-spoke VPLS that restricts connectivity only between hub and spokes [i.e no spoke-spoke connectivity] using site-ids and site-range:
Cheers,
Ashvin