Virtual Private LAN Services
7210 SAS-X, R6 OS Services Guide Page 327
values. The VSI-ID value is generated from the MPLS router-ID. All of these parameters are
configurable and can be coded to suit requirements and build different topologies
Figure 44: BGP-AD CLI Command Tree
A helpful command displays the service information, the BGP parameters and the SDP bindings
in use. When the discovery process is completed successfully each endpoint will have an entry for
the service.
PE134># show service l2-route-table
When only one of the endpoints has an entry for the service in the l2-routing-table, it is most likely
a problem with the RT values used for import and export. This would most likely happen when
different import and export RT values are configured using a router policy or the route-target
command.
Service specific commands continue to be available to display service specific information,
including status.
PERs6# show service sdp-using
BGP AD advertises the VPLS-ID in the extended community attribute, VSI-ID in the NLRI and
the local PE ID in the BGP next hop. At the receiving PE, the VPLS-ID is compared against
locally provisioned information to determine whether the two PEs share a common VPLS. If it is
found that they do, the BGP information is used in the signaling phase.
PE134>config>service>vpls>bgp-ad#
[no] pw-template-bi* - Configure pw-template bind policy
[no] route-target - Configure route target
[no] shutdown - Administratively enable/disable BGP auto-discovery
vpls-id - Configure VPLS-ID
[no] vsi-export - VSI export route policies
vsi-id + Configure VSI-id
[no] vsi-import - VSI import route policies
To Next Page
Loading...
