This section describes one way to configure BGP signaling for VPLS, but does not provide complete details about configuring BGP and BGP/MPLS VPNs.
Table 1 lists the commands discussed in this section to configure BGP signaling for VPLS.
Table 1: Commands to Configure BGP Signaling for VPLS
address-family l2vpn | neighbor next-hop-self |
address-family vpls | neighbor remote-as |
exit-address-family | neighbor send-community |
ip router-id | neighbor update-source |
neighbor activate | router bgp |
To configure BGP signaling for VPLS on the PE router:
The AS number identifies the PE router to other BGP routers.
This example configures only the update-source and next-hop-self attributes. The update-source attribute allows the BGP session to use the IP address of a specific operational interface as the update source address for TCP connections. the next-hop-self attribute forces the BGP speaker to report itself as the next hop for an advertised route that it learned from a neighbor.
This example configures only the next-hop-self attribute, forcing the BGP speaker to report itself as the next hop for an advertised route that it learned from a neighbor.
You must issue the address-family vpls command separately for each VPLS instance configured on the router.
After you configure MPLS LSPs and BGP signaling, the router automatically generates a VPLS virtual core interface for each VPLS instance. The VPLS virtual core interface represents all of the MPLS tunnels from the router to the remote VE device.
See Unresolved xref for information about configuring BGP.
See Unresolved xref for information about configuring BGP/MPLS VPNs.