Alert Type
SRN - Software Release Notification
Risk
Risk Description
Low/Notification
Software Release Notification
Impact
Impact Description
Low/Notification
Software Release Notification
Product Affected
ACX MX NFX PTX QFX SRX vSRX
Alert Description
Junos Software Service Release version 19.4R3-S11 is now available for download from the Junos software download site
Download Junos Software Service Release:
Go to
Junos Platforms - Download Software page
Input your product in the "Find a Product" search box
From the Type/OS drop-down menu, select
Junos SR
From the Version drop-down menu, select your version
Click the Software tab
Select the Install Package as need and follow the prompts
Solution
Junos Software service Release version 19.4R3-S11 is now available.
19.4R3-S11 - List of Fixed issues
PR Number
Synopsis
Category: a20a40 specific issue
1698797
Fabric monitoring suspension and control link failure may cause HA cluster outage
Product-Group=junos
In HA cluster, a local node failure which causes control link to go down may not guarantee the other node to take over primary if the fabric link monitoring suspension was triggered earlier before (e.g. - caused by a minor hardware failure), as the fabric link down event would be ignored when the other node was in RG0 ineligible state. This is a corner case to https://www.juniper.net/documentation/us/en/software/junos/chassis-cluster-security-devices/topics/topic-map/security-chassis-cluster-failover-parameters.html#id-understanding-chassis-cluster-control-link-heartbeats-failure-and-recovery__d27575e82. And PR1698797 fixed this defect.
PR Number
Synopsis
Category: BBE dynamic profile related issues
1537512
Version-alias is missed for subscribers configured with dynamic profiles after ISSU
Product-Group=junos
On all MX platforms, after performing an "in-service software upgrade" (ISSU), some of the configured subscriber profiles may go missing.
PR Number
Synopsis
Category: Border Gateway Protocol
1635390
BGP routes might be left stale on the router
Product-Group=junos
On all Junos and Junos Evolved platforms, if the BGP peer goes down, and the very last route in the list is marked as a high priority, BGP might assume no more routes to delete, causing routes to be stale.
PR Number
Synopsis
Category: Express PFE L2 fwding Features
1627566
QFX10002-60C platform might not respond back to ICMP packets received with TTL or hop limit value of 1
Product-Group=junos
On QFX10002-60C platform when ICMPv4 (Internet Control Message Protocol) packet with TTL (Time To Live) value of 1 or ICMPv6 packet with hop limit value of 1 is received at the IRB (Integrated Routing and Bridging) interface, it might not respond back with the corresponding ICMP error codes [TTL expired or hop limit exceeded] to the source device.
1693424
Traffic loss is observed when the ECMP path is IRB over AE (IPv4->MPLS)
Product-Group=junos
On QFX10002 platforms, when the ECMP (Equal-cost multi-path) path is IRB (Integrated routing and bridging) over AE (Aggregated Ethernet) {IPv4->MPLS (Multiprotocol Label Switching)} results in packets getting discarded for which traffic loss is observed.
PR Number
Synopsis
Category: ISIS routing protocol
1515967
rpd memory leak if more than one ip-reach tlv is originated for same prefix.
Product-Group=junos
RPD memory leak and eventually coredump if ISIS receives more than one ip-reach tlv is originated for same prefix.
PR Number
Synopsis
Category: jl2tpd daemon
1667950
VMcore or RE crash might be triggered due to the memory corruption when the FPC is restarted for LNS subscribers
Product-Group=junos
On all MX platforms, when Flexible PIC Concentrators (FPCs) restart for L2TP network server (LNS) subscribers stacked over aggregated service interface (asi) and LNS subscribers belong to more than one routing instance causes the VMcore or Routing Engine (RE) crash and brings down all the traffic.
PR Number
Synopsis
Category: Multiprotocol Label Switching
1697982
[MX]L2VPN ping is failing when UHP rsvp LSP is used
Product-Group=junos
MPLS L2VPN ping is getting failed when MX is egress. In egress, RE verifies whether received label is VC label or not. For most of the platforms, tunnel label will be removed in PFE before punting the echo request packet to RE. But in this platform, tunnel label is not removed hence RE verifies this tunnel label and it is returning no-mapping.
1701800
Memory leak issue in TED
Product-Group=junos
On all Junos and Junos Evolved platforms, a memory leak is observed in TED (Traffic Engineering Database) when the inet tables is not cleaned up after routing instance deactivation.
PR Number
Synopsis
Category: Kernel MPLS / Tag / P2MP Infrastructure
1681892
The RE crashes when MPLS next-hop is created and deleted frequently
Product-Group=junos
On all Junos platforms, when the system is up for a very long time, tag stats counters increase and cross the 32-bit capacity when MPLS next-hop is created/deleted frequently, resulting in RE (routing engine) crash.
PR Number
Synopsis
Category: OSPF routing protocol
1700966
OSPF stuck in InitStrictBFD state for the neighbor which doesn't send LLS header
Product-Group=junos
When Strict BFD (Bidirectional Forwarding Detection) for OSPF (Open Shortest Path First) configured on all Junos OS and Junos OS Evolved platforms, and one or more OSPF neighbors don't support Link-Local Signaling ("LLS", RFC5613), the adjacency with these neighbor(s) might stuck in InitStrictBFD state upon adjacency initialization. Neighbor doesn't support LLS, hence it doesn't attach the LLS header, which is a pre-requisite for Strict BFD.
PR Number
Synopsis
Category: QFX L2 PFE
1629680
Traffic might get dropped when "family ethernet-switching" is configured on the interface in Q-in-Q scenario
Product-Group=junos
In Q-in-Q scenario, traffic starts getting dropped when "family ethernet-switching" is added to ingress interface, which is already configured with "encapsulation extended-vlan-bridge". This is due to incorrect port setting in hardware.
PR Number
Synopsis
Category: Cover Logical System Infrastrcuture Development
1694449
The process srxpfd/ flowd will crash on SRX devices
Product-Group=junos
On all SRX platforms (except branch SRX series) configured with chassis cluster redundancy group, when numerous logical interfaces or IFLs (> 1K) are deleted and traffic is running for those IFLs, or if the RG failover then the process srxpfed/ flowd will crash.
PR Number
Synopsis
Category: SRX branch platforms
1658276
The reth member interface does not come up due to speed mismatch after RG0 failover
Product-Group=junos
On SRX series platform with chassis cluster enabled, the reth (Redundant Ethernet) interface might not come up due to speed mismatch when the reth interface speed is changed after RG0 (redundancy group) failover.
19.4R3-S11 - List of Known issues
PR Number
Synopsis
Category: Anything related to Multicast
1461339
Mcast traffic drops is observed with the following error message: brcm_rt_ip_mc_ipmc_install.
Product-Group=junos
Following two Failure messages seen brcm_rt_ip_mc_ipmc_install:2455 Failed (Invalid parameter:-4) This message is due to IPMC Group being used is not created, when RE tried to add this check indicates there is a parameter mis-match. brcm_rt_ip_mc_ipmc_install:2455 Failed (Internal error:-1) This message is due to Failure to read IPMC Table or any memory/register
Resolved In:
PR Number
Synopsis
Category: Border Gateway Protocol
1601163
Some routes might get incorrectly programmed in the forwarding table in the kernel with next-hop installed as dead
Product-Group=junos
On all platforms with high-scaled routes scenario, after Flexible PIC Concentrator (FPC) restart some routes might get incorrectly programmed in the forwarding table in the kernel with next-hop installed as "dead". This would lead to traffic impact. This is a timing issue.
Resolved In:
evo:20.4R3-EVO evo:21.1R3-EVO evo:21.2R2-EVO evo:21.3R1-EVO evo:21.4R1-EVO junos:19.3R3-S4 junos:19.4R3-S6 junos:20.1R3-S2 junos:20.2R3-S1-J5 junos:20.2R3-S2-J1 junos:20.2R3-S2-J14 junos:20.2R3-S3 junos:20.3X75-D32 junos:20.3X75-D40 junos:20.4R3 junos:21.1R3 junos:21.2R2 junos:21.3R1 junos:21.4R1
PR Number
Synopsis
Category: QFX52xx platforms Interface running EVO
1545455
The chip on FPC line card might crash when the system reboots.
Product-Group=junos
On the FPCs with Broadcom chip, if the jinsightD (health-mon) is not disabled ("set system processes health-mon disable"), the FPC might crash during the system booting. Traffic loss is seen during the FPC crash and restart.
Resolved In:
evo:20.1R3-EVO evo:20.2R3-EVO evo:20.3R2-EVO junos:18.3R3-S4 junos:18.4R2-S9 junos:19.1R3-S4 junos:19.2R3-S2 junos:19.3R3-S2 junos:19.4R3 junos:20.1R2 junos:20.1R3 junos:20.2R2 junos:20.2R3 junos:20.3R1-S1 junos:20.3R2 junos:20.3X75-D10 junos:20.4R1 junos:21.1R1
PR Number
Synopsis
Category: Firewall Filter
1571399
Packet loss might be observed when sample based action is used in firewall filter
Product-Group=junos
On MX Series routers or the EX9200 line of switches, if sample-based action is used in a firewall filter for an interface, such as syslog, log, port-mirror or JFlow, traffic loss might be observed if the sampled packets rate exceeds default DDoS sample bandwidth.
Resolved In:
junos:18.2X75-D61 junos:20.2R3-S2 junos:20.3R3 junos:20.3X75-D30 junos:20.4R3 junos:21.1R2 junos:21.2R1 junos:21.3R1
PR Number
Synopsis
Category: Express PFE L2 fwding Features
1654215
The ARP might not resolve with the native-vlan configuration
Product-Group=junos
On all QFX10002-36Q/QFX10002-72Q/QFX10008/QFX10016 platforms, when Service Provider(SP) style is configured with IRB and native-vlan leads to ARP failure.
Resolved In:
junos:20.2R3-S6 junos:20.4R3-S4 junos:21.2R3-S2 junos:21.3R3-S1 junos:21.4R3 junos:22.1R2 junos:22.2R1 junos:22.2R2 junos:22.3R1
PR Number
Synopsis
Category: Express ASIC platform
1683562
On PTX5000 platforms when a command is issued to power off an FPC, it gets stuck in the 'Announce Offline' state
Product-Group=junos
When an FPC (Flexible PIC Concentrator) on PTX5000 platforms is shut down by issuing a request command (request chassis offline slot ) or by FPC power off configuration (set chassis fpc x power off), it gets stuck in the 'Announce Offline' state since the associated timer (fru_graceful_offline_timer) doesn't increment and expire as it is supposed to.
Resolved In:
junos:19.2R3-S5-J2 junos:20.4R3-S2-J17 junos:20.4R3-S6 junos:21.4R3-S2 junos:22.3R2 junos:22.4R1 junos:22.4R2 junos:23.1R1
PR Number
Synopsis
Category: Adresses ALG issues found in JSF
1604123
Junos OS: MX Series and SRX Series: The flowd daemon will crash if the SIP ALG is enabled and specific SIP messages are processed (CVE-2022-22175)
Product-Group=junos
An Improper Locking vulnerability in the SIP ALG of Juniper Networks Junos OS on MX Series and SRX Series allows an unauthenticated networked attacker to cause a flowprocessing daemon (flowd) crash and thereby a Denial of Service (DoS). Continued receipt of these specific packets will cause a sustained Denial of Service condition. Refer to https://kb.juniper.net/
JSA11281
[juniper.net]
for more information.
Resolved In:
junos:20.4R3-S1 junos:21.1R2-S2 junos:21.1R3 junos:21.2R1-S2 junos:21.2R2 junos:21.2R3 junos:21.3R1-S1 junos:21.3R2 junos:21.4R1 junos:22.1R1
PR Number
Synopsis
Category: Platform infra to support jvision
1615045
Export memory and temperature metrics for all existing components when it subscribes to telemetry sensor
Product-Group=junos
On all Junos platforms, the device may export memory, allocated power and temperature metrics for all existing components no matter if those leafs are supported on the components, such as exporting memory utilization for a PIC component or a transceiver, which could consume more resources on both the device and collector.
Resolved In:
junos:19.4R3-S8 junos:20.3R3-S2 junos:20.4R3-S3 junos:21.2R3 junos:21.3R2 junos:21.4R1 junos:22.1R1
PR Number
Synopsis
Category: Label Distribution Protocol
1550158
NSR may get in out of sync status due to race condition
Product-Group=junos
LDP add duplicate registertion and infra does not like it. This happen during the race condition between rpd and kernel to detect the unreplicate NSR config with error condition.
Resolved In:
evo:20.4R1-EVO evo:21.1R1-EVO junos:20.4R1 junos:20.4R2 junos:21.1R1
PR Number
Synopsis
Category: Multiprotocol Label Switching
1694648
The rpd crash will be observed during the MPLS label block allocation
Product-Group=junos
On all Junos and Junos Evolved platforms in the Multiprotocol Label Switching (MPLS) scenario, the rpd crash will happen in rare conditions during MPLS label block allocation.
Resolved In:
evo:20.4R3-S6-EVO evo:21.2R3-S4-EVO evo:22.1R3-S1-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.3R3-EVO evo:22.4R2-EVO evo:23.1R1-EVO junos:20.2R3-S7 junos:20.4R3-S6 junos:21.1R3-S5 junos:21.2R3-S4 junos:21.4R3-S3 junos:22.2R3 junos:22.3R2 junos:22.3R3 junos:22.4R2 junos:23.1R1
PR Number
Synopsis
Category: Neo Interface
1576370
MIC specific alarms might not be cleared after MIC reboot
Product-Group=junos
An alarm raised due to a transient HW problem with MIC does not get cleared automatically after MIC restart.
Resolved In:
evo:21.2R3-EVO evo:21.3R2-EVO evo:21.4R1-EVO junos:19.4R3-S5 junos:21.2R3 junos:21.3R2 junos:21.4R1
PR Number
Synopsis
Category: Microkernel for neo mpc
1670137
Multibit ECC error causes the whole MX platform chassis to go down
Product-Group=junos
Faulty FPC (Flexible PIC Concentrator) on the MX platform chassis exhibiting multibit ECC (Error Checking and Correction) error (L2 cache error) will trigger this issue. The whole chassis goes down until the faulty FPC is removed from the chassis.
Resolved In:
junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:22.4R2
PR Number
Synopsis
Category: Odin Timing software
1632761
ACX710 running G.8275.2 stuck at PTP Acquiring state if the connection is through some timing unaware nodes
Product-Group=junos
On the ACX710 platform, in Precision Time Protocol (PTP) with G.8275.2 profile scenario where topology has some intermediate non-PTP aware nodes, the clock might be stuck in ACQUIRING state.
Resolved In:
junos:21.2R2-S1 junos:21.2R3 junos:21.3R2 junos:21.4R2 junos:22.1R1
PR Number
Synopsis
Category: Category for tracking Olympus-MX issues
1671649
Traffic loss seen due to SPC3's packets getting stuck
Product-Group=junos
On Junos MX960, MX480 platforms, Flowd restart or PIC offline/online( Physical Interface Cards) causes SPC3's sending of packets to get stuck.
Resolved In:
evo:22.1R3-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R1-EVO evo:23.1R1-EVO junos:20.4R3-S5 junos:21.1R3-S4 junos:21.2R3-S3 junos:21.3R3-S3 junos:21.4R3-S1 junos:22.1R2-S1 junos:22.1R3 junos:22.2R1-S2 junos:22.2R2 junos:22.2R3 junos:22.3R1-S1 junos:22.3R2 junos:22.4R1 junos:23.1R1
PR Number
Synopsis
Category: Express Chip L3 software
1660606
MVPN traffic is getting dropped on PTX/QFX series platforms
Product-Group=junos
On all Junos PTX and QFX10k series platforms, MVPN (Multicast Virtual Private Network) traffic is getting dropped with a discarded error. This is because, the way LSI (Label Switched Interface) interface data is carried from ASIC (Application-Specific Integrated Circuit) to PFE (Packet Forwarding Engine) is changed, causing MVPN to break.
Resolved In:
junos:19.3R3-S7 junos:19.4R3-S9 junos:20.3X75-D35 junos:20.3X75-D41 junos:20.3X75-D42 junos:20.3X75-D43 junos:20.4R3-S4 junos:21.1R3-S3 junos:21.2R3-S1 junos:21.2R3-S2 junos:21.3R3 junos:21.4R3 junos:22.1R2 junos:22.2R1 junos:22.2R2 junos:22.3R1
PR Number
Synopsis
Category: vMX Data Plane Issues
1669261
vMX crashes due to MBUF leaks
Product-Group=junos
vMX platforms (MX150) will crash as a result of the MBUF (Memory Buffer) leak.
Resolved In:
junos:20.4R3-S5 junos:21.4R3 junos:22.1R3 junos:22.3R1 junos:23.1R1
PR Number
Synopsis
Category: uboot & loader for DCG TOR and CB
1536799
Software recovery or installation using the Bootable USB Flash Drive option might fail
Product-Group=junosvae
Using "Bootable USB Flash Drive" to recover/install software may fail on the platforms with releases starting from 19.2, after power cycle (off/on).
Resolved In:
junos:19.3R3-S2 junos:19.4R2-S3 junos:19.4R3 junos:20.1R2 junos:20.2R2 junos:20.2R3 junos:20.3R1 junos:20.3R2 junos:20.3X75-D10 junos:20.4R1
PR Number
Synopsis
Category: DDos Support on MX
1549656
The kernel might crash if GRES is performed on either new iteration or after swapping the Routing Engine and restoring the HA configuration
Product-Group=junos
On dual Routing Engine platforms with only two slots, the kernel crash may be seen on the backup Routing Engine after performing multiple GRES.
Resolved In:
junos:19.3R3-S2 junos:20.1R3 junos:20.2R3 junos:20.3R3 junos:20.3X75-D10 junos:20.3X75-D20 junos:20.4R2 junos:21.1R1 junos:21.2R1
PR Number
Synopsis
Category: UI Infrastructure - mgd, DAX API, DDL/ODL
1572768
MX10k8: Smaller config db size when compared to other platforms (MX10003 MX960)
Product-Group=junos
Smaller config db size is given when a tvp image is installed on boxes which can handle higher config db size. This is because the box becomes pvi-model platform as a result gets low size
Resolved In:
evo:20.4R1-S1-EVO evo:20.4R2-EVO evo:20.4X50-EVO junos:20.2R3-S3 junos:20.3R3-S1 junos:20.4R2 junos:20.4R3 junos:21.1R1-S1 junos:21.1R2 junos:21.2R1
PR Number
Synopsis
Category: PTX/QFX100002/8/16 Fabric software
1615942
90% traffic got dropped when the number of Switch Interface Board (SIB) plane is reduced from 4 to 3 on PTX10008 and PTX10016
Product-Group=junosvae
On PTX10008 and PTX10016 routers, when the number of Switch Interface Board (SIB) planes is reduced from 4 to 3, traffic might drop by 90%.
Resolved In:
junos:19.3R3-S7 junos:19.4R3-S8 junos:20.3X75-D32 junos:20.3X75-D40 junos:21.2R2 junos:21.2R2-S1 junos:21.2R3 junos:21.3R2 junos:21.4R1 junos:22.1R1
PR Number
Synopsis
Category: MX10K linecard
1688651
JUNOS_REG:MX10008:Carrier transition count is more than expected at DUT(mx10008) after flapping the interface at peer non-DUT end.
Product-Group=junos
When laser off and on happens on the remote end, within an interval of less than 500 ms, the local interface undergoes additional flap, before the link comes up. There is no impact of the additional flap, as the link does come up eventually.
Resolved In:
PR Number
Synopsis
Category: Unified Services Framework
1465888
"TALUS(number) PCIe(number) DMA RX interrupt received. Queue stuck status 0xeeeeee0" are spurious messages which are triggered in system logs due to queue-back pressure or FPGA drops.
Product-Group=junos
"TALUS(number) PCIe(number) DMA RX interrupt received. Queue stuck status 0xeeeeee0" are spurious messages which are triggered in system logs due to queue-back pressure or FPGA drops.
Resolved In:
Modification History
First publication 2023-01-04
19.4R3-S11: Software Release Notification for JUNOS Software