Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Junos OS Release Notes for PTX Series Packet Transport Routers

 

These release notes accompany Junos OS Release 16.2R2 for the PTX Series. They describe new and changed features, limitations, and known and resolved problems in the hardware and software.

You can also find these release notes on the Juniper Networks Junos OS Documentation webpage, located at https://www.juniper.net/documentation/software/junos/.

Note

Unified ISSU is not supported in Junos OS Release 16.2R2.

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

Release 16.2R2 New and Changed Features

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

Release 16.2R1 New and Changed Features

Hardware

  • The Interoperation for third-generation FPCs with first-generation and second-generation FPCs (PTX5000)—Starting in Junos OS Release 16.2R1, when third-generation FPCs are installed on a chassis with first-generation and second-generations FPCs, the FPCs can interoperate with each other.

    Note

    For the third-generation FPCs to interoperate with the older generation FPCs, the enhanced-mode statement cannot be configured on the chassis.In such a scenario, the third-generation FPCs can provide the same functionality as the first-generation and second-generation FPCs. Any advanced features that third-generation FPCs might provide are disabled.

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

  • New P3-15-U-QSFP28 PIC (PTX5000)—Starting in Junos OS Release 16.2R1, the PIC P3-15-U-QSFP28 is supported on PTX5000 routers that have third-generation FPCs installed.

    Note

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



    Following is the available port configuration for each FPC:

    • FPC3-PTX-U1-L and FPC3-PTX-U1-R—10 ports configurable as 10-Gigabit Ethernet ports (using a 4x breakout cable), 40-Gigabit Ethernet ports, or 100-Gigabit Ethernet ports.

    • FPC3-PTX-U2-L and FPC3-PTX-U2-R—10 ports configurable as 10-Gigabit Ethernet ports (using a 4x breakout cable), 40-Gigabit Ethernet ports, or 100-Gigabit Ethernet ports.

    • FPC3-PTX-U3-L and FPC3-PTX-U3-R—15 ports configurable as 10-Gigabit Ethernet ports (using a 4x breakout cable), 40-Gigabit Ethernet ports, or 100-Gigabit Ethernet ports.

High Availability and Resiliency

  • ISSU Feature Explorer—The ISSU Feature Explorer is an interactive tool that you can use to verify your device’s ISSU compatibility with different JUNOS releases.

    [See ISSU Feature Explorer.]

Interfaces and Chassis

  • Support for unicast RPF (PTX Series)—Starting in Junos OS Release 16.2R1, you can configure unicast reverse path forwarding (RPF) to reduce the impact of denial-of-service (DoS) attacks on PTX Series routers that have third-generation FPCs installed.

    Note

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

  • Support for DCU and SCU accounting (PTX Series)—Starting in Junos OS Release 16.2R1, destination class usage (DCU) and source class usage (SCU) accounting are supported on PTX Series routers that have third-generation FPCs installed.

    Note

    DCU and SCU accounting are supported only when the enhanced-mode statement is configured at the [edit chassis network-services] hierarchy level.

MPLS

  • Support for IPv6 tunneling over an MPLS-based IPv4 network (PTX Series)—Starting in Junos OS Release 16.2R1, IPv6 tunneling over an MPLS-based IPv4 network using IPv6 Provider Edge (6PE) is supported on PTX Series routers that have third-generation FPCs installed.

Network Management and Monitoring

  • Support for accounting profiles (PTX Series)—Starting in Junos OS Release 16.2R1, you can configure accounting profiles to collect data on PTX Series routers that have third-generation FPCs installed.

    Note

    Configuring accounting profiles is supported only when the enhanced-mode statement is configured at the [edit chassis network-services] hierarchy level.

Routing Policy and Firewall Filters

  • Support for filter-based generic routing encapsulation (GRE) for IPV4 and IPV6 tunneling (PTX Series with third-generation FPCs)—Starting in Junos OS Release 16.2R1, 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 the no-decrement-ttl tunneling attribute (PTX Series)—Starting in Junos OS Release 16.2R1, you can configure the no-decrement-ttl tunneling attribute for filter-based generic routing encapsulation (GRE) for IPV4 and IPV6 tunneling.

    Note

    The no-decrement-ttl tunneling attribute is supported only when the enhanced-mode statement is configured at the [edit chassis network-services] hierarchy level.

VPNS

  • Support for Layer 3 VPN (PTX Series)—Starting in Junos OS Release 16.2R1, Layer 3 VPN is supported on PTX Series routers that have third-generation FPCs installed.

    Note

    Layer 3 VPN is supported only when the enhanced-mode statement is configured at the [edit chassis network-services] hierarchy level.

Changes in Behavior and Syntax

