Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

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

Resolved Issues

This section lists the issues fixed in Junos OS Release 15.1F6 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.1F6

Class of Service (CoS)

  • In case of member links of an AE (aggregated Ethernet) interface scatter over multiple Packet Forwarding Engines, if the FPC where member links of the AE interface reside gets reset or interface disable, there may be a dip in the output of SNMP walk on AE related queue MIB (such as jnxCosQstatTxedPkts). The behavior is intermittent and not seen every time. PR1122343
  • This PR does optimization in AE SNMP handling. If all the links in an AE bundle go down, then any CoS SNMP query for this AE IFD/IFL will return cached values. PR1140440

General Routing

  • Enhance error handling when TL-chip encounters KHT memory parity error. With the enhancement, when KHT memory parity error is detected, the content of the memory will be corrected using software shadow copy. PR1001052
  • Sending 500G Packet Forwarding Engine line rate with small size packets ( < 168B) without pre-classifier enabled in ingress buffering block (IPW) is not supported, which leads to loss of control packets resulting in routing instances flapping. PR1093170
  • On PTX Series platforms, SIB temperature-threshold configuration cannot be changed for off-lined SIBs. PR1097355
  • The "clear services accounting flow" command should not be used in 15.1F4 or 15.1F5 releases 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
  • In certain rare conditions, FPC VoQ will wedge which will drop packets on ingress Packet Forwarding Engine for PTX Series routers. Since the wedge cannot be reproduced, detection of wedge condition is introduced that alarm would be raised once the wedge condition is detected within 10 seconds. PR1127958
  • When 2M IPv6 routes point to a single NH then IFD down or PIC offline of the PIC hosting the port related to the NH would crash the FPC. PR1129183
  • When hold-time Up is configured on IFDs of PTX, SyncE line clocks can fail by restarting the associated FPCs. In a particular test scenario with relatively large hold-time Up 60,000 ms, SyncE line clock can fail by restarting the associated FPC, and it is never recovered until the IFD is dis/enabled. Both 10GbE and 100GbE interfaces indicate the same clock fail issue. PR1130084
  • Link Fault signaling message are not logged on PTX Series Gladiator FPCs. PR1132114
  • On PTX Series platforms with FPC3 equipped, the ifinfo (i.e., ifinfo is a short-live process that is created when the show interfaces command is issued via the Junos CLI) might crash during making changes on AE member link while running show interface related command on AE interface (such as make speed change (mixed<=.10G) with continuous retrieval of the LACP status using show lacp interfaces ae <n>). It will recover itself and there is no service impact. PR1139409
  • In Junos OS Release 15.1F4, "show chassis environment" "Routing Engine 0 CPU" does not show Routing Engine CPU temperature as Junos OS Release 15.1F4 does not have the fix to make available the CPU temperature in Junos OS from HOST. "Routing Engine 0 CPU" instead shows the maximum of the Routing Engine inlet and exhaust sensors reading. PR1140187
  • After removing a child link from AE bundle, the AE interface statistics in the SNMP MIB might show a spike. PR1140533
  • FPC might restart while issuing "write coredump" from fpc shell. PR1140870
  • When smart configuration is configured and the user does a VMhost regular upgrade, user observes an error print NG_RE_VMM: "/usr/bin/vmsmartd.sh: Command not found." This can be ignored. This has no impact on upgrade. PR1144881
  • Due to buffer size issue for FPC-SFF-PTX-P1-A (PTX3000) and FPC2-PTX-P1A (PTX5000) will be hitting "ISSU RECONNECT TIMEOUT" or "READY Message Without Reconnect" during unified ISSU (it will be hit if this fix not available in the from build). PR1155936
  • With Junos OS Release 15.1F3 or 15.1F4, when a PTX Series router is performing penultimate-hop popping (PHP) and has an egress interface on FPC3, the MPLS EXP rewrite rule will not take effect on the exposed header after POP. PR1160486
  • As per design, whenever configuration is committed in Hendricks, chassisd tries to bring the OFFLINE SIBs ONLINE. The SIB might not have power because of hardware issues (such as seen in this PR where the SIB couldn't be brought ONLINE because of a voltage rail failure). In such cases, software shouldn't try to ONLINE the SIB. This attempt is resulting in the software state for this SIB getting stuck in "TRANSITION" state, thereby resulting in all future offline/online commands to not take effect on this SIB. Fixed software to check if there are any hard errors on that SIB before trying to bring it ONLINE. Fix comes in 14.2R7, 15.1F6, 15.1R4. PR1161110
  • When per-VLAN shaping rate is changed on the router with FPC3 and FPC2, the "expr_cos_scheduler_map_unbind_ifl @ 1658: Failed to drain ifl" message is displayed and a short traffic outage may be observed. PR1161306
  • TTL-1 (IP and MPLS) packets are not reported as Normal-Discards. PR1162572
  • The description of the newer PTX5000 Control Board has changed from "PTX 5K CB" to "Control Board 2" to make the description consistent with existing Control Boards. PR1163501
  • RPD core seen in krt_comp_rnhc_msg_set_af_info at ../../../../../../../src/junos/usr.sbin/rpd/lib/krt/krt_comp_util.c:179 observed during feature integration test. PR1163553
  • Control packets may get dropped when Packet Forwarding Engine is under heavy congestion. PR1163759
  • A vmcore may be seen if there are 65000 pfestats requests in a short amount of time (70-90 seconds). PR1163772
  • On a full box FPC3 chassis, FPC CPU utilization reaches 100% for a short period of time (between 30 seconds to 1 minute) during AE member links speed changes. PR1163830
  • PTX FPC2 might core-dump after FPC reload or non-GRES Routing Engine mastership change due to memory corruption when processing IPC messages. We have enhanced the way DFWD for interface-specific filters is being handled. With this fix when the TLV decode has errors we would not continue processing and problem should no longer be seen. PR1164055
  • FPC3 should not send the MTU exceeded MPLS packets to the Routing Engine. PR1164145
  • In case that LSP Ping echo request rate is higher than the implemented rate-limit spec for MPLS-OAM application on PTX Series, some bursty LSP Ping packets get dropped and PTX Series cannot send LSP Ping echo reply for these dropped LSP Ping echo request. It causes that VCCV BFD session get destroyed by L2CKT-OAM client due to LSP Ping Reply timed out for L2CKT PW on the other remote endpoint that sent those LSP Ping echo requests. Since the remote endpoint stops sending BFD packets for those VCCV BFD sessions having become in AdminDown, the corresponding VCCV BFD session on PTX gets down as CtlExpire with Detect Timer Expiry event. The existed MPLS-OAM rate-limiter was increased to support a scaled MPLS-OAM scenario, 450 pps per Packet Forwarding Engine likely. PR1164880
  • In mixed mode when the PVQ configuration is changed while there is traffic flowing, ifds may go down. PR1167096
  • On PTX Series platforms, when a high priority clock source (bits-a) goes down, the clock status transits from "locked to bits-a" to "holdover" to "acquiring" to "locked to bits-b", and when the bits-a comes up, the clock status reverts from "locked to bits-b" to "holdover" to "acquiring" to "locked to bits-a". In such scenarios, it should not drop by "holdover" and "acquiring" states as per the standard. PR1168000
  • When stats are polled for tc-count, it was retaining stats read from multiple Packet Forwarding Engines when members of AE are spread across Packet Forwarding Engines of same FPC. Stats read from later Packet Forwarding Engines was overwriting the stats read from earlier Packet Forwarding Engines. PR1170226
  • After booting up PTX Series, some setting is not set correctly with 15.1F5.15 and will trigger loopback wedge error message. PR1171101
  • Traceroute will not work if a PTX5000 router-based line card is the ingress line card of a transit router (SWAP router) in 15.1F5.14. PR1171119
  • In a very rare cases, multiple Routing Engine switchovers may result in SNGPMB crash. PR1176094
  • When running interfaces on QSFP28 PIC in 40G or 100G mode, some of the interfaces the QSFP28 PIC may not come up after a system reboot. This issue does not impact interface running in 10G mode. PR1176641
  • Gladiator: idle insert settings wrong on some SIBs, after do GRES for 3-4 times, then ungracefully power off/on SIBs. PR1177652
  • "show t6e-pic 0 fec" on vty of fpc does not show xcvr type for QSFP+ optics. PR1181430

Interfaces and Chassis

  • On PTX Series routers, TX optical threshold value is shown incorrectly for the interfaces in the PIC P1-PTX-2-100G-WDM. This PR will fix only the TX power issue reported in the 2x100G DWDM OTN PIC. PR1084963
  • This command shows the Tx/Rx power/thresholds and alarms incorrectly. Here are the changes to address this PR: 1. The "-18 to -5 dBm" as defined in the spec refers to the per wavelength power, but the thresholds in the CLI are the cumulative power which can be received from multiple channels. So the change will be to keep the values as is and remove the "Laser" from the Receive power thresholds. 2. Remove the "laser output power xxxxx" thresholds as they do not have corresponding alarms. 3. Change the "laser output power alarms" to "Tx power xxx alarm/warn", these do not have corresponding thresholds. 4. Rename the "Laser rx power xxxx threshold" to "Rx power xxxx" 5. Rename "laser xxx power" to "xxx power". 6. Add the two los alarm/warn thresholds, which when configured will change the defaults for Rx low power warning and alarm. "set interfaces et-x/y/z optics-options los-alarm-threshold"/"set interfaces et-x/y/z optics-options los-warning-threshold". PR1115135
  • On PTX Series platforms, whenever there is config change followed by a commit on 100GbE interfaces, the continuity-check (OAM) interval of 100 ms should be insufficient. The system keeps busy for longer than 100 ms in processing the configuration commit, so it can miss the continuity-check messages, then trigger Interface (OAM) flap in the same PIC. PR1164329
  • 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 used to complain about speed mismatch Commit error: Interface ae0 with child links of mixed speed but link-speed mixed is not configured. PR1167780

MPLS

  • 14.1R6 - P2MP + NSR may observe ~100 ms loss during Routing Engine switchover in steady state with link protection enabled. This is not observed in Junos OS Releases 14.2 and later. The problem is undergoing further triage and is targeted to enter the 14.1R7 release window. PR1095488
  • When automatic bandwidth is enabled on router acting as ingress and transit routers for scaled LSPs (for example, 4k ingress LSPs and 36k transit LSPs), "Max AvgBW util" update for ingress LSP will get delayed (for example, the statistics interval is set to 60s, but get updated almost 3+ minutes). It is because, even though the "no-transit-statistics" configuration statement is enabled, transit LSPs' statistics are still being considered for polling. This is noticed when there are large number of transit LSPs (such as 36k transit LSPs) present on the router. PR1154212
  • The output of "show rsvp interfaces" was not being displayed in desired format. For higher number units, FPC in slot higher than 9 or channelized interfaces, output was being moved to the next line. That was harder to read and matching was not possible as part of the output was in another line, so nothing was returned in the CLI. atajer@sangria-re1# run show rsvp interface | match "et-11/0/11|lo0" et-11/0/11:0.0 et-11/0/11:0.4000 et-11/0/11:1.0 et-11/0/11:2.0 et-11/0/11:3.0 lo0.0 Up 0 100% 0bps 0bps 0bps 0bps With the fix for this PR, no matter how many characters we have in the interface name, there will always be a space separating interface name and state. Formatting is not done using fixed length spaces anymore. State will not be aligned in a single column for all interfaces, but customer can see data using match conditions. Commit went into 15.1R4, 15.1F6 & 16.1x. atajer@sangria-re1# run show rsvp interface | match "et-11/0/11|lo0" et-11/0/11:0.0 Down 0 100% 10Gbps 10Gbps 0bps 0bps et-11/0/11:0.4000 Down 0 100% 10Gbps 10Gbps 0bps 0bps et-11/0/11:1.0 Down 0 100% 10Gbps 10Gbps 0bps 0bps et-11/0/11:2.0 Down 0 100% 10Gbps 10Gbps 0bps 0bps et-11/0/11:3.0 Down 0 100% 10Gbps 10Gbps 0bps 0bps lo0.0 Up 0 100% 0bps 0bps 0bps 0bps PR1170790

Network Management and Monitoring

  • Eventd might run out of memory and crash because of excessive kernel logging. PR1162722

Platform and Infrastructure

  • In certain cases, with some events such as disable/enable of links followed by Routing Engine rebooting or GRES enabled switch-over, the following error message could be seen due to a software bug where it does not handle an internal flag properly: “KERNEL/PFE APP=NH OUT OF SYNC: error code 1 REASON: invalid NH add received for an already existing nh ERROR-SPECIFIC INFO” PR1107170
  • Configuring one group with configuration of routing-instances and applying this group under routing-instances, then the rpd process will crash after executing "deactivating/activating routing-instances" commands. As a workaround, you can avoid using "apply-groups" under routing-instances hierarchy. PR1109924
  • With delta-export command enabled, "show|compare" output still shows after last successful commit. PR1129577

Routing Protocols

  • In multicast environment, when the RP is FHR (first-hop router) and it has MSDP peers, when the rpf interface on RP changed to MSDP facing interface, due to the multicast traffic is still on the old rpf interface, a multicast discard route will be installed and traffic loss will be seen. PR1130238
  • Even though no information is actually changed (all IS-IS adjacencies remain the same, etc.) when the IS-IS LSP is regenerated, the different TLVs that compose the LSP might move between the different fragments of the LSP. Although the sum of all the TLVs remains the same, the order of the TLVs and their location relative to each fragment might change. The fact that a TVL might move between two different fragments might cause issues for IS-IS "clients", CSPF for example. PR1159482

Resolved Issues: 15.1F5

General Routing

  • It is reported that on PTX Series platforms, when the firewall filter is configured on the loopback interface of the device, due to bad error handling or NULL pointer, all the FPCs on device may continuously crash and be unstable. Because the issue is not reproducible, the trigger of the issue is not clear. PR996749
  • On PTX Series platform with FPC3, if the egress sampled packets that are less than one cell size (128 bytes including Ethernet header), the packets get chopped this host cannot receive the full IPv4/6 header. This issue might affect all the egress sampled packets sent to host (this can be syslog, log, or any other feature that samples the packet to host in the egress pipeline). PR1100505
  • Interface status may not change accurately when FPC CPU is usage is 100%. The problem will be seen if the following conditions are met on Gladiator. 1) Laser off/on are introduced from remote end in order to change the status of an interface on local end (Gladiator). 2) On local end (Gladiator), the FPC (with the interface for which status change is expected) CPU is 100% during this laser on/off event. An interface will not change its status from Down to Up or Up to Down triggered because of laser off/on from end, when the FPC CPU usage is 100%. The interface will correctly reflect its status as soon as FPC CPU usage drops below 100%. PR1130920
  • On PTX platform with FPC3 equipped, the ifinfo (i.e., ifinfo is a short-live process that is created, when the show interfaces command is issued via the Junos CLI) might crash during making changes on AE member link while running show interface related command on AE interface (such as make speed change (mixed<=.10G) with continuous retrieval of the LACP status using show lacp interfaces ae <n>). It will recover itself and there is no service impact. PR1139409
  • In 15.1F4 "show chassis environment" "Routing Engine 0 CPU" does not show Routing Engine CPU temperature as 15.1F4 does not have fix to make available CPU temperature in Junos OS from HOST. "Routing Engine 0 CPU" instead shows maximum of Routing Engine inlet and exhaust sensors reading. PR1140187
  • After removing child link from AE bundle, the AE interface statistics in SNMP MIB might show a spike. PR1140533
  • When an FPCs i2c register contents are reported in syslogs, the names of failed power rails are printed with the message. PR1140556
  • IPv6 packet will be dropped on FPC3 of PTX Series platform if length of the IPv6 payload is smaller than 8 bytes. PR1141384
  • On PTX Series platform with FPC3, the octets of IPv4 source and destination addresses in firewall log are listed reversely, it might affect troubleshooting. IPv6 log works fine. This is a minor issue, no other service impact. PR1141495
  • On PTX Series platform with FPC3, the "disable" configuration statement under the hierarchy "forwarding-options sampling instance <instance name> family <inet>" does not take effect, so the packets are still getting sampled. As a workaround, please use "deactivate" command instead of "disable" command. PR1142279
  • For In-Line J-Flow feature: When send traffic at line rate, sometime Inactive timeouts are incrementing, this issue will be fixed in 15.1F4-S1 and 15.1F5. PR1142977
  • Packet drops are not reported as info cell drops in FPC3. PR1145321
  • When exceeding the filter term limitation, the filter programming fails. When it fails it cleans up the failed filter. During the cleanup operation it tries to clean the FPC resources which were never actually allocated as the filter programming failed before the allocation. As a result it leads to assertion/FPC crash. PR1148249
  • Counter defined with tc_cntr as substring will not appear in mibwalk. PR1151884
  • Inline-Jflow on PTX FPC Type3 cards is now using the correct Domain Identifier ID in IPFIX exports based on FPC slot number. Previously, a value of 0x4 was always used. PR1151955
  • In affected releases, when inline-jflow is used, certain debug information is logged by default. This is just a cosmetic issue and the fix will prevent these messages from being generated. PR1152216
  • When per-VLAN shaping rate is changed on the router with FPC3 and FPC2, “expr_cos_scheduler_map_unbind_ifl @ 1658: Failed to drain ifl” messages is displayed and a short traffic outage may be observed. PR1161306
  • TTL-1 (IP and MPLS) packets are not reported as Normal-Discards.PR1162572
  • The description of the newer PTX5000 Control Board has changed from "PTX 5K CB" to "Control Board 2" to make the description consistent with existing Control Board. PR1163501
  • Control packets may get dropped when Packet Forwarding Engine is under heavy congestion. PR1163759
  • FPC3 should not send the MTU exceeded MPLS packets to the Routing Engine. PR1164145

