On an IP RAN where VPLS is still used at the access layer but the aggregation network has evolved to MPLS EVPN, interworking between VPLS and MPLS EVPN E-LAN needs to be enabled.
During IP RAN evolution towards EVPN, if VPLS is still commonly used on access-layer devices, it is difficult to implement E2E evolution towards MPLS EVPN. However, the aggregation network has already evolved to MPLS EVPN. In this case, the IP RAN needs to be configured with interworking between VPLS and MPLS EVPN E-LAN.
As shown in Figure 1, CSGs and ASGs are connected over the access network where the VPLS function is deployed to carry services, and ASGs and RSGs are connected over the aggregation network where the BD EVPN function is deployed to carry services. On ASGs, a BD needs to be configured and bound to a BD EVPN instance and a VSI to achieve interworking between VPLS and MPLS EVPN E-LAN.
Before configuring interworking between VPLS and MPLS EVPN E-LAN, complete the following tasks:
Configure LDP VPLS between CSGs and ASGs.
Configure BD EVPN between ASGs and RSGs.
Perform the following operations on each ASG:
The system view is displayed.
The global EVPN configuration view is displayed.
The name of a static ESI instance is configured.
The redundancy mode of the static ESI instance is set to single-active.
Return to the global EVPN configuration view.
Return to the system view.
The VSI view is displayed.
LDP is configured as the PW signaling protocol, and the VSI-LDP view is displayed.
A VSI ID is configured.
A PW is created, and the VSI-LDP-PW view is displayed.
An ESI is configured for the PW interface.
The value of esi must be consistent with the name of the static ESI instance.
The leaf attributes of the PW interface are configured.
If users do not want the CE1-to-CSG1 traffic to be sent back to CSG2 and then CE1 over ASG1 and ASG2, users can configure leaf attributes for ASG1 and ASG2 in the VSI-LDP-PW view.
Return to the VSI-LDP view.
Return to the VSI view.
Return to the system view.
The BD view is displayed.
The BD is bound to a VSI instance.
The BD is bound to an EVPN instance.
The configuration is committed.
Run the display bgp evpn { all | route-distinguisher route-distinguisher | vpn-instance vpn-instance-name } routing-table { ad-route | es-route | inclusive-route | mac-route | prefix-route } prefix command on an ASG to view details about BGP EVPN routes, including information about access-side PWs.
Run the display evpn vpn-instance name vpn-instance-name df result [ esi esi ] command on an ASG to view the DF election result of an EVPN instance, including information about access-side PWs.