[Contents] [Prev] [Next] [Index] [Report an Error]

Configuring a VPLS Instance with BGP Signaling

You must enable a VPLS instance to isolate VPLS traffic from other network traffic. To configure, 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.

Note: 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.



[edit]
routing-instances;



instance-name {

instance-type vpls;        
  

interface ge-0/1/0.0;
route-distinguisher 10.245.14.218:1;
vrf-target target:11111:1;


protocols {


vpls {

site-range 10;



site greenPE1 {

site-identifier 1;
}


}


}


}

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:



[edit]
protocols {


bgp {


family l2vpn;

signaling;
}


}


}

[Contents] [Prev] [Next] [Index] [Report an Error]