Configuring a VPLS Instance with BGP Signaling
Like other Layer 2 VPNs, you must enable a VPLS instance to isolate VPLS traffic from other network traffic. An important element of a VPLS instance is the signaling protocol. You can configure BGP signaling, LDP signaling, or both BGP and LDP signaling in a VPLS instance.
You must enable a VPLS instance to isolate VPLS traffic from other network traffic. To enable a VPLS instance, include the instance-type vpls statement at the [edit routing-instances instance-name] hierarchy level.
Within the instance, you can define the maximum number of sites that can participate in this VPLS instance, a local site name, and a local site identifier. To configure the maximum number of sites, include the site-range statement at the [edit routing-instances instance-name protocols vpls] hierarchy level. The maximum number of sites is 65,535.
The site ID must be less than the site range. If you specify a site ID that is greater than the site range, your connections do not come up, even though the commit operation succeeds.
To configure a site name, include the site statement at the [edit routing-instances instance-name protocols vpls] hierarchy level. To configure the site ID, include the site-identifier statement at the [edit routing-instances instance-name protocols vpls site name] hierarchy level.
To complete the configuration, you must configure the Layer 2 VPN family for BGP by including the signaling statement at the [edit protocols bgp family l2vpn] hierarchy level: