Alert Type

SRN - Software Release Notification

Product Affected

T PTX MX JAM-STOUT VRR VMX series

Alert Description

Junos Software Service Release version 15.1F5-S6 is now available for download from Junos software download site.

Download Junos Software Service Release:

1. Go to Junos Platforms - Download Software page .
2. Select your product.
3. From the Type/OS drop-down menu, select Junos SR.
4. From the Version drop-down menu, select your version.
5. Click the Software tab.
6. Select the Install Package Release needed, and follow the prompts.

Solution

↵ Junos Software Service Release version 15.1F5-S6 is now available.

The following are incremental changes in 15.1F5-S6:
PR Number Synopsis Description
1066336 DPD/IKEv2 informational messages are dropped at the peer. DPD/IKEv2 informational messages are dropped at the peer. Adding vendor ID in the INFORMATIONAL message is causing peer to drop such packets.
1150316 Kernel might crash when login/logout tunneled PPPoE subscribers over an extended period When using MX Series platform as Layer 2 Tunnel Protocol (L2TP) L2TP access concentrator (LAC), if login/logout tunneled PPPoE subscribers over an extended period (e.g., login/logout 16K subscribers for 24- 48 hours), kernel crash may occur due to next-hop issue.
1164665 High CPU load of sampled (50-80%) caused by lots of Class of Service updates In rare situation, if the "forwarding-option" is configured, and the sampled process of device receives lots of Class of Service updates such as changing the QoS configuration on interfaces (5-7 times per hour), high CPU utilization of sampled process(50-80%) might occur.
1175654 PTX might blackhole traffic when certain combination of FPCs is installed within the same chassis Traffic drop might be observed on PTX platform working in interoperability mode when chassis is populated with ( FPC-PTX-P1-A (FPC) OR FPC2-PTX-P1A (FPC E) ) AND ( FPC3-PTX-U2 (FPC-P1) OR FPC3-PTX-U3 (FPC-P2)), due to bug in CRC computation logic.
1184504 Incorrect consistent hashing behavior caused by next-hop resolve failure With BGP add-path and consistent-hash enabled, when a BGP learnt route prefix with multiple paths(next-hop) is installed in the forwarding-table, all the next-hops should be reachable/resolvable at the time of installing the route in the forwarding-table. However, there might be a chance that any of the next-hops are not resolvable at that time, which will lead PFE's incorrect route programming. In this case, traffic forwarded to this prefix will be affected.
1185362 BGP routes received in "inet6 labeled-unicast" family might not be installed in forwarding-table when multipath is configured A PTX node with PR 1169289 fix may not be able to play the role of 6PE ingress node for inet6 traffic, if multipath is enabled for the peer giving the inet6 routes in "inet6 labeled-unicast" family. This is because PR 1169289 makes the PTX create a composite-nexthop for the inet6.0 route, which is not supported.
1186537 Packets destined to VIP address or transit packets with dmac as VRRP VMAC with payload size greater than 166 bytes getting dropped on MPC7E/8E/9E Traffic destined to VRRP VIP address or transit traffic with destination mac as VRRP VMAC which has paylod beyond 166 bytes (excluding headers) are dropped as "my-mac check failed" on MPC7E/8E/9E
1187721 The changes to srrd process will reduce available memory for sampling on MX80 series The changes to srrd (sampling route reflector daemon - new architecture for sampling) process between 14.2R5.8 and 14.2R6.5 severely reduce MX80 series available memory and therefore RIB/FIB scaling.
1203147 NAT service route is available in route table even after disabling service interface When configuring Network Address Translation (NAT) service, the service route is still available in route table even after disabling service interface. Any types of service interfaces (except ams- interface) that supports NAT might be affected.
1216300 Memory allocation failure due to the memory fragmentation In large scale configurations or environment with high rates of churn, the FPC ASIC memory will become "fragmented" over time. It is possible in an extreme case that memory of a particular size will become exhausted and due to the fragmentation, the available memory will not fulfill the pending allocation.
1220185 Linecard crash after firewall filter configuration change Trio-based linecards might crash after firewall filter configuration change is committed.
1222179 Multiple stale LSP entries for single LSP could be seen if the link/node failure that triggered a bypass persists for a long time If the link/node failure that triggered a bypass persists for a long time, and there are LSPs that don't get globally repaired, multiple stale LSP entries are showing down and listed multiple times in the MPLS LSP.
1224820 PTX FPC3 login fails, core-dumps or reloads when receiving noise on the console port PTX FPC3 might receive noise on the FPC console port, and interprets it as valid signals. This might cause login fails on the console port, core-dumps or even reloads.
1235504 BGP ORR related rpd core RPD might potentially crash and restart when following conditions are met: - ISIS is configured. - bgp orr (optimal-route-reflection) is configured - ISIS LSP is purged (e.g. topology change after a link flap) Note: The likelihood of an RPD crash is higher in larger databases, where ISIS LSP can?t fit into a single fragment.
1237164 jflow v9 cannot sample multicast traffic in multi-copy scenario in MX2010/MX2020. MX2010/2020 cannot sample multicast traffic when this multicast is copied to multiple interfaces. This behavior is specific to MX2010/MX2020 with MS-MIC.
1237531 RSVP bandwidth load-balance is not working once LSPs are advertised in the ISIS or ISIS TE shortcuts is configured When there are different LSPs towards the same egress endpoint and they are up and advertised in ISIS or ISIS TE shortcuts is configured, the active route is expected to use the LSPs as ECMP nexthops in inet.0. If in addition, rsvp load-balance bandwidth is configured it would be expected that traffic is load balanced taking into a consideration the LSP's bandwidth. The later was not happening and the traffic was load balanced equally across all ECMP LSPs which shouldn't have been the case.