Enabling BGP Peers to Exchange VPLS Information

Context

BGP AD VPLS shares a TCP connection with BGP. Most BGP AD VPLS configurations are the same as BGP configurations. Unlike BGP, BGP AD VPLS requires the exchange of VPLS member information between BGP peers. Therefore, BGP peers need to be enabled to exchange VPLS member information in the BGP L2VPN AD address family view.

Perform the following steps on PEs at both ends of a 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
A BGP peer is configured.

ipv4-address is the remote LSR ID.
Run peer ipv4-address connect-interface interface-type interface-number
An interface on which a TCP connection is established is specified.

To improve reliability, a loopback interface on a PE is usually used to set up a TCP connection. If this command is not configured, a PE uses its interface that directly connects to a peer to set up a TCP connection.
Run l2vpn-ad-family
The BGP L2VPN AD address family view is displayed.
Run peer ipv4-address enable
BGP peers in the AS are enabled to exchange VPLS member information.

By default, BGP peers are not enabled to exchange VPLS information in the L2VPN AD address family view.

ipv4-address in this command is the same as ipv4-address specified in the peer command in the BGP view, which is the remote LSR ID.