EVPN
- Enhanced platform, routing, and switching support for EVPN-VPWS
flexible cross-connect (FXC) forwarding (ACX7509)—Starting in Junos OS Evolved Release
22.1R1, forwarding support for EVPN-VPWS/FXC leverages the existing platform-dependent
infrastructure of the EVO routing engine and the Environment Abstraction Layer (EAL), as
well as all EVO-PFEMAN infra process layers. Forwarding features are enabled on ACX7509
routers using infrastructure and kernel services provided by EVO.
The following forwarding feature categories are supported:
- Layer 2 Bridging
- Layer 3 Routing (IPv4 | IPv6)
- MPLS VPNs
- VPLS
- QoS
- Firewall
- OAM (CFM, BFD)
- DHCP/Services
- Statistics
- Multicast support
- VRRP
[See Overview of Flexible Cross-Connect Support on VPWS with EVPN.]
-
EVPN E-LAN Active-Active Multihoming with EVPN Aliasing Support for ESI LAG (ACX7100-32C and ACX7100-48L)—Starting in Junos OS Evolved Release 22.1, BGP-signalled EVPN services are supported over a MPLS WAN network with active-active multihoming redundancy and EVPN aliasing support for Ethernet segment interface (ESI) link aggregation group (LAG) implementations.
Configure EVPN for multihomed CE devices in the active-active redundancy mode, so the Layer 2 unicast traffic is load-balanced (aliased) across all multihomed links on and toward the CE device. Type 1 AD/ESI and AD/EVI routes are supported where the designated forwarder (DF) PE is responsible for forwarding BUM traffic towards multihomed CE devices. In general, Unicast traffic is received on any multihoming PEs because the CE is connected via LAG, and Unicast traffic also flows from the core to the multihomed CE IFL logical interfaces. BUM traffic flows from the multihomed CE to the core. If a packet is flooded in one of the multihoming PEs, regular BUM forwarding will happen with outgoing packets carrying IM labels. Note that the ESI value must always be unique across all IFDs and IFLs.
EVPN aliasing provides the ability of a remote device to load balance Layer 2 Unicast traffic. It allows a device to quickly recover when a link to a multihomed PE device fails. EVPN aliasing enables load balancing that depends on a Hash key configuration using:
set forwarding-options hash-key <hash key parameters>
Both overlay and underlay load balancing is supported.
[See
-
EVPN E-LAN Single homing support (ACX7509)—Starting in Junos OS Evolved Release 22.1R1, forwarding features are supported for EVPN-MPLS vlan-based and bundle-based services on single-homing Ethernet - Local Area Networks (E-LANs).
[See Single-Homed EVPN Example.]
-
Support for EVPN-MPLS service (ACX7100-32C, ACX7100-48L, and ACX7509)—Starting in Junos OS Evolved Release 22.1R1, you can configure EVPN-MPLS services using MAC-VRF routing instance provisioning. No new CLI are introduced with this release.
[See EVPN Overview.]
-
Support for EVPN-VPWS MultiHoming All-Active for Segment Routing over MPLS (ACX7100-32C and ACX7100-48L)—Starting in Junos OS Evolved Release 22.1R1, EVPN-VPWS multihoming for segment routing over MPLS consists of two variants: all-active and single-active models. All-active instances share traffic to each multihomed provider edge (PE). The single-active instances are cold-standby acting as single-homed models where the routing protocol daemon (RPD) is aware of the backup path. If the primary goes down, RPD performs a global repair and updates the packet forwarding engine (PFE) with the new path. Multiple multihomed neighbors are supported, up to 512 instances. Note that asynchronous notification is not supported in this release.
- Support for all-active multihoming redundancy in
both Ethernet VPN–virtual private wire service (EVPN-VPWS) and EVPN-VPWS with flexible
cross-connect (ACX7100-32C and ACX7100-48L)—Starting in Junos OS Evolved Release
22.1R1, you can configure ACX7100-32C and ACX7100-48L devices in both EVPN-VPWS networks
with flexible cross-connect (FXC) or legacy EVPN-VPWS (non-FXC) networks to support
all-active multihoming redundancy.
[See Overview of Flexible Cross-Connect Support on VPWS with EVPN.]