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 
ContentIndex
  
[+] Expand All
[-] Collapse All

No index entries found.

Known Issues

This section lists the known issues in hardware and software in Junos OS Release 15.1F3 for the MX Series and T 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

  • A PE device running EVPN IRB with an IGP configured in a VRF associated with the EVPN instance will be unable to establish an IGP adjacency with a CE device attached to a remote PE. The IGP instance running in the VRF on the PE may be able to discover the IGP instance running on the remote CE through broadcast or multicast traffic, but will be unable to send unicast traffic directly to the remote CE. PR977945
  • On MX Series platform with IPsec, NAT or RTM service configured on MS-MPC or MS-MIC inserted in an XM chip based MPC, if the packet undergoes fragmentation over the multiservice (ms) interface and the last fragment is very small (the last fragment packet length is less than 120 bytes), the MPC may crash and reboot due to the packet length calculation defect. As a workaround, we can disable fragmentation over the ms interface. PR1025824
  • If precision timers and traceoptions are enabled for BGP, then both main-thread and precision timers pthread try to rotate the same tracefile without taking any locks. As a result, all the status commands for rpd and krt may be timed out. PR1044141
  • On the MX Series and T Series with BGP configured to carry flow-specification route, in case of deleting a filter term and policer, then adding the same term and policer back (it usually happens in race condition when adding/deleting/adding the flow routes), since confirmation from dfwd for the deleting policer might not be received before attempting to add the same policer, the rpd would skip sending an add operation for it to dfwd. As a result, when the filter term is sent to dfwd and tells it to attach to the policer, dfwd had already deleted the policer, and since rpd skipped re-adding it, dfwd will reject the attach filter with policer not found error and rpd will crash. PR1052887
  • Terminating a signal PPPoE session might cause all clients in this VLAN to be deleted. PR1081361
  • The rpd process might crash on both master and backup Routing Engines when a routing instance is deleted from configuration if the routing instance is cleaned up before the interface delete is received from device control daemon (dcd). This is a rare timing issue. PR1083655
  • On XL-based cards such as MPC5/MPC6, PPE thread timeout errors (resulting in PPE trap files) can be triggered when the FPC allocates illegal memory space for the forwarding state of router operations. - In certain cases, this can result in packet loss depending on how many packets use this forwarding state. PR1100357
  • When the null pointer of jbuf is accessed (jbuf, that is, a message buffer is allocated only when the packet is ready to process. The buffer is freed after the packet completes ALG handling is accessed), for example, when using the Microsoft Remote Procedure Call (MS RPC) (as observed, issue may also happen on Sun Microsystems RPC) Application-level gateway (ALG) with NAT (stateful firewall is used as a part of the service chain), if the traffic matching configured universal unique identifier (UUID) is arrived on the ALG, the mspmand (which manages the Multiservice PIC) crash occurs. PR1100821
  • If fpc offline configuration statement is configured after the presence of non-recoverable faults, then offline action will not be performed. PR1103185
  • The commands "show igmp interface <interface name>" and "show mld interface <interface name>" may sometimes result in memory corruption and generate a core file of smg-service daemon. PR1120484

Interfaces and Chassis

  • Chap Local-name defaults to 8 characters. Should be 32. PR996760
  • The following log can be seen on OTN capable pics after each commit , which indicates incorrect stats TLV setting. No service impact found. /kernel: ge-1/1/0: Unknown TLV type 356 /kernel: ge-1/1/0: Unknown TLV type 361 /kernel: ge-1/1/0: get tlv ppfeid 0xe-0/2/0: get tlv ppfeid 0xe-0/3/0: get tlv ppfeid 0xe-1/2/0: get tlv ppfeid 0xe-1/3/0: get tlv ppfeid 0xe-2/0/0: get tlv ppfeid 0xe-2/1/0: get tlv ppfeid 0xe-2/2/0: get tlv ppfeid 0xe-2/3/0: get tlv ppfeid 0xe-5/1/0: get tlv ppfeid 0xe-5/1/1: get tlv ppfeid 0xe-5/1/2: get tlv ppfeid 0xe-5/1/3: get tlv ppfeid 0xe-5/1/4: get tlv ppfeid 0xe-5/1/5: get tlv ppfeid 0xe-5/1/6: get tlv ppfeid 0xe-5/1/7: get tlv ppfeid 0xe-5/1/8: get tlv ppfeid 0xe-5/1/9: get tlv ppfeid 0. PR1057594
  • During scaling login/logout different types of subscribers (e.g. 17K) on LAC router, there might be some L2TP LAC subscribers stuck in terminating state and never get cleared, blocking new sessions from establishing on the same interface. PR1094470
  • On PB-2OC12-ATM2-SMIR PIC, port 0 and port 1 are configured with clock source as external. If Loss of signal (LOS) is inserted on port 0, the port 0 will down. The expected behavior is clock being used from port 1. But in this case, port 0 down will result in port 1 flapping and reporting SONET phase lock loop (PLL) errors. PR1098540

