Alert Type

SRN - Software Release Notification
Low/NotificationSoftware Release Notification
Low/NotificationSoftware Release Notification

Product Affected

ACX, EX, MX, PTX, QFX, NFX, SRX, VRR, vMX, vSRX

Alert Description

Junos Software Service Release version 19.4R2-S5 is now available for download from the Junos software download site
Download Junos Software Service Release:
  1. Go to  Junos Platforms - Download Software page
  2. Input your product in the "Find a Product" search box
  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 as need and follow the prompts

Solution

Junos Software service Release version 19.4R2-S5 is now available.

19.4R2-S5 - List of Fixed issues

PR Number Synopsis Category: Covers Application classification workflows apart from custo
1563280 The AppID DB not erased after 'request system zeroize'
Product-Group=junos 		On all SRX platforms, the AppID DB not erased after 'request system zeroize'. It will not impact any traffic but customers might confuse due to this issue.
PR Number Synopsis Category: EX4400 platform
1573889 EX4400: Mgmt LEDs are not working as per expectations
Product-Group=junos 		Below is the status of management LED when speed is set to: 1. 10m - Activity LED is not blinking when ping/traffic is runnig (instead it is remaining steady GREEN) 2. 100m - Activity LED is blinking without any ping/traffic.
PR Number Synopsis Category: FreeBSD Kernel Infrastructure
1549754 While loading the kernel displays the following error message: GEOM: mmcsd0s.enh: corrupt or invalid GPT detected.
Product-Group=junos 		While loading the kernel, user sees the message "GEOM: mmcsd0s.enh: corrupt or invalid GPT detected." This message has no impact on functionality.
1551193 VM might crash if file is shared between host operating system and guest operating system using virtFS
Product-Group=junos 		On Virtual Machines (VM) based platforms running Junos images, file might not be shared between host operating system and guest operating system via Virtual Filesystem (virtFS). When this issue happens, device might be restarted.
1552952 The vme/me0 management interface cannot process any incoming packets.
Product-Group=junos 		On EX2300/EX2300-MP/EX3400 platforms, when me0 interface is deleted and vme interface is configured, the device cannot process any incoming packet on vme/me0 management interface.
1555748 Devices might get stuck in "OK" prompt while loading the image.
Product-Group=junos 		EX, MX, PTX & SRX series devices may stuck in the "OK" prompt while loading image for certain junos versions like 18.3R1, 21.1R1.
1563647 Memory corruption of any binary in /usr/bin/ or /usr/sbin/ may be triggered when a recovery snapshot is being copied to the OAM volume or system while it's in heavily stressed condition
Product-Group=junos 		Memory corruption of a binary from /usr/bin/ or /usr/sbin/ directory can occur if such binary is invoked when a recovery snapshot creation is in progress. The exact symptoms will be different depending on the exact binary and JUNOS version - some programs will show an error, and some programs will crash every time it is executed. Such memory corruption will be persistent until the affected Routing Engine is restarted. Please refer to TSB17954 [juniper.net] (https://kb.juniper.net/TSB17954 [juniper.net]) for further details. In addition to recovery snapshot, a device reboot could also be a possible trigger when the system is under heavier read operations across the mounted packages.
1572963 The upgrading might fail when upgrading from Junos with FreeBSD 6
Product-Group=junos 		On all platforms (For SRX, only SRX5k with RE-1800x4) while directly upgrading from Junos with FreeBSD 6 (e.g. 15.1X49 or before) to the affected releases, the system will check the USB connection. The upgrading will fail if there is no USB device detected during the upgrading process.
1602005 Upgrade might fail when upgrading from legacy release
Product-Group=junos 		On all platforms (For SRX, only SRX5k with RE-1800x4) while directly upgrading from Junos with FreeBSD 6 (e.g. 15.1X49 or before) to the affected releases, the system will check the USB connection. The upgrading will fail if there is no USB device detected during the upgrading process.
PR Number Synopsis Category: RPM and TWAMP
1541808 The rmopd process memory leak might be seen if the TWAMP client is configured.
Product-Group=junos 		If TWAMP (Two-Way Active Measurement Protocol) client is configured, memory leak in rmopd process may be observed after executing "request services rpm twamp start client" command.
PR Number Synopsis Category: Generic platform and infra issues for MS-MIC and MS-MPC(XLP)
1569894 The mspmand process might crash if the packet flow-control issue occurs on MS-MPC/MS-MIC.
Product-Group=junos 		In MX platforms with MS-MPC/MS-MIC scenario, the Packet Ordering Engine (POE) recovery operation will control the right packet descriptor of packet flow and detect jbuf (memory) leak. But, if some rare race conditions happen during this time, this kind of flow-control operation might cause the mspmand to crash. Then, MS-MPC/MS-MIC might restart.
1600619 The Multiservices card doesn't drop the TCP ACK packet received as a reply to the self-generated TCP keepalive
Product-Group=junos 		On MX with Multiservices card (MS-PIC/MS-MPC) installed, when the user's TCP session is passing the Multiservices card, TCP tickle functionality tries to extend TCP session after the inactivity-timeout expires by sending self-generated TCP keepalive packets to both parts of TCP connection and expecting the TCP ACK to be seen from both parts. While the expected behavior is to drop that TCP ACK packet on Multiservices card upon receiving, it sends to another part of TCP connection, this causes confusion and inability to extend TCP session, and then causes impact on long-lived TCP sessions with low volume of traffic.
 

19.4R2-S5 - List of Known issues

PR Number Synopsis Category: Firewall Filter
1471310 Firewall filter monitoring using SNMP might not provide accurate results
Product-Group=junos 		On all Junos except MX platforms, the firewall filter monitoring using SNMP OID 1.3.6.1.4.1.2636.3.5.2.1.6 might not provide the entire output of configured filters, when configured filters are using actions or matches that are not supported by the compiled filters. Below is the list of actions and matches that are not supported by the compiled filters: actions: "then policy map", "clear-policy-map", "then encapsulate/decapsulate" matches: "payload-protocol", "gre-key", "flex-offset range/prefix", "policy-map"
PR Number Synopsis Category: RPD route tables, resolver, routing instances, static routes
1525363 Traffic loss might occur during VRF route resolution over indirect next hop.
Product-Group=junos 		This applies to an L3VPN with the "chain-composite-nexthop" environment in which next-hops are indirect next-hops (such as labels). When committing a change in VRF configuration, the router may drop packets.
PR Number Synopsis Category: SW PRs for SCBE3 related kernel drivers
1564539 MX platforms with MX-SCBE3 may reboot continuously
Product-Group=junos 		A recent change in the kernel boot loader causes a system with MX-SCBE3 to experience the Routing Enginne's kernel memory corruption which causes the system to reboot continuously.
 

Modification History

First publication 2021-10-01