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.

Resolved Issues: 14.1R9

General Routing

  • This occurs in a race condition. The unilist is created before ARP learns the MAC addresses, then the selector table is corrupted.On FPC-SFF-PTX-P1-A (PTX3000), FPC-SFF-PTX-T (PTX3000), FPC-PTX-P1-A (PTX5000), and FPC2 -PTX-P1A (PTX5000), packet loss might be observed in an ECMP or an aggregated Ethernet scenario. PR1120370

  • For PTX Series routers, the IPv6 unilist next-hop member is moved to "replaced" status on the Packet Forwarding Engine after interface flapping with IPv6 Neighbor Discovery timeout. While the problem occurs, the routing table displays an acceptable next-hop status but cannot forward traffic because the forwarding next-hop in the Packet Forwarding Engine is in "replaced" status and thus no longer active. PR1177023

  • When an ARP entry is learned through the aggregated Ethernet interface, and a route is pointing to that ARP next hop, 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 the aggregated Ethernet interface getting stuck in unicast state even if the remote end is not reachable, and the routing protocol process (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

Infrastructure

  • When deleting a child link from the aggregated Ethernet bundle, the output statistics for aggregated Ethernet IFD can return 0 from the Packet Forwarding Engine and get summed incorrectly later. The aggregated Ethernet logical interface (IFL) however has correct statistics, including the residual value from the removed child logical interface (IFL). Input statistics are displayed properly and unaffected by this bug. PR1098264

Platform and Infrastructure

  • BFD session fails to come up when it is configured over the sonet interface, which is configured without an IP address. This occurs because the IFA GET operation performed by BFD fails because there is no address configured on the interface. PR1165720

Resolved Issues: 14.1R8

General Routing

  • It is reported that on PTX 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

  • 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 unsoliciited (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

  • On FPC-SFF-PTX-P1-A(PTX3000)/FPC-SFF-PTX-T(PTX3000)/FPC-PTX-P1-A(PTX5000)/FPC2 -PTX-P1A(PTX5000), packet loss may be observed in ECMP or AE scenario. That occurs in a race condition: the unilist is created before ARP learned MAC addresses, then the selector table is corrupted. PR1120370

  • In the multicast network topology, when making normal changes, such that paths are added or deleted, the rpd leaks 8-bytes memory per operation. The system logs RLIMIT_DATA messages similar to the following when the memory usage reaches 85%: kernel: Process (2634,rpd) has exceeded 85% of RLIMIT_DATA: used 3084524 KB Max 3145728 KB PR1144197

  • For PTX routers, the IPv6 unilist next-hop member will become "replaced" status on Packet Forwarding Engine (PFE) after interface flapping with IPv6 ND (Neighbor Discovery) timeout. While the problem is happening, routing-table will display all right next-hop status but cannot forward traffic since forwarding next-hop in PFE is in "replaced" status and no longer active. PR1177023

Class of Service

  • 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

MPLS

  • In P2MP with NSR scenario, it might be observed about 100 ms traffic loss during Routing Engine switchover in steady state with link protection enabled. It is because that the nexthops added by applications in the backup RE do not match nexthops fetched from kernel. This nexthops mismatch causes LSPs to reestablish after switchover. PR1095488

Routing Protocols

  • With SRLG (Shared Risk Link Group) enabled under corner conditions, after executing command of "clear isis database", the rpd might crash due to the ISIS database tree gets corrupted. PR1152940

User Interface and Configuration

  • From Junos OS 12.1X44-D50 12.1X46-D35 12.1X47-D25 12.3X48-D15 14.1R3-S1 14.1R4 14.2R1 with large scale configuration configured, due to a software bug --- drastic increase in the number of calls to "action acceptable" function, a performance issue might occur. For example, even thought there is no configuration set for "protocols mpls lsp-external-controller ...", the action acceptable function is called repeatedly when performing a configuration commit. As a result, the configuration load time takes more than before. 15.1 might take more than 10 minutes. The same configuration was able to load in 14.1 in 5 minutes 35 seconds. The fix/optimization has now been provided to decrease processing time during configuration load and rollback. PR1065659

Resolved Issues: 14.1R7

General Routing

  • When a labeled BGP route resolves over a route with MPLS label (e.g. LDP/RSVP routes), after clearing the LDP/RSVP routes, in the short window before the LDP/RSVP routes restore, if the BGP routes resolves over a direct route (e.g. a one-hop LSP), the rpd process might crash. PR1063796

High Availability (HA) and Resiliency

  • With NSR enabled on multiple RE system, when dynamic GRE tunnel is configured, performing RE switchover might causing rpd crash repeatedly on backup RE. PR1130203

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

Multiprotocol Label Switching (MPLS)

  • MPLS auto-bandwidth does not reset MAX Avg Bandwidth when overflow or underflow threshold limit is configured. It may lead to wrong bandwidth reservations occasionally. PR954663

  • When an LSP is link-protected and has no-local-reversion configured, if the primary link (link1) is down and LSP on bypass (link2), then another link (link3) is brought up, before the LSP switch to link3, if link1 is enabled and link3 is disabled, the LSP will stuck in bypass LSP forever. This is a timing issue. PR1091774

  • When multipoint LDP (M-LDP) in-band signaling is enabled to carry multicast traffic across an existing IP/MPLS backbone and routing process is enabled to use 64bit mode, the rpd might crash due to accessing an uninitialized local variables. PR1118459

Platform and Infrastructure

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

Routing Protocols

  • From Junos release 14.1R1 or above, the rpd process might crash while executing CLI command "show isis backup spf results". PR1037114

  • 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

Software Installation and Upgrade

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

VPNs

  • For Layer 2 circuit, PTX3000 uses different VCCV (Virtual Circuit Connectivity Verification) BFD control packet format from that of MX and the other PTX platforms. PTX3000 negotiates Router-alert control channel type, and uses PW Associated Channel Header of Channel Type : 0x0021. However, MX and the other PTX platforms use the Channel Type is 0x0007 without IP/UDP headers. JUNOS takes the Channel-type 0x0007 as default. MX and the other PTX platforms work as expected. This is PTX3000 specific issue. PR1116356

Resolved Issues: 14.1R6

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 may never come out of that loop which may result in high CPU usage (up to 90% sometimes). Because, sampled is not able to consume any states (such as route updates, interface updates) generated by kernel and this results in memory exhaustion and finally resulting in the router not making any updates and forcing a router reboot. PR1092684

General Routing

  • On the PTX3000, if the distributed Bidirectional Forwarding Detection (BFD) session is configured over aggregated Ethernet interface with member links hosted on different FPCs, the BFD session might not come up due to the hello packets can not find the proper outgoing interface. PR992652

  • 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 will be seen. PR1084259

  • On PTX Series platforms, some non-fatal interrupts (for example, CM cache or AQD interrupts) are logged as fatal interrupts. The following log messages will be shown on CM parity interrupt: fpc0 TQCHIP 0: CM parity Fatal interrupt,Interrupt status:0x10 fpc0 CMSNG: Fatal ASIC error, chip TQ fpc0 TQCHIP 0: CM cache parity Fatal interrupt has occurred 181 time(s) in 180010 msecs TQCHIP 0: CM cache parity Fatal interrupt has occurred 181 time(s) in 180005 msecs PR1089955

  • Entropy Label Capability is enabled by-default. 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 is associated with the 'stale' entry is re-used, data errors are seen for packets using the corresponding label. PR1100637

  • On PTX Series platform, when pulling 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

Interfaces and Chassis

  • After removing a child link from aggregated Ethernet bundle, in the output of "show interface <AE> detail", the packet count on the remaining child link spikes, then if add back the previous child link, the count recover to normal. PR1091425

MPLS

  • In the output of the cli command "traceroute mpls ldp", the addresses of the interfaces on transit PTX 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

Resolved Issues: 14.1R5

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 with MPLS environment (30k transit LSP), large number of MPLS interfaces (in this case, 200 interfaces) are configured with 0 or 1 MPLS labels. When these interfaces flap, the FPC kernel memory usage might leak. PR995893

  • A reboot may be required when chassis is powered up first time. PR1034662

  • When there is link/node protection/ECMP for RSVP/LDP transit or egress LSPs with huge scaling and continuous flapping of LSPs like auto-bandwidth case, traffic might get black-holed upon LSP re-optimizations. The issue would get triggered if the same unilist list-id (unilist list-id is a unique id for unilist nexthop) is allocated for two different unilist forwarding topologies. This situation arises when the unilist list-id wraps around after max value of 65535. After the wraparound, if there is long living list-id (which can be due to some node/link protected LSP that has not been re-optimized for a long time), the Packet Forwarding Engine assigns the same list-id during allocation (upon other LSP re-optimizations) and this will trigger the issue as the new unilist will be directed to incorrect interface. PR1043747

  • On PTX Series or T Series platform running Junos OS release 12.1 or later, for interface connected via optical system like DWDM, when the interface is admin disabled, there might be a delay (300-400msec) for system to detect the event and during which time, traffic blackhole might be seen. Please note if disable the interface by breaking the Rx or Tx link, issue will not happen. PR1043762

  • On PTX Series platform with one of the following protocols configured, flapping the protocols will trigger the Composite Next-hop change operation. In rare condition, since it is not properly programmed, the FPC might crash. This is a day-1 issue. - LDP - MPLS - Point-to-multipoint LSP - RSVP - Static LSPs PR1045794

  • For PTX Series router, the unilist next-hop member will become 'replaced' status on Packet Forwarding Engine after interface flapping with ARP timeout. While the problem is happening, routing-table will display all right next-hop status but can not forward traffic since forwarding next-hop in Packet Forwarding Engine is in 'replaced' status and no longer active. PR1046778

  • On PTX Series platform, non-revertive feature for clock synchronous sources does not work correctly. After deleting the primary clock and then adding it back, it will fallback to the primary clock but not stay in secondary. PR1052549

  • When the port on 24x 10GE(LWO) SFP+ (which never went link up since the PIC is onlined) is configured as CLI loopback, the ports will receive framing error until the interface gets physically linked up (that is, with real fiber instead of CLI loop). There would be no problem in normal use. This is only seen in self-loopback testing with CLI loopback. PR1057364

  • In LDP tunneling over single hop RSVP based LSP environment, after enabling "chained-composite-next-hop", the router may fail to create the chained composite next hops if the label value of VPN is equal with the label value of LDP. PR1058146

  • 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 a unified in-service software upgrade (ISSU). The interrupt might got prevented after performing unified ISSU due to disable the interrupt registers before unified iSSU but never restored after. PR1059098

  • On PTX Series routers, the interrupt-driven link down detection may stop working. When the line card is receiving multiple back-to-back fault in very short duration (no matter from remote or local), it may fail to detect all the received interrupts, and this failure may cause delay of the link down detection (for example, it may take PTX Series router ~300ms to make interface down). PR1060279

  • The configured buffer-size will not take effect until either "transmit-rate" or "excess-rate" is configured. PR1072179

Interfaces and Chassis

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

MPLS

  • This is a regression issue related to a timing factor. When LDP session flaps, over which entropy label TLV or any unknown TLV is received, the LDP speaker might not send label withdraw for some prefixes to some neighbors. As a result, these neighbors will still use stale labels for the affected prefixes. PR1062727

  • In Junos OS Release 14.1 and later, the "load-balance-label-capability" knob 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. PTX Series router have the capability and it is reflected in their default forwarding-options configuration. However, there is a software defect in the way Entropy Label Capability (ELC) TLV is encoded in the LDP label mapping message. It might cause the LDP session between routers to go down. PR1065338

Platform and Infrastructure

  • If the system has service-related configurations, error message generated by mountd might be seen: "can't delete exports for /packages/mnt/jbase: Bad address" PR991814

  • In some rare conditions, setting up configuration access privileges, using the "allow-configuration-regexps" or "deny-configuration-regexps” statements will crash the management daemon (mgd), which serves a central role in the user-interface component of Junos OS. PR1029384

Routing Protocols

  • In MPLS TE scenario, if IS-IS shortcuts for family inet6 are enabled, the LSP flapping might cause memory leak, which could result in traffic blackhole or FPC crash. PR1049675

  • When running Simple Network Management Protocol (SNMP) polling to specific IS-IS Management Information Base (MIB) with invalid variable, it will cause routing protocol process (rpd) crash. PR1060485

  • On PTX Series platform with transit BGP-LU chained composite next-hop configured, when advertising LDP routes via BGP labeled unicast (BGP-LU), if the LDP LSP itself is tunneled over an RSVP LSP, the rpd process might crash. Notes: The "set routing-options forwarding-table chained-composite-next-hop transit labeled-bgp" is enabled by default on PTX Series routers. PR1065107

Resolved Issues: 14.1R4

General Routing

  • On PTX5000, the packet drop is observed along with the parity error read from l3bnd_ht entry corresponding to certain addresses. With this SRAM parity error, ASIC will unconditionally drop the packet even if PTX Series does not use l3bnd_ht during lookup. The parity check for l3bnd_ht lookup for PTX5000 will be disabled to avoid the SRAM parity error and packet drop as a workaround. We also add new log message to report the counter value change for slu.hw_err trap count - TL[num]: SLU hw error count xxx (prev count yyy). PR1012513

  • LACP on aggregated Ethernet interfaces does not currently support unified ISSU on PTX Series. A warning message is present before performing unified ISSU if LACP is configured. So the user can discontinue the unified ISSU process. PR1018233

  • On PTX Series with equal-cost multipath (ECMP) route, bouncing the route next-hop interface hosted PIC, the Packet Forwarding Engine might get the route next-hop change message before the interface up message when the PIC is coming up, which results in the next-hop not installed in Packet Forwarding Engine leading to traffic black-holing. PR1035893

MPLS

  • On P2MP MPLS LSP transit router with NSR enabled, when RSVP refresh reduction feature is enabled and LSP link protection is configured on all interfaces, slight P2MP traffic loss might be seen after the graceful Routing Engine switchover is done. PR1023393

  • In MPLS traffic engineering with link or node protection enabled, after adding Shared Risk Link Group (SRLG) configuration, the bypass LSP might ignore the constraint and use a unexpected path. PR1034636

Network Management and Monitoring

  • jnxpic 380 and jnxpic 381 definitions have been added in the "mib-jnx-chas-define" file from 14.1R4 release. PR1036706

Routing Protocols

  • Do not use "ifconfig interface name down" within shell to bring an interface down. This command may cause unexpected behavior. Use the legitimate CLI configuration command "set interfaces interface-name disable" PR1015736

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

Resolved Issues: 14.1R3

General Routing

  • On PTX Series platform, when receiving high rate ipv4/ipv6/mpls packets with TTL equals 1, the ICMP TTL expired messages are sent back to the sender not according with the ICMP rate limit settings. PR893129

  • This PR fixes the issue where output ifIndex was being exported as 0. PR964745

  • When "request system halt" is executed on the PTX Series router, the Routing Engine is halted, but the PTX Series router does not display Halt message on the CRAFT-Interface confirming that the system has halted. PR971303

  • If Routing Engine based link protection is enabled on P2MP ingress LSPs in PTX Series and exit interfaces for P2MP LSP branches via ae bundles, packet might duplicate. PR987005

  • On PTX Series routers with GRES configuration, the chassis daemon might crash when Routing Engine switchover is executed. PR993857

  • Because of MCNH change from Release 13.3 to 14.1 and later, which used new FLOOD_MCNH to replace old MCNH_P2MP, while unified ISSU was upgrading, rpd would crash. PR1000494

  • On PTX Series platform working as LSP ingress router, the MPLS auto-bandwidth feature might cause FPC to wedge condition with all interfaces down. PR1005339

  • When large number of IGMP join packets are trying to reach the router, some IGMP packets might get dropped. PR1007057

  • The problem is seen in PTX Series routers where the composite next hops are not observed, for a given VPN mpls route and hence the show route output command gives a truncated value which results in script failure. This may be due to default disabled l3vpn-cnh in case of transit l3vpn router on PTX Series platform. PR1007311

Infrastructure

  • "delete" or "deactivate" of apply-group defining the entire TACACS or RADIUS configuration configured under [edit system apply-group <>] does not take effect on commit. This could lead to TACACS or RADIUS-based authentication to still continue working despite removal (delete/deactivate) of configuration. PR992837

Interfaces and Chassis

  • On PTX Series platform, CFP-100G-LR4 and CFP2-100G-LR4 optics report incorrect "Laser output power" values on all 4 lanes in show interface diagnostics optics <intf>. PR1021541

MPLS

  • When issue "traceroute mpls rsvp lsp-name" from the MPLS LSP ingress node, if there are PTX Series routers on the LSP path, PTX Series would not list correct downstream router's IP in the TLV of the response packet. PR966986

  • When a PTX Series router is at the merge-point (MP) of a bypass LSP, if MPLS explicit-null has been enabled on the router, and the loopback interface has not been configured under protocol RSVP, the bypass LSP might not work correctly. PR1012221

Routing Protocols

  • Do not use "ifconfig <interface name> down" within shell to bring an interface down because it might cause unexpected behavior. Use the legitimate cli configuration command set interfaces <interface name> disable. PR1015736

  • Establish two BFD sessions between two routers, one is single-hop BFD for directly connected interface and the other is multi-hop MPLS OAM BFD. If configuring the MPLS OAM on the same interface with single-hop BFD, when bringing down MPLS OAM from the ingress, it might result in the OAM BFD session deleted on ingress but it still receiving OAM BFD down packet from egress. Since there is no session matching this BFD packet, it does a normal look up and brings down the single-hop BFD session which is on the same interface. PR1021287

User Interface and Configuration

  • Commit Error happens with load patch or load replace, which is while applying commit difference on backup Routing Engine as part of fast commit process. PR1029474

Resolved Issues: 14.1R2

General Routing

  • On PTX Series platform, when receiving high rate ipv4/ipv6/mpls packets with TTL equals 1, the ICMP TTL expired messages are sent back to the sender not according with the ICMP rate limit settings. PR893129

  • This PR fixes the issue where output ifIndex was being exported as 0. PR964745

  • When "request system halt" is executed on the PTX Series router, the Routing Engine is halted, but the PTX Series router does not display Halt message on the CRAFT-Interface confirming that the system has halted. PR971303

  • If Routing Engine based link protection is enabled on P2MP ingress LSPs in PTX Series and exit interfaces for P2MP LSP branches via ae bundles, packet might duplicate. PR987005

  • On PTX Series routers with GRES configuration, the chassis daemon might crash when Routing Engine switchover is executed. PR993857

  • Because of MCNH change from Release 13.3 to 14.1 and later, which used new FLOOD_MCNH to replace old MCNH_P2MP, while unified ISSU was upgrading, rpd would crash. PR1000494

  • On PTX Series platform working as LSP ingress router, the MPLS auto-bandwidth feature might cause FPC to wedge condition with all interfaces down. PR1005339

  • When large number of IGMP join packets are trying to reach the router, some IGMP packets might get dropped. PR1007057

  • The problem is seen in PTX Series routers where the composite next hops are not observed, for a given VPN mpls route and hence the show route output command gives a truncated value which results in script failure. This may be due to default disabled l3vpn-cnh in case of transit l3vpn router on PTX Series platform. PR1007311

Platform and Infrastructure

  • "delete" or "deactivate" of apply-group defining the entire TACACS or RADIUS configuration configured under [edit system apply-group <>] does not take effect on commit. This could lead to TACACS or RADIUS-based authentication to still continue working despite removal (delete/deactivate) of configuration. PR992837