The device supports EVPN service activation by device or interface. If EVPN service resources have been purchased based on the number of ports in the current project, you must allocate these resources to specified ports.
Configuring bridge domain BD-EVPN functions involves configuring an EVPN instance in BD mode, creating a BD and binding an EVPN instance to the BD, configuring an L3VPN instance and binding it to a VBDIF interface, and configuring BGP EVPN peer relationships.
When the EVPN E-LAN model is used to carry multipoint-to-multipoint (MP2MP) VPLSs, EVPN VPLS over SRv6 BE can be configured to transmit EVPN E-LAN data over public SRv6 BE paths.
This section describes how to configure EVPN virtual private wire service (VPWS) over SRv6 TE Policy so that EVPN VPWSs can be carried over SRv6 TE Policies.
Currently, EVPN + SRv6 is a mainstream transport solution for 5G services. To prevent live network services from being affected, a new transport solution must be deployed based on the existing services on live networks. If a large number of EVPN VPWS over MPLS services exist on the live network, you can configure dual-stack to prevent traffic interruption caused by direct IPv4-to-IPv6 service switching when IPv4 and IPv6 networks coexist, facilitating evolution from EVPN VPWS over MPLS to EVPN VPWS over SRv6.
When an L3VPN is being reconstructed into an EVPN L3VPN, co-existence of the EVPN L3VPN and L3VPN occurs. To prevent network reconstruction from compromising communication, configure interworking between L3VPN and EVPN L3VPN so that the EVPN L3VPN and L3VPN can communicate with each other.
This section describes how to configure interworking to enable communication between an anycast VXLAN in an EVPN active-active scenario and a VPLS in PW redundancy mode configured.
An EVPN can carry multicast services. To reduce redundant traffic and conserve bandwidth resources, you can configure EVPN to use an mLDP P2MP tunnel for service transmission.
In CE dual-homing networking, to balance the broadcast, unknown unicast, and multicast (BUM) traffic between the CE and PEs, you can configure virtual local area network (VLAN)-based designated forwarder (DF) election.
When PEs are interconnected both through network-side and access-side links, MAC route flapping may occur. To resolve this issue, you can configure MAC duplication suppression.
After EVPN outbound route filtering (ORF) is configured, the BGP-EVPN address family can filter the routes being advertised to a peer by comparing the export VPN target (ERT) of the routes with the import VPN target (IRT) of the remote peer. This reduces network load.
EVPN recursion suppression in case of next hop flapping prevents the system from processing changes in EVPN routes that recurse to a frequently flapping next hop, thereby reducing system resource consumption and CPU usage.
Traditional VLL is still used at the aggregation layer of a network, whereas the core network has evolved into EVPN. To allow communication between different layers, interworking between VLL and common EVPN E-LAN must be configured.
The traditional VLL is still used at the aggregation layer of a network, whereas the core network has evolved into EVPN. To allow communication between different layers, VLL and MPLS EVPN E-Line interworking must be configured.
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.
When a conventional VPLS network and an EVPN VPLS over SRv6 network are converged, you need to configure interworking between VPLS and EVPN VPLS over SRv6.
When both a conventional VPLS network and an EVPN VPLS over SRv6 network are deployed, you need to configure the coexistence of VPLS and EVPN VPLS over SRv6.
If point-to-multipoint Layer 2 services are carried using EVPN E-LAN and Layer 3 services are carried using MPLS L3VPN, EVPN E-LAN accessing L3VPN must be configured on L2-to-L3 devices.
In MetroFabric scenarios deployed with CU separation, interworking betweenMPLS EVPN and static VXLAN must be deployed on metro edge function (MEF) devices.
During network evolution, EVPN L3VPN over SRv6 BE and L3VPN over MPLS may coexist. To allow these two types of networking to interwork, perform this task.
An EVPN L3VPN hierarchical VPN (HVPN) over MPLS is a hierarchical EVPN, on which PEs play different roles and provide different functions. These PEs form a hierarchical architecture to provide functions that are provided by one PE on a non-hierarchical VPN. EVPN L3VPN HVPNs over MPLS lower the performance requirements for PEs.
An EVPN L3VPN HoVPN over SRv6 is a hierarchical EVPN over SRv6 network. Multiple PEs play different roles and form a hierarchical structure to implement the functions of a single PE, reducing PE performance requirements.
During the evolution from L3VPN HoVPN to EVPN HoVPN over SRv6, these two types of services may coexist. In this case, you need to configure interworking between an L3VPN HoVPN and an EVPN L3VPN over SRv6.
During network evolution, an EVPN L3VPN over SRv6 and a common L3VPN over MPLS may coexist. To ensure normal communication between the two types of networks, configure interworking between an EVPN L3VPN over SRv6 and a common L3VPN over MPLS.
During network evolution, an EVPN L3VPN over SRv6 TE Policy and a common L3VPN over MPLS may coexist. To allow these two networks to communicate, configure each border leaf node to provide interworking between EVPN L3VPN over SRv6 TE Policy and common L3VPN over MPLS.
If EVPN VPLS over SRv6 is used to carry E-LAN services, configure EVPN VPLS over SRv6 on each device that functions as a BRAS that provides access services for users.
If EVPN VPWS over MPLS is used to carry E-Line services on a network, configure EVPN VPWS over MPLS accessing BRAS on each device that provides access for users.
If EVPN VPWS over MPLS or EVPN VPWS over SRv6 in dual-homing single-active mode is deployed on the network and VRRP or VRRP6 is configured on the devices responsible for user access to determine their master/backup status, you need to configure EVPN VPWS accessing BRAS and associate VRRP or VRRP6 with EVPN VPWS to determine the primary/secondary status of EVPN VPWS PWs.
If EVPN VPWS over MPLS or EVPN VPWS over SRv6 in dual-homing single-active mode is deployed on the network and VRRP or VRRP6 is configured on PEs to determine their master/backup status, you need to configure EVPN VPWS accessing L3VPN and associate VRRP or VRRP6 with EVPN VPWS to determine the primary/secondary status of EVPN VPWS PWs.
Currently, EVPN over SRv6 is used as a mainstream transport solution for 5G services. To ensure that services on live networks are not affected, a new transport solution must be deployed based on the existing services on live networks. When there are a large number of VPWS accessing L3VPN over MPLS services on the live network, you need to evolve VPWS accessing L3VPN over MPLS to VPWS accessing EVPN over SRv6.
In the network function virtualization infrastructure (NFVI) telco cloud solution, the NFVI distributed gateway function allows mobile phone service traffic to be transmitted to virtual unified gateways (vUGWs) and virtual multiservice engines (vMSEs) through a SR tunnel over a data center network (DCN) in load balancing mode.
In the NFVI telco cloud solution, the NFVI distributed gateway function allows mobile phone traffic to be processed by vUGWs and vMSEs and transmitted over a DCN through E2E SR tunnels as well as being transmitted within a DCN in load balancing mode.
In the NFVI telco cloud solution, the NFVI distributed gateway function allows mobile phone traffic to be processed by vUGWs and vMSEs and transmitted over a DCN through E2E SR tunnels as well as being transmitted within a DCN in load balancing mode.
If EVPN VPLS over MPLS or EVPN VPLS over SRv6 in ring network access mode needs to be deployed on a network, you need to configure EVPN in this mode and deploy a loop avoidance protocol to prevent loops.