This section lists the changes in behavior of Junos OS features and changes in the syntax of Junos OS statements and commands in Junos OS Release 16.2R2 for the PTX Series.

General Routing

  • Support for deletion of static routes when the BFD session goes down (PTX Series)—Starting with Junos OS 16.2R2, the default behavior of the static route at the [edit routing-options static static-route bfd-admin-down] hierarchy level is active. So, the static routes are deleted when the BFD receives a session down message.

Interfaces and Chassis

  • Message now displayed when SIB autohealing is complete (PTX3000 and PTX5000)—Starting in Junos OS Release 16.2R2, the output of show chassis fabric errors autoheal displays a message when SIB autohealing is complete, as shown in the following example:

Management

  • Support for status deprecated statement in YANG modules (PTX Series)—Starting with Junos OS Release 16.1R2, Juniper Networks YANG modules include the status deprecated statement to indicate configuration statements, commands, and options that are deprecated.

Network Management and Monitoring

  • Possible change to the object identifier (PTX Series)—Starting in Junos OS Release 16.2R2, the many warnings that occurred previously during MIB loading in the SNMP client has been reduced. This update could change the resulting OID depending on the SNMP client-loading logic. For example, jnxProductACX1000 is defined under the two following nodes:

    • jnxProductACX1000 OBJECT IDENTIFIER ::= { jnxProductVariationACX 1 }

    • jnxProductACX1000 OBJECT IDENTIFIER ::= { jnxProductVariationACX1000 1 }

    Because the second definition is the duplicate, it is removed. Previously, the SNMP client referred to the second OID based on MIB loading logic, and then you would see a change in OID for the client.

  • Improved usage of wildcard in SNMP notify-filter OID (PTX Series)—Starting in Junos OS Releases 13.3R10 and 16.2R2, the filter subtree using an asterisk (*) is correctly read as a wildcard and not as ASCII value of 42. The problem occurred in the following routers:

    • M Series running Junos OS Release 11.4R13.5, 13.3R7-S1

    • ACX2000 Series running Junos OS Release 12.3X54-D20.9

    • MX Series running Junos OS Release 14.1X50-D125

    A sample of the change appears in the output of the show snmp v3 command:

    Old Output

    New Output

  • Update to SNMP support of apply-path statement (PTX Series)—In Junos OS Release 16.2R2, SNMP implementation for the apply-path configuration statement supports only two lists:

    • apply-path "policy-options prefix-list <list-name> <*>"

      This configuration has been supported from day 1.

    • apply-path "access radius-server <*>"

      This configuration is supported as of this release.

  • Juniper MIBs Loading Errors Fixed (PTX Series)—In junos OS Release 16.2R1, duplicated entries and errors while loading MIBs on ManageEngine MIB browser are fixed for the following MIB files:

    • jnx-gen-set.mib

    • jnx-ifotn.mib

    • jnx-optics.mib

    [See MIB Explorer.]

  • SNMP syslog messages changed (PTX Series)—In Junos OS Release 16.2R2, two misleading SNMP syslog messages were rewritten to accurately describe the event:

    • OLD --AgentX master agent failed to respond to ping. Attempting to re-register

      NEW –- AgentX master agent failed to respond to ping, triggering cleanup!

    • OLD –- NET-SNMP version %s AgentX subagent connected

      NEW --- NET-SNMP version %s AgentX subagent Open-Sent!

    [See the MIB Explorer.]

Platform and Infrastructure

  • Improvements to MIB validation during Junos OS build (libjsnmp) (PTX Series)— Many warnings can be ignored if produced while MIBs are compiling. The following warnings should be considered as errors because they can break the build:

    [0-9]:.*failed to locateAn OID failed to be located.
    [0-9]:.*redefinition of identifierRedefinition of OIDs found in jnx-chas-defines.
    [0-9]:.*sequence-type-mismatchType mismatch found in sequence syntax of the table and actual OID type.
    [0-9]:.*cannot be imported from moduleMIB failed to import because order is not defined properly.

Routing Protocols

  • Change in default behavior of router capability (MX Series)—Starting in Junos OS Release 15.1F7, 16.1R4, 16.2R2, 16.1X65, and 17.1R1 and later, router capability TLV distribution flag (S-bit), which controls IS-IS advertisements, will be reset so that the segment routing capable sub-TLV is propagated throughout the IS-IS level and not advertised across IS-IS level boundaries.

