Configuring BGP VPLS

This section describes how to configure BGP VPLS, which uses VPN targets for automatic VPLS member discovery.

BGP VPLS applies to scenarios where PEs can use BGP as the VPLS signaling.

On the network shown in Figure 1, PE1, PE2, and PE3 belong to the same VPLS domain.

To enable PE1, PE2, and PE3 to communicate, specifically, to construct a full-mesh VPLS network, ensure that PE1, PE2, and PE3 have matching VPN targets.
To enable CE1 to communicate with both CE2 and CE3 but prevent CE2 and CE3 from communicating, ensure that the import VPN target on PE1 is the same as the export VPN targets on PE2 and PE3, the export VPN target on PE1 is the same as the import VPN targets on PE2 and PE3, and PE2 and PE3 have mismatching VPN targets.

Figure 1 BGP VPLS networking

Before configuring BGP VPLS, complete the following tasks:

Configuring PEs to Exchange VPLS Information as BGP Peers: BGP VPLS inherits BGP configurations in a large part and shares TCP connections with BGP. A major difference between BGP and BGP VPLS is that BGP VPLS requires PEs to exchange VPLS information as BGP peers in the L2VPN-AD address family view.

Configuring a VSI and BGP Signaling: This section describes how to configure a VSI and BGP signaling.

(Optional) Configuring Flow Label-based Load Balancing: After flow label-based load balancing is configured for an L2VPN, L2VPN services can be classified by flow labels and forwarding paths can be selected based on the flow labels, improving forwarding efficiency.

(Optional) Configuring a Huawei Device to Communicate with a Non-Huawei Device

Binding an AC Interface to a VSI: AC interfaces can be bound to VSIs based on access link types.

Verifying the BGP VPLS Configuration: After configuring BGP VPLS, check VSI and VPLS connection information.