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.1F4 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.

Forwarding and Sampling

  • When "shared-bandwidth-policer" is configured with aggregate Ethernet (AE), if there are filters configured on the logical interface family (IFF) of the AE interface, the FPC may crash upon rebooting (it is also seen when new FPC coming up) because the running thread is stuck at the association of the filter which is in the resolved state (this happens when the filter has not yet come down to the Packet Forwarding Engine whereas its association has already been reached). It is a timing issue in the above circumstance. However, it could be consistently reproduced when moving links from one aggregate Ethernet to another and then rebooting the FPC by scripts. As a workaround, if it is possible, the administrator could disable all the filter configurations and then bring up the line card. PR1113915

General Routing

  • 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 get timed out. PR1044141
  • When flag is specified under ipsec-vpn traceoptions to trace IPsec operations, no message is logged to the specified trace file as expected. The issue impacts on debug capability only. PR1073705
  • From Junos OS Release 13.3, configuration changes like activating "fast-lookup-filter", adding or deleting "interface-specific" or any other filter property, adding or deleting any term, or changing any match condition in any term in the filter, which updates the firewall filter in a rare sequence might result in loss of DMEM and kernel memory resources or some free error messages. This issue impacts only MX Series-based line card and occurs in rare cases. The following log messages might be observed from Junos OS Release 13.3: [LOG: Err] jnh_free(10040): ERROR [FW/0]:1 Paddr 0x00400000, addr 0x0, part_type 0call_stack 0x404906b4 0x418ecdbc 0x418ed2e0 0x418baca0 0x418becc8. And the following log messages might be observed from Junos 14.2: [LOG: Err] FREE ERR FW[0]: FW, 1 dw (1 blk) @ PA 0x7c63f00d addr 0x23f00d PR1077338
  • 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
  • There are entries for PEM in jnxFruEntry in VMX. It is not necessary and is cosmetic. PR1094888
  • The OpenSSL project has published a set of security advisories for vulnerabilities resolved in the OpenSSL library in June and July 2015. Junos OS is affected by one or more of these vulnerabilities. PR1095598
  • When route convergence occurred, the new gateway address is not updated correctly in inline-jflow route-record table (route-record table is used by sampling), and the sampling traffic forwarding might be affected, but normal routing would be not affected. PR1097408
  • When DHCP subscribers are terminated at specific routing-instances and the interface stack is IP demux over vlan-subinterface over AE interface, there might be a memory leak in kernel AE iffamily when subscribers login/logout. 1097824
  • Fragmenting a special host outbound IP packet with invalid IP header length (IP header length is greater than actual memory buffer packet header length), can trigger NULL mbuf accessing and dereferencing, which may lead to a kernel panic. PR1102044
  • On MS-MPC equipped MX Series platform, during the "three-way handshake" process, when receiving ACKs (e.g. after sending SYN and receiving SYN/ACK) with window size 0 (as reported, it is set to 0 by TCP client when using some proprietary protocol), the ACKs would be incorrectly dropped by the line card due to failure in TCP check. This issue could be avoided by preventing software from dropping packets that fail in the check, for example, by CLI command below, re# set interfaces ms-3/0/0 services-options ignore-errors tcp. PR1120079
  • MX Series router acting as L2TP access concentrator (LAC) may not recognize the MLPPP protocol field (0x003d) in the inbound PPP packet from customer premise equipment (CPE) and could disconnect the session not respecting idle-timeout. The traffic forwarding might be affected. PR1123233
  • When GRES is enabled and EVPN is configured, the kernal crash may be seen during the Routing Engine mastership switchover. PR1126195
  • When Junos OS devices use Link Layer Discovery Protocol (LLDP), the command 'show lldp neighbors' displays the contents of PortID Type, Length, and Value (TLV) received from the peer in the field 'Port Info', and it could be the neighbor's port identifier or port description. Junos OS CLI configuration statement can select which 'interface-name' or 'SNMP ifIndex' to generate for the PortID TLV, so we do not have any problem as long as two Junos OS devices are connected for LLDP, but we might have an interoperability issue if other vendor device which can map the configured 'port description' in the PortID TLV is used. In such case, Junos OS displays the neighbor's PortDescription TLV in the 'Port info' field, and if the peer sets 'port description' whose TLV length is longer than 33 byte(included), Junos OS is not able to accept the LLDP packets, then discards packets as errors. The PortID TLV is given as : "the port id tlv length = port description field length + port id subtype(1B)". PR1126680
  • In multi-homing Ethernet VPN (EVPN), if there are two loopback addresses and the router-id and the primary loopback addresses are different on the designated forwarder (DF) PE, when the link between CE and DF PE is down, the Type 4 route of old DF are not deleted properly from the backup PE and causing the new DF election failure. The traffic forwarding will be affected. As a workaround, we should configure single primary loopback address and remove "router-id" configuration statement on both multi-homing PEs. PR1126875
  • On MX Series routers with MS-MIC, changing configuration of sampling input parameters, such as "rate" under forwarding-options, is not reflected without restarting the MS-MIC. PR1131227
  • CLI output of "clear services sessions" gives an impression to the user that session is marked for deletion in case of delayed delete but the XML output "clear services sessions|display xml"of the above command says "session removed". Ideally both should convey the same message to the user. The changes have been made to make sure CLI and XML information given to the user in sync. PR1132006
  • In certain Junos OS releases, making changes to the router-advertisement protocol stanza does not trigger new RAs to be sent after the commit. PR1132345
  • MXVC-Same subnet VC-heartbeat polling failed to recover. PR1136119

Interfaces and Chassis

  • Chap Local-name default to 8 characters. Should be 32. PR996760
  • Two redundant logical tunnels (rlt) interfaces are configured with configuration statement "per-unit-mac-disable" enabled. After configuring the second one, the first rlt interface goes down. rlt0 { logical-tunnel-options { per-unit-mac-disable; <<<<<< } } PR1055005
  • 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
  • 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, port 0 will be 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
  • When an interface is added as part of an interface-set configuration, then there should be a valid configuration defined for that interface. PR1128038
  • MX-VC specific behavior for SNMP walk of jnxOperating* containers was divergent from physical MX Series router. Returned to vergence. PR1136414

Layer 2 Features

  • In a VPLS network that has a combination of automatic-site-id and fixed site-id together, if automatic-site-id is configured the first time and without deactivating/activating the VPLS protocol, it might not auto-recover when site id collision is detected, and the VPLS connections are stuck in LN/RN state. As a workaround, we can deactivate/activate the VPLS protocol. PR1065952
  • There was bug in handling the code while redistributing the xmit and adj entries to ppman, when the interface entry was in pending distribution state. PR1116741
  • In scenario that DHCP relay is used along with Virtual Extensible Local Area Network (VXLAN), if DHCP discover packet is received with the broadcast bit set via a VXLAN interface on MX Series platform (which is acting as DHCP relay), the OFFER back from the DHCP server will not be forwarded back to the client over the VXLAN interface. Unicast offers (that is, DHCP offer packet with unicast bit set) over VXLAN and both broadcast and unicast offers over native VLAN interfaces work fine. PR1126909
  • When AE is core facing ifl in ldp-mesh vpls instance with local-switching in it, the traffic is looped back. PR1138842

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 scenario of egress-protection using stub-alias advertise mode where Point of Local Repair (PLR) use 'dynamic-rsvp-lsp' in LDP link protection, if protected PE get isolated, unexpected packet drops will be observed. PR1030815
  • In MPLS scenarios, removing the "family mpls" configuration from an outgoing interface may cause inet and/or inet6 nexthops associated with that interface to unexpectedly transit to dead state. Even adding back "family mpls" cannot restore it. PR1067915
  • These benign error messages can occur when bringing up new interfaces or line cards and can be ignored. The Junos OS code will be cleaned up to remove these messages in later code. PR1136033
  • There is no entropy-label for LDP route in scenario of LDP tunneling across 1hop RSVP LSP + explicit-null RSVP label. Either remove LDP tunneling or RSVP explicit-null will resolve the issue as work-around. PR1142357

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 TRIO-only filter applied. router-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) router-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) router-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) router-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
  • Mib2d cores while trying to re-add a lag child into the internal DB since the entry is already present in the internal DB. Before adding the child link, mib2d does a lookup on the tree to know if the entry is not already there. However, this lookup returns no results, since the child link is part of snmp filter-interface configuration. PR1039508
  • A merge conflict was incorrectly resolved by changing snmp trap value of jnxDomLaneNotifications to 26. The correct value will always be 25. PR1145144

Platform and Infrastructure

  • 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
  • With MX Series-based FPC, Load balance hash seed will be changed after unified ISSU. Since the hash seed value will be reverted to original value by rebooting FPC, there would be hash value inconsistency in the system which might introduce blackholing on multicast flavor traffic (mcast or BUM on vpls/l2-bridge). PR1086286
  • 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
  • The kernel next-hop acknowledgement timeout maximum interval configured (krt-nexthop-ack-timeout) under the CLI hierarchy "routing-options forwarding-table" has been increased to 400 seconds to avoid performance issues with scaled subscribers. PR1102346
  • Improved VTY commands to show internal JNH memory usage. PR1103660
  • With scaled firewall filters attached to interfaces (e.g. 10k+ filters), running "show configuration" command can cause high CPU of the mgd process. As a workaround, we can use "show configuration |display set" command to view the configuration. PR1134117

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
  • BFD session might reset on commit if version is configured. The adaptive RX interval gets set to 0 which results in the reset. A sample configuration of BFD version is as following: protocols { bgp { bfd-liveness-detection { version 1; minimum-interval 1000; transmit-interval { minimum-interval 1000; } } } PR1045037

Services Applications

  • In some cases after unified ISSU upgrade/GRES switch/jl2tpd restarts, if the subscriber is terminated during the unified ISSU/GRES/restart process, jl2tpd may core. PR1109447

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
  • When committing a configuration with very long as-path, in this case the as-path name is almost 12000 characters long, the committed process might crash. The committed process restart results in a minimal impact of system. PR1119529

VPNs

  • In L2VPN or VPLS scenario with Junos OS Release 14.2R4, after executing some negative operations, e.g., deactivate/active BGP and IGP, or restart FPCs, the rpd process might crash due to a NULL pointer access in code. PR1104472
  • Source PE will send the duplicate multicast traffic over P-tunnel when Receiver PE advertises the different label for IPV4 and IPV6 in type 1 BGP route. PR1128376

Related Documentation

Modified: 2016-04-20