Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

New and Changed Features

 

This section describes the new features and enhancements to existing features in the Junos OS main release and the maintenance releases for PTX Series.

Release 17.1R2 New and Changed Features

  • There are no new features or enhancements to existing features for PTX Series in Junos OS Release 17.1R2.

Release 17.1R1 New and Changed Features

Hardware

  • P3-10-U-QSFP28 PIC (PTX3000 and PTX5000)—Starting in Junos OS Release 17.1R1, the P3-10-U-QSFP28 is supported on PTX3000 and PTX5000 routers that have third-generation FPCs installed. The P3-10-U-QSFP28 PIC has ten ports that are configurable as 10-Gigabit Ethernet, 40-Gigabit Ethernet, and 100-Gigabit Ethernet ports. The interface speeds are configured by port group—ports 0 through 4 and ports 5 through 9. To configure the port speed, use the following command:

    [See the PTX Series Interface Module Reference.]

  • Upgrade of FPCs in an operational PTX5000—Starting in Junos OS Release 17.1R1, you can upgrade the first-generation FPCs or second-generation FPCs to third-generation FPCs in an operational PTX5000.

    You might need to upgrade the following components before you can upgrade the FPCs in a PTX5000:

    • SIBs

    • Fan tray

    • Power distribution unit

    • Power supply module

    [See the PTX5000 Packet Transport Router Hardware Guide.]

  • New PIC P3-24-U-QSFP28 (PTX3000 and PTX5000)—Starting in Junos OS Release 17.1R1, the PIC P3-24-U-QSFP28 is supported on PTX3000 and PTX5000 routers. The P3-24-U-QSFP28 PIC has 24 ports configurable as either 10-Gigabit Ethernet ports or 40-Gigabit Ethernet ports.

    To install the P3-24-U-QSFP28 PIC, you must have a third-generation FPC installed on your system.

    [See the PTX Series Interface Module Reference.]

  • New SIB SIB3-PTX5K (PTX5000)—Starting in Junos OS Release 17.1R1, the SIB3-PTX5K SIB is supported on PTX5000 routers.

    [See the PTX5000 Packet Transport Router Hardware Guide.]



  • New FPCs FPC3-PTX-U1-L, FPC3-PTX-U1-R, FPC3-PTX-U2-L, FPC3-PTX-U2-R, FPC3-PTX-U3-L, and FPC3-PTX-U3-R (PTX5000)—Starting in Junos OS Release 17.1R1, the FPC3-PTX-U1-L, FPC3-PTX-U1-R, FPC3-PTX-U2-L, FPC3-PTX-U2-R, FPC3-PTX-U3-L, and FPC3-PTX-U3-R FPCs are supported on PTX5000 routers. The FPCs provide the following throughput:

    • FPC3-PTX-U1-L and FPC3-PTX-U1-R—1.0 Tbps

    • FPC3-PTX-U2-L and FPC3-PTX-U2-R—2.0 Tbps

    • FPC3-PTX-U3-L and FPC3-PTX-U3-R—3.0 Tbps

    When installing these third-generation FPCs on the PTX5000 chassis, you might need to install the following components:

    • SIB3-PTX5K SIBs

    • FAN3-PTX-H fan tray

    • PDU2-PTX-DC power distribution unit

    • PSM2-PTX-DC power supply module

    Note

    Some new features provided by these third-generation FPCs can be accessed only when the enhanced-mode statement is configured at the [edit chassis network-services] hierarchy level.

    [See the PTX5000 Packet Transport Router Hardware Guide.]

  • New horizontal fan tray FAN3-PTX-H (PTX5000)—Starting in Junos OS Release 17.1R1, the FAN3-PTX-H horizontal fan tray is supported on PTX5000 routers.

    [See the PTX5000 Packet Transport Router Hardware Guide.]

  • Third-generation FPCs (PTX3000)—Starting in Junos OS Release 17.1R1, third-generation FPCs are supported on PTX3000 routers. FPC3-SFF-PTX-U1 FPCs (model numbers FPC3-SFF-PTX-U1-L and FPC3-SFF-PTX-U1-R) support 1.0 Tbps of throughput. FPC3-SFF-PTX-U0 FPCs (model numbers FPC3-SFF-PTX-U0-L and FPC3-SFF-PTX-U0-R) support 500 Gbps of throughput.

    Third-generation FPCs (FPC3-SFF-PTX-U0 and FPC3-SFF-PTX-U1) are supported only in a PTX3000 with SIB3-SFF-PTX SIBs. Third-generation FPCs and FPC-SFF-PTX-P1-A first-generation FPCs can interoperate with each other in the same system.

    Note

    Some features provided by these third-generation FPCs can be accessed only when the enhanced-mode statement is configured at the [edit chassis network-services] hierarchy level.

    [See the PTX3000 Packet Transport Router Hardware Guide.]

  • SIB3-SFF-PTX SIBs (PTX3000)—Starting in Junos OS Release 17.1R1, SIB3-SFF-PTX SIBs are supported on PTX3000 routers. The SIB3-SFF-PTX SIBs are required with third-generation FPCs (FPC3-SFF-PTX-U0 and FPC3-SFF-PTX-U1). The SIB3-SFF-PTX SIBs also support FPC-SFF-PTX-P1-A first-generation FPCs—third-generation FPCs and FPC-SFF-PTX-P1-A first-generation FPCs can interoperate with each other in the same system.

    [See the PTX3000 Packet Transport Router Hardware Guide.]

  • Upgrading to third-generation FPCs and SIBs in an operational router (PTX3000)—Starting in Junos OS Release 17.1R1, you can upgrade to third-generation FPCs (FPC3-SFF-PTX-U0 and FPC3-SFF-PTX-U1) and SIB3-SFF-PTX SIBs in an operational PTX3000.

    [See the PTX3000 Packet Transport Router Hardware Guide.]

  • Support for P2-10G-40G-QSFPP and P2-100GE-OTN PICs on third-generation FPCs (PTX3000 and PTX5000)—Starting in Junos OS Release 17.1R1, the P2-10G-40G-QSFPP PIC is supported on PTX Series routers that have third-generation FPCs installed.

    [See the PTX Series Interface Module Reference.]

  • The P1-PTX-24-10G-W-SFPP PIC is supported on third-generation FPCs (PTX3000 and PTX5000)—Starting in Junos OS Release 17.1R1, the P1-PTX-24-10G-W-SFPP PIC is supported on PTX Series routers that have third-generation FPCs installed.

    [See the PTX Series Interface Module Reference.]

  • 5-port 100-Gigabit DWDM OTN PIC with CFP2 (PTX3000 and PTX5000)—Starting in Junos OS Release 15.1F6 and 17.1R1, the 5-port 100-Gigabit dense wavelength division multiplexing (DWDM) optical transport network (OTN) PIC (PTX-5-100G-WDM) with CFP2 analog coherent optical (CFP2-ACO) pluggable optics on third-generation FPCs is supported on the PTX3000 and PTX5000 series routers. The 5-port 100-Gigabit DWDM OTN PIC supports the following features:

    • Transparent transport of five 100-Gigabit Ethernet signals with optical channel transport unit, OTU4 (V) framing.

    • Dual-polarization quadrature phase shift keying (DP-QPSK) modulation with coherent receiver and soft-decision forward error correction (SD-FEC) for long-haul and metro applications.

    • International Telecommunication Union (ITU)-standard OTN performance monitoring and alarm management

    • Extensive optical, digital signal processing (DSP) and bit error ratio (BER) performance monitoring statistics for the optical link.

    [See the PTX5000 Packet Transport Router Hardware Guide.]

  • New Routing and Control Board RCB-PTX-X6-32G (PTX3000)—Starting in Junos OS Release 17.1R1, the Routing and Control Board (RCB) is supported on PTX3000 routers. The RCB combines the functionality of a Routing Engine, Control Board, and Centralized Clock Generator (CCG) in a single FRU. Although the functionality is combined in a single FRU, you must install an RCB companion card in the RE0 and RE1 slots adjacent to each RCB to enable the RCBs to communicate through the backplane.

