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:

  • Inline active flow monitoring IPv6 addressing support for IPFIX and version 9 flow collectors (PTX10001-36MR, PTX10003, PTX10004, and the PTX10008 and PTX10016 routers with the JNP10K-LC1201 or the JNP10K-LC1202 line card). You can configure either IPv4 or IPv6 collectors for each family within a sampling instance; you cannot specify both for the same family. You can specify up to four collectors for each family within a sampling instance.

    [See Understand Inline Active Flow Monitoring.]

  • MVPN feature support with sharding (PTX10001-36MR, PTX10003, PTX10004, PTX10008, QFX5130-32CD, and QFX5700).We support the following MVPN features:

    • With sharding, the information required by MVPN, such as inactive L3vpn routes, primary, and secondary details for auto-exported routes were only in the shard thread due to which some MVPN features were only partially supported earlier.

    • As part of the update, these information will be retrieved from shard to main thread. MVPN upstream multicast hop (UMH) mechanisms, sender-based Reverse-path Forwarding (RPF), extranet, and bootstrap (BSR) using auto-export scenarios which depend on these information, will now be in parity/compliant with non-sharding deployments.

    You can use the “show mvpn c-multicast” command to display all the routes on the main thread.

    [See rib-sharding and show mvpn c-multicast.]

  • MVPN support for MLAN, PIM-DIM, and type 7 withdrawal on stream threshold (sharding and non-sharding) (PTX10001-36MR, PTX10003, PTX10004, PTX10008, QFX5130-32CD, and QFX5700). We support MVPN for MLAN, PIM-DIM, and type 7 withdrawal on stream threshold.

    [See source-active-advertisement, rib-sharding, and show mvpn c-multicast.]

  • Next-Generation MVPN (PTX10003). We 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.]

  • Next-generation MVPN Inter-AS option B with or without sharding enabled (PTX10001-36MR, PTX10004, PTX10008, and PTX10016).

    [See BGP-MVPN Inter-AS Option B Overview and Sharding and UpdateIO on cRPD.]

  • Prevent script execution based on current system memory usage (ACX7024, ACX7100-32C, ACX7100-48L, ACX7509, PTX10001-36MR, PTX10003, PTX10004, PTX10008, PTX10016, QFX5130-32CD, QFX5220, and QFX5700). You can configure the system memory usage threshold above which the device prevents the execution of certain op, event, SNMP, or Juniper Extension Toolkit (JET) scripts. [See Configure Script Start Options.]

  • Real-time Performance Monitoring (RPM) IPv6 source and target address support (ACX7024, ACX7100, ACX7509, PTX10001-36MR, PTX10003, PTX10004, PTX10008, PTX10016, QFX5130-32CD, QFX5220, and QFX5700). You can configure IPv6 source and target addresses for RPM. We've also added support for IPv6 addresses to the SNMP RFC2925a MIB control and results tables. For IPv6 RPM probes, you can enable timestamps only in the Routing Engine.

    [See source-address and target.]

  • Support for hybrid mode (Synchronous Ethernet and PTP) over LAG with PTP over Ethernet (PTX10001-36MR with LC1201-36CD). [See Hybrid Mode.]

  • Support for IPv6 payload-protocol match condition for management interface in ingress and/or egress direction and loopback interface in egress direction (ACX7100-32C, ACX7100-48L, ACX7509, ACX7024, PTX10001-36MR, PTX10003, PTX10004, PTX10008, PTX10016, QFX5700, QFX5220, and QFX5230-64CD).

    [See Firewall Filter Match Conditions for IPv6 Traffic.]

  • Support for PTP, Synchronous Ethernet, and hybrid mode over LAG (PTX10001-36MR). We support Precision Time Protocol (PTP), synchronous Ethernet, and hybrid mode over a LAG.

    [See Precision Time Protocol and Hybrid Mode.]

  • Support for QSFP-100G-4WDM40 optics (PTX10001-36MR).

    [See optics-options.]

  • Support for remote authorization on tacplus servers for locally certificate-based authenticated users (ACX7100-32C, ACX7100-48L, ACX7509, ACX7024, PTX10001-36MR, PTX10003, PTX10004, PTX10008, PTX10016, QFX5130-32CD, QFX5700, and QFX5220). We support remote authorization on TACPLUS servers for locally authenticated users by using certificate-based authentication.

    Note:

    You must configure the password under authentication-order when password-options is configured. The feature does not work in a local fallback scenario, because the password is not configured under authentication-order for a local fallback scenario.

    To configure remote authorization, include the tacplus-authorization option under the password-options configuration statement at the [edit system] hierarchy level.

    [See password-options.]

  • 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.