Layer 2 Features

  • When "input-vlan-map" with "push" operation is enabled for dual-tagged interfaces in "enhanced-ip" mode, there is a probability that the broadcast, unknown unicast, and multicast (BUM) traffic may be blackholed on some of the child interfaces of the egress Aggregated Ethernet (AE) interfaces. PR1078617
  • When a DHCP relay request is received with the broadcast bit set via a VTEP interface, the OFFER back from the DHCP server will not be sent back to the client over the VxLAN interface. Unicast offers over VxLAN and both broadcast and unicast offers over native VLAN interfaces work fine. PR1126909

MPLS

  • RSVP graceful restart does not function for LSPs that have a forwarding adjacency (FA) label-switched path (LSP) as a next hop. PR60256
  • 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 MX Series and the T4000 have the capability and it is reflected in their default forwarding-options configuration. However, there is a software defect in the way which 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
  • When local bandwidth accounting for inactive/adaptive standby path figures that there is not enough bandwidth to fit it in an already full link and brings it down, CSPF will not be retried on the path unless there is some change in TE database. PR1129602

Network Management and Monitoring

  • When a firewall filter has one or more terms which have MX Series-only match condition or actions, such filters will not be listed during SNMP query. This behavior is seen typically after Routing Engine reboot/upgrade/master-ship switch. Restarting mib2d process will cause to learn these MX Series-only filters: cli > restart mib-process After mib2d restart, SNMP mib walk of firewall OIDs will: - list all the OIDs corresponding this MX Series-only filter - count correctly as configured in the filter Now, despite the SNMP mib walk for firewall OIDs lists all OIDs and appropriate values, messages logs will report the following logs for every interface that has this MX Series-only filter applied. > Jul 8 15:52:09 galway-re0 mib2d[4616]: %DAEMON-3-MIB2D_RTSLIB_READ_FAILURE: get_counter_list: failed in reading counter names ae33.1009-i: 288 (No such file or directory) > Jul 8 15:52:09 galway-re0 mib2d[4616]: %DAEMON-3-MIB2D_RTSLIB_READ_FAILURE: get_counter_list: failed in reading counter names ae31.1004-i: 257 (No such file or directory) > Jul 8 15:52:09 galway-re0 mib2d[4616]: %DAEMON-3-MIB2D_RTSLIB_READ_FAILURE: get_counter_list: failed in reading counter names ae33.1010-i: 289 (No such file or directory) > Jul 8 15:52:09 galway-re0 mib2d[4616]: %DAEMON-3-MIB2D_RTSLIB_READ_FAILURE: get_counter_list: failed in reading counter names ae31.1004-i: 257 (No such file or directory) The above 2 issues are addressed in this PR fix. PR988566
  • SNMPD's Response time calculation was seen as a very high (-)tive value, in the output of "show snmp statistics extensive". PR1112521

Platform and Infrastructure

  • Bad udp checksum for incoming DHCPv6 packets as shown in monitor traffic interface output. The UDP packet processing is normal. This is a monitor traffic issue as system decodes checksum=0000. PR948058
  • On MX Series-based platform, when using inline Two-Way Active Measurement Protocol (TWAMP) server (the server address is the inline service interface address), because the TWAMP server may incorrectly calculate the packet checksum, the packet may get dropped on the TWAMP client. PR1042132
  • On MX Series routers, when using FPC with feature inline sampling activated, memory partition error messages and memory leak might be observed on the FPC. In some cases, this issue only affects sample route records but not regular Packet Forwarding Engine routes or next-hops. However, in the extreme case, it is also possible to cause the Packet Forwarding Engine to fail to install routes into forwarding next hops, and hence traffic drops. On MX Series routers, when using FPCs, or T4k or TXP-3D routers, when using FPC-3D FPCs, Junos OS Release 13.3R5 and Release 14.1R4 are exposed. Junos OS Release 14.2R1 and later are not exposed. PR1071289
  • LMEM is an internal memory in LU/XL ASIC chip. It has private and shared regions for Packet Processing Engines. LMEM data errors are very rare events caused by environmental factors (this is not created by software). Due to a software defect, an error in the shared LMEM region will result in corruption of critical data structures of Packet Processing Engines that causes unpredictable communication of LU/XL ASIC chip with MQ/XM ASIC chip. These events will corrupt the state in MQ/XM and lead to a MQ/XM wedge. The MQ/XM wedge would cause fabric blackhole and finally reboot the line card. PR1082932
  • On MX Series-based platform, when the type of the IPv6 traffic is non-TCP or non-UDP (for example, next header field is GRE or No Next Header for IPv6), if the traffic rate is high (for instance, higher than 3.5Mpps), the packet re-ordering may occur. PR1098776
  • After changing an outer vlan-tags, the ifl is getting programmed with incorrect stp state (discarding), so the traffic is getting dropped. PR1121564