Class of Service (CoS)

  • Support for shaping of traffic exiting third-generation FPCs on PTX3000 and PTX5000 routers (PTX Series)—Beginning with Junos OS Release 17.1R1, you can shape the output traffic of an FPC3 physical interface on a PTX3000 or PTX5000 packet transport router so that the interface transmits less traffic than it is physically capable of carrying. Shaping on all PTX Series packet transport router interfaces has a minimum rate of 1 Gbps and an incremental granularity of 0.1 percent of the physical interface speed after that (for example, 10 Mbps increments on a 10 Gbps interface). You can shape the output traffic of a physical interface by including the shaping-rate statement at the [edit class-of-service interfaces interface-name] or [edit class-of-service traffic-control-profiles profile-name] hierarchy level and applying the traffic control profile to an interface.

    [See shaping-rate (Applying to an Interface).]

  • ISSU Feature Explorer—Starting in Junos OS Release Feature Explorer, an interactive tool, to verify your device’s unified ISSU compatibility with different Junos OS releases.

    [See ISSU Feature Explorer.]

Interfaces and Chassis

  • Aggregated Ethernet Statistics Enhancements (PTX Series Routers)—Starting in Junos OS Release 17.1R1, multicast and broadcast counters from individual links are supported for aggregated Ethernet interfaces and are displayed in the show statistics ae interfaces command.

  • Support for different Ethernet rates in aggregated Ethernet interfaces (PTX5000)—Starting in Junos OS Release 17.1R1, the mixed statement is supported for the link-speed configuration statement on aggregated Ethernet interfaces. The mixed configuration statement is configured at the [edit interfaces interface-name aggregated-ether-options link-speed (speed | mixed)] hierarchy level.

    [See link-speed (Aggregated Ethernet).]

  • Support for configuring the port speed (PTX3000 and PTX5000)—Starting in Junos OS Release 17.1R1, the speed configuration statement is used to configure the port speed on interface modules that support multiple port speeds. The speed (10G | 40G | 100G) configuration statement is configured at the [edit chassis fpc slot-number pic pic-number port port-number] hierarchy level.

    [See speed.]

  • Support for configuring interface loopback (PTX3000 and PTX5000)—Starting in Junos OS Release 17.1R1, the loopback (local | remote) configuration statement is used to specify whether local or remote loopback is enabled. This allows you to test the transceiver cable connection from the far end to the retimer interface without changing the cable. The loopback (local | remote) configuration statement is configured at the [edit interfaces interface-name gigether-options] hierarchy level.

    See loopback (Local and Remote).]

  • Support for configuring the LED on a port to flash (PTX3000 and PTX5000)—Starting in Junos OS Release 17.1R1, the led-beacon command causes the LED for the specified port to flash green. This enables you to physically locate a specific optic port on the PIC. The led-beacon configuration statement is configured at the [edit interfaces interface-name (with port number)] hierarchy level.

    [See led-beacon.]

  • Synchronous Ethernet clock synchronization on third-generation FPCs (PTX3000)—Starting in Junos OS Release 17.1R1, Synchronous Ethernet clock synchronization is supported on third-generation FPCs (FPC3-SFF-PTX-U0 and FPC3-SFF-PTX-U1) on the PTX3000.

    [See Synchronous Ethernet Overview.]

  • Integrated photonic line card (IPLC) (PTX3000)—Starting in Junos OS Release 17.1R1, the PTX3000 can provide a fully integrated photonic line system for converged core and metro core packet optical networks running point-to-point and ring topologies. The following optical components are available for the PTX3000:

    • Integrated photonic line card (IPLC) base module—Provides the combined functionality of a 32-port reconfigurable optical add/drop multiplexer (ROADM), optical amplifier, optical equalizer, and optical channel monitor on a single card.

    • IPLC expansion module—Increases the channel capacity of the IPLC node to 64 channels.

    The standalone optical inline amplifier (ILA) provides periodic amplification of the optical line signal to enable long-distance transmission.

    To complete the optical solution, you can use Juniper Networks 100G Coherent transponders, along with the IPLC, optical ILA, and Connectivity Services Director (CSD), which runs on the Junos Space Network Management platform to provide an end-to-end, fully managed packet optical solution.

    You can configure, manage, and monitor the IPLC through Junos Space Connectivity Services Director 2.0, the Junos CLI, or your SNMP management system.

    [See PTX3000 Integrated Photonic Line Card Feature Guide.]

  • Support for configuring and managing Juniper Networks optical inline amplifier (ILA) through Junos OS CLI—Starting with Junos OS release 17.1R1, you can configure and manage certain capabilities of the optical inline amplifiers (ILA)s over the optical supervisory channel (OSC) of the PTX3000 integrated photonic line system, including authentication, performing resets, software upgrades, and performance monitors thresholds.

    [See Understanding Optical Supervisory Channel Communication in the Amplifier Chain.]