System Logging

  • Changes in syslog MIB timeout messages (all routers and switches)—Starting in Junos OS Release 16.2, timeout messages logged in /var/log/messages for requests sent from snmpd to mib2d have changed:.

    • The frequency of AgentX timeout logs has been reduced.

      When a request sent from snmpd to mib2d times out, a timeout message is put in the messages log. Previously, one timeout message was written in the messages log for each such request, leading to flooding the log file with repetitive messages. Starting in Junos OS Release 16.2, one syslog message is created for all requests that time out at the same instant.

    • The “clearing the current stats” part in the logs has been removed.

      The timeout message has been changed because the subagents stats on timeout are no longer cleared. For example, the following is an old log message:

      Jul 11 20:56:50 re1-bx04.cbf14 snmpd[2436]: %-LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX session, /var/run/mib2d-11, noticed request timeout. Clearing the current stats. Request PDUs: 1482, Response PDUs: 471, Request variables: 37186, Response variables: 11866, Average response time: 1826.42, Maximum response time: 40162.90

      New messages read as follows:

      Jul 16 10:32:30 Gladiator snmpd[2241]: %-LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX session, /var/run/mib2d-11, noticed 3 request timeout.

      Jul 16 10:32:30 Gladiator snmpd[2241]: %-LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX session, /var/run/mib2d-11, noticed 1 request timeout.

      Jul 16 10:32:30 Gladiator snmpd[2241]: %-LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX session, /var/run/mib2d-11, noticed 1 request timeout.

User Interfaces and Configuration

  • Integers in configuration data in JSON format are displayed without quotation marks (PTX Series)—Starting in Junos OS Release 16.2R2, integers in Junos OS configuration data emitted in JavaScript Object Notation (JSON) format are not enclosed in quotation marks. Prior to Junos OS Release 16.2R2, integers in JSON configuration data were treated as strings and enclosed in quotation marks.

  • Changes to the XML and JSON output when displaying the differences between the candidate and active configurations (PTX Series)—Starting in Junos OS Release 16.2R2, when you compare the candidate and active configurations and display the differences in XML or JSON format, for example by using the show | compare | display (json | xml) CLI command or the <get-configuration compare="rollback" format="(json | xml)"> RPC, the device omits the <configuration> tag in the XML output and omits the configuration object in the JSON output if the comparison either returns no differences or if the comparison returns differences for only non-native configuration data, for example, configuration data associated with an OpenConfig data model.

Known Behavior

There are no known limitations in Junos OS Release 16.2R2 for PTX Series.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

Known Issues

This section lists the known issues in hardware and software in Junos OS Release 16.2R2 for the PTX Series.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

General Routing

  • PTX 100GbE-LR4 interfaces may flap when the reference clock switches over from "line clock" to "holdover" initiated by offlining the PIC, on which the "line clock" sources reside. When PTX 100GbE-LR4 interface uses the "line clock" sources and when it does not have any external clocks from BITS-a or BITS-b, offlining the PIC, which is recovering clock from line, brings the "line clock" down and the reference clock is switched from "line clock" to "holdover". This reference clock transition may cause a large clock phase-shift in the 100GbE-LR4 CFP modules, and this phase-shift may cause the output optical pulse waveform distortion on the 100GbE-LR4 interfaces. Hence, it results in interface flap. This issue cannot be fixed by software due to hardware limitation. PR1130403

  • While upgrading from 15.1F based images to 16.x+ images or downgrading from 16.x+ images to 15.1F based images, if validate option is enabled, there may be a chassisd crash and upgrade/downgrade will fail. This issue should not be seen if both base and target images are from 15.1F train or 16.x+ train. PR1171652

  • Major errors might be seen on MPC3/FPC3 with 1X100 and 5x100 DWDM MIC/PIC. user@router> show chassis alarms no-forwarding 1 alarms currently active Alarm time Class Description <timestamp> . Major FPC 3 Major Errors The following messages are seen in the logs: fpc3 Cmerror Op Sub Set: CORDOBA : CORDOBA(3/0) link 0 : DSP loss of lock fpc3 Cmerror Op Sub Set: CORDOBA : CORDOBA(3/0) link 0 : DFE tuning failed alarmd[16241]: Alarm set: FPC color=RED, class=CHASSIS, reason=FPC 3 Major Errors craftd[15906]: Major alarm set, FPC 3 Major Errors. PR1212089

MPLS

  • LDP to BGP stitching with eBGP indirect nexthop having implicit null label had never worked on PTX Series routers. It works only when BGP indirect nexthop has real label. Workaround (1) Ensure the peer advertises real label by adding another router between the egress and Ingress PE. (2) Use IBGP that gets resolved over LDP or RSVP-TE LSPs. This will ensure that the BGP indirect nexthop has real label. PR1254702

Platform and Infrastructure

  • On PTX Series router, parity memory errors might happen in pre-classifier engines within a MPC. Packets will be silently discarded, as such errors are not reported and makes it harder to diagnose. After the change in this PR, CM-ERRORs, such as syslogs and alarms, will be raised when parity memory errors occur. PR1059137

Resolved Issues

