BGP VPLS uses a dynamic discovery mechanism to discover VPLS members using BGP signaling. BGP VPLS uses MP-BGP Update packets to transmit VPLS member information. In an MP-BGP Update packet, the MP-REACH and MP-UNREACH attributes carry VPLS label information, and the extended community attributes carry interface parameters, RDs, and VPN targets. The RDs and VPN targets are used to identify VPN member relationships.
BGP VPLS involves the following concepts:
Figure 1 shows the process of establishing a PW using BGP signaling.
Figure 2 shows the process of tearing down a PW using BGP signaling.
Ignoring MTU Match Check Results
By default, a VSI MTU check is performed on both ends of a VC in a VSI. If VSI MTUs on the two ends do not match, the VC cannot go Up.
When Huawei devices interwork with non-Huawei devices that do not support the VSI MTU check, configure the Huawei devices to ignore VSI MTU check results and encapsulate VPLS packets in the standard type 19 format.
RRs Not Filtering Received VPN Routes or Label Blocks Based on VPN Targets
Full-mesh connections need to be established between IBGP peers to ensure interconnectivity between them. If there are n BGP speakers in an AS, n(n-1)/2 IBGP connections need to be established. Establishing full-mesh connections for a large number of IBGP peers consumes lots of network resources.
In an AS, one router serves as the RR, although; whereas the other routers serve as clients. The clients establish IBGP connections with the RR. The RR and its clients form a cluster. The RR reflects routes among the clients, eliminating the need for the clients to establish BGP connections with each other. In an AS with n routers, if one router serves as the RR and others serve as clients, only (n-1) IBGP connections need to be established. This implementation greatly reduces the consumption of network and CPU resources.
After an RR is configured, VPNs or VPN targets no longer need to be configured on RR, eliminating the need for the RR to save VPN routes or label blocks. In this situation, VPN-target-based filtering must be disabled for received VPN routes or label blocks.
Support for Intercommunication Between the L2VPN-AD Address Family and the BGP VPLS Address Family on the Peer Device
Both the BGP VPLS address family and L2VPN-AD address family use the standard 25/65 address family. When the L2VPN-AD address family receives the encapsulation type of 4 or 5 from the peer end, it determines the BGP VLL if the TLV sent by the peer end carries the CSV flag (identifying the PW status) and BGP VPLS if the TLV does not carry the CSV flag.
BGP VPLS applies to the core layers of large-scale networks with BGP-running PEs.
BGP VPLS offers the following benefits: