Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary
Navigation  Back up to About Overview 
ContentIndex
  
[+] Expand All
[-] Collapse All

No index entries found.

Resolved Issues

This section lists the issues fixed in Junos OS Release 15.1F3 for the PTX Series. The identifier following the description is the tracking number in the Juniper Networks Problem Report (PR) tracking system.

Resolved Issues: 15.1F3

General Routing

  • When a switchover is done from one Routing Engine to the other, in graceful-switchover redundancy mode, there is a brief period early in the transition of the SIB to online state, during which unsolicited (not corresponding to an attempt by the CPU to access the SIB via PCIe) errors are received at the downstream PCIe port on the CB to the SIB. The fix is to mute the generation of such errors during this brief period of the switchover. PR1068237
  • The configured buffer-size will not take effect until either "transmit-rate" or "excess-rate" is configured. PR1072179
  • Tunable SFP+ optics are not supported on P1-PTX-24-10G-W-SFPP PIC in Junos OS Release 15.1R1. On Tunable Optics in this PIC, with Junos OS Release 15.1R1, the wavelength will not be configurable and the tunable parameters will not be correctly displayed in the CLI. PR1081992
  • The FPC on PTX Series router might crash and reboot when the Packet Forwarding Engine is handling a fatal error. When the error happened, "TQCHIP0: Fatal error pqt_min_free_cnt is zero" log message is seen. PR1084259
  • On PTX Series platform with external clock synchronization interface configured, when both BITS external clocks are disconnected at the same time, the 100GbE-LR4 FINISAR interface might flap. This link flap issue is narrowed down to the operation of data-path FIFO within CFP. When both the BITS clocks are disconnected, the reference clock jumps to "free-running" mode. This transition leads to a phase shift in reference clock. Due to this phase shift, the data rates into and out of the FIFO will temporarily not match, leading to a FIFO over-run or under-run condition. This over-run or under-run condition forces a FIFO reset, and the output signal is distorted. So the far-end interface detects 'local-fault', then returns 'remote-fault' back to the near-end, hence a link flap. After change for this PR: - User needs to manually configure FPC recovered clock port for each clock put into "chassis synchronization source". - Only one clock of each FPC can be put into "chassis synchronization source". PR1091228
  • On PTX Series platform, if there are scaled configurations (for example, 5000 routes and each of them with 64 ECMP paths configured) on a single interface and L2 rewrite profile is applied for the interface, the FPC may crash when deactivating and then activating the CoS configuration of the interface. PR1096958
  • On PTX Series platform, SIB temperature-threshold configuration cannot be changed for off-lined SIBs. PR1097355
  • When the PTX Series only has bits-a and bits-b as configured clock sources (and there is no interface on FPC configured as clock souce), and it is losing signal from both of bits-a and bits-b simultaneously, clock sync state will go to FREERUN mode immediately. This is unexpected behavior. After the fix of this PR, clock sync state will stay HOLDOVER , then will go to FREERUN mode after the timeout. PR1099516
  • Starting with Junos OS Release 14.1, Entropy Label Capability is enabled by-default on all Juniper Networks PTX Series routers. On PTX Series transit LSRs that carry LSPs with Entropy Label Capability, packet loss can be observed due to data errors when one or more labeled route entries are not properly removed from the hash table (ie. following LSP optimization or MBB event) because the 'stale' entries are pointing to corrupted route memory. As a result, when the MPLS label that's associated with the 'stale' entry is re-used, data errors are seen for packets using the corresponding label. PR1100637
  • On PTX Series platform, when yanking out FPC or SIB ungracefully (for example, pulling the line card out of the chassis unintentionally when the line card is carrying the traffic), there might be small probability that it can impact any of the FPCs with Grant Scheduler (GS) and Request Table (RT). Fatal interrupt occurred. PR1105079
  • Suppose we have x mldp lsps and AE members with y child members. Then the scale supported is 4x*y < 60K. PR1107077
  • No decrement ttl does not work for incoming v6 traffic over mpls ipv4 core. PR1115203

