Configuring a VPLS Service with CLI
Page 326 7210 SAS-X, R6 OS Services Guide
Configuring BGP Auto-Discovery
This section provides important information to explain the different configuration options used to
populate the required BGP AD and generate the LDP generalized pseudowire-ID FEC fields.
There are a large number of configuration options that are available with the this feature. Not all
these configurations option are required to start using BGP AD. At the end of this section, it will
be apparent that a very simple configuration will automatically generate the required values used
by BGP and LDP. In most cases, deployments will provide full mesh connectivity between all
nodes across a VPLS instance. However, capabilities are available to influence the topology and
build hierarchies or hub and spoke models.
Configuration Steps
Using Figure 43, assume PE6 was previously configured with VPLS 100 as indicated by the
configurations lines in the upper right. The BGP AD process will commence after PE134 is
configured with the VPLS 100 instance as shown in the upper left. This shows a very basic and
simple BGP AD configuration. The minimum requirement for enabling BGP AD on a VPLS
instance is configuring the VPLS-ID and point to a pseudowire template.
Figure 43: BGP AD Configuration Example
In many cases, VPLS connectivity is based on a pseudowire mesh. To reduce the configuration
requirement, the BGP values can be automatically generated using the VPLS-ID and the MPLS
router-ID. By default, the lower six bytes of the VPLS-ID are used to generate the RD and the RT
OSSG247
S-PE-1
S-PE-2
spoke-sdp 1:100
spoke-sdp 2:200 spoke-sdp 4:400
spoke-sdp 3:300
sap 1/2/1:100
sap 1/1/1:100
spoke-sdp 6:600
S-PE-3
T-PE-1 T-PE-2
To Next Page
Loading...