Management

  • gRPC support for the Junos Telemetry Interface (PTX Series)–The Junos Telemetry Interface supports using a set of gRPC remote procedure call interfaces to provision sensors, subscribe to, and receive telemetry data. gRPC is based on an open source framework and provides secure and reliable transport of data. Use the telemetrySubscribe RPC to specify telemetry parameters and stream data for a specified list of OpenConfig commands paths. Telemetry data is generated as Googl e protocol buffers (gpb) messages in a universal key/value format. If your Juniper Networks device is running a version of Junos OS with an upgraded FreeBSD kernel, you must download the Network Agent package, which provides the interfaces to manage gRPC subscriptions. The package is available on the All Junos Platforms software download URL on the Juniper Networks webpage. Support for gRPC for Junos Telemetry Interface was introduced in Junos OS Release 16.1R3.

    [See Understanding OpenConfig and gRPC on Junos Telemetry Interface.]

  • Support for Junos Telemetry Interface (PTX Series)—Starting in Junos OS Releases 15.1F3, 15.1F5, 15.1F6, and 16.1R3, you can use the Junos Telemetry Interface to export telemetry data from supported interface hardware. Sensor data, such as interface events, are sent directly to configured collection points without involving polling. FPC1, FPC2, and FPC3 are supported. For sensors that stream data through the User Datagram Protocol, all parameters are configured at the [edit services analytics] hierarchy level. For sensors that stream data through gRPC, use the telemetrySubscribe RPC to specify telemetry parameters. Not all hardware and sensors are supported in previous releases.

    [See Overview of the Junos Telemetry Interface.]

  • Support for adding non-native YANG modules to the Junos OS schema (PTX Series)—Starting in Junos OS Release 17.1R1, you can load custom YANG models on devices running Junos OS to add data models that are not natively supported by Junos OS but can be supported by translation. Doing this enables you to extend the configuration hierarchies and operational commands with data models that are customized for your operations. The ability to add data models to a device is also beneficial when you want to create device-agnostic and vendor-neutral data models that enable the same configuration or RPC to be used on different devices from one or more vendors. You can load custom YANG modules by using the request system yang add operational command.

    [See Understanding the Management of Non-Native YANG Modules on Devices Running Junos OS.]

MPLS



  • Egress peer engineering of service labels (BGP, MPLS) and egress peer protection for BGP-LU (PTX3000 and PTX5000)—Starting in Junos OS Release 17.1R1, you can enable traffic engineering of service traffic, such as MPLS LSP traffic between autonomous systems (ASs), using BGP labeled unicast for optimum utilization of the advertised egress routes. You can specify one or more backup devices for the primary egress AS boundary router. Junos OS installs the backup path in addition to the primary path in the MPLS forwarding table, which enables MPLS fast reroute (FRR) when the primary link fails. It provides support for the FRR protection backup scheme to do an IP lookup to determine a new egress interface.

    [See Egress Peer Traffic Engineering Using BGP Labeled Unicast Overview.]

  • Order-aware abstract hops for MPLS LSPs (PTX Series)—Starting in Junos OS Release 17.1, support is provided for abstract hops, which are user-defined router clusters or groups that can be sequenced and used for setting up a label-switched path (LSP). They resemble real-hop constraints.

    The router groups are created using constituent lists that include constituent attributes, which is a logical combination of the existing traffic engineering constraints, such as administrative groups, extended administrative groups, and Shared Risk Link Groups (SRLGs). Ordering among the router groups that satisfy the specified constituent attributes is achieved by using operational qualifiers in the abstract-hop definition.

    A path can use a combination of real and abstract hops as constraints. To configure abstract hops, you need to create constituent lists with traffic engineering attributes, include the lists in the abstract-hop definition, and define path constraints that use the abstract hops.

    [See Abstract Hops For MPLS LSPs Overview and Example: Configuring Abstract Hops for MPLS LSPs.]

Multicast

  • Support for next generation MVPN and Internet multicast (PTX5000 and PTX3000)—Starting in Junos OS Release 17.1R1, the mpls-internet-multicast routing instance type uses ingress replication provider tunnels to carry IP multicast data between routers through an MPLS cloud, using MBGP (or Next Gen) MVPN. Next generation MVPN is available only for PTX Series routers that have third-generation FPCs installed.

    Note

    Next-generation MVPN is supported only when the enhanced-mode statement is configured at the [edit chassis network-services] hierarchy level.

    [See Multiprotocol BGP MVPNs Overview.]

Network Management and Monitoring

  • Support for hrProcessorTable object (PTX Series)—Starting in Junos OS Release 17.1R1, support is provided for the hrProcessorTable object (object id: 1.3.6.1.2.1.25.3.3) described in the RFC2790, Host Resources MIB. The hrProcessorTable object provides the load statistics information per CPU for multi-core devices.

    [See SNMP MIB Explorer.]

  • Support for mplsL3VpnIfConfTable object (PTX Series)— Starting in Junos OS Release 17.1R1, support is provided for the mplsL3VpnIfConfTable object (object id: 1.3.6.1.2.1.10.166.11.1.2.1) described in RFC 4382, MPLS/BGP Layer 3 Virtual Private Network (VPN) MIB. The mplsL3VpnIfConfTable object represents the Layer 3 VPN enabled interfaces that are associated with a specific Virtual Routing and Forwarding (VRF) instance and shows the bitmask values of the supported protocols. The mplsL3VpnIfConfTable object creates entries for the interfaces that are associated with the VRF instances. If an interface is later removed from a VRF instance, the corresponding entry in the mplsL3VpnIfConfTable object gets deleted. To view details of the mplsL3VpnIfConfTable object, use the show snmp mib walk mplsL3VpnIfConfTable command.

    [See SNMP MIB Explorer.]

Routing Policy and Firewall Filters

  • Optimized performance for DSCP and traffic-class firewall filter match conditions (PTX Series with third-generation FPCs)—Starting in Junos OS Release 17.1R1, the promote dscp and promote traffic-class indicators are supported in firewall filters for IPv4 and IPv6 traffic. When either are applied to a filter, the entire filter is compiled in a way that optimizes its performance for the dscp or traffic-class match condition. The indicators are configured at the [edit firewall family (inet | inet6) filter filter-name] hierarchy level.

    Note

    Enabling the indicators requires that network services be set to enhanced-mode. Use of the indicators might impact the performance of the source-port match condition.

    [See Promote DSCP and Promote traffic-class.]

  • Support for firewall feature matching on gre-key (PTX3000 and PTX5000)—Starting in Junos OS Release 17.1R1 on PTX3000 and PTX5000, the promote gre-key statement is supported to configure gre-key as one of the matches in a filter. When promote gre-key is configured and gre-key is used in any of the terms in a filter, the entire filter is compiled in a way that optimizes its performance for gre-key matching. The promote gre-key configuration statement is configured at the [edit firewall family family-name filter filter-name] hierarchy level.

    [See promote gre-key.]

  • Support for filter-based generic routing encapsulation (GRE) for IPV4 and IPV6 tunneling (PTX Series with third-generation FPCs)—Starting in Junos OS Release 17.1R1, filter-based generic routing encapsulation (GRE) for IPV4 and IPV6 tunneling uses firewall filters to provide decapsulation of GRE traffic. The filter-based GRE decapsulation also supports routing-instance as an action.

    Note

    Configuring filter-based generic routing encapsulation (GRE) for IPV4 and IPV6 tunneling is supported only when the enhanced-mode statement is configured at the [edit chassis network-services] hierarchy level.

  • Support for configuring the GTP-TEID field for GTP traffic (PTX3000 and PTX5000)—Starting in Junos OS Release 17.1R1, the gtp-tunnel-endpoint-identifier statement is supported to configure the hash calculation of IPv4 or IPv6 packets that are included in the GPRS tunneling protocol–tunnel endpoint identifier (GTP-TEID) field hash calculations. The gtp-tunnel-endpoint-identifier configuration statement is configured at the [edit forwarding-options hash-key family inet layer-4] or [edit forwarding-options hash-key family inet6 layer-4] hierarchy level.

    [See gtp-tunnel-endpoint-identifier.]

Routing Protocols

  • Support for BGP to carry flow-specification routes (PTX5000 and PTX3000)—Starting in Junos OS Release 17.1R1, BGP can carry flow-specification network layer reachability information (NLRI) messages on PTX Series routers that have third-generation FPCs installed. Propagating firewall filter information as part of BGP enables you to propagate firewall filters against denial-of-service (DOS) attacks dynamically across autonomous systems.

    [See Example: Enabling BGP to Carry Flow-Specification Routes.]

  • Support for Bidirectional Forwarding Detection protocol intervals (PTX3000 and PTX5000)—Starting in Junos OS Release 17.1R1, longer configuration ranges for Bidirectional Forwarding Detection (BFD) protocol intervals are supported on PTX Series routers that have third-generation FPCs installed.

    Note

    The longer configuration ranges are supported only when the enhanced-mode statement is configured at the [edit chassis network-services] hierarchy level.

Security

  • Support for Secure Boot (PTX3000)—Starting in Junos OS Release 17.1R1, a significant system security enhancement, Secure Boot, has been introduced. The Secure Boot implementation is based on the UEFI 2.4 standard. The BIOS has been hardened and serves as a core root of trust. The BIOS updates, the bootloader, and the kernel are cryptographically protected. No action is required to implement Secure Boot.

Services Applications

  • Support for inline-jflow (PTX Series routers with third-generation FPCs)—Starting in Junos OS Release 17.1R1, you can use inline-jflow’s export capabilities with IP Flow Information Export (IPFIX) to define a flow record template suitable for IPv4 or IPv6 traffic on PTX Series routers that have third-generation FPCs installed.

    [See Monitoring Network Traffic Flow Using Inline Flow Monitoring on PTX Series Routers.]

User Interface and Configuration

  • Monitoring, detecting, and taking action on degraded physical 100-Gigabit Ethernet links to minimize packet loss (PTX3000 and PTX5000)—Starting with Junos OS Release 17.1R1, you can monitor physical link degradation (indicated by bit error rate (BER) threshold levels) on Ethernet interfaces, and take corrective actions if the BER threshold value drops to a value in the range of 10-13 to 10-5.

    The following new configurations have been introduced at the [edit interfaces interface-name] hierarchy level to support the physical link degrade monitoring and recovery feature on Junos OS:

    • To monitor physical link degrade on Ethernet interfaces, configure the link-degrade-monitor statement.

    • To configure the BER threshold value at which the corrective action must be triggered on or cleared from an interface, use the link-degrade-monitor thresholds (set value | clear value) statement.

    • To configure the link degrade interval value, use the link-degrade-monitor thresholds interval value statement. The configured interval value determines the number of consecutive link degrade events that are considered before any corrective action is taken.

    • To configure link degrade warning thresholds, use the link-degrade-monitor thresholds (warning-set value | warning-clear value) statement.

    • To configure the link degrade action that is taken when the configured BER threshold level is reached, use the link-degrade action media-based statement.

    • To configure the link degrade recovery options, use the link-degrade recovery (auto interval value | manual) statement.

    You can view the link recovery status and the BER threshold values by using the show interfaces interface-name command.