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 PTX QFX running Junos Evolved software
Alert Description
Junos Software Service Release version 22.4R1-S1-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 22.4R1-S1-EVO is now available.
22.4R1-S1-EVO - List of Fixed issues
PR Number
Synopsis
Category: CoS support on DNX
1703567
Port-mirroring is not working if hierarchical-scheduler is enabled on the analyzer output port
Product-Group=evo
On ACX7100 platform, the mirrored packets are not sent thru the output inteface if the "hierarchical-scheduler" is configured under the output interface.
PR Number
Synopsis
Category: Layer 3 forwarding, both v4+v6
1671451
Some VPLS and L2VPN streams are dropped on the AE interface after a change in MTU configuration on the AE interface
Product-Group=evo
On all Junos OS Evolved platforms the MTU change on the LAG interface triggers an interface flap leading to ECMP next-hop modification. When this issue happens some of the Layer 2 Virtual Private Network (L2VPN) and Virtual Private LAN Services (VPLS) flows may get dropped. The issue is not observed consistently.
PR Number
Synopsis
Category: Application controller related issues
1685995
The fibd process will crash when a large number of interfaces are deleted and added back
Product-Group=evo
On all Junos Evolved platforms, fibd process will crash when a large number of logical interfaces (> 1K) are deleted and added back in a single commit or multiple commits in a very less time (<5 seconds). When fibd crashes, Forwarding Information Base (FIB) will restart and function as normal.
PR Number
Synopsis
Category: Issues related to evo operations - libevo infra, typeinfo ..
1702734
On Junos OS Evolved platforms, the traffic impact is seen as the "set system process routing enable/disable" knob is not working as expected
Product-Group=evo
On Junos OS Evolved platforms, if the routing is stopped using "set system process routing disable" and commit, the routing process will not come online once "delete system process routing disable" and commit is done.
PR Number
Synopsis
Category: Issues related to Junos licensing infrastructure
1658869
The license might get out of sync between master and backup RE
Product-Group=evo
On all Junos OS Evolved platforms, the license might get out of sync between master and backup RE after the addition/deletion of licenses.
1696879
License key is not installed after upgrade
Product-Group=evo
On all Junos Evolved platforms, Installation of node-lock license key on config mode doesn't get installed after upgrade. If any of the protocols are enabled by the license key, it will be impacted after the software upgrade.
PR Number
Synopsis
Category: Shard routing infrastructure within RPD
1696035
An rpd crash is observed while creating indirect-next-hop in the BGP sharding environment with bgp.l3vpn.0 with next-shop as a color route
Product-Group=evo
On Junos MX and Junos Evolved PTX platforms with BGP (Border Gateway Protocol) sharding enabled, an rpd crash is observed for indirect-next-hop is not created properly for the tunnel route when the route is received in the sharding thread in bgp.l3vpn.0 with next-hop as the color route.
PR Number
Synopsis
Category: RPM and TWAMP
1703104
The TWAMP test session packets are dropped when the payload is less than 52 bytes
Product-Group=evo
On all Junos OS Evolved platform and Junos platform is using MPC10E/MPC11E/JNP10K-LC9600 linecards, If a Two-Way Active Management Protocol (TWAMP) client from a different vendor is transmitting a packet that is smaller than the 52 bytes then (the minimum allowed by RFC5357 is 41), the TWAMP reflector will be unable to function. Any packets from the TWAMP client will therefore be ignored. Similar to this, juniper boxes will also block any answers that are less than 52 bytes long, causing TWAMP test sessions to report a packet loss.
22.4R1-S1-EVO - List of Known issues
PR Number
Synopsis
Category: EVO L3 routing for BCM XGS Platforms
1697143
QFX5220-32CD: evo-pfemand core is seen after ISSU upgrade via automated script.
Product-Group=evo
On QFX5220-32CD, evo-pfemand core is seen after ISSU upgrade via automated script. In this scenario, evo-pfemand restarts and service is resumed. There will be impact to traffic until evo-pfemand initialisation completes.
Resolved In:
PR Number
Synopsis
Category: Gnats category for dynamic rendering infrastructure
1695523
The routing protocol daemon may core dump when streaming telemetry data
Product-Group=evo
There are edge cases where the routing protocol daemon may core dump when streaming the telemetry data for paths under the protocol container. For example: "/network-instances/network-instance[name='DEFAULT']/protocols/protocol/isis"
Resolved In:
evo:22.2R2-S1-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.3R3-EVO evo:22.3X80-D30-EVO evo:22.3X80-D31-EVO evo:22.4R2-EVO evo:23.1R1-EVO evo:23.2R1-EVO junos:21.2R3-S4 junos:21.4R3-S3 junos:23.1R1 junos:23.2R1
PR Number
Synopsis
Category: System Management daemon and related issues
1696668
Sapphire :: Qfx5220-128c: System reboot related log message SYSTEM_REBOOT_EVENT may not be displayed in 'show log messages' | match SYSTEM_REBOOT_EVENT.
Product-Group=evo
On a QFX5220 system, system reboot from cli, log related to system reboot event may not appear in message log or cli> show log messages | match SYSTEM_REBOOT_EVENT. Users can see the log in journalctl logs.
Resolved In:
evo:22.3R3-EVO evo:22.4R2-EVO evo:23.1R1-EVO evo:23.2R1-EVO junos:22.3R3 junos:22.4R2 junos:23.1R1
PR Number
Synopsis
Category: EVO RPD agent PRs
1694773
RPD core is seen after the switchover
Product-Group=evo
On all dual-RE Junos Evolved platforms, RPD core will be seen in the new master RE after the switchover when NSR is enabled. This issue will be seen when before the switchover, any catastrophic configuration change like 'evpn protocol normalization' is done.
Resolved In:
evo:22.4R2-EVO evo:23.1R1-EVO evo:23.2R1-EVO junos:22.4R2 junos:23.1R1 junos:23.2R1
PR Number
Synopsis
Category: EVPN control plane issues
1691132
In the EVPN-MPLS multihoming scenario, MAC-IP route deletion and addition result in traffic drop
Product-Group=evo
On all platforms, MAC-IP route deletion and addition are triggered when re-ARP (Address Resolution Protocol) on MH (Multihoming) device fails in the EVPN-MPLS multihoming scenario resulting in traffic drop.
Resolved In:
evo:23.1R1-EVO junos:23.1R1
PR Number
Synopsis
Category: Express PFE FW Features
1699323
JDI_REG:: EVO:Scapa[BFD]: one of the BFD state is down after Performing BT Restart"
Product-Group=evo
This issue is seen during CLI triggered onlining of the PFE, i.e., when "request chassis fpc slot pfe restart" is executed. Please use the workaround provided.
Resolved In:
PR Number
Synopsis
Category: Configuration management, ffp, load action
1671112
Test Configuration might fail even though the config file is having valid configurations
Product-Group=evo
Root cause; In test configuration flow we are calling mustd as "/usr/sbin/mustd -q /var/run/db/file.data /var/run/db/file.data+ -F -m" where we just copy the existing cog.db (generated out of committed config) as cdg.db+ , use it for testing the configuration passed, and remove it once the testing is done. This is creating the issue because the configuration is tested against the existing cdg.db. Fix would be to create the cdg.db fresh from the configuration to be tested and test the configuration against that. This new cdg.db should not replace the existing one in /var/run/db.
Resolved In:
evo:22.2R2-S2-EVO evo:22.2R3-EVO evo:22.3R1-S2-EVO evo:22.3R2-EVO evo:22.3R3-EVO evo:22.4R1-EVO evo:22.4R2-EVO evo:23.1R1-EVO evo:23.2R1-EVO junos:22.1R3-S1 junos:22.2R2-S2 junos:22.2R3 junos:22.3R1-S2 junos:22.3R2 junos:22.3R3 junos:22.4R1 junos:22.4R1-S1 junos:22.4R2 junos:23.1R1
PR Number
Synopsis
Category: UI Infrastructure - mgd, DAX API, DDL/ODL
1679413
Configuration filtering doesn't work when the logical system is present
Product-Group=evo
On SRX platforms, configuration filtering doesn't work when the logical system is present.
Resolved In:
evo:22.2R2-S2-EVO evo:22.2R3-EVO evo:22.3R1-S2-EVO evo:22.3R2-EVO evo:22.3R3-EVO evo:22.4R2-EVO junos:21.4R3-S3 junos:22.1R3-S1 junos:22.2R2-S2 junos:22.2R3 junos:22.3R1-S2 junos:22.3R2 junos:22.3R3 junos:22.4R1-S1 junos:22.4R2 junos:23.1R1
1699245
The mgd process might crash during commit synchronize
Product-Group=evo
On all Junos and Junos Evolved platforms with dual Routing Engines, during commit script synchronize, the backup Routing Engine mgd get process crashes once the memory leak reaches 65K. When this happens, commit configurations from the primary Routing Engine fail.
Resolved In:
evo:22.2R2-S2-EVO evo:22.2R3-EVO evo:22.3R1-S2-EVO evo:22.3R2-EVO evo:22.3R3-EVO evo:22.4R2-EVO evo:23.1R1-EVO evo:23.2R1-EVO junos:20.3X75-D35 junos:20.3X75-D50 junos:21.2R3-S4 junos:21.4R3-S3 junos:22.1R3-S1 junos:22.2R2-S2 junos:22.2R3 junos:22.3R1-S2 junos:22.3R2 junos:22.3R3 junos:22.4R1-S1 junos:22.4R2 junos:23.1R1
PR Number
Synopsis
Category: ACX7000 interface software related issues.
1670033
Performance Monitoring for 400ZR optics reporting data as Suspect with reason "Int Too Short"
Product-Group=evo
For ACX7100-32C and ACX7100-48C platforms, increase the Performance Monitoring (PM) Engine polling interval from one every 2 and 4 seconds, respectively, to 1 per second for both platforms.
Resolved In:
evo:22.3R3-EVO evo:22.4R2-EVO junos:22.4R1-S1 junos:22.4R2 junos:23.1R1
Modification History
First Publication 2023-02-28
22.4R1-S1-EVO: Software Release Notification for JUNOS Evolved Software