This section lists the issues fixed in the Junos OS main release and the maintenance releases. The identifier following the description is the tracking number in the Juniper Networks Problem Report (PR) tracking system.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

Resolved Issues: 16.2R2

General Routing

  • Under certain conditions in PTX Series platform with non NG-RE, the master Routing Engine may fail to relinquish the mastership upon Control Board (CB) internal switch failure. PR1132557

  • On an FPC with Express chipset using multicast with an aggregate interface environment. When there are multiple network events, such as a multicast route churn or flap, especially when these changes are of multicast next-hop on an aggregate Ethernet (AE), the FPC may restart unexpectedly. PR1196644

  • On PTX Series routers, when an ARP entry is learned through the aggregated Ethernet interface, and a route is pointing to that ARP nexthop, the ARP entry might not expire even though the ARP IP is no longer reachable. This issue is due to the route next hop on aggregated Ethernet interface getting stuck in unicast state even if the remote end is not reachable, and the RPD never gets to determine that ARP is invalid. The route next hop on the aggregated Ethernet interface should be shown in 'hold' state when the remote end is not reachable. PR1211757

  • A higher number of QoS drops may be seen during large micro-bursts of traffic on the low priority queues on PTX Series FPC type 3 than FPC type 1 or 2. This is due to the delay band-width buffer being reduced to ~64ms on the PTX FPC type 3 versus ~200ms on PTX FPC type 1 or 2. PR1223440

  • On PTX Series routers, if you repeatedly disable and enable a physical interface, memory leak of daemon l2ald (Layer 2 address learning daemon) might occur. PR1224271

  • PTX Series FPC3 might receive noise on the FPC console port, and interpret it as valid signals. This might cause login fails on the console port, core files, or even reloads. PR1224820

  • When a PTX Series router has inline J-Flow configured, and the interfaces where sampling is configured are receiving TCP traffic, "DMA - memory map failed" error messages might be reported by the FPC3-PTX-U2 card. PR1227687

  • In a third generation PTX3000 system (PTX3K + FPC3 + SIB3), due to a timing issue, 10x100GE PIC may not come online upon a FPC restart and will remain offline with “FPC X PIC 0 Failure” message seen in alarms. PR1236048

  • The "show route forwarding-table all" command is needed for tlb (Traffic load balancer) and srd (Service Redundancy Daemon) while these daemons are running. And these outputs are being collected from tlb script as well as srd script. The "show system commit" command is getting executed from default-junos-show script. When the CLI command "request support information" is issued, "show route forwarding-table all" and "show system commit" are taken twice by RSI (Request Support Information). PR1236180

  • When the user configures a TPID value other than 0x8100 on a single tagged interface with the configuration command "vlan-tags outer <TPID>. <VLAN-ID>” , the TPID value 0x8100 will be used instead of the user-specified TPID value. PR1237687

  • This issue occurs on PTX Series routers with a unilist application (such as ECMP) with member links with MPLS LSPs. If one member link has MPLS LSP protection configured and another does not, the router might send the wrong packets. PR1239634

  • This is a day one behavior where there is traffic from multiple Ingress Packet Forwarding Engines to single Egress Packet Forwarding Engine, and the scheduler assign will have extreme rate distribution (very high to one queue compare to others), you see the high configured queue will not get all its shared of Tx-rate config. This is due to small size OQB on GS scheduler (an ASIC property).PR1241291

  • Junos telemetry interface client might notice slower arrival of packets for the configured sensors. PR1243810

  • On PTX Series routers, add 'set' parameter (optional) to CLI 'request system software add'. It provides a way to install multiple software packages and software add-on packages at the same time. PR1246675

  • While processing lookup results, IRP block would raise an interrupt upon detecting an error condition. The interrupt would be active until the trapcode error is read. Under certain condition, software is not reading this trapcode error upon IRP interrupt. This issue causes the following syslog message to be generated:

    fpc5 INTR: throttle 60sec PECHIP[2]:pe.irp.intr.status:ap0_trap(0): (Count:1)

    fpc5 INTR: throttle 3630sec PECHIP[2]:pe.irp.intr.status:ap0_trap(0): (Count:3434)

    fpc5 INTR: throttle 3600sec PECHIP[2]:pe.irp.intr.status:ap0_trap(0): (Count:6841)PR1256736

  • The following log message may be printed frequently during normal operation on the backup Routing Engine of a PTX5000 router when the Routing Engine type is RE-DUO-C2600:

    /kernel: mastership: sent other RE mastership loss signal PR1260884

  • On PTX Series routers, if running interfaces on QSFP28 PIC in 10G mode, some of the interfaces on the QSFP28 PIC may not come up after a system reboot or PIC restart. PR1263413

  • This only affects PTX5000 and PTX3000 platforms with third-generation FPCs. Software periodically monitors voltages on the FPCs to check if they are within the proper range. This change adjusts the expected values for voltages on certain power rails of the FPCs. In rare cases it is possible that a marginal FPC was operating inside the older limits but outside the new limits, in which case a new chassis alarm will be raised for that FPC. PR1263675

  • If pio errors are encountered at a certain stage during asic initialization, some data structures are not correctly updated. Later an attempt to recover from the error automatically may detect data structure inconsistencies and abort, resulting in a ukern core file. PR1268253

  • In PTX Series routers equipped with a next-generation Routing Engine (RE-S-X6-64G, REMX2K-X8-64G, RE-PTX-X8-64G/CB2-PTX), the following log messages might be displayed as error messages after a 'commit' command is executed: sdk-vmmd: %USER-3: is_platform_rainier: Platform found as rainier. PR1271134

