If PEs support the usage of LDP as the VPLS signaling protocol, you can configure LDP VPLS. To fully mesh PEs on a VPLS network using PWs, set up LDP sessions between all the PEs.
BGP VPLS applies to scenarios where PEs can use BGP as the VPLS signaling. In BGP VPLS, automatic discovery of VPLS PEs is implemented by configuring VPN targets.
Inter-AS LDP VPLS Option C applies to scenarios where each AS requires large numbers of inter-AS PWs. In inter-AS LDP VPLS Option C, PEs in different ASs directly exchange VPLS label block information. This solution frees ASBRs from maintaining a large amount of VPLS label block information and prevents ASBRs from becoming a bottleneck to network expansion.
Inter-AS BGP VPLS Option C applies to scenarios where each AS requires large numbers of inter-AS VPLS PWs. In inter-AS BGP VPLS Option C, PEs in different ASs directly exchange VPLS information, preventing ASBRs from being a significant factor in network expansion.
In inter-AS BGP AD VPLS Option C, ASBRs do not need to create or maintain VCs. This solution is recommended for scenarios where large numbers of inter-AS VPLS PWs are required.
In CE dual-homing networking, a CE is dual-homed to PE1 and PE2 through a switch, and PE1, PE2, and the switch constitute a ring network physically. In this case, you can enable loop detection on AC interfaces of PE1 and PE2 and specify blocking priorities for the interfaces on the active and standby links, which helps the devices break loops and prevent subsequent broadcast storms.
If PEs use BGP as VPLS signaling, BGP AD VPLS can be configured. BGP AD VPLS allows automatic discovery of VPLS PEs and automatic negotiation on the creation of PWs.
This section provides an example of configuring interworking between Label Distribution Protocol (LDP) virtual private LAN service (VPLS) and Border Gateway Protocol Auto-Discovery (BGP AD) VPLS in hierarchical virtual private LAN service (HVPLS) mode.
This section provides an example of configuring interworking between Label Distribution Protocol (LDP) virtual private LAN service (VPLS) and Border Gateway Protocol Auto-Discovery (BGP AD) VPLS in pseudo wire (PW) redundancy mode.
This section provides an example for configuring VPLS multi-homing to prevent routing loops in multi-homing scenarios, when they support BGP signaling.
This section provides an example for configuring OAM mapping. When an intermediary such as a switch exists between a PE and a CE, you can configure OAM mapping to associate the OAM status on an AC interface with the PW status.
To configure ERPS over VPLS in scenarios where a CE is dual-homed to PEs through VLANIF interfaces, enable ERPS on PE1, PE2, and the CE and configure ERPS to access the VPLS network in non-virtual channel (NVC) mode.
To configure ERPS over VPLS in scenarios where a CE is dual-homed to PEs through Ethernet sub-interfaces, enable ERPS on PE1, PE2, and the CE and configure ERPS to access the VPLS network in non-virtual channel (NVC) mode. Using Ethernet sub-interfaces to access the VPLS network must have the TC notification function enabled so that the VPLS network can have ARP and MAC address entries updated promptly after receiving TC packets. This function, however, does not need to be enabled when VLANIF interfaces are used for VPLS network access.