Enabling the BGP Peer to Exchange VPLS Information

Context

BGP VPLS shares the TCP connection with the common BGP protocol. Therefore, most BGP VPLS configurations are the same as the configurations of the common BGP protocol. Nevertheless, VPLS label blocks need to be exchanged in BGP VPLS. Therefore, you need to enable peers to exchange VPLS label blocks in the BGP VPLS address family view.

Perform the following steps on the PEs of the two ends of the PW:

Procedure

Run system-view
The system view is displayed.
Run bgp { as-number-plain | as-number-dot }
The BGP view is displayed.
Run peer ipv4-address as-number as-number
The BGP peer is configured.
Run peer ipv4-address connect-interface loopback interface-number
The interface used to set up the TCP connection is specified.

To improve reliability, on the PE, the local loopback interface is generally specified as the interface to set up the TCP connection.
Configure the Kompella VPLS signaling capability:
Kompella VPLS can use either the BGP-VPLS address family or the BGP-L2VPN-AD address family. You can use either of the following methods to configure the Kompella VPLS signaling capability. Method 1 is recommended.
- Method 1
  1. Run l2vpn-ad-family
    
    The L2VPN-AD address family view is displayed.
  2. Run peer ipv4-address enable
    
    A peer is specified, and the function to exchange route information with the specified peer is enabled.
    
    After you specify a peer in the L2VPN-AD address family view, the BGP AD signaling capability is enabled by default.
  3. Run signaling vpls or peer ip-address signaling vpls
    
    The Kompella VPLS signaling capability is enabled.
  4. (Optional) Run signaling vpls-ad disable
    
    The BGP AD signaling capability is disabled.
- Method 2
  1. Run vpls-family
    
    The BGP-VPLS address family view is displayed.
  2. Run peer ipv4-address enable
    
    A peer is specified, and the function to exchange route information with the specified peer is enabled.