Class of Service (CoS)

  • The following error log message might be seen with hierarchical CoS and strict-high scheduling configured:

    Dec 27 11:08:02.293 mand-re0 fpc1 cos_check_temporal_buffer_status: IFD ge-1/2/1 IFL 358: Delay buffer computation incorrect.^M If hierarchical scheduler is configured for an IFD and if guaranteed rate is not set for an IFL under this IFD, then the temporal buffer configured.

    The display of this error message is valid when the guaranteed rate is '0', but it is not valid when 'guaranteed rate' is disabled. PR1238719

Infrastructure

  • In an RSVP scenario, provision RSVP LSP with ldp-tunneling enabled and the LSPs configured with link protection, continuous kernel logs and LDP statistics timeout errors might be seen when executing 'show ldp traffic-statistics.' PR1215452

Interfaces and Chassis

  • Configuring ODU FRR under otn-options for 2x100G DWDM PIC is an unsupported command on the PTX Series router; incorrectly adding such a configuration could result in an FPC crash and restart. PR1038551

  • When QSFP28-100GBASE-LR4/QSFP+-40G-LPBK PICs speed is configured at chassis hierarchy. DCD was not reading the speed specified in set chassis fpc <fpc> pic <pic> port <port> speed <speed> As a result, when IFDs created using this configuration are added in the aggregated Ethernet bundle along with IFD of any other kind of pics, DCD gave a commit error. DCD was able to read the speed for other IFDs in the aggregated Ethernet bundle and was not able to read the speed of IFDs on QSFP28 PIC. Therefore, the following speed mismatch commit error was seen: Interface ae0 with child links of mixed speed but link-speed mixed is not configured. PR1167780

MPLS

  • When there are statically configured ingress and transit LSPs, due to timing issue, there could be a scenario wherein the selfID used by the transit LSP might be allocated to the ingress LSP. Ingress static LSP does not reuse the same selfID during rpd restart, whereas the transit static LSP tries to reuse the same selfID. This leads to rpd crash due to the collision when the transit LSP tries to reuse the same selfID. PR1084736

  • After MBB, new LSP will not have "explicit route." PR1207039

  • In an MPLS OAM environment, a rare timing condition can result in rpd crash when a memory clean task is delayed. PR1233042

  • On PTX Series routers, the LDP may fail to install LDP route in inet.3 table if IS-IS is configured with source-packet-routing and ldp-tunneling is enabled, which might cause the LDP to fail to install routes when IS-IS routes are present. PR1248336

  • When the rpd daemon is terminating, the process of signaling the deletion of all RSVP LSPs may take so long that a watchdog timer is firing, resulting in an rpd core. PR1257367

Platform and Infrastructure

  • In a very rare scenario, during TAC accounting configuration change, the auditd process crashes due to a race condition between auditd and its sigalarm handler. PR1191527

  • A race condition occurs between database creation and database access. This issue is reproducible, and there is no functional impact of the core. PR1225086

  • The mgd might crash after executing the command "show ephemeral-configuration | display inheritance". This is an unsupported option. PR1258823

Routing Protocols

  • When multiple labels become stale in stale-label-holddown-duration (default 60 secs), it restarts the timer and accumulates all the stale-labels without getting deleted. This might cause memory for allocating labels to be exhausted and then MPLS traffic might be affected due to abnormal/failing label allocation. PR1211010

  • In the rare scenario with a maximum number of routes in the BGP RIB_OUT table (for example: if there are more than 700K BGP routes in route table), if flapping BGP protocol, it might cause the rpd process to crash. PR1222554

  • On Junos OS devices during a graceful restart, the restarting node might send "End of RIB" maker too soon to its helper nodes, before the actual route updates are completed causing traffic loss. PR1225868

  • On all platforms, if MPLS goes down due to link, FPC reboot, or restart, rpd core files could be seen. PR1228388

Resolved Issues: 16.2R1