Routing Protocols

  • Continuous soft core-dump may be observed due to bgp-path-selection code. RPD forks a child and the child asserts to produce a core-dump. The problem is with route-ordering. And it is auto-corrected after collecting this soft-assert-coredump, without any impact to traffic/service. PR815146
  • In rare cases, rpd may write a core file with signature "rt_notbest_sanity: Path selection failure on ..." The core is 'soft', which means there should be no impact to traffic or routing protocols. PR946415
  • There are two issues in the PR: (1) In multicast environment, incoming interface list (IIF) list has only RPF interface. Designated forwarder (DF) winners are not added in the list in backup Routing Engine. (2) "Number of downstream interfaces" in show pim join extensive is not accounting Pseudo-VXLAN interface. PR1082362
  • When the IS-IS configuration has been removed, the IS-IS LSDB contents get flushed. If at the same time of this deletion process, there is an SPF execution (that is, try to access the data structures at same time when/a fraction of seconds after freeing its content), routing protocol process (rpd) crash occurs. PR1103631

Services Applications

  • The cause of the kmd crash is not known. This is not due to SA(Security Associations) memory corruption. The code looks like SA is getting freed without clearing the table entry. PR1036023
  • In the NAT environment, the jnxNatSrcPoolName OID is not implemented in jnxSrcNatStatsTable. PR1039112
  • In some cases after unified ISSU upgrade/GRES switch/jl2tpd restart, if the subscriber is terminated during the unified ISSU/GRES/restart process, jl2tpd may generate a core file. PR1109447

Subscriber Management and Services (MX Series)

  • In subscriber management environment, subscriber login/logout causes multiple daemons to interact via Inter-Process Communication (IPC). A 32-bit counter "Current time" is used internally for this type of communication to collect stats like elapsed time. The error log message, such as "invalid current (31902492), baseline (4287968879), time (0)", might be observed when "Current time" is overflowing and holding an invalid time. PR1079507
  • In subscriber management environment with three or more radius-servers connected to an MX Series router, when AAA sends a request to one radius-server, if that particular request and all retries time out, AAA records the time. For the next request, AAA incorrectly uses the recorded time and marks that the radius-server down even before trying to send out the request. PR1091157

User Interface and Configuration

  • User needs to wait until the page is completely loaded before navigating away from the current page. PR567756
  • Using the Internet Explorer 7 browser, while deleting a user from the Configure > System Properties > User Management > Users page on the J-Web interface, the system is not showing warning message, whereas in the Firefox browser error messages are shown. PR595932
  • If you access the J-Web interface using the Microsoft Internet Web browser version 7, on the BGP Configuration page (Configure > Routing > BGP), all flags might be shown in the Configured Flags list (in the Edit Global Settings window, on the Trace Options tab) even though the flags are not configured. As a workaround, use the Mozilla Firefox Web browser. PR603669
  • On the J-Web interface, next hop column in Monitor > Routing > Route Information displays only the interface address and the corresponding IP address is missing. The title of the first column displays "static route address" instead of "Destination Address." PR684552
  • On the J-Web interface, Configure > Routing> OSPF> Add> Interface Tab is showing only the following three interfaces by default: - pfh-0/0/0.16383 - lo0.0 - lo0.16385 To overcome this issue and to configure the desired interfaces to associated ospf area-range, perform the following operation on the CLI: - set protocols ospf area 10.1.2.5 area-range 12.25.0.0/16 - set protocols ospf area 10.1.2.5 interface fe-0/3/1. PR814171
  • When entering "restart r" incomplete command in CLI, even though there are multiple options available, command "restart routing" is executed finally. It should throw an error like "error: invalid daemon: r". PR1075746

Related Documentation

Modified: 2016-08-18