Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

19.4R1-S3: Software Release Notification for JUNOS Software Version 19.4R1-S3

0

0

Article ID: TSB17877 TECHNICAL_BULLETINS Last Updated: 12 Oct 2020Version: 1.0
Alert Type:
SRN - Software Release Notification
Product Affected:
ACX, EX, MX, PTX, QFX, NFX, SRX, VRR, vMX, vSRX
Alert Description:
Junos Software Service Release version 19.4R1-S3 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.4R1-S3 is now available.

19.4R1-S3 - List of Fixed issues
PR Number Synopsis Category: EX driver issues
1515689 The IP communication between directly connected interfaces on EX4600 would fail
Product-Group=junosvae
The IP communication between directly connected interfaces on EX4600 TVP platforms would fail. This issue only might occur in this special scenario and it might have traffic/service impact.
PR Number Synopsis Category: Junos Fusion Infrastructure
1454335 The SDPD generates core files at vfpc_all_eports_deletion_complete vfpc_dampen_fpc_timer_expiry.
Product-Group=junos
SDPD core found @ vfpc_all_eports_deletion_complete vfpc_dampen_fpc_timer_expiry on following triggers 1) Delete and add same SD device with some attribute change in single commit 2) Interchange slot id between two SD devices in single commit
PR Number Synopsis Category: Border Gateway Protocol
1482209 The BGP multipathed traffic might not fully load-balance for a while after adding a new path for load sharing.
Product-Group=junos
On all Junos platforms with the BGP-ECMP (Equal Cost Multi-Path) scenario, if adding a new path for load sharing, the traffic might not fully load-balanced for a while. The worst-case scenario is much traffic moving to the new path and lead to a link oversubscription.
PR Number Synopsis Category: Device Configuration Daemon
1476199 Failure to configure proactive ARP detection
Product-Group=junos
When trying to configure proactive ARP detection configuration under interface, the configuration may fail to commit.
PR Number Synopsis Category: ChassisD changes specific for DNX series.
1456593 The ACX5448-D and ACX5448-M devices does not display airflow information and temperature sensors as expected.
Product-Group=junos
Airflow information does not display as front to back(AFO) or back to front (AFI) under show chassis environment pem command.
PR Number Synopsis Category: Layer 3 forwarding, both v4+v6
1519372 The IPv6 neighbor state change causes Local Outlif to leak by two values, which leads to the following error: DNX_NH::dnx_nh_tag_ipv4_hw_install.
Product-Group=junos
On ACX5448/ACX5448-D, PFE memory exhaustion is reported due to continuous IPv6 neighbor flaps.
PR Number Synopsis Category: DNX platform MPLS FRR features
1482529 On the ACX5448 routers, the following logs are reported: dnx_nh_mpls_tunnel_install.
Product-Group=junos
On ACX5448, ACX5448-D,ACX5448-M routers acting as LSR(label switching router), forwarding may get impacted due to PFE resource exhaustion caused by network churn.
PR Number Synopsis Category: EVPN Layer-2 Forwarding
1498534 Packets may not be sent out of IRB interface if there is no L2 interface in the associated bridge-domains
Product-Group=junos
In the EVPN (Ethernet VPN) MPLS scenario, if there is no L2 interface in the associated bridge-domains, the packets might not be sent out of the IRB (Integrated Routing and Bridging) interface.
PR Number Synopsis Category: Flow-tap software
1472109 The flow-tap add function may not work as expected on MX platforms
Product-Group=junos
On MX platforms with FlowTapLite configured, if the dynamic flow capture(dfcd) process restarts or if services flow-tap configuration is deactivated and then activated, a request by the mediation device to add an additional flow filter will not take effect. This causes incomplete flow information being sent to the content destination.
PR Number Synopsis Category: Aggregated Sonet Interfaces
1472439 The 'sonet-options' configuration stanza is disabled for xe interface working in wan-phy mode
Product-Group=junos
On all MX platforms, the 'sonet-options' stanza cannot be configured on xe interface working in wan-phy mode after Junos 19.4R1. This issue may cause software upgrade failure to 19.4R1 or onwards due to configuration validation fails.
PR Number Synopsis Category: ISSU related issues for MMx
1476505 Dark window size is more than expected. 31.0872721524375 seconds of traffic lost is observed.
Product-Group=junos
On MX2020/MX2010/MX960 platforms, a traffic loss during the ISSU procedure might be observed, and the duration of traffic loss can be 30 seconds or more, it depends upon the number of FPCs in chassis.
PR Number Synopsis Category: jdhcpd daemon
1525052 The memory leak in jdhcpd might be seen if access-profile is configured under "dhcp-relay" or "dhcp-local-server" stanza
Product-Group=junos
With access-profile being configured under "forwarding-options dhcp-relay" or "system services dhcp-local-server" stanza, there might be memory leak in jdhcpd when DHCP request is processed. The leaked memory size for each processing will be the number of bytes equal to the length of the access profile.
PR Number Synopsis Category: Adresses ALG issues found in JSF
1510678 The srxpfe/mspmand process may crash if FTPS is enabled in a specific scenario
Product-Group=junos
If FTPS service is enabled on an SRX/MX device where both source NAT and "ssl-proxy" are not configured, then the device may crash upon receiving FTPS traffic.
PR Number Synopsis Category: Layer 2 VPN related issues
1503282 MPLS label manager could allow configuration of a duplicated VPLS static label
Product-Group=junos
On all JUNOS and all Junos EVO platforms, when configuring wrong static label-range or duplicated static labels for l2circuit or LDP-based VPLS, the instance will not be up.
PR Number Synopsis Category: Layer 2 Circuit issues
1512834 The rpd might crash when deleting l2circuit configuration in a specific sequence
Product-Group=junos
If l2circuit local-switching is enabled with connection-protection, the rpd could crash in the following configuration change sequence. 1. First, delete the logical interface (IFL) used by a l2circuit and commit the change. 2. Then, delete the corresponding l2circuit configuration. The rpd could crash after committing the change.
PR Number Synopsis Category: Multiprotocol Label Switching
1517018 The rpd might crash after upgrading Junos software release from pre 18.1 to 18.1 onwards
Product-Group=junos
The rpd might continuously crash after upgrading pre Junos OS Release 18.1 to Junos OS Release 18.1 and later while graceful-restart and RSVP/static LSP are configured. This is because there is a change in the data structure written to the restart database file from Junos OS Release 18.1 and later. So, when rpd comes up and tries to read the restart database file written by pre Junos OS Release 18.1 image, the rpd might crash.
PR Number Synopsis Category: DNS filtering on MX.
1474056 Junos OS: MX Series: Services card might restart when DNS filtering is enabled (CVE-2020-1645)
Product-Group=junos
When DNS filtering is enabled on Juniper Networks Junos MX Series with one of the following cards MS-PIC, MS-MIC or MS-MPC, an incoming stream of packets processed by the Multiservices PIC Management Daemon (mspmand) process, responsible for managing "URL Filtering service", may crash, causing the Services PIC to restart. Refer to https://kb.juniper.net/JSA11028 for more information.
PR Number Synopsis Category: Neo Interface
1453433 Interfaces shutdown by 'disable-pfe' action might not be up using MIC offline/online command
Product-Group=junos
On MX Series devices, MPC wedge might cause disable-pfe action. The disable-pfe action shuts down interfaces to avoid traffic being silently dropped. MIC bouncing (offline/online) operation brings WAN interfaces up, causing traffic to be dropped or silently discarded. Restoring the Packet Forwarding Engine entity upon disable-pfe action needs MPC restart.
PR Number Synopsis Category: vMX Platform Infrastructure related issue tracking
1493805 Viewing a large file from vFPC console may hog the console.
Product-Group=junos
Viewing a large file from vFPC console using "cat" application may hog the console.
PR Number Synopsis Category: PTX10K Routing Engine
1503169 On the PTX10008 and PTX10016 routers, a few TCP-based application sessions might flap upon Routing Engine switchover or application sessions bouncing in the backup Routing Engine.
Product-Group=junosvae
In a rare case on a PTX10008/PTX10016 router with dual Routing Engines (RE) and GRES/NSR enabled, a few TCP-based application sessions like BGP/LDP might flap upon RE switchover or application (protocol) sessions bouncing at the backup RE. Once those sessions flap, they will be re-established automatically. The TCP sessions re-connection will impact the respective routing protocol sessions and therefore could impact the traffic. This is a timing issue; the more TCP-based application sessions the router has established prior the switchover, the higher chances to hit the issue. Usually when the issue happens, only a few TCP sessions are getting affected and not all of them.
PR Number Synopsis Category: Trio pfe l3 forwarding issues
1461593 \More number of output packets are seen than expected when the ping function is performed.
Product-Group=junos
During host ping with gr- tunnel endpoint lt- interface termination, gr- interface input and lt- interface output counters come as (host path + transit counter).
1478279 FPC memory leak might occur after executing the show pfe route command
Product-Group=junos
On all Junos OS platforms, if the command "show pfe route " is executed to dump the Packet Forwarding Engine (PFE) routes, and then the routes get deleted by some events (for example, Virtual Routing and Forwarding (VRF) configuration removal or Border Gateway Protocol (BGP) flap), the FPC memory leak might happen due to this issue. In large scaled scenario, the memory leak will increase by a large amount, which might be easier to cause FPC crash.
PR Number Synopsis Category: Configuration mgmt, ffp, load-action, commit processing
1468119 On Junos OS Release from 16.2R1 onwards, if commit is executed after commit check, the daemon (for example, dhcpd and sampled) might not get started even after the related configuration is successfully committed
Product-Group=junos
On Junos OS Release from 16.2R1 onwards, if commit is executed after commit check, the daemon (for example, dhcpd and sampled) might not get started even after the related configuration is successfully committed.
PR Number Synopsis Category: usf nat related issues
1491036 When NAT/SFW rule configured with application-set with multiple applications having different TCP inactivity-timeout, Sessions are not getting TCP inactivity-timeout as per the configured application order.
Product-Group=junos
When NAT/SFW rule configured with application-set with multiple applications having different TCP inactivity-timeout, Sessions are not getting TCP inactivity-timeout as per the configured application order.
PR Number Synopsis Category: usf service set related issues
1482968 Fragmentation limit and reassembly time-out configuration under services option is missing for SPC3
Product-Group=junos
New CLI's are added to set "fragment-limit" and fragment "reassembly-timeout" values. The default values in the Unified Services Framework (USF) is the same as MX's default values (the default value for the fragment-limit is 250, the reassembly-timeout default value is 4 seconds)
PR Number Synopsis Category: Unified Services Framework
1475220 Stateful firewall rule configuration deletion might lead to memory leak.
Product-Group=junos
On MX240/MX480/MX960 and SRX platforms, when the SFW rule (Stateful Firewall Rules) configuration deletion occurs, user heap memory increases and memory leak might take place.
 

