I did some lab trying to understand this. What I do not understand is the following:
root@PE1# show routing-instances | display set
set routing-instances CustA instance-type l2vpn
set routing-instances CustA interface ge-0/0/1.0
set routing-instances CustA interface ge-0/0/2.521
set routing-instances CustA interface ge-0/0/2.522
set routing-instances CustA interface ge-0/0/3.531
set routing-instances CustA interface ge-0/0/3.532
set routing-instances CustA route-distinguisher 192.168.100.1:1
set routing-instances CustA vrf-target target:65100:65100
set routing-instances CustA protocols l2vpn encapsulation-type ethernet-vlan
set routing-instances CustA protocols l2vpn site Local-site-1 site-identifier 1
set routing-instances CustA protocols l2vpn site Local-site-1 interface ge-0/0/2.521
set routing-instances CustA protocols l2vpn site Local-site-1 interface ge-0/0/2.522
set routing-instances CustA protocols l2vpn site Local-site-1 interface ge-0/0/3.531
set routing-instances CustA protocols l2vpn site Local-site-6 site-identifier 6
set routing-instances CustA protocols l2vpn site Local-site-6 interface ge-0/0/3.532 remote-site-id 7
Local-site-1 has not remote-site-id configured, it is mapped to remote-site-id 2,3,4.
Can Local-site-6 use auto-provision to save the remote-site-id configuration ? In my lab, if I do not configure remote-site-id, it does not work.
Also I remember jl2v training mentioning auto-provision only works for local site-identifier is 1, otherwise, you have to configure remote-site-id, I will double check.
thanks a lot for your coaching !!
Original Message:
Sent: 11-20-2020 06:38
From: Elchin Khudiyev
Subject: L2 VPN site identifier auto provision questions
Hi, you can check https://tools.ietf.org/html/draft-ietf-l2vpn-signaling-08 for explanation of L2VPN signalling where Section 3.2.2.1 explains BGP-based auto-discovery process:
In order to use BGP-based auto-discovery, there must be at least one globally unique identifier associated with a VPLS, and each such identifier must be encodable as an 8-byte Route Distinguisher (RD). Any method of assigning one or more unique identifiers to a VPLS and encoding each of them as an RD (using the encoding techniques of [RFC4364]) will do.
There is no restriction for site-identifier required for auto-discovery process. This value is simply represents numerical identifier for the Layer 2 VPN site, which can be any number from 1 through 65,534.
From JL2v materials you can also find the following explanation:
Each interface listed under the l2vpn portion of a Layer 2 VPN VRF is associated with a remote site. Each subsequent interface inherits by default a site association that is one higher than the previous interface. The default inheritance value is increased by two when an interface's default inheritance would cause it to be associated with the PE router's local site identifier.
------------------------------
Regards,
Elchin
Original Message:
Sent: 11-18-2020 12:20
From: Unknown User
Subject: L2 VPN site identifier auto provision questions
I am taking JL2v training. Need some assistance to understand site identifier auto provision