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

Known Issues

This section lists the known issues in hardware and software in Junos OS Release 15.1F2 for the M Series, 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.

Class of Service (CoS)

  • On MX Series platform, when class-of-service (CoS) adjustment control profiles and "overhead-accounting" are configured, if the ANCP adjust comes before the logical interface (IFL) adding message and the IFL is in "UP" state when added (for example, it may occur when carrying scaling subscribers, for instance, 8K subscribers), for some of the subscribers, the local shaping rate from dynamic profile for the subscriber logical interface may not be overridden by shaping-rate of ANCP. PR1098006

Forwarding and Sampling

  • On MX Series platform, when deleting firewall filter and the routing instance it is attached to, in some race conditions, the filter might not be deleted and remains in resolved state indefinitely. PR937258
  • This defect is seen only when a existing child link from an AE is moved to a newly created AE, simultaneously from both-ends. The new AE is listed as child link in the existing AE in 'show interface ae<>.0 extensive' CLI. PR965872

General Routing

  • Periodic "show subscribers" CLI requests during the GRES recovery (on a scaled system) might lead to spawning of too many subinfo processes. As a side effect, CoA requests might not be serviced while system is kept busy by subinfo processes as authd might take long time to be recovered (it was observed that authd is not recovered after 1+ hours). PR915677
  • When BCM0 interface goes down, the Routing Engine should switch over on M320. PR949517
  • DHCPv6 advertise is sent with source MAC all zeroes if the subscriber is terminated on non-default routing instance. For subscribers on default instance there is no such issue observed. PR972603
  • 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
  • In point-to-point (P2P) SONET/SDH interface environment, there is a destination route with this interface as next-hop. When this interface is disabled, the destination route is still kept in the forwarding table and might cause ping fails with "Can't assign requested address" error. PR984623
  • By default, the syslog utility exports 800,000 logs per second to a remote syslog server. You can modify the number of syslogs to be sent by including the message-rate-limit statement at the [edit interfaces interface-name services-options syslog] hierarchy level to suit your deployment needs. The rate at which syslog messages can be sent to the Routing Engine is 10,000 logs per second. PR1001201
  • 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
  • On MX Series with MPCs and MICs, in Connection-less Network Service (CLNS) L3VPN over Ethernet scenario, because the IS-IS route may be incorrectly treated as ARP-type route (32 bits routes with the MAC and outgoing interface specified in the nexthop), the routing protocol process (rpd) of Provider Edge (PE) device may reject to add the route. PR1041251
  • When enabling pseudowire subscribers the "show subscribers extensive" command does not display CoS policies applied to the subscriber interface. PR1060036
  • Output MTU counter shows incorrect data in the show pfe statistics traffic command output. PR1061111
  • For MX-VC platform, performing unified ISSU in scaled subscribers environment might cause all VC members to get restarted unexpectedly. PR1070542
  • On MX Series routers with MPC based line cards in a setup involving Packet Forwarding Engine fast reroute (FRR) applications, when BFD session flaps the next-hop program in the Packet Forwarding Engine may get corrupted. It may lead to incorrect selection of next-hop or traffic blackhole. PR1071028
  • Traffic throughput test between MPC1/1E/2/2E card and MPC2E/3E NG card, flowing from MPC1/1E/2/2E card to MPC2E/3E NG card is less than from MPC2E/3E NG card to MPC1/1E/2/2E card. PR1076009
  • In subscriber management environment, the PPP daemon (jpppd) might crash repeatedly due to a memory double-free issue. PR1079511
  • 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
  • TCP messages do not have their MSS adjusted by the MS-MPC (SPARKS) card, if they do not belong to an established session. PR1084653
  • After upgrading to Release 14.2R3.8, loopback ISO family address may be stuck in KRT queue. PR1097778
  • Neighbor deletion and re-creation on a session when back pressure is applied on all the active neighbor sessions could cause the new session to be in stuck state. This PR addresses this problem by ensuring that the neighbor session is established first. PR1098549
  • If a loopback logical interface has greater than 400 addresses configured, we will have memory leak in bbe-smgd. This bug exists in 14.1X51-D50. PR1101652
  • In VRRP for IPv6 environment, when feature "forwarding IPv6 Solicited Router Advertisement as unicast" is enabled (by enabling configuration statement "solicit-router-advertisement-unicast"), if the configuration statement "virtual-router-only" is also configured on the interface, the interface (if the groups are in the master state) may not respond with router-advertisement (RA) messages after receiving the router-solicit messages (RS). PR1103113
  • If fpc offline configuration statement is configured after the presence of Non-recoverable faults, then offline action will not be performed. PR1103185
  • After executing CLI command "show route extensive", routing protocol process (rpd) may get into infinite loop and not respond anymore because the command may get executed a couple times itself. In this situation, rpd high CPU utilization (running over 90% sometimes) might be seen on the device, and also the memory which used to store the command output would not be freed during those executions (in normal utilization, the memory uses about 160KB, but in problematic situation, it can swell to 3GB size), which would lead to rpd crash eventually after memory exhaustion. PR1104090

