Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Additional Features

We have extended support for the following features to the platforms shown in parentheses:

  • Additional options to automatically derive the ESI (PTX10008)—You can configure multihomed devices on an EVPN-VXLAN network to automatically generate the ESI from:

    • The system ID and administrative key on the remote customer edge device (partner).

    • The locally configured mac and local discriminator values.

    [See Understanding Automatically Generated ESIs in EVPN Networks.]

  • Break-out port state sensor support (PTX10003 and PTX10008)

    [See Telemetry Sensor Explorer and sensor (Junos Telemetry Interface).]

  • Fabric, optical, and FPC environment sensor support on Junos telemetry interface (JTI) (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)

    [See Telemetry Sensor Explorer and Guidelines for gRPC and gNMI Sensors (Junos Telemetry Interface).]

  • HMAC-SHA-2 authentication support for users of SNMPv3 USM (ACX7100-32C, ACX7100-48L, ACX7509, ACX7024, PTX1000136MR, PTX10003, PTX10004, PTX10008, PTX10016, QFX5130-32CD, QFX5700, and QFX5220)—Starting in Junos OS Evolved Release 22.4R1, you can configure HMAC-SHA-2 authentication protocols for users of the SNMPv3 user-based security model (USM) with the following new CLI configuration statements:

    • authentication-sha224

    • authentication-sha256

    We’ve introduced these statements for local-engine users at [edit snmp v3 usm local-engine user username] and for remote-engine users at [edit snmp v3 usm remote-engine engine-id user user-name].

    [See authentication-sha224 and authentication-sha256.]

  • Inline Active Flow Monitoring support for configuring the options template ID, template ID, source ID, and observation domain ID (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)

    [See options-template-id, template-id, source-id, and observation-domain-id.]

  • Inline Monitoring Services support for packet mirroring with metadata (PTX10001-36MR, PTX10004, PTX10008, and PTX10016)

    [See Inline Monitoring Services Configuration.]

  • Keep bypass tunnels operational during configuration changes (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)

    [See link-protection (RSVP) Link Protection for MPLS LSPs.]

  • NETCONF and shell sessions over enhanced outbound HTTPS (ACX7100-32C, PTX10001-36MR, PTX10003, PTX10004, PTX10008, PTX10016, QFX5130-32CD, and QFX5700)

    [See NETCONF and Shell Sessions over Enhanced Outbound HTTPS.]

  • SNMP MIB support for Real-Time Performance Monitoring (RPM) (PTX10004)

    [See traps.]

  • Static Adjacency SID support per AE member link (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS 22.4R1 Evolved Release, we support static adjacency SID for any specific aggregated Ethernet interface member link.

    [See Configuring Static Adjacency Segment Identifier for Aggregate Ethernet Member Links Using Single-hop Static LSP.]

  • Support for asynchronous notification for EVPN-VPWS (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved 22.4R1, we’ve extended support for asynchronous notification (laser-off signal) on the port of the physical interface in the PTX series router. You can configure asynchronous notification for ethernet-ccc, Ethernet-VPLS, and vlan-ccc encapsulation type in an EVPN-VPWS network. This feature is not supported on aggregated Ethernet interfaces.

    [See asynchronous-notification.]

  • Support for G.8275.1 Telecom Profile (PTX10001-36MR)

    [See G.8275.1 Telecom Profile.]

  • Support for hybrid mode (Synchronous Ethernet and PTP) over LAG with PTP over Ethernet (PTX10008 with PTX10K-LC1202-36MR Line Card)

    [See Hybrid Mode and PTP over Ethernet.]

  • Supported transceivers, optical interfaces, and direct attach copper (DAC) cables—Select your product in the Hardware Compatibility Tool to view supported transceivers, optical interfaces, and DAC cables for your platform or interface module. We update the HCT and provide the first supported release information when the optic becomes available.

  • Support for automatic ingress LSP Policing in P2MP LSPs (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)

    [See Configuring Automatic Policers.]

  • Support for ANY firewall filter family (PTX10003)

    [See family (Firewall).]

  • Support for displaying load balancing decision result for L3 unicast traffic (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)

    [See show forwarding-options load-balance.]

  • Two-Way Active Measurement Protocol (TWAMP) monitoring service (RFC5357) IPv4 address support (PTX10016)

    [See Understand Two-Way Active Measurement Protocol.]

  • Two-Way Active Measurement Protocol (TWAMP) monitoring service (RFC5357) IPv6 address support (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)

    [See Understand Two-Way Active Measurement Protocol.]

  • Two-Way Active Measurement Protocol (TWAMP) monitoring service (RFC5357) SNMP support (PTX10016)

    [See Understand Two-Way Active Measurement Protocol.]