Additional Features | Junos OS Evolved

Avoid microloops in IS-IS segment routing MPLS networks (ACX7024, ACX7100-32C, ACX7100-48L, and ACX7509). You can enable post-convergence path calculation on a device to avoid microloops between network devices.

[See Understanding IS-IS Microloop Avoidance and How to Configure Microloop Avoidance in OSPFv2 Segment Routing Networks.]

Interoperability of segment routing with LDP (ACX7024, ACX7100-32C, ACX7100-48L, and ACX7509). You can use OSPF or IS-IS to enable segment routing devices to operate with the LDP devices that are not segment routing capable.

[See Mapping Client and Server for Segment Routing to LDP Interoperability.]

EVPN-VXLAN to EVPN-VXLAN stitching for unicast routing . Starting in Junos OS Evolved Release 23.2R1, EVPN-VXLAN to EVPN-VXLAN seamless stitching T2/T2 is supported for unicast and BUM functionality.

[See EVPN Type 2 Symmetric Routing with DCI Stitching.]

Resiliency support for ASIC error and CM infra (ACX7024, ACX7100-32C, and ACX7100-48L). We introduce resiliency support for ASIC errors.

Nonstop active routing (NSR) support for EVPN-MPLS (ACX7509). Support includes EVPN virtual private wire service (VPWS), Ethernet LAN (unicast or Broadcast Unknown Multicast).

[See Non-stop Active Routing Concepts for Junos OS Evolved.]

Support for multiple classifier rules on interfaces (ACX7024, ACX7100-32C, ACX7100-48L, and ACX7509) [See Classifiers and Rewrite Rules at the Global, Physical, and Logical Interface Levels Overview.]

Layer 3 routing and protocols statistics (ACX7900)—Starting in Junos OS Evolved Release 23.2R1, JTI provides Layer 3 and routing protocols IPv4, IPv6, BGP, IS-IS and ARP streaming sensor support using gRPC services.

[See Telemetry Sensor Explorer.]

Support for multiple classifier rules on interfaces (ACX7024, ACX7100-32C, ACX7100-48L, and ACX7509) [See Understanding Applying CoS Classifiers and Rewrite Rules to Interfaces.]

Support of LACP link protection (ACX7100-32C, ACX7100-48L, ACX7509, ACX7204)—Support for 1:1 and N: N link-protection. To enable this feature, use the existing link-protection statement in the [edit interfaces aex aggregated-ether-options lacp] hierarchy level.[See link-protection.]

Support for entropy and flow label for EVPN-ELAN (ACX7024, ACX7100-32C, ACX7100-48L, and ACX7509). The listed ACX Series devices support entropy and flow label for EVPN-ELAN.

[See Configuring Entropy Labels.]

Support for entropy label for LDP, RSVP, L3VPN, and BGP-LU (ACX7024, ACX7100-32C, ACX7100-48L, and ACX7509). We introduce support for entropy label for LDP, RSVP, L3VPN, and BGP Labeled Unicast (BGP-LU).

[See Entropy label support for BGP Labeled Unicast (BGP-LU) and Configuring Entropy Labels .]

Support for multiple classifier rules on interfaces (ACX7024, ACX7100-32C, ACX7100-48L, and ACX7509). We introduce support for multiple classifier rules on interfaces.

[See Understanding Applying CoS Classifiers and Rewrite Rules to Interfaces.]

Support for TI-LFA SRLG protection and fate-sharing protection for IS-IS and OSPFv2 (ACX7024, ACX7100-32C, ACX7100-48L, and ACX7509). We introduce support for TI-LFA SRLG protection and fate-sharing protection for IS-IS and OSPFv2.

[See Understanding Topology-Independent Loop-Free Alternate with Segment Routing for IS-IS and Topology-Independent Loop-Free Alternate with Segment Routing for OSPF.]

IGMP snooping support on leaf devices for EVPN-VXLAN CRB overlay network (ACX7100-32C, ACX7100-48L, and ACX7024 devices)– Support for multicast forwarding with Internet Group Management Protocol (IGMP) snooping is supported on ACX leaf devices for an EVPN-VXLAN centrally routed bridging overlay network. Leaf devices forward multicast traffic at layer-2 within a VLAN only.

The leaf devices forward multicast traffic on the access side only to interested listeners based on IGMP snooping state and continue to use ingress replication to flood multicast traffic into the EVPN core to reach other spine or leaf devices that might serve interested listeners. The ACX devices support intra-VLAN multicast traffic as multicast receivers within the EVPN-VXLAN Network.

Spine devices, for example MX-series devices, perform forwarding within a VLAN and can also be configured with IRB interfaces to perform inter-VLAN routing. To route multicast traffic from or to multicast sources and receivers external to the EVPN-VXLAN network, spine devices use PIM on a multicast VLAN through an external gateway.

[See Overview of Multicast Forwarding with IGMP Snooping or MLD Snooping in an EVPN-VXLAN Environment.]