Additional Features
We have extended support for the following features to these platforms.
-
RPM and TWAMP support (EX4100, EX4400, and EX4650 switches). Starting in Junos OS Release 24.2R1, these EX Series switches fully support RPM and Two-Way Active Measurement Protocol (TWAMP):
-
You can configure RPM probe generation, reception, and reflection and enable timestamps on RPM probe messages.
-
You can also use RPM probes to detect link status and to change the preferred-route state on the basis of the probe results. RPM-tracked routes can be IPv4 or IPv6, and support up to 16 next hops for each IPv4 or IPv6 RPM-tracked static route. You can configure route preference and tag values for each IPv4 or IPv6 destination prefix.
-
You can also configure RPM services to automatically determine whether a path exists between a host device and its configured BGP neighbors. You can view the results of the discovery using an SNMP client. The results are stored in
pingResultsTable,jnxPingResultsTable,jnxPingProbeHistoryTable, andpingProbeHistoryTable. -
For TWAMP, we support IPv4 and IPv6 (including link-local addresses) traffic for control sessions and test sessions.
-
For TWAMP Light, we support IPv4 and IPv6 traffic, including IPv6 link-local addressing.
[See Understanding Real-Time Performance Monitoring on EX and QFX Switches, rpm-tracking, show route rpm-tracking, and Understand Two-Way Active Measurement Protocol.]
-
-
Seamless EVPN-VXLAN stitching (EX4100-48MP, EX4400-24MP, EX4400-24P, EX4400-24T, EX4400-24X, EX4400-48F, EX4400-48MP, EX4400-48P, EX4400-48T). We support the seamless stitching of unicast and broadcast, unknown unicast, and multicast (BUM) routes in an interconnected Ethernet VPN–Virtual Extensible LAN (EVPN-VXLAN) environment.
[See interconnect.]
-
Support for preventing event, op, SNMP, or JET script execution based on current system memory usage (SRX300, SRX320, SRX340, SRX345, SRX380, SRX1500, SRX1600, SRX2300, SRX4100, SRX4200, SRX4600, SRX5400, SRX5600, and SRX5800)
-
Supported transceivers, optical interfaces, and DAC cables Select your product in the Hardware Compatibility Tool (https://apps.juniper.net/hct/product/) to view supported transceivers, optical interfaces, and direct attach copper (DAC) cables for your platform or interface module. We update the HCT and provide the first supported release information when the optic becomes available.
-
Symmetric IRB with EVPN Type 2 routes (MX Series). You can enable EVPN Type 2 routing over symmetric integrated routing and bridging (IRB) interfaces in an EVPN-MPLS edge-routed bridging (ERB) overlay.
[See Symmetric Integrated Routing and Bridging with EVPN Type 2 Routes in EVPN-VXLAN Fabrics.]
-
On-box monitoring support on the control plane (SRX300, SRX320, SRX340, SRX345, SRX380, SRX1500, SRX1600, SRX2300, SRX4100, SRX4200, SRX4600, SRX5400, SRX5600, and SRX5800).You can configure the memory monitoring system to monitor the system memory and raise a major or minor alarm using the
set system monitor memory system alarmcommand statement on a device. The system raises an alarm when the device runs low on memory.[See Memory (System).]
-
Reduce operational time by using the JET Interfaces Service API to perform port bounces (SRX300, SRX320, SRX340, SRX345, SRX380, SRX1500, SRX1600, SRX2300, SRX4100, SRX4200, SRX4600, SRX5400, SRX5600, and SRX5800)
[See Overview of JET APIs.]
-
Precision Time Protocol (PTP) enterprise profile (QFX5110-48S)
[See PTP Enterprise Profile.]
-
sFlow ingress support (ACX710, ACX5448, ACX5448-D, and ACX5448-M)
[See sFlow Monitoring Technology.]
-
Support for ISSU with slice-based HCoS (MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10004, MX10008, and MX10016)
-
Support for enhanced firewall filter processing using hardware-assisted segmented filters for large filters (EX9200)
[See fast-lookup-filter.]
-
Firewall filter support on demux interfaces (MX240, MX480, MX960, MX10004, and MX10008)
-
Interface-specific filters attached on
inet,inet6,ccc, andanyfirewall filter families -
Firewall filter attachment on a demux interface in input and output directions
-
Policer attachment on demux interface in input and output directions
-
Flexible firewall filter match conditions
-
Two-color and three-color policers
[See Subscriber Interfaces and Demultiplexing Overview and Firewall Filters Overview.]
-
-
Support for TCAM group optimization (EX4100-48MP, EX4100-H-12P, EX4100-H-12P-DC, EX4100-H-24F, EX4100-24MP, EX4100-48P, EX4100-48T, EX4100-24P, EX4100-24T, EX4100-F-48P, EX4100-F-24P, EX4100-F-48T, EX4100-F-24T, EX4100-F-12P, EX4100-F-12T, EX4400-24MP, EX4400-24P, EX4400-24T, EX4400-24X, EX4400-48F, EX4400-48MP, EX4400-48P, and EX4400-48T)
-
G.8275.2 (PTS) profile BC and OC support with LAG (IPv4 and IPv6) on MX10008 Universal Routing Platform (MX Series) G.8275.2 Enhanced Profile
-
Wake-on LAN targeted-broadcast feature for EVPN-VXLAN networks (EX4100-24P, EX4100-24T, EX4100-48MP, EX4100-48P, EX4100-48T, EX4100-F-12P, EX4100-F-12T, EX4100-F-24P, EX4100-F-24T, EX4100-F-48P, EX4100-F-48T, EX4400-24MP, EX4400-24P, EX4400-24T, EX4400-24X, EX4400-48F, EX4400-48MP, EX4400-48P, EX4400-48T, EX4650, QFX5120-32C, QFX5120-48T, QFX5120-48Y, and QFX5120-48YM)
[See Targeted Broadcast and targeted-broadcast.]
-
Offload constraint-based path computation onto the cPCE with cRPD support— A containerized routing protocol process (daemon) enables containerized Path Computation Engine (cPCE) to run on-device or off-device. You can offload constraint-based path computation onto the cPCE. cPCE is useful for computing and delegating traffic-engineered label-switched paths in an RSVP–Traffic Engineering (RSVP-TE) network deployment.
[See cPCE Deployment Guide.]