19.4R1-S3 - List of Known issues
PR Number Synopsis Category: NFX Layer 2 Features Software
1514244 Vlan doesn't take affect on Flowd Interfaces.
Product-Group=junos
The Vlans configured on Flowd interfaces doesn't take affect on OVS. It can be seen via CLI "show vmhost network nfv-backplane".
PR Number Synopsis Category: Argus Platform issues
1480217 On the ACX6360 router, the disk usage might keep increasing.
Product-Group=junos
On PTX1000/ACX6360 Series platforms, the vmhost disk usage might keep increasing due to an incorrect sensor path.
PR Number Synopsis Category: Border Gateway Protocol
1456260 Packet drop and CPU spike on Routing Engine might be seen in certain conditions if labeled-unicast protection is enabled for a CsC-VRF peer.
Product-Group=junos
On all Junos OS platforms under carrier supporting carrier (CsC) scenario, when PE link protection (labeled-unicast protection) is enabled, after one of the redundant links between CsC-CE flap or RSVP-TE LSP re-route from the primary path happens, it might result in slow convergence issue. Packets drop and CPU spike on the Routing Engine might be seen during this period.
PR Number Synopsis Category: build and packaging related PRs and features using WRL Yocto
1470217 The router might become nonresponsive and bring the traffic down when the disk space becomes full.
Product-Group=junos
On the PTX10001/ACX6360 platforms, the unionfs filesystem may get full on vmhost, this bacause there is a mail package in the WRlinux 8 continue to fill the mail logs into the unionfs filesystem. This issue will cause the router to hand and bring traffic down.
PR Number Synopsis Category: Device Configuration Daemon
1539719 Syslog "should have at least one member link on a different fpc" might occurs after commit for configuration under interface hierarchy
Product-Group=junos
This log could occur after commit for configuration under interface hierarchy f we have AE configuration with logical-interface-fpc-redundancy config, even if the AE interface have multiple legs on different FPCs. Sep 11 15:57:22.395 2020 lab-router-mx dcd[41283]: %DAEMON-4: Interface: ae5, should have at least one member link on a different fpc Trigger: 1- AE interfaces with logical-interface-fpc-redundancy are configured 2- Config change under interface hierarchy 3- Commit config
PR Number Synopsis Category: DNX L2 related features
1517074 The l2ald process crashes during stability test with traffic on a scaled setup.
Product-Group=junos
The L2ALD process on an ACX platform may restart unexpectedly during interface flaps.
PR Number Synopsis Category: Sflow on qfx10k/ptx series PRs for defect & enhancement req
1521732 Output interface Index in SFLOW packet will be zero when receiving transit traffic on IRB interface which VRRP enabled
Product-Group=junos
When VRRP is enabled on IRB interface and SFLOW is enabled, output interface Index in SFLOW packet will be zero for the traffic destined to VRRP MAC address
PR Number Synopsis Category: IPSEC/IKE VPN
1517262 The flowd might crash in IPsec VPN scenario
Product-Group=junos
On SRX platforms with IPsec VPN configured, the flowd might crash during the IPsec VPN rekey window. The traffic/service might be impacted if hitting this issue.
PR Number Synopsis Category: Jflow and sflow on MX
1487876 Incorrect 'frame length' of 132 bytes might be captured in packet header
Product-Group=junos
On all MX/PTX5k/EX platforms with Trio based line cards, if a packet is send with more than 128 bytes it will always show incorrect "Frame length" of 132 bytes in raw packet header of sflow collector captured data.
PR Number Synopsis Category: Generic platform and infra issues for MS-MIC and MS-MPC(XLP)
1489942 Prolonged flow-control might happen on MX platforms with MS-MPC/MS-MIC
Product-Group=junos
On MX platforms with MS-MPC/MS-MIC, if there are lots of self-generated packets like TCP-tickle and UDP-logging, there might be data congestion on the data path due to no throttling functionality for such types of packets. When the data path is blocked, prolonged flow-control might happen with the service interfaces being brought down and the PIC reboot. At the same time, the mspmand core file will be generated if dump-on-flow-control is enabled.
PR Number Synopsis Category: platform related PRs on SRX branch platforms
1474985 request system [halt | power-off] reboots the system instead of halting the system.
Product-Group=junos
The command "request system power-off" and "request system halt" might not work, it may cause a reboot instead of halting it.
PR Number Synopsis Category: UI Misc
1457602 The version information under the configuration changes from Junos OS release 19.1.
Product-Group=junos
Under configuration on 19.x, version info is different from prior 18.x release.
PR Number Synopsis Category: Web-Management UI
1513612 Installing J-Web application package may fail on the EX2300/EX3400 platforms
Product-Group=junos
On the EX2300/EX3400 platforms, J-Web application package may fail to be installed with the affected releases.
Modification History:
First publication 2020-10-09
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search