Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

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


  • 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


  • 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: ""

    • Incorrect trap: Name: "jnxFruRemoval"

      OID: ""


  • 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


  • 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