Interfaces and Chassis

  • On dual Routing Engine platforms, when adding the logical interfaces (IFLs) and committing, due to the device control process (dcd) on backup Routing Engine may fail to process the configuration and keep it in the memory, in some cases (not happening all the time), it might be observed that the memory of the dcd keeps increasing on backup Routing Engine. PR1014098
  • Release prior to 15.1F5 has buffer size issue for FPC-SFF-PTX-P1-A (PTX3000) and FPC2-PTX-P1A (PTX5000). Prior releases cannot use unified ISSU to upgrade to Junos OS Release 15.1F5. PR1155936

MPLS

  • When Auto BW is enabled on Ingress Router, MaxAvgBW Util field will get delayed when large number of transit LSPs present though no-transit-statistics-polling. Though no-transit-statistics-polling configuration statement is enabled, still transit LSPs are being considered for polling. This is noticed when there are large number of transit LSPs present on the router. PR1154212

Platform and Infrastructure

  • With delta-export command enabled, "show |compare" output still shows after last successful commit. PR1129577

Routing Protocols

  • In multicast environment, when the RP is FHR (first-hop router) and it has MSDP peers, when the rpf interface on RP changed to MSDP facing interface, due to the multicast traffic is still on the old rpf interface, a multicast discard route will be installed and traffic loss will be seen. PR1130238