Infrastructure

  • On PTX Series platform with Junos OS Release 15.1R1 and later, while a core dump is in progress, if we try to access the dump directory, due to the deadlock defect, the system might hang and crash. As a workaround, we should not access the "/var/crash" directory till the core dump is complete. PR1087082

Interfaces and Chassis

  • During subscriber login/logout, the below error log might occur on the device configured with GRES/NSR. /kernel: if_process_obj_index: Zero length TLV! /kernel: if_pfe: Zero length TLV (pp0.1073751222). PR1058958

MPLS

  • In the output of the CLI command "traceroute mpls ldp", the addresses of the interfaces on transit PTX Series routers might be shown as "127.0.0.1". PR1081274

Network Management and Monitoring

  • Due to inappropriate cleanup in async library, disabling multiple interfaces while SNMP is polling interface oids might cause mid2d process to crash. PR1097165.
  • While the router is rebooting and SNMP polling is not stopped, SNMP requests might land on mib2d process before Routing Engine protocol mastership is resolved, causing the mib2d process crash. PR1114001

Platform and Infrastructure

  • The MIB counter or "show pfe statistics traffic" shows junk PPS and invalid total traffic output counter. PR1084515

Routing Protocols

  • With any single-hop BFD session and MPLS OAM BFD session configured over the same interface, when the interface is disabled and enabled back immediately (e.g. a delay of 10 seconds between the two commit checks in), the single-hop BFD session might get stuck into Init-Init state because the Down packet is received from other end for MPLS BFD session on the same interface might get demultiplexed to single-hop BFD session incorrectly. PR1039149

Software Installation and Upgrade

  • In certain conditions, when /var is not mounted from a persistent filesystem, executing a Junos OS upgrade will have unexpected results. This is caused by an inexact check of whether we are running from an Emergency VAR. PR1112334

Resolved Issues: 15.1F2

Forwarding and Sampling

  • In PTX Series Carrier-Grade Service Engine (CSE) jflow solution environment, because the sampling process (sampled) may get into a continuous loop when handling asynchronous event (for example, aggregated tethered services interface flapping, or route update, or IFL/IFD update), the sampled process may never come out of that loop which may result in high CPU usage (up to 90% sometimes). Also, the flabel might be exhausted because sampled is not able to consume states (such as route updates, interface updates) generated by kernel, and finally the router would not make any updates. PR1092684

General Routing

  • Prior to this fix "show interface diagnostics optics" command shows output for all four lanes for 10G ports of 48x10GE 12x40GE QSFP+ PIC. Normal behavior would be to display output for only the lane that the port belongs to. PR959514
  • On PTX Series routers, the interrupt-driven basis link down detection (an interrupt-driven link-down notification is generated to trigger locally attached systems to declare the interface down within a few milliseconds of failure) may fail after performing unified in-service software upgrade (ISSU). The interrupt might be prevented after performing unified ISSU due to disabling the interrupt registers before unified ISSU, but never restored after. PR1059098
  • The configured buffer-size will not take effect until either "transmit-rate" or "excess-rate" is configured. PR1072179
  • On Junos OS Release 15.1R1, when the multicast next-hop is changed, the grafting and pruning operations take more time than before. PR1090608

Interfaces and Chassis

  • If we load jinstall/jinstall64 image on PTX Series and if we have CFM configured over AE interfaces, this issue will be seen. PR1085952

MPLS

  • When fast-reroute, node-link-protection or link-protection is configured, if a Shared Risk Link Group (SRLG) is associated with a link used by an LSP ingressing at a router, then on deleting the SRLG configuration from the router, the SRLG entry still stays in the SRLG table even after the re-optimization of this LSP. PR1061988
  • In Junos OS Release 14.1 and later, the "load-balance-label-capability" configuration statement is introduced to enable the router to push and pop the load-balancing label, which causes LDP and RSVP to advertise the entropy label TLV to neighboring routers. The PTX Series routers have the capability and it is reflected in their default forwarding-options configuration. However, there is a software defect in the way that Entropy Label Capability (ELC) TLV is encoded in the LDP label mapping message, which might cause the LDP session between the routers to go down. PR1065338

Related Documentation

Modified: 2016-08-18

Previous Page Next Page