Configuring BGP Signaling for VPLS

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 116 lists the commands discussed in this section to configure BGP signaling for VPLS.

Table 116: 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:

  1. Enable the BGP routing protocol on the PE router and specify the local AS; that is, the AS to which this BGP speaker belongs.
    host1(config)#router bgp 100

    The AS number identifies the PE router to other BGP routers.

  2. Configure the PE-to-PE BGP session by first adding an entry to the BGP neighbor table.
    host1(config-router)#neighbor 10.4.4.4 remote-as 100
  3. Use neighbor commands to specify the peers to which BGP advertises routes.

    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.

    host1(config-router)#neighbor 10.4.4.4 update-source loopback 0 host1(config-router)#neighbor 10.4.4.4 next-hop-self
  4. Create the L2VPN address family to configure the router to exchange layer 2 NLRI for all VPLS instances.
    host1(config-router)#address-family l2vpn signaling
  5. Activate the PE-to-PE session in the L2VPN address family by specifying neighbors that exchange routes from within the current address family.
    host1(config-router-af)#neighbor 10.4.4.4 activate
  6. Use neighbor commands to configure additional address family parameters for the session, then exit the address family.

    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.

    host1(config-router-af)#neighbor 10.4.4.4 next-hop-self host1(config-router-af)#exit-address-family
  7. Create the VPLS address family to configure the router to exchange layer 2 NLRI for each VPLS instance configured on the router.

    You must issue the address-family vpls command separately for each VPLS instance configured on the router.

    host1(config-router)#address-family vpls customer1 host1(config-router-af)#exit-address-family host1(config-router)#address-family vpls customer2

     

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 Configuring BGP Routing for information about configuring BGP.

See Configuring BGP-MPLS Applications for information about configuring BGP/MPLS VPNs.

Related Documentation