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:

  • Accept BGP routes with accept-own community (ACX7100-32C, ACX7509, PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)

    [See BGP accept-own Community and accept-own.]

  • Adaptive RSVP update-threshold for optimal IGP flooding (PTX10001-36MR, PTX10002, PTX10003, PTX10004, PTX10008, and PTX10016)—You can now configure the RSVP update threshold percentage and threshold value to adaptively pace IGP updates.

    [See update-threshold.]

  • Collect ON_CHANGE BGP RIB telemetry statistics (PTX10001-36MR, PTX10003, PTX10004, PTX10008, PTX10016, and QFX5220)

    [See Telemetry Sensor Explorer.]

  • Collect ON_CHANGE BGP RIB telemetry statistics and BGP neighbor telemetry with sharding (ACX7100-32C, ACX7100-48L, ACX7509, PTX10001-36MR, PTX10004, PTX10008, PTX10016, QFX5130-32CD, and QFX5700)

    [See Telemetry Sensor Explorer.]

  • Inline active flow monitoring using IP Flow Information Export (IPFIX) and version 9 templates (PTX10003)—We now support:

    • IPv4 and IPv6 traffic on IRB interfaces.

    • A BGP next-hop address in the IPv6 and MPLS-IPv6 templates: Information Element 63, IPv6 BGP NextHop Address, is now available.

    [See Inline Active Flow Monitoring on IRB Interfaces and IPFIX and Version 9 Templates.]

  • Inline monitoring services (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016 routers with the JNP10K-LC1201 or JNP10K-LC1203 linecards)—

    Inline monitoring services enable you to monitor different streams of traffic at different sampling rates on the same interface. The inline monitoring services in the Junos OS Evolved implementation show the following differences from the inline monitoring services in the Junos OS implementation:

    • A maximum of seven inline-monitoring instances

    • A maximum clip length of 256 bytes starting from the Ethernet header

    • Sampling rate per instance only

    • Port-mirroring and inline-monitoring firewall filter actions on different terms

    • Some inline-monitoring-services configuration options are available only in the Junos OS implementation, such as the options to specify the DSCP bits, forwarding class, routing instance, template ID, and option template ID.

      [See Inline Monitoring Services Configuration.]

  • IP-IP tunnel stitching (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)

    [See Overview of Next-Hop-Based Dynamic Tunneling Using IP-Over-IP Encapsulation and Example: Configuring Next-Hop-Based IP-Over-IP Dynamic Tunnels.]

  • IPFIX IPv4 and IPv6 template support for forwarding class and packet loss priority (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)

    [See IPFIX and Version 9 Templates.]

  • Juniper Resiliency Interface (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016 routers with the JNP10K-LC1201 or JNP10K-LC1203 linecards)

    [See Juniper Resiliency Interface.]

  • Next-Generation MVPN (PTX10001-36MR, PTX10004, PTX10008, and PTX10016)—We now support:

    • Rendezvous-point tree (RPT)-shortest-path tree (SPT) mode.

    • Restart individual PFE instances.

    • Turnaround provider edge (PE) device.

    • RP Mechanisms, including auto rendezvous point (RP), bootstrap router (BSR), and embedded RP.

    [See Understanding Next-Generation MVPN Control Plane.]

  • NSR Support for RIP and RIPng (PTX10004, PTX10008, and PTX10016)

    [See Nonstop Active Routing Concepts.]

  • Per Packet Forwarding Engine-Restart support (PTX10004, PTX10008, and PTX10016)—

    Support includes:

    • Disable, offline, and restart of individual Packet Forwarding Engines.

    • Filter-based GRE encapsulation.

    • Segment routing–traffic engineering (SR-TE) per path telemetry statistics support, including ingress IP/binding-segment identifiers (SIDs) and MPLS transit traffic.

    • Flow Aware Transport (FAT) label transport for Layer 2 VPN.

    • VLAN tag manipulation support for CCC.

    • Segment routing over UDP.

    • Multicast-only fast reroute (MoFRR) for both IPv4 and IPv6 traffic flows.

    [See fpc (M320, T320, T640, and PTX Series Routers), Understanding Filter-Based Tunneling Across IPv4 Networks, source-packet-routing, flow-label-transmit, Configuring an MPLS-Based VLAN CCC with Pop, Push, and Swap and Control Passthrough, Next-Hop-Based Dynamic Tunnels, and Understanding Multicast-Only Fast Reroute.]

  • Support for BGP Classful Transport (CT) with underlying colored Segment Routing Traffic-Engineered (SRTE) tunnels (PTX10001-36MR, PTX10003, PTX10004, PTX10008 and PTX10016)

    —BGP-CT can resolve service routes using the transport routing information bases (RIB)s, also known as routing tables and compute the next hop. Services currently supported over BGP-CT can also use the underlying SRTE colored tunnels for route resolution.

    [See use-transport-class.]

  • Support for EVPN-virtual private wire service (VPWS) (PTX10001-36MR, PTX10004, PTX10008, and PTX10016)—We've extended support for EVPN-VPWS to the listed PTX Series routers. By default, control-word is enabled on these platforms. To disable the control word feature, use the set routing-instances routing-instance-name protocols evpn no-control-word command.

    [See Overview of VPWS with EVPN Signaling Mechanisms.]

  • Support for firewall filtering using flood policer, IRB, and service provider egress filtering (PTX10003)

  • Support for match conditions next-header and payload-protocol to filter IPv6 packets based on Next Header (NH) values of first and last headers (PTX10003)

    The next-header matches on intermediate extension headers are not supported. The payload-protocol match is applicable only if the first extension header is Hop-by-Hop.

    [See Firewall Filter Match Conditions for IPv6 Traffic]

  • 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 this tool and provide the first supported release information when the optic becomes available.

  • Translation of multicast virtual private network (MVPN) Type 5 routes to Multicast Source Discovery Protocol (MSDP) SA routes (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)

    [See Converting MVPN Type 5 Routes to MSDP SA.]