Alert Type
PSN - Product Support Notification
Risk
Risk Description
Low/Notification
Software Release Notification
Impact
Impact Description
Low/Notification
Software Release Notification
Alert Description
Junos Software Service Release version 20.4R3-S6-EVO 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 20.4R3-S6-EVO is now available.
20.4R3-S6-EVO - List of Fixed issues
PR Number
Synopsis
Category: Configd, ffp issues
1698347
The BFD fails to come up when RE filter is configured with apply-path
Product-Group=evo
On Junos OS Evolved platforms, the Bidirectional Forwarding Detection (BFD) protocol will fail to come up. This happens when the Routing Engine (RE) filter is applied with the filter term having source-prefix-list derived from apply-path configured with - "interfaces <*> aggregated-ether-options bfd-liveness-detection neighbor". The issue occured in the commit handling after correcting the apply-path string.
PR Number
Synopsis
Category: Control plane EVPN multicast
1670435
EVPN multicast traffic may get impacted because of routes getting stuck in the kernel routing table (krt) queue
Product-Group=evo
On all Junos and Junos Evolved platforms with Ethernet Virtual Private Network(EVPN) enabled, in the presence of certain triggers like rpd restart, rollback of configuration etc., EVPN multicast routes might get stuck in the kernel routing table (krt) queue due to which the corresponding routes in the forwarding table may point to 'fictitious' next hops, resulting in traffic disruption.
PR Number
Synopsis
Category: Issues related to Junos licensing infrastructure
1568788
Warning "Ignoring the key for unknown feature id: XXX" is generated when a valid license is installed into a device
Product-Group=evo
The license file may include features that can be used without the license and you may see the following warning messages when you install a license. We have changed the "warning" with "information" as follows. "information: 31f85f9c-49c7-4e58-a8d1-80bb57ee4369: Ignoring the key for feature id: 164. This feature is not used by your product."
PR Number
Synopsis
Category: MPC11 ULC interface software related issues.
1698135
XQSS_CMERROR_DSTAT_INT_REG_DROP0_QDEPTH_UNDRN alarm is seen on MX2K platforms with MPC11E line cards upon aggregate interface down/flap event
Product-Group=evo
On MX2010 or MX2020 platforms with MPC11E line cards, if a member link of an aggregate interface goes down or flaps, it might trigger "XQSS_CMERROR_DSTAT_INT_REG_DROP0_QDEPTH_UNDRN" alarm and disable-pfe action is executed. The affected PFE (Packet Forwarding Engine) will be disabled and no traffic will pass through it.
PR Number
Synopsis
Category: Multiprotocol Label Switching
1690458
On a controller based MPLS setup with container LSPs, rpd daemon crashes after LSP deletion occurs
Product-Group=evo
On all Junos-based platforms, in a scenario where an external controller is provisioned, rpd crashes when an externally controlled container LSP (Label Switched Path) is deleted and the software tries to update its status.
1694648
The rpd crash will be observed during the MPLS label block allocation
Product-Group=evo
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.
1697982
[MX]L2VPN ping is failing when UHP rsvp LSP is used
Product-Group=evo
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.
PR Number
Synopsis
Category: OSPF routing protocol
1700966
OSPF stuck in InitStrictBFD state for the neighbor which doesn't send LLS header
Product-Group=evo
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: QFX5100 Interface related issues
1688023
The LLDP output packets are not transmitting on the em0 interface of Junos and Junos OS Evolved platforms
Product-Group=evo
On Junos and Junos OS Evolved platforms, if a management Ethernet interface(em0) has an inet or inet6 family configured and "delete interfaces em0" is issued, the Link Layer Discovery Protocol (LLDP) output packets will stop transmitting, causing the LLDP neighborship to remain down in peer router.
PR Number
Synopsis
Category: Virtual Router Redundancy Protocol
1680178
VRRP master-master condition might occur when there are more than two devices in the VRRP group
Product-Group=evo
When more than two devices are part of the VRRP group and a lower priority master sends a keepalive as master, low priority backup may transition to master state and get stuck.
20.4R3-S6-EVO - List of Known issues
PR Number
Synopsis
Category: EVO platform software
1597999
PTX10001-36MR: Inconsistency in the platform name used in multiple places, version, snmp mibs, etc
Product-Group=evo
"show snmp mib walk sysDescr" will show ptx10001-36mr.
Resolved In:
evo:21.2R1-J3-EVO evo:21.2R2-EVO evo:21.2R2-S1-EVO evo:21.2R3-EVO evo:21.3R1-S1-EVO evo:21.3R2-EVO evo:21.4R1-EVO evo:22.1R1-EVO junos:21.2R2 junos:21.2R2-S1 junos:21.2R3 junos:21.3R1-S2 junos:21.3R2 junos:21.4R1 junos:21.4R2 junos:22.1R1
PR Number
Synopsis
Category: PFE L2 forwarding features on BT based platforms
1666921
MVRP enabled trunk ports might go into blocked/designated state on the PTX EVO platforms
Product-Group=evo
On the PTX EVO platforms, MVRP enabled trunk ports with xSTP configured might go into blocked/designated state if the peer connects to the interface has no VLANs configured in its trunk port.
Resolved In:
evo:20.4R3-S6-EVO evo:22.2R2-EVO evo:22.3R1-EVO evo:22.4R1-EVO
PR Number
Synopsis
Category: Express BT PFE L3 Features
1671065
Fragment frames errors will be seen on the 400G interface
Product-Group=evo
On the PTX10003 platform, fragment frames error will be seen on the 400G optics interface when the optics cable interoperates with third-party equipment. Due to this, some packets would be lost.
Resolved In:
evo:21.2R3-S3-EVO evo:21.4R3-S1-EVO evo:22.1R3-EVO evo:22.2R2-EVO evo:22.2R3-EVO evo:22.4R1-EVO evo:23.1R1-EVO junos:22.1R3 junos:22.2R3 junos:22.4R1
PR Number
Synopsis
Category: AAA, auditd issues
1622936
Idle/inactive netconf user sessions not terminated as per the config set under class
Product-Group=evo
Session idle time was not supported for netconf session in EVO, as part of the current PR extending this feature support. This might result in dangling sessions.
Resolved In:
evo:20.4R3-S5-EVO evo:22.1R1-EVO junos:20.4R3-S5 junos:20.4R3-S6 junos:22.1R1
PR Number
Synopsis
Category: mgd, ddl, odl infra issues
1703745
upgrade validation mgd -I fails to detect invalid hostname, mgd -I fails post reboot
Product-Group=evo
When an EVO box running with non-lts19 image having host-name with underscore is upgraded to an EVO image which is post lts19 upgrade, then validation will fail during upgrade validation, which is the expected behavior. Earlier during upgrade - validation does not detect the invalid hostname with underscore and upgrade validation used to pass.
Resolved In:
evo:23.2R1-EVO
PR Number
Synopsis
Category: SRX branch platforms
1594014
During reboot, "warning: requires 'idp-sig' license" can be seen on the screen even when the device has valid license
Product-Group=evo
If a device is rebooted manually or reboots for any other reason, The following messages can be seen on the boot up screen even when the device has valid license and proper configuration to use the features like IDP/UTM
Resolved In:
evo:21.4R3-S1-EVO evo:22.1R3-EVO evo:22.2R2-EVO evo:22.2R3-EVO junos:20.3R3-S6 junos:20.4R3-S6 junos:21.1R3-S4 junos:21.2R3-S4 junos:21.2X32-D10 junos:21.3R3-S3 junos:21.4R3-S1 junos:22.1R2-S2 junos:22.1R3 junos:22.2R2 junos:22.2R3 junos:22.3R1-S1 junos:22.3R2 junos:22.4R1 junos:23.1R1
Modification History
First publication 2023-01-20
20.4R3-S6-EVO: Software Release Notification for JUNOS Evolved Software