The deployment roadmap is as follows:
Before deploying PBB VPLS, complete the following tasks:
Deploy PBB VPLS to solve the scalability problem of the VPLS network:
Residential service
On the network shown in Figure 1, an Internet service provider (ISP) network is dual-homed to two network provider edges (NPEs), and an E-Trunk is configured between the two NPEs to determine the master/backup status of NPEs. After the E-Trunk detects a fault on the primary link, the E-Trunk sends an LACP packet to the ISP network, instructing the ISP network to switch traffic to the secondary link. Meanwhile, the new master NPE sends MAC Withdraw messages to SPEs, instructing SPEs to delete B-MAC addresses.
Enterprise service
On the network shown in Figure 2, enterprise devices attached to switches are dual-homed to UPEs. An E-Trunk is configured between each pair of UPEs to determine the master/backup status of UPEs. After an E-Trunk detects a fault on the primary link, the E-Trunk sends an LACP packet to the enterprise devices, instructing these devices to switch traffic to the secondary link. Meanwhile, the master UPE sends MAC Withdraw messages to SPEs, instructing SPEs to delete B-MAC addresses.
On the network shown in Figure 3, a UPE is dual-homed to SPEs over primary and secondary VPLS PWs. A Management Virtual Router Redundancy Protocol (mVRRP) backup group is configured on the SPEs and a management VSI (mVSI) is configured on the UPE. The mVSI is associated with multiple service VSIs. Link and peer BFD sessions are configured to track the mVRRP group. If a master/backup mVRRP switchover occurs, the new master SPE sends gratuitous Address Resolution Protocol (ARP) packets to the UPE. After receiving the packets, the UPE converts unicast traffic in all service VSIs associated with the mVSI to multicast traffic. The return traffic carrying a label mapped to the previous secondary PW is unicast traffic and traverses the new primary PW.