Interfaces and Chassis

  • Packet Forwarding Engine continues to forward traffic to DHCP client on a demux interface when ae0 interface is down. In this scenario the AE interface bundle has five members and configured with minimum link value of 4. When two members are down, the ae0 interface also goes down, but Packet Forwarding Engine continues to forward traffic on other members for the demux interface. PR836846
  • Chap Local-name defaults to 8 characters. Should be 32. PR996760
  • In rare case, when a child link flaps within an aggregate bundle which happens twice within a short period of time (that is, if the child interface comes up within a short period of time after it has gone down), there is a probability that a race condition might happen. The result is to have child next hop within aggregate next hop to be in "Replaced" state on the FPC, leading to traffic blackholing. PR1032931
  • In some configurations agg_pfe_get_fwd_options, log message is generated at the excessive rate. This log message can be helpful during troubleshooting, but it is not needed during normal operation. Though it is not impacting service, it may increase the load of the system and it was decided to cover this message under traceoptions in order to optimize system performance. PR1047564
  • 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
  • show interface extensive will show these additional counters... <<<< Preclassifier statistics: Traffic Class Received Packets Transmitted Packets Dropped Packets real-time 0 0 3 network-control 0 0 3 best-effort 0 0 3 <<<< PR1060070
  • Link Up/Down SNMP traps for AE member links might not be generated, but the SNMP traps for the AE bundle works well. PR1067011
  • Deactivating/activating logical interfaces may cause BGP session flap when BGP is using VRRP VIP as source address. This is caused by a timing issue between DCD and VRRP overlay file. When DCD reads the overlay file, it is not the updated one or yet to be updated. This results in error and DCD stops parsing VRRP overlay file. PR1089576
  • On MX Series platform, "cfp_lh_update_1sec_pm_var received" messages are periodically logged with Warning level. The severity of this message has been revised. PR1089592
  • In the dual Routing Engines scenario with GRES and ae0 interfaces configuration, if GRES is disabled on system, the backup Routing Engine should remove the ae0 bundle. However, it does not go clean and ae0 remains in backup Routing Engine. After switching, Routing Engine mastership to make other Routing Engine as master, the new master Routing Engine (which was backup earlier) continues to use invalid MAC address "00:00:00:00:00:00". PR1089946

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
  • V44 defines the next generation of Juniper Networks Fabric using MX as the aggregation device (AD) and EX4300/QFX5100Â’s as the Satellite Devices (SD). When V44 port extension is in use, after switching from Master to Backup Routing Engine, the ppman daemon on the SDs may crash and not be restarted. It results in the aggregated Ethernet (ae) bundle over v44 extended ports does not come up. PR1101266

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 gets isolated, unexpected packet drops will be observed. PR1030815
  • In Resource Reservation Protocol (RSVP) environment, if CoS-based forwarding (CBF) for per LSP (that filter out traffic not related to that LSP) is configured, and either the feature fast-reroute or link-protection is used on the device, when the primary link is down (for example, turning off the laser of the link), due to some next hops of the traffic may be deleted or reassigned to different class of traffic, the RSVP local repair may fail to process more than 200 LSPs at one time. The traffic may get dropped by the filter on the device before the new next hop is installed. In this situation, the feature (fast reroute or link protection) may take longer time (for example, 1.5 seconds) to function and the traffic loss might be seen at the meantime. In addition, the issue may not be seen if the CBF for per LSP is not configured on the device. PR1048109

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). PR988566