Forwarding and Sampling

  • Sampling Route-Record Daemon (SRRD) process does not delete routes when the DELETE is received from RPD in few configuration cases. This results in build-up of memory in SRRD daemon and once SRRD reaches the limit, it crashes and restarts itself. This happens only when one certain family is not configured on all of the FPC clients (for example, FPC with inline J-Flow enabled or PIC with PIC-based sampling enabled is one client). For example, only IPv4 family is configured in all the clients, and IPv6 and MPLS families are not configured for sampling in any of the clients. PR1180158

General Routing

  • OK LED on the CB not lighting up in the following scenarios:

    • When you insert only one Routing Engine or CB on the router and power on . Only the Master LED lights up but not the OK LED

    • When you test the issue with either Routing Engine or CB on slot 0 or slot 1, leaving the other slot empty.

    • When both slots have the Routing Engine or CB inserted, the problem is not seen. Master and OK LED is lightup on the master CB, and the backup CB has the OK LED lit up.

    Engineering is debugging this cosmetic issue. PR1115148

  • The clear services accounting flow command should not be used in Junos OS Release 15.1F4 or Junos OS Release 15.1F5 on inline J-Flow on PTX5000 router for PTX Series. This command is specific to J-Flow and is not supported in these releases. PR1117181

  • After booting up FPC3 on a PTX Series router, the internal link communication between some chips on the FPC might fail to establish and, as a result, the Host Loopback Wedge error message is displayed. PR1171101

  • In a very rare cases, multiple Routing Engine switchovers may result in SNGPMB crash. PR1176094

  • On a PTX Series router, with FPC3 card, after soft restart of SIBs (it could be GRES or performing "restart chassis-control immediately" if on the same Routing Engine), then offline/online of any SIB, traffic loss is observed. PR1177652

  • For FPC3 on a PTX Series router, in rare scenarios, while restarting FPC, a PIC index mismatch issue might result in FPC crash if it is configured with inline-JFlow. PR1183215

  • The FPC might generate a core file when issuing clear threads and show threads simultaneously. PR1184113

  • SIB Link errors are seen during GRES, when mixed FPC types are present with EIP mode enabled. PR1192348

  • On a PTX Series router, when Bits external clock is down/up, the incorrect SNMP trap, jnxFruRemoval(CB), is generated. jnxExtSrcLockAcquired should be the correct one.

    • Correct trap: Name: "jnxExtSrcLockAcquired"

      OID: "1.3.6.1.4.1.2636.4.2.5"

    • Incorrect trap: Name: "jnxFruRemoval"

      OID: "1.3.6.1.4.1.2636.4.1.5"

    PR1195686

  • On a PTX Series router with FPC3, if inline J-Flow is enabled with high scale of IPv4 and IPv6 routes and aggressive route flapping, a multiservice crash and FPC reboot might be triggered. PR1196793

  • When inline sampling is configured in a PTX Series router with third-generation FPC, a debug messageis logged even though a debug command is not issued. PR1197695

  • On a PTX Series router with FPC type 1 and FPC type 2, if there is a problem with the ASIC in the FPC, might cause FPC being disconnected from Routing Engine. PR1207153

  • A vulnerability in IPv6 processing has been discovered that might allow a specially crafted IPv6 Neighbor Discovery (ND) packet to be accepted by the router rather than discarded. The crafted packet, destined to the router, will then be processed by the Routing Engine. A malicious network-based packet flood, sourced from beyond the local broadcast domain, can cause the Routing Engine’s CPU to spike, or cause the DDoS protection ARP protocol group policer to engage. When this happens, the DDoS policer may start dropping legitimate IPv6 neighbors as the legitimate ND packet times out. Refer to JSA10749 for more information. PR1207527

  • On PTX Series routers, when an FPC type 1 or 2 is restarted, CoS profiles can be applied incorrectly to certain virtual output queues (VOQs). This can lead to RED drops on that VOQs for traffic those enters the router on the restarted FPC. PR1211509

  • In some conditions where the fan tray is not properly seated in PTX Series routers, the present PIN from the fan tray might not be detected and the fan tray is declared Absent in the output of theshow chassis environment command. However, the alarm for this condition is not raised under "show chassis alarms" if the alarm is to be raised during a system reboot. PR1216335

  • Power budget values for PTX 5K chassis, FPC, and PICs have been revised. For routers operating on limited power, this can change the point where alarms for power-over-budget or insufficient power are raised or cleared. PR1216404

  • The options accepted for "set chassis fpc <n> license-mode" configuration of PTX FPC3 are changed to "IR" and "R". PR1221096