Resolved Issues: 15.1F4

Class of Service (CoS)

  • This PR does optimization in AE SNMP handling. If all the links in an AE bundle go down, then any CoS SNMP query for this AE IFD/IFL will return cached values. PR1140440

General Routing

  • Sending 500G Packet Forwarding Engine line rate with small size packets ( < 168B) without pre-classifier enabled in ingress buffering block (IPW) is not supported, which leads to loss of control packets resulting in routing instances flapping. PR1093170
  • On PTX5000 platform, show interfaces voq CLI command is not updating VOQ drops stats correctly. PR1127725
  • In 15.1F3 RPD core can be seen on previous master after performing Routing Engine switchover. PR1128023
  • On Next Generation PTX Series platform, FPC CPU spike might be observed if there is optic failure or mis-configuration, for example, one side is configured in 100G and another side in 10/40G. PR1129057
  • On rare occasions, the PCI link on the SPMB CPU may not come up correctly due to a software error. This will prevent the SIBs from coming up properly if the SPMB happens to be Master. The problem can be resolved by restarting the SPMB using the command "request chassis spmb slot <id> restart". PR1129203
  • On FPC3 equipped next-generation PTX5000 (model number: PTX5000BASE2) platform, packets drop would be seen when mac-address of the interface which has "ethernet-ccc" or "ethernet-tcc" encapsulation, is changed. As a workaround, deleting the "ethernet-ccc" (or "ethernet-tcc") encapsulation of the interface, making the mac-address change, doing the commit, then reverting back the "ethernet-ccc" encapsulation, and again doing the commit would avoid the issue. PR1129641
  • When one of SIBs is offlined on PTX Series router, the performance might be affected and unable to reach line rate. PR1129733
  • On PTX Series platform, when receiving large amount of TTL=1 MPLS packets on AE interface, the LACP packets might be affected and causing the AE interface to flap. PR1129739
  • On Next Generation PTX Series platform with 100G interface, when we disable and enable the interface, in rare conditions, the link comes up and quickly goes down and then again comes up. This is not the expected behavior. PR1132611
  • On PTX Series platforms while performing PIC offline/online or interface flap, FPC might generate a core file. PR1132689
  • If the total combined PPS traffic exceeds a Packet Forwarding Engine limit, the Packet Forwarding Engine does not send out MAC-PAUSE Frame out of its interface indicating the downstream device to slow down. All control plane protocol packets are affected. In this case, the LACP hello packet is not sent out, so the LACP might flap, the traffic forwarding will be affected. PR1136038
  • PTX FPC3 - ifinfo core seen@#0 0x0808fa95 in pif_agg_traffic (ifl=0xffffd554) at ../../../../../../src/junos/usr.sbin/ifinfo/libifinfo/ifinfo_agg.c:935 during AE member link speed change (mixed<=.10G). PR1139409

Routing Protocols

  • In multicast environment, when the RP is FHR (first-hop router) and it has MSDP peers, when the rpf interface on RP changed to MSDP facing interface, due to the multicast traffic is still on the old rpf interface, a multicast discard route will be installed and traffic loss will be seen. PR1130238

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, 5,000 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 (i.e., 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 following 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 check-ins), 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: 2017-03-22