Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

EVPN

  • Remote port mirroring with an IP address (GRE encapsulation) on EVPN-VXLAN (ACX7100-32C and ACX7100-48L)—Starting in Junos OS Evolved 22.3R1, you can configure remote port mirroring with an IP address on an EVPN-VXLAN fabric. The router sends the mirrored traffic output through a GRE tunnel to the remote IP destination address that you specify in the configuration. The configuration is an analyzer instance.

    Note:

    Configure the feature under the [edit forwarding-options analyzer] hierarchy level. You cannot configure it under [edit forwarding-options port-mirroring].

    Configuration guidelines include:

    • You can configure a nonzero logical unit number for an input analyzer; however, the chip in an ACX7100 router supports mirroring in the hardware on the physical interface, not on a logical interface.

    • In ingress mirroring, incoming traffic is mirrored at the ingress pipeline, and therefore pruning or filtering at the egress pipeline does not have any impact on the mirroring behavior.

    • Input families for the input port are inet, inet6, ethernet-switching, and bridge.

    • The destination address for mirrored output must be an IPv4 address.

    [See Port Mirroring and Analyzers.]

  • Support for EVPN ELAN active-active multihoming and EVPN over segment routing (ACX7024)—Starting in Junos OS Evolved Release 22.3R1, we support the following EVPN segment routing features:

    • EVPN-ELAN active-active multihoming

    • EVPN-ELAN over segment routing

      • Segment routing global block (SRGB) for OSPF and IS-IS

      • Segment routing services for IPv4

      • Metro Ethernet services over segment routing infrastructure

      • Static segment routing (node segment)

      • MPLS fast reroute

      • Topology-independent loop-free alternate (TI-LFA) with segment routing for OSPF and IS-IS

    [See EVPN Multihoming Overview and Example: Configuring EVPN Active-Active Multihoming.

  • Support for all-active multihoming redundancy in FXC and non-FXC EVPN-VPWS networks (ACX7024)—Starting in Junos OS Evolved Release 22.3R1, you can configure an ACX7024 device in both types of EVPN–virtual private wire service (EVPN-VPWS) network 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.]

  • Support for EVPN-VPWS all-active multihoming for segment routing over MPLS (ACX7024)—Starting in Junos OS Evolved Release 22.3R1, we support two variants of EVPN-VPWS multihoming for segment routing over MPLS: all-active and single-active. All-active instances share traffic to each multihomed provider edge. 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 path goes down, the Packet Forwarding Engine (PFE) is updated with the new path. This release supports up to 512 instances of multihomed neighbors. Note that this release does not support asynchronous notification.

    [See Overview of VPWS with EVPN Signaling Mechanisms.]