Interfaces and Chassis

  • If QSFP28-100GBASE-LR4/QSFP+-40G-LPBK PICs speed is configured at chassis hierarchy. DCD was not reading speed specified in (set chassis fpc <fpc> pic <pic> port <port> speed <speed>) and as a result, when IFDs created using this configuration are added in AE bundle along with IFD of any other kind of pics, DCD used to give commit error. DCD was able to read speed for other IFDs in AE bundle and was not able to read speed of IFDs on QSFP28 PIC and hence use to complain about speed mismatch Commit error: Interface ae0 with child links of mixed speed but link-speed mixed is not configured PR1167780

MPLS

  • This behavior is Junos OS 16.1 release specific. When an ingress side link failure and LSP uses bypass path, LSR(DUT) cannot send proper "RSVP RRO" even if egress side topology changes. Please refer the following example. --- example --- 1. This is initial state. LSP of RRO has Link A and B IP address. bypass bypass Link C Link D +--------------------+ +------------------+ | | | | [Ingress LER] [ LSR ] [ Egress LER] | | | | +--------------------+ +------------------+ Link A Link B strict path strict path 2. Link A is down. LSP of RRO has Link B and C IP address because LSR sends out RSVP RESV including proper RRO to Ingress LER. bypass RSVP RESV bypass Link C <-----+ Link D +--------------------+ | +------------------+ | | | | | [Ingress LER] [ LSR ] [ Egress LER] | | | | +--------- X --------+ +------------------+ Link A Link B strict path strict path 3. Link B is down. LSP of RRO has Link B and C IP address because LSR does not send out RSVP RESV including proper RRO to Ingress LER. (wrong) bypass RSVP RESV bypass Link C <-----+ Link D +--------------------+ | +------------------+ | | | | | [Ingress LER] [ LSR ] [ Egress LER] | | | | +--------- X --------+ +-------- X -------+ Link A Link B strict path strict path PR1207862

Platform and Infrastructure

  • In a very rare scenario, during TAC accounting configuration change, the auditd daemon crashes because of a race condition between auditd and its sigalarm handler. PR1191527

  • On a PTX Series router with chassis network-services enhanced-mode configured, the default policy junos-ptx-series-default is not loaded correctly in case of some configuring operations, which can cause BGP routes not to be installed in the forwarding table as expected. To avoid this issue, reboot the router after any configuring operations on network-services. PR1204827

  • MIB file was updated to use official names of released products only. No queryable objects were changed. PR1219906

User Interface and Configuration

  • When persist-groups-inheritance is configured and you issue a rollback, you might see that the configuration is not propagated properly after a commit. PR1214743

Documentation Updates

There are no errata or changes in Junos OS Release 16.2R2 documentation for PTX Series.

Migration, Upgrade, and Downgrade Instructions

This section contains the procedure to upgrade Junos OS, and the upgrade and downgrade policies for Junos OS for the PTX Series. Upgrading or downgrading Junos OS can take several hours, depending on the size and configuration of the network.

Upgrading Using Unified ISSU

Caution

Unified ISSU is not supported in Junos OS Release 16.2R1.

Unified in-service software upgrade (ISSU) enables you to upgrade between two different Junos OS releases with no disruption on the control plane and with minimal disruption of traffic. Unified in-service software upgrade is only supported by dual Routing Engine platforms. In addition, graceful Routing Engine switchover (GRES) and nonstop active routing (NSR) must be enabled. For additional information about using unified in-service software upgrade, see the High Availability Feature Guide for Routing Devices.

For information on ISSU support across platforms and Junos OS releases, see the In-Service Software Upgrade (ISSU) Web application.

Upgrading a Router with Redundant Routing Engines

If the router has two Routing Engines, perform a Junos OS installation on each Routing Engine separately to avoid disrupting network operation as follows:

  1. Disable graceful Routing Engine switchover (GRES) on the master Routing Engine and save the configuration change to both Routing Engines.

  2. Install the new Junos OS release on the backup Routing Engine while keeping the currently running software version on the master Routing Engine.

  3. After making sure that the new software version is running correctly on the backup Routing Engine, switch over to the backup Routing Engine to activate the new software.

  4. Install the new software on the original master Routing Engine that is now active as the backup Routing Engine.

For the detailed procedure, see the Installation and Upgrade Guide.

Basic Procedure for Upgrading to Release 16.2

When upgrading or downgrading Junos OS, use the jinstall package. For information about the contents of the jinstall package and details of the installation process, see the Installation and Upgrade Guide. Use other packages, such as the jbundle package, only when so instructed by a Juniper Networks support representative.

Note

Back up the file system and the currently active Junos OS configuration before upgrading Junos OS. This allows you to recover to a known, stable environment if the upgrade is unsuccessful. Issue the following command:

Note