Platform and Infrastructure

  • MX Series-based line card might crash when trying to install the composite next-hop used for the next-hop-group configuration related to port mirroring of traffic over IRB to an LSI attached to VPLS instance for a remote host. PR1029070
  • 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
  • When using the "ping detail" command, the interface number is provided on the output instead of the interface name. PR1078300
  • 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
  • If with both MPC/MSDPC and other type of DPCs equipped, for local switching at mesh group level, split horizon on PW interfaces won't work and this would cause packets to loop back to same PW interface. PR1084130
  • IPv6 packets with non-UDP and non-TCP payload belonging to the same flow might get re-ordered when being forwarded by MX Series MPC Packet Forwarding Engine. PR1098776
  • Due to a software defect found in 13.3R7.3 and 14.1R5.4 inclusively, Juniper Networks strongly discourage the use of Junos software version 13.3R7.3 on routers with MQ-based MPC. This includes MX-Series with MPC1, MPC2; all mid-range MX-Series; and some of EX9200 line cards. PR1108826

Routing Protocols

  • It is necessary that the MSDP peer local-address matches the PIM RP address on routers that are RP. MSDP RPF check might fail in rare cases when both these addresses are not equal. PR35806
  • Continuous soft core-file may be observed due to bgp-path-selection code. RPD forks a child and the child asserts to produce a core-file. The problem is with route-ordering and it is auto-corrected after collecting the soft-assert-corefile, without any impact to traffic/service. PR815146
  • Support for the Pragmatic General Multicast protocol (daemon pgmd) is being phased out from Junos OS. In Junos OS Release 14.2 the CLI is now hidden (although the component is still there and configurable). In Junos OS Release 15.1 the code and its corresponding CLI are removed. PR936723
  • 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

Services Applications

  • 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 core. This PR addresses/fixes this issue. PR1109447
  • With scaling Layer 2 Tunneling Protocol (L2TP) sessions (for example, 128k sessions), when executing L2TP "show" command in one terminal and "clear" command in another terminal simultaneously, pressing Ctrl-C or closing the terminal on one terminal might cause the jl2tpd process crash. PR1063207

Subscriber Access Management

  • When the MX router acting as the Policy and Charging Enforcement Function (PCEF) uses Gx-Plus to request service provisioning from the Policy Control and Charging Rules Function (PCRF), the authentication service process (authd) might crash during the subscribers logout. PR1034287
  • This issue was introduced as part of another fix. Please contact JTAC for the recommended release for your deployment. PR1049955
  • authd core at /src/junos/usr.sbin/authd/authd_ipc.c:1145 with JSRC. PR1094674

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

VPNs

  • When you modify the frame-relay-tcc statement at the [edit interfaces interface-name unit logical-unit-number] hierarchy level of a Layer 2 VPN, the connection for the second logical interface might not come up. As a workaround, restart the chassis process (chassisd) or reboot the router. PR32763
  • It is planned that future releases of Junos OS will modify the default BGP extended community value used for MVPN IPv4 VRF Route Import (RT-Import) to the IANA-standardized value. Thus, default behavior is expected to change such that the behavior of the configuration 'mvpn-iana-rt-import' will become the default and the 'mvpn-iana-rt-import' configuration will be deprecated. PR890084

Related Documentation

Modified: 2017-07-06