The installation process rebuilds the file system and completely reinstalls Junos OS. Configuration information from the previous software installation is retained, but the contents of log files might be erased. Stored files on the router, such as configuration templates and shell scripts (the only exceptions are the juniper.conf and ssh files), might be removed. To preserve the stored files, copy them to another system before upgrading or downgrading the routing platform. For more information, see the Junos OS Administration Library.

Note

We recommend that you upgrade all software packages out of band using the console because in-band connections are lost during the upgrade process.

To download and install Junos OS Release 16.2R2:

  1. Using a Web browser, navigate to the All Junos Platforms software download URL on the Juniper Networks webpage:

    https://www.juniper.net/support/downloads/

  2. Select the name of the Junos OS platform for the software that you want to download.
  3. Select the release number (the number of the software version that you want to download) from the Release drop-down list to the right of the Download Software page.
  4. Select the Software tab.
  5. In the Install Package section of the Software tab, select the software package for the release.
  6. Log in to the Juniper Networks authentication system using the username (generally your e-mail address) and password supplied by Juniper Networks representatives.
  7. Review and accept the End User License Agreement.
  8. Download the software to a local host.
  9. Copy the software to the routing platform or to your internal software distribution site.
  10. Install the new jinstall package on the router.Note

    We recommend that you upgrade all software packages out of band using the console because in-band connections are lost during the upgrade process.

    All customers except the customers in the Eurasian Customs Union (currently composed of Armenia, Belarus, Kazakhstan, Kyrgyzstan, and Russia) can use the following package:

    user@host> request system software add validate reboot source/junos-install-ptx-x86-64-16.2R2.9.tgz

    Customers in the Eurasian Customs Union (currently composed of Armenia, Belarus, Kazakhstan, Kyrgyzstan, and Russia) can use the following package (limited encryption Junos OS package):

    user@host> request system software add validate reboot source/junos-install-ptx-x86-64-16.2R2.9-limited.tgz

    Replace the source with one of the following values:

    • /pathname—For a software package that is installed from a local directory on the router.

    • For software packages that are downloaded and installed from a remote location:

      • ftp://hostname/pathname

      • http://hostname/pathname

      • scp://hostname/pathname (available only for Canada and U.S. version)

    The validate option validates the software package against the current configuration as a prerequisite to adding the software package to ensure that the router reboots successfully. This is the default behavior when the software package being added is a different release.

    Adding the reboot command reboots the router after the upgrade is validated and installed. When the reboot is complete, the router displays the login prompt. The loading process might take 5 to 10 minutes.

    Rebooting occurs only if the upgrade is successful.

Note

You need to install the Junos OS software package and host software package on the routers with the RE-PTX-X8 Routing Engine. For upgrading the host OS on this router with VM Host support, use the junos-vmhost-install-x.tgz image and specify the name of the regular package in the request vmhost software add command. For more information, see the VM Host Installation topic in the Installation and Upgrade Guide.

Note

After you install a Junos OS Release 16.2 jinstall package, you cannot return to the previously installed software by issuing the request system software rollback command. Instead, you must issue the request system software add validate command and specify the jinstall package that corresponds to the previously installed software.

Note

Most of the existing request system commands are not supported on routers with RE-PTX-X8 Routing Engines. See the VM Host Software Administrative Commands in the Installation and Upgrade Guide.

Changes Planned For Future Releases

  • Change in default behavior of traffic engineering shortcuts in labeled IS-IS segment routing (MX and PTX Series)—In Junos OS Releases 15.1F6, 15.1F7, 16.2R1, and 17.1R1, traffic engineering shortcuts are enabled for labeled IS-IS segment routes, when you configure shortcuts at the following hierarchy levels.

    • [edit protocols is-is traffic-engineering family inet] for IPv4 traffic.

    • [edit protocols is-is traffic-engineering family inet6] for IPv6 traffic.

    Starting with Junos OS Release 17.2R1 onwards, explicit configuration of traffic engineering shortcuts for labeled IS-IS segment routes is planned to be introduced by configuring shortcuts at the following hierarchy levels:

    • [edit protocols is-is traffic-engineering family inet-mpls] for IPv4 traffic.

    • [edit protocols is-is traffic-engineering family inet6-mpls] for IPv6 traffic.

Product Compatibility

Hardware Compatibility

To obtain information about the components that are supported on the devices, and special compatibility guidelines with the release, see the Hardware Guide and the Interface Module Reference for the product.

To determine the features supported on PTX Series devices in this release, use the Juniper Networks Feature Explorer, a Web-based application that helps you to explore and compare Junos OS feature information to find the right software release and hardware platform for your network. Find Feature Explorer at: https://pathfinder.juniper.net/feature-explorer/.

Hardware Compatibility Tool

For a hardware compatibility matrix for optical interfaces and transceivers supported across all platforms, see the Hardware Compatibility tool.