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 Platforms running Junos Evolved software
Alert Description
Junos Software Service Release version 22.2R3-S4-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.2R3-S4-EVO is now available.
22.2R3-S4-EVO - List of Fixed issues
PR Number
Synopsis
Category: EX2300/3400 PFE
1695771
Traffic loss is seen when a MAC moves from dot1x port to non-dot1x port
Product-Group=evo
On all Junos and Junos OS Evolved platforms is having dot1x enabled interface. When two or more MAC addresses are learnt on a dot1x port, and if one of them is shifted to a non-dot1x port, the MAC address that was moved is still seen as a MAC-based VLAN entry on the Layer2 Address Learning Manager (l2alm). This could lead to network traffic being lost.
PR Number
Synopsis
Category: "agentd" software daemon
1715377
The agentd would become unresponsive on all Junos platforms
Product-Group=evo
When using Junos Telemetry Interface (JTI) with subscriptions to Packet Forwarding Engine (PFE) based sensors, agentd might slowly leak memory. After prolonged runtime agentd may stop functioning properly, which will affect JTI data export. This will affect telemetry services.
PR Number
Synopsis
Category: MPC Fusion SW
1777534
On MX and EX platform replacing the line-cards may trigger FPC to be offlined due to unreachable destinations
Product-Group=evo
On Junos MX and EX9200 platforms when replacing MPC2E-NG and EX9200-40XS with MPC3E-NG, SCBE3 and EX9200-MPC cards, inserting the new MPC may cause new and other line cards to go offline due to unreachable destinations. This happens due to some registers on the fabric card is not properly updated once the fabric channel bonding has changed and impacts the traffic.
PR Number
Synopsis
Category: EVO interface software
1775320
The Control Board and FPC will restart if the optics present in the first three ports of PTX10001-36MR draw 50W or more power
Product-Group=evo
On Junos Evolved PTX10001-36MR with coherent optics QSFP56-DD-400G-ZR-M, QSFP56-DD-400G-ZR or QSFP56-DD-400G-ZR-HP, if the optics present in the first three ports draw combined power of 50w or more the power rail will experience fault, resetting the Control Board (CB) and Flexible PIC Concentrators (FPC). The entire device traffic will be impacted when CB and FPC go for a reset.
PR Number
Synopsis
Category: Border Gateway Protocol
1728829
In a high scaled environment, high rpd CPU utilization might be observed when a routing related commit is performed
Product-Group=evo
On all platforms, high rpd CPU utilization might be observed when a routing related commit is performed in a high-scaled environment having BGP groups configured with VPN family (inet-vpn, inet6-vpn). No traffic impact or protocol flap will be seen but unexpected high rpd CPU utilisation will raise operational challenges, especially if the system is very scaled.
1789863
The rpd crash can be seen when large number of VRF instances are created and bgp peering terminated
Product-Group=evo
On all Junos and Junos Evolved platforms, the rpd (Routing Protocol Daemon) crash will be observed when BGP (Border Gateway Protocol) is terminated by the user and if large number of VRF instances are created. This happens as some BGP internal data structure is not cleaned up properly. This crash can lead to a temporary traffic drop, but the system will automatically recover.
PR Number
Synopsis
Category: Track PRs in BGP BMP area & is part of BGP inside RPD.
1767785
The EOR message is missed for one peer in a scaled BMP scenario
Product-Group=evo
On all Junos and Junos OS Evolved platforms with BGP Monitoring Protocol (BMP) enabled in scaled scenario (4K BGP peers, 6 BMP stations), after disabling/enabling BMP, due to timing issues, one out of six BMP stations will not receive End-of-RIB (EOR) message for one peer. This will not impact routing or data forwarding, however will have impact on data collection.
1770976
Routes getting stuck in hidden state forever in BMP scenario
Product-Group=evo
On all Junos and Junos Evolved platforms where BMP (BGP Monitoring Protocol) is configured, the routes are not removed from the RIB (Routing Information Base) even when the damping timer expires and they are stuck in the hidden
PR Number
Synopsis
Category: Track PRs in BGP Flow Spec area & is part of BGP inside RPD.
1740257
The inetflow6 routes are not installed on firewall filter table using BGP FlowSpec
Product-Group=evo
On all Junos and Junos OS Evolved platforms configured with BGP FlowSpec, ipv6 routes are installed in flow route table but not in firewall filter table. FlowSpec routes are blocked and dropped leading to traffic disruption. This is especially seen when BGP UPDATE Message does not include "Filter: Packet Length filter" within "FLOW_SPEC_NLRI" from BGP flowspec server thereby inetflow6 routes do not have "Action(s)"
PR Number
Synopsis
Category: PTX10003 Platform related issues
1706688
The device will undergo a silent reboot due to disk related failures
Product-Group=evo
On all Junos Evolved platforms, if a disk related failure is detected, a software reboot will be triggered even if the error is a transient or temporary one. A resiliency fix to check the SSD freeze multiple times before triggering the reboot is added.
PR Number
Synopsis
Category: EVO L3 routing for BCM XGS Platforms
1797319
Traffic drop on AE interfaces when MPLS FRR is enabled
Product-Group=evo
On the QFX5220 platform, when enabling fast reroute (FRR) on an Multiprotocol Label Switching (MPLS) label-switched path (LSP), traffic drop will be seen if an aggregated ethernet (AE) interface is part of an equal-cost multipath (ECMP) group.
PR Number
Synopsis
Category: PFE L2 forwarding features on BT based platforms
1785084
IFBD lookup Failure in DLU, packets needs to be dropped rather than learned through control IFL in packetio.
Product-Group=evo
Related to L2 level security fix.
PR Number
Synopsis
Category: Express BT PFE L3 Features
1716767
Protocol hello and keep-alive messages will not work on the mac accounting interface
Product-Group=evo
On PTX10003, PTX10008, PTX10016 and PTX10001-36MR Junos OS Evolved Platforms , when mac accounting is enabled under any interface and that same interface is also used to exchange hello/keep-alive protocol messages, then those multicast-based hello and keep-alive messages will not function on the mac accounting interface and any dynamic routing protocol which uses multicast for exchanging hello and keep-alive packets got affected by this PR when mac accounting is enabled in the communication path.
1777759
LAG interfaces will take longer than usual to come up in a scaled scenario with ALB
Product-Group=evo
On PTX10001, PTX10004, PTX10008 and PTX10016 platforms, if Adaptive load balancing (ALB) is configured on LAG interface, the LAG interfaces will take longer than usual to be up if they are all enabled in the same commit. LAG interfaces get stuck in 'attached' state. This issue happens in a scaled Link Aggregation Group (LAG) (~65 ae*) scenario.
1789679
PTX10K EVO platforms with high multicast route changes can trigger multicast traffic queue drops
Product-Group=evo
Due to pfe internal logging processing time of multicast next-hop changes, multicast route convergence might take longer on one FPC versus other FPCs in the same system. This can cause multicast traffic amplification resulting in multicast traffic queue drops. The condition is transient and may last for sub-seconds to seconds.
1790095
The pfestatsd process may fail to restart when running out of file descriptors
Product-Group=evo
The pfestatsd process runs out of file descriptors when there are 16 FPCs in the system as the number of concurrent connections exceeded 1024 for PTX platform.
1792173
Traffic loops and convergence issues in a scaled multicast churn scenario
Product-Group=evo
On PTX10008, PTX10016 and PTX10001-36MR platforms, incorrect internal processing at the Packet Forwarding Engine (PFE) leads to congestion.
PR Number
Synopsis
Category: BX PFE firewall issues
1772149
Balerion-FT:Firewall: aftmand-bx cores continuously at JexprHandleFilter:: updatePfeInst, when attaching filter which has 5-tuples+FC+DP+TTL+Fragment+ifl matches
Product-Group=evo
If a filter does not compile due to an unsupported match combination (i.e. the set of matches configured in the filter is not supported by hardware), attaching this filter to an interface will cause aftmand-bx to crash.
PR Number
Synopsis
Category: QFX Control Plane VXLAN
1777635
Traffic loss for few seconds will be observed after restarting l2-learning process on L3 VxLAN gateway
Product-Group=evo
On all Junos and Junos Evolved platforms, in the EVPN-VXLAN( Ethernet Virtual Private Network- Virtual Extensible Local Area Network) scenario, traffic loss for few seconds would be observed when a user restart l2-learning process on a Layer-3 VXLAN gateway. This happens because of timing issues in the kernel, which mistakenly delete MAC routes of its associated devices instead of updating them in the table. The traffic from devices with those MAC addresses won't flow until the system is back on track and syncing properly.
PR Number
Synopsis
Category: Firewall related development
1674893
Error messages are observed while configuring the firewall filter with family inet6 with next-header and no payload-protocol and committing them
Product-Group=evo
On all Junos evolved PTX platforms, when firewall filter with family inet6 is configured with source-port/destination-port and has next-header and no payload-protocol, error messages are observed causing the filter fail to install.
1800262
Unable to apply loopback firewall filter. checkloFilterBindingListCallback error thrown
Product-Group=evo
On PTX EVO running 22.2R3-S3 commit check fails with checkloFilterBindingListCallback when trying to apply filters on lo0 interface.
PR Number
Synopsis
Category: Index management related issues; idmd* daemons
1794401
PTX EVO fabric token index versioning enhancements
Product-Group=evo
Upon heavy multicast route changes, fabric tokens can get out of sync between difference FPCs and potentially trigger multicast traffic loops for a short period.
PR Number
Synopsis
Category: management ethernet related issues - mgmt-ethd daemon
1705245
PTX10004/8/16 EVO : GARP is not sent from new master RE's mgmt interface upon RE switchover
Product-Group=evo
GARP(Gratuitous ARP) is not sent from new master RE's mgmt interface upon RE switchover on PTX10004/8/16 EVO. The ARP table of the network devices located in the same segment is not updated.
PR Number
Synopsis
Category: Issues related to evo operations - libevo infra, typeinfo ..
1776828
The evo-aftmand-bt process crash is observed during an RE switchover
Product-Group=evo
On Junos Evolved PTX platforms with hundreds of firewall terms configured, an extremely rare timing scenario during Routing Engine (RE) switchover can cause evo-aftmand-bt process on the FPC to crash which can impact traffic services. This issue has only been observed once.
PR Number
Synopsis
Category: EVO Netstack Juniper Tunnel Driver Module
1713989
Junos OS Evolved: Packets which are not destined to the router can reach the RE (CVE-2023-44195)
Product-Group=evo
An Improper Restriction of Communication Channel to Intended Endpoints vulnerability in the NetworkStack agent daemon (nsagentd) of Juniper Networks Junos OS Evolved allows an unauthenticated network based attacker to cause limited impact to the availability of the system. Please refer to https://supportportal.juniper.net/
JSA73160
[juniper.net]
for more information.
1718999
TCP connection will be terminated when sent with incorrect MSS
Product-Group=evo
On all Junos Evolved platforms, Transmission Control Protocol (TCP) packets whose size is larger than its interface Maximum Transmission Unit (MTU) will be dropped impacting TCP connections.
1731219
Junos OS Evolved: Packets which are not destined to the device can reach the RE (CVE-2024-21590)
Product-Group=evo
An Improper Input Validation vulnerability in the Juniper Tunnel Driver (jtd) and ICMP module of Juniper Networks Junos OS Evolved allows an unauthenticated attacker within the MPLS administrative domain to send specifically crafted packets to the Routing Engine (RE) to cause a Denial of Service (DoS). Please refer to https://supportportal.juniper.net/
JSA75728
[juniper.net]
for more information.
PR Number
Synopsis
Category: EVO linux defects & enhancement requests
1698495
Junos OS Evolved: libslax: Multiple vulnerabilities in libslax resolved
Product-Group=evo
Multiple vulnerabilities resolved in libslax 0.22.1. Please refer to https://supportportal.juniper.net/
JSA79102
[juniper.net]
for more information.
PR Number
Synopsis
Category: EVO category to hold IPv6 Neighbor Discovery Protocol and re
1802833
The egress traffic loss occurs when IPv6 Router Solicitation (RS) packets are processed just after interface flap(down/up)
Product-Group=evo
On all Junos Evolved platforms, the the egress traffic loss occurs when IPv6 Router Solicitation (RS) packets are processed just after interface flap(down/up).
PR Number
Synopsis
Category: Express PFE MPLS for EVO platforms
1765107
Unknown sensors are added in PFE on all Junos OS Evolved platforms
Product-Group=evo
On all Junos OS Evolved platforms, any client (in this case it was LDP), a route (with a sensor attached) is added and deleted immediately. This is a timing issue and easily reproducible.
PR Number
Synopsis
Category: EVO RPD agent PRs
1732786
The rpd process will crash if too many trace options are initialised
Product-Group=evo
On all Junos OS Evolved platforms, rpd crash will be seen when debug tracing is enabled, routing services will be impacted during rpd crash recovery.
1792740
Observed "MCNHMBB index availability" alarm when system is subjected to heavy PIM join/prune churn
Product-Group=evo
On Junos OS Evolved platforms, During heavy multicast route changes or PIM join/prune churn, MCNHMBB (Multicast NextHop Make Before Break) index space is running low and will flow control back to RPD (Routing Protocol Daemon). This is not a bug, a small enhancement.
PR Number
Synopsis
Category: Configd, ffp issues
1736884
the cosd crash can be seen when forwarding-classes and classifiers hierarchies are getting modified in single commit
Product-Group=evo
On all Junos Evolved platforms, when forwarding-classes and classifiers hierarchies are getting modified in single commit will lead the cosd crash.
PR Number
Synopsis
Category: eventd, syslog infra issues
1726925
Syslog filter not functioning with generating /etc/syslog.conf+ file after syslog config is deactivated and re-activated
Product-Group=evo
On Junos Evolved platforms, after syslog config is deactivated and re-activated, syslog filter does not function because /etc/syslog.conf file is not updated with generating /etc/syslog.conf+ file.
PR Number
Synopsis
Category: mgd, ddl, odl infra issues
1665008
The system will ask for password while saving configuration files on single RE platforms
Product-Group=evo
The system may ask for your password when you are thing to save configuration file.
PR Number
Synopsis
Category: SNMP, mib2d issues
1675456
[SNMP_Hardening] On executing IWL SilverCreek SNMP v2c and v3 suites mib2d core is triggered
Product-Group=evo
There is no service impact due to the failure of these test suites and these issues are not reported by any customer. These are silver creek hardening tests for EVO and issues raised by internal test team. The plan is to fix the issues in the future release as part of the PR-1713908
1755599
The snmpd-subagent core is generated if snmpwalk is executed on SNMP server for jnxLED mibs while the system is rebooting
Product-Group=evo
The snmpd-subagent core is generated if snmpwalk is executed on SNMP server for jnxLED mibs while the system is rebooting.
PR Number
Synopsis
Category: Express PFE FW Features
1711521
EVO | COS classification is not working as expected
Product-Group=evo
CoS classification is not working as expected.
PR Number
Synopsis
Category: MX Inline Jflow
1708195
Monitoring services are impacted due to SRRD crashes and restarts
Product-Group=evo
On all Junos Evolved platforms, SRRD (Sampling Route Record Daemon) cores and restarts impacting the monitoring services.
PR Number
Synopsis
Category: ISIS routing protocol
1746557
Stale IP prefixes when issuing "show isis route flex-algorithm-id"
Product-Group=evo
The Flex algorithm in IS-IS does not install IP (v4/v6) routes into the RIB. However, when using the current IS-IS show CLI command, "show isis route flex-algorithm-id <>", it still displays certain IPv4/IPv6 IS-IS routes in the output, even though these routes are not actually being placed in the RIB. After implementing the fix, the IPv4/IPv6 IS-IS routes will no longer be displayed in the output of the CLI for the flex-algorithm.
1760334
Routing loop will be observed during ISIS-FRC implementation
Product-Group=evo
On Junos and Junos Evolved platforms, routing loop will be observed, when configuring FRC (Flood-Reflector Client) and processing anycast Layer 2 prefix advertisements, it leads to the installation of ISIS routes with incorrect nexthops .
1781103
Gradual memory leak seen in the rpd process on Junos based PTX and QFX10002/10008 platforms
Product-Group=evo
On Junos based PTX and QFX10002/10008 platforms configured as Intermediate System to Intermediate System (ISIS) Flood-Reflectors (FR client/servers) and running images between 20.3X75-D44.4 and 20.3X75-D44.8, the Routing Protocol Daemon (rpd) process shows gradual and consistent increase in memory utilisation which eventually leads to swap memory exhaustion and the rpd process restarts impacting service. The leak is caused due to special handling of ISIS-FR routes during installation.
PR Number
Synopsis
Category: Layer 2 Circuit issues
1768323
JUNOS and JUNOS EVO-RPD process crash under High Availability Route Engine (RE) scenarios when L2circuits are enabled
Product-Group=evo
Routing Protocol Daemon (RPD) process crash when l2circuits are enabled in scenarios with backup Route Engine (RE).
PR Number
Synopsis
Category: Layer 2 Control Module
1770053
xSTP configured interface will remains in discarding state
Product-Group=evo
On all Junos and Junos OS Evolved Platforms, when an interface is added inside RSTP (Rapid Spanning Tree Protocol), VSTP (VLAN Spanning Tree Protocol), MSTP (Multiple Spanning Tree Protocol) or STP (Spanning Tree Protocol), because of STP port creation fail from l2cpd (Layer 2 control protocol daemon), port will remains in discarding state. This leads to traffic impact.
PR Number
Synopsis
Category: Layer2 forwarding on EX/NTF/PTX/QFX
1772424
Connectivity between static and LDP signaled pseudowires broken in VPLS after upgrade and results in VPLS traffic drop
Product-Group=evo
On all Junos and Junos OS Evovled platforms, when there is a upgrade and also when one mesh group of routing instance is substring of other, the connection between static and LDP (Label Distribution Protocol) signaled psuedowires is broken will lead to traffic drop.
1776991
ARP resolution issues will be observed in the H-VPLS environment
Product-Group=evo
On Junos and Junos Evolved platforms, traffic impact will be observed due to ARP (Address Resolution Protocol) resolution issues when multiple mesh-group is configured under the same routing-instance and the name of each mesh-group is not unique i.e. substring of another mesh-group in the H-VPLS (Hierarchical Virtual Private LAN Service) environment.
1803898
Traffic flooding occurs when deactivating and activating interfaces in EVPN scenario
Product-Group=evo
On all Junos and Junos OS Evolved platforms, while deactivating/activating the interface, the first control MAC for a BD and IFL combination can get lost when L2alm'd ifbd Mac sequence num is different from what is sent by L2ald. This will lead to traffic flooding for the MAC which will be impacted.
PR Number
Synopsis
Category: Interface PR for LC1202 LC
1740145
Error/warning message is missing for unsupported speed in syslog file
Product-Group=evo
On all Junos Evolved platforms, error/warning message is missing for unsupported speed or invalid caonfiguration.
PR Number
Synopsis
Category: Issues related to Junos licensing infrastructure
1783509
License key is not installed after USB upgrade, via "set system license keys key"
Product-Group=evo
Issue: During the USB upgrade, "/tmp/root/chas_ser_num.id" file does not exist. So the USB bootup commit causes failure. Fix: Added file existing check for ?/tmp/root/chas_ser_num.id? file, to avoid validation issue during USB upgrade. In normal upgrade "/var/db/scripts/validation/" path is persistant , you will not see this issue.
1792672
License is lost on NG-RE platforms after device/routing-engine reboot
Product-Group=evo
On NG-RE (Next Generation Routing Engine) platforms, license is lost after restarting device/routing-engine. If any service depends on that license, that service will be impacted.
PR Number
Synopsis
Category: Port-based link layer security services and protocols that a
1729467
MACsec interoperability issue between Juniper and non Juniper platforms
Product-Group=evo
On all Junos and Junos Evolved platforms with MACsec (Media Access Control security) configured , frequent SAK (Secure Association Key) rollover is observed when the peer device is a non-Juniper box and the Juniper device is acting as the key-server. This results in unstable MACsec sessions between the juniper device and the non Juniper device.
PR Number
Synopsis
Category: Multiprotocol Label Switching
1719162
MPLS LSP stats will not increment post the rpd restart
Product-Group=evo
On all Junos and Junos OS Evolved platforms post rpd restart using cmd "restart routing immediately" mpls lsp statistics will not work.
1743957
When MPLS is configured with in-place-lsp-bandwidth-update command, an incorrect error message and traffic loss are observed after the make-before-break failure
Product-Group=evo
On all Junos and Junos Evolved platforms, when in-place-lsp-bandwidth-update knob is configured in MPLS (Multi Procotol Label System), the auto-bandwidth adjust timer expires, when make-before-break is undergoing, an incorrect error message is seen in the "show mpls lsp" command, and in some cases where MBB takes more time to complete or aborted, it also results in traffic loss.
PR Number
Synopsis
Category: OSPF routing protocol
1774715
OSPF route flap might be observed
Product-Group=evo
On all Junos and Junos OS Evolved platforms OSPF (Open Shortest Path First) route flaps can be observed which will cause a traffic drop. This is a rare timing issue happening after an OSPF adjacency flap.
PR Number
Synopsis
Category: Protocol Independant Multicast
1792886
The rpd crash is observed when PIM SSM mode with RPF-Vector and MoFRR is configured
Product-Group=evo
On Junos and Junos Evolved platforms , when PIM SSM (PIM Source-Specific Multicast) with RPF (Reverse Path Forwarding)-Vector and MoFRR (Multicast-only fast reroute) is configured , rpd crash if the device receives PIM Prune message for (S, G) state with RPF vector TLV. interface is freed for the (S, G) from the outgoing interface list i.e. RPF-Vector TLV (Type, Length, and Value) having (S, G) is getting freed but that same (S, G) is still used by MoFRR. The issue happens when MoFRR Backup upstream interface is also listed at the outgoing interface list for the (S, G)
PR Number
Synopsis
Category: RPD Interfaces related issues
1798801
MPLS/RSVP LSP self-ping behaviour differs from expected behaviour causing self-ping time out
Product-Group=evo
On Junos OS Platforms, configured with Multiprotocol Label Switching (MPLS)/Resource Reservation Protocol(RSVP) Label Switched Path(LSP) and firewall filter applied on the loopback with prefix list that does not include the interface address of local router, self-ping time out is observed.
PR Number
Synopsis
Category: KRT Queue issues within RPD
1745509
rpd core at #2 0x00007f9b2512742c in __assert_fail_base (fmt=0x7f9b2528bae8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x55be37507a48 "nh_idx_t_getval(nhid) == nh_idx_t_getval(rt_nexthops_nhid(rtnh))", file=0x55be375077e8 "../../../../../../../../src/layer3/usr.sbin/rpd/lib/krt/common/krt_ack.c", line=1306, function=) at assert.c:92
Product-Group=evo
RPD core is sometimes seen if there are many unilist nexthop with identical key values but different metric in Evo, esp when ACK is requested for those nexthops
PR Number
Synopsis
Category: RPD Next-hop issues including indirect, CNH, and MCNH
1777068
Policy Evaluation causing unrelated route flaps in Dynamic Tunnel setup
Product-Group=evo
On all Junos and Junos Evolved platforms that support Dynamic tunnels, a policy evaluation of the routing policy causes flaps for unrelated tunnel routes. The route flap for the tunnel route will cause traffic loss.
1785884
The rpd crash is observed due to segment fault
Product-Group=evo
On Junos OS Evolved platforms, when no acknowledgment is received from PFE (Packet Forwarding Engine) within timeout results in the rpd (Routing Process Daemon) crash. This issue happens when routes requesting acknowledgment do not receive acknowledgment leading to segment fault.
1793196
Multicast traffic black-holing upon MoFRR primary link went down
Product-Group=evo
On all Junos and Junos Evolved platforms, when MoFRR (Multicast-only fast reroute) is configured with NSR (Non-stop routing) while interface flapping or RE switchover, there is a next-hop leak and the next-hop in RIB (Routing Information Base) is different from the next-hop in FIB (Forwarding information base) due to that multicast traffic will be impacted.
1808463
CPU utilization of the rpd process stays high on all Junos and Junos OS Evolved platforms
Product-Group=evo
On all Junos and Junos OS Evolved platforms in a corner case, the Routing Protocol Daemon (rpd) CPU utilization will be seen high in scenarios where recursive route resolution is involved. The rpd process will be continuously spinning in the re-resolution job which could impact scheduling of other jobs and re-resolution of other routes impacting traffic.
PR Number
Synopsis
Category: Issues related route resolution routing infrastructure
1737594
Traffic drop can be seen in the MPLS traffic Engineering scenario
Product-Group=evo
On all Junos and Junos Evolved platforms, traffic drop can be seen in MPLS (Multi-Protocol Label Switching) traffic engineering with IGP-FRR (Interior Gateway Protocol Fast Reroute) and preserve next-hop hierarchy. This issue happens when the BGP (Border Gateway Protocol) routes are resolving over BGP and there is a change in the active route. The session ID for the IGP-FRR is assigned to the new active route and the old active route is withdrawn, while the above processing is done the session ID is associated with both the old and new active route, and the old active route, the route gets deleted which triggers the IGP-FRR session ID to be down and the unilist (ECMP)path get stuck causing traffic impact.
PR Number
Synopsis
Category: PTX10K specific platform PRs
1708892
The jnxLEDState mib shows green(2) when PSM (JNP10K-PWR-AC2) is switched off and "OK LED" is unlit off
Product-Group=evo
On Junos Evolved PTX platforms, when PSM (JNP10K-PWR-AC2) is switched off and "OK LED" is unlit off, but jnxLEDState mib shows green(2). There is no impact on traffic.
1745749
The hwdre application restarted due to memory leak
Product-Group=evo
On all Junos Evolved platforms, the hwdre application restarted due to a memory leak.
1766097
PTX10008: When NSR Enabled and FMBB Knobs are configured and if SIB is Offline/Online casue resiliencyd core
Product-Group=evo
PTX10008: When NSR Enabled and FMBB Knobs are configured and if SIB is Offline/Online casue resiliencyd core
PR Number
Synopsis
Category: SNMP Infrastructure (snmpd, mib2d)
1691986
Consistent high CPU usage is seen on the device post reboot
Product-Group=evo
On all Junos and Junos Evolved platforms consistent high CPU usage in snmpd immediately after reboot.
1804856
Warning messages seen while Custom Yang Package Deletion
Product-Group=evo
Warning message is displayed when custom yang package is deleted.
PR Number
Synopsis
Category: ZT/YT pfe l3 forwarding issues
1774127
Memory leak for deactivation/activation of SCU
Product-Group=evo
On MX platforms with MPC10, MPC11, LC9600, and MX304-LMIC16, the heap memory leaks every time the SCU (source-class-usage) policy is removed i.e. removed and re-applied resulting in restart of the line card. Heap leak is proportional to the number of source classes or indices being removed by related policy.
PR Number
Synopsis
Category: Authentication, Authorization, Accounting, PAM (RADIUS/tacplus)
1797496
Config login class with allow/deny-configuration-regexps not working as expected with Routing-instances
Product-Group=evo
Config login class with allow/deny-configuration-regexps not working as expected with Routing-instances
PR Number
Synopsis
Category: UI Infrastructure - mgd, DAX API, DDL/ODL
1794536
The device goes into configuration locked state due to stale mgd
Product-Group=evo
The device is went into config locked state due to stale mgd. For netconf sessions with , if ungraceful exit happens, the lock is not released. There is auto cleanup supported for such cases, But it is not triggered under problem conditions as faced in this PR. This leads to device remain in locked state due to stale entry. "request system logout pid " can be used for cleanup and to recover from this state.
PR Number
Synopsis
Category: PFE COS features on ZX based platforms
1733509
In TCP flow, the initial SYN+ACK packet will not be marked with specified CoS related action on Junos Evolved platforms
Product-Group=evo
On all Junos Evolved platforms the first SYN+ACK packet in the TCP (Transmission Control Protocol) flow will not be marked with the action of the CoS (Class of Service) configuration. This issue is seen when the firewall filter is configured on the loopback outbound interface. Ideally there is no impact on data traffic because of this issue, but in rare cases peer device can drop the SYN + ACK packet.
22.2R3-S4-EVO - List of Known issues
PR Number
Synopsis
Category: Bi Directional Forwarding Detection (BFD)
1698373
A few BFD sessions might flap after FPC reload and stabilization
Product-Group=evo
On all Junos platforms and Junos Evolved with scaled BFD sessions, FPC reload/restart results in few BFD session flap.
Resolved In:
junos:20.3X75-D44 junos:20.4R3-S10 junos:21.4R3-S6 junos:22.1R3-S5 junos:22.2R3-S3 junos:22.3R3-S2 junos:22.4R3 junos:23.2R1 junos:23.4R2
PR Number
Synopsis
Category: Border Gateway Protocol
1669514
The rpd process might crash on removing the BGP-LU configuration
Product-Group=evo
On PTX Series routers enabled with BGP Labeled Unicast family, the rpd process might crash if the IBGP-LU peer is enabled before the EBGP-LU peer, and in the same sequence, the BGP-LU configuration is removed.
Resolved In:
evo:22.4R1-EVO junos:20.3X75-D42 junos:22.4R1
1729733
BMP leads to prolonged high rpd CPU utilization upon committing the BGP peer import policy configuration
Product-Group=evo
On all Junos and Junos Evolved platforms, with BGP Monitoring Protocol (BMP) configured when a Border Gateway Protocol (BGP) peer import policy configuration change is committed that triggers the BGP reconfiguration job for routes re-evaluation, then high Routing Protocol Daemon (rpd) CPU utilization up to 100% will be observed for a long time which may impact routing as high rpd utilization can starve some processes.
Resolved In:
evo:22.2R3-S3-EVO evo:22.3X50-EVO evo:22.3X80-D43-EVO evo:22.3X80-D44-EVO evo:22.4R3-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.4R1-EVO junos:20.3X75-D36 junos:20.3X75-D44 junos:21.4R3-S7 junos:22.2R3-S3 junos:22.2R3-S4 junos:22.4R3 junos:23.2R2 junos:23.3R1 junos:23.4R1
1779533
The RPD crash is observed on Junos and Junos Evolved platforms in Route Reflector scenario
Product-Group=evo
On all Junos and Junos Evolved platforms, the RPD (Routing Protocol Daemon) crash can be seen in BGP-multipath scenario if it has more than 512 routes for a prefix. The RPD crash will cause a traffic drop but the system will self-recover.
Resolved In:
evo:22.2R3-S3-EVO evo:22.3X50-EVO evo:22.3X80-D43-EVO evo:22.3X80-D44-EVO evo:23.2R2-EVO evo:23.4R1-S1-EVO evo:23.4R2-EVO evo:24.1R1-EVO junos:19.4R3-S13 junos:20.3X75-D44 junos:20.3X75-D440 junos:20.3X75-D52 junos:20.4R3-S10 junos:21.2R3-S8 junos:21.4R3-S6 junos:22.1R3-S5 junos:22.2R3-S3 junos:22.2R3-S4 junos:22.3R3-S2 junos:22.4R3 junos:22.4R3-S1 junos:23.2R2 junos:23.4R1-S1 junos:23.4R2 junos:24.1R1
PR Number
Synopsis
Category: EVO Layer-2 switching for BCM XGS Platforms
1796159
QFX5130/QFX5700: In some specific configuration commit sequences, intermittent traffic drop is seen on a few VXLAN enabled VLANs.
Product-Group=evo
On QFX5130/QFX5700 platforms, intermittent traffic drop might be seen when VXLAN configurations and UFT host-profile configuration are changed in the same commit operation. This problem will not be seen if the UFT profiles are changed in a separate commit
Resolved In:
evo:23.2R2-S1-EVO evo:23.4R2-EVO evo:24.1R2-EVO evo:24.2R1-EVO evo:24.3R1-EVO
PR Number
Synopsis
Category: PFE L2 forwarding features on BT based platforms
1777003
PTX10001-36MR: epp_epc_intr_shmem_err seen in logs
Product-Group=evo
PTX10001-36MR : epp_epc_intr_shmem_err seen in logs
Resolved In:
evo:21.4R3-S6-EVO evo:23.2R2-EVO evo:23.4R1-S1-EVO evo:23.4R2-EVO evo:24.1R1-EVO evo:24.2R1-EVO
PR Number
Synopsis
Category: Express BT PFE L3 Features
1784498
Higher AE traffic convergence observed in ALB configured AE interface
Product-Group=evo
On PTX10001-36MR/PTX10004/PTX10008 and PTX10016 platforms, if Adaptive load balancing (ALB) is configured on AE (Aggregated Ethernet) interface and link up/down, the AE interfaces will take higher traffic convergence during FRR (Fast Reroute) compared to regular AE.
Resolved In:
evo:23.4R2-EVO evo:24.2R2-EVO evo:24.3R1-EVO junos:24.2R2 junos:24.3R1
PR Number
Synopsis
Category: VPWS, L2 CKT, EVPN-VPWS
1775809
In the scaled L2circuit configured with L2circuit redundancy configuration traffic drops may be observed
Product-Group=evo
On Junos OS Evolved ACX platforms, in the scaled L2circuit (Layer 2 Circuit) configured (200+ L2circuits) with L2circuit redundancy configuration traffic drops may be observed on a few instances only when deactivating/activating IGP (Interior Gateway Protocol) protocol or restart routing.
Resolved In:
evo:22.4R3-EVO evo:22.4R3-S1-EVO evo:23.2R2-EVO evo:23.4R1-S1-EVO evo:23.4R2-EVO evo:24.1R1-EVO
PR Number
Synopsis
Category: DNX Multicast
1816540
OSPFv3 neigborship forming issue on IRB when mld-snooping enabled on the BD where IRB hosted
Product-Group=evo
OSPFv3 neighborship is not getting established on IRB when mld snooping is enabled for the BD on which IRB is hosted.
Resolved In:
evo:23.2R2-S2-EVO evo:23.4R2-EVO evo:24.2R1-EVO evo:24.2R2-EVO evo:24.3R1-EVO evo:24.4R1-EVO
PR Number
Synopsis
Category: ACX IFL, IFF creation
1662174
Ipv6 transit traffic statics output is missing
Product-Group=evo
Ipv6 transit traffic statics output is missing
Resolved In:
PR Number
Synopsis
Category: EVO ARP related PRs
1776871
Functionality provided by arp/ndp publish argument doesn't work on all Junos OS Evolved platforms
Product-Group=evo
Functionality provided by publish argument for static arp and static ndp configuration is not working on all Junos OS Evolved platforms.
Resolved In:
evo:23.2R2-S1-EVO evo:23.4R1-S2-EVO evo:23.4R2-EVO evo:24.1R1-EVO evo:24.2R1-EVO
PR Number
Synopsis
Category: OFP related issues
1714333
Junos OS Evolved: Specific TCP traffic causes OFP core and restart of RE (CVE-2024-21612)
Product-Group=evo
An Improper Handling of Syntactically Invalid Structure vulnerability in Object Flooding Protocol (OFP) service of Juniper Networks Junos OS Evolved allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS). Please refer to https://supportportal.juniper.net/
JSA75753
[juniper.net]
for more information.
Resolved In:
evo:20.4R3-S9-EVO evo:20.4X6-EVO evo:21.2R3-S7-EVO evo:21.3R3-S5-EVO evo:21.4R3-S5-EVO evo:22.1R3-S4-EVO evo:22.2R3-S3-EVO evo:22.3R3-EVO evo:22.3X50-EVO evo:22.3X80-D39-EVO evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO evo:23.4R2-EVO evo:24.1R2-EVO evo:24.2R1-EVO evo:24.2R2-EVO junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.3R1
PR Number
Synopsis
Category: Issues related to evo operations - libevo infra, typeinfo ..
1711265
The rpd and rpd-agent crash are observed after the reboot of Master RE or Switchover
Product-Group=evo
On all Junos Evolved platforms with Dual Routing Engine(RE), if Master RE is rebooted or Switchover happens, the Multicast Composite Next Hop (MCNH) is deleted by the Routing Protocol daemon(rpd) of the new Master RE, which leads to a crash of rpd and rpd-agent and routing protocols are impacted, which could cause service impact.
Resolved In:
evo:22.2R3-S2-J8-EVO evo:22.2R3-S3-J1-EVO evo:22.3R3-EVO evo:22.3X50-EVO evo:22.3X80-D43-EVO evo:22.3X80-D44-EVO evo:22.4R3-EVO evo:23.1R1-S1-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:22.3R3 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.3R1
PR Number
Synopsis
Category: software upgrade infra issues
1699699
The commit changes will not take effect post software upgrade once the system is rebooted on Junos OS Evolved platforms
Product-Group=evo
On Junos OS Evolved Platforms, any UI (user interface) set (configuration, script, license) changes done post software addition were being lost after the subsequent reboot.
Resolved In:
evo:23.2R2-EVO evo:23.3R1-EVO junos:23.2R1 junos:23.2R2 junos:23.3R1 junos:24.3R1
PR Number
Synopsis
Category: Interface PRs defect & enhancement requests
1743461
Changing speed and adding to AE in the same commit fails
Product-Group=evo
On all Junos OS Evolved platforms, If the changing of the speed and the creation of the ae interfaces is in the same commit, the commit fails with "Interface aeX with child links of mixed speed but link-speed mixed is not configured".
Resolved In:
evo:21.4R3-S5-EVO evo:22.2R3-S3-EVO evo:22.3X50-EVO evo:22.3X80-D38-EVO evo:22.3X80-D39-EVO evo:22.4R2-S1-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.4R1-EVO
1762065
monitor interface or show interface does not display the interface description
Product-Group=evo
Enhancement in EVO platform for the command "monitor interface" and "show interface" include interface description
Resolved In:
evo:22.3R3-S3-EVO evo:23.2R2-S1-EVO evo:23.4R1-S2-EVO evo:23.4R2-EVO evo:24.1R1-EVO
PR Number
Synopsis
Category: EVO L2 Control Plane PRs
1769086
Data center interconnect configuration addition needs to be non-catastrophic.
Product-Group=evo
Adding interconnect configuration can be catastrophic behaviour which means BD (Bridge domain) and routing instance object will be deleted and added back, during this window there will be traffic drop.
Resolved In:
evo:21.4R3-S6-EVO evo:22.2R3-S3-EVO evo:22.4R3-EVO evo:22.4R3-S1-EVO evo:23.2R2-EVO evo:23.4R2-EVO evo:24.1R1-EVO junos:21.4R3-S6 junos:21.4R3-S7 junos:22.2R3-S4 junos:22.3R3-S2 junos:22.4R3 junos:22.4R3-S1 junos:22.4R3-S2 junos:23.2R2 junos:23.4R2 junos:24.1R1
1808779
L2ald-agent core and IRB ifl stays Hardware-down after deletion of irb(with virtual-gateway-address config) , readding same virtual-gateway-address as IRB address and move back to irb with same virtual-gateway-address
Product-Group=evo
l2ald-agent core and IRB ifl may stay in hardware-down state after following irb config changes which involves assigning VGA IP directly to IRB IFL, commit, delete the VGA from IRB IFL and add it as virtual-gateway-address again.
Resolved In:
evo:21.4R3-S8-EVO evo:22.4R3-S3-EVO evo:23.2R2-S2-EVO evo:23.4R2-EVO evo:24.2R1-EVO evo:24.2R2-EVO evo:24.3R1-EVO
PR Number
Synopsis
Category: EVO linux defects & enhancement requests
1750699
Observing routes missing in few scale VRF configuration after doing "Interface Flap"
Product-Group=evo
In scaled scenario (1 million BGP routes and 1000 VRF's), interface flap will impact relearning routes with few VRFs and the routes are missing. Clearing BGP neighbors should recover the issue. Issue is applicable to all EVO platforms.
Resolved In:
evo:22.3R3-S4-EVO evo:22.3X50-EVO evo:22.4R3-S3-EVO evo:23.2R2-S2-EVO
PR Number
Synopsis
Category: mgd, ddl, odl infra issues
1801505
When the value of the "firewall family inet filter fbf_v4_tc001 term t1 then routing-instance <>" is changed in the next commit, the subsequent commit can fail.
Product-Group=evo
When the value of the "firewall family inet filter fbf_v4_tc001 term t1 then routing-instance <>" is changed in a commit, later when the hierachy is deleted explicitly or by loading base-line config in the further commit, the commit fails with no appropriate error.
Resolved In:
evo:22.3X80-D45-EVO evo:23.4R2-EVO evo:24.3R1-EVO
PR Number
Synopsis
Category: SW PRs for MPC10E PMB
1731258
MPC10 and MPC11 line cards experiencing unexpected reboots
Product-Group=evo
Line cards such as MPC10 and MPC11 experience unexpected reboots because of CPU C-states which are enabled by default thus impacting the customer production traffic.
Resolved In:
evo:23.4R2-EVO evo:24.1R1-EVO junos:21.4R3-S7 junos:22.2R3-S4 junos:22.2R3-S5 junos:22.4R3 junos:22.4R3-S1 junos:22.4R3-S2 junos:23.2R2 junos:23.4R2 junos:24.1R1
PR Number
Synopsis
Category: Multiprotocol Label Switching
1698889
The rpd process will crash when rpd is restarted
Product-Group=evo
On all Junos and Junos OS Evolved platforms, when MPLS (Multiprotocol Label Switching) statistics is configured without LSP (Label-Switched Path) configuration, the rpd process will crash and impact the routing protocols. This leads to traffic disruption due to the loss of routing information.
Resolved In:
evo:22.3R3-EVO evo:22.3X50-EVO evo:22.3X80-D38-EVO evo:22.4R3-EVO evo:23.1R1-EVO evo:23.1R2-EVO evo:23.2R1-EVO junos:20.3X75-D43 junos:21.2R3-S6 junos:21.3R3-S5 junos:21.4R3-S5 junos:22.1R3-S3 junos:22.2R3-S1 junos:22.3R3 junos:22.4R2-S2 junos:22.4R3 junos:23.1R1 junos:23.1R2 junos:23.2R1
PR Number
Synopsis
Category: Resource Reservation Protocol
1706887
PathErr originated when next-hop lookup fails at a PLR post FRR may sometimes carry an incorrect error-origin
Product-Group=evo
On all Junos and Junos Evolved platforms, when next-hop lookup fails at a point of local repair (PLR) post fast-reroute (FRR), the PathErr that is originated should carry the incoming Traffic Engineering TE-link address as the error-origin. In certain circumstances when there is a next-hop change post FRR, the PathErr originated may end up carrying a different local address as the error-origin. This PathErr doesn't get acknowledged by the Previous Hop (PHOP) node, resulting in multiple retransmissions. In a scaled setup, this can potentially cause an unnecessary storm of PathErr messages. The fix involves introducing a new field in nhop_result_t to carry the error address. This is used when providing a custom error source address to routines that generate and send PathErr. This ensures that the PathErr doesn't inadvertently carry an irrelevant address as the error source.
Resolved In:
evo:22.3R3-EVO evo:22.3X50-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO junos:20.3X75-D43 junos:22.3R3 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.4R2
PR Number
Synopsis
Category: PTX10K specific platform PRs
1701983
The snmp mib walk jnxOperatingState on fan tray X returns running(2), although fan tray X speed is set to full-speed
Product-Group=evo
On all Junos Evolved platforms, snmp mib walk jnxOperatingState on Fan Tray X returns running(2), although fan tray X speed is set to full-speed. It is expected runningAtFullSpeed(5) when fan tray speed is set to full-speed.
Resolved In:
evo:21.4R3-S3-EVO evo:22.3R3-EVO evo:22.3X50-EVO evo:22.3X80-D38-EVO evo:22.3X80-D39-EVO evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:22.3R3 junos:23.1R2 junos:23.2R1 junos:23.3R1
1720259
System calls for shutdown after RE switchover
Product-Group=evo
When Routing Engine (RE) mastership switchover is performed, CoolingApp from the new backup Routing Engine might incorrectly interpret the temperature sensor reading and initiates a system shutdown request.
Resolved In:
evo:21.4R3-S2-J14-EVO evo:21.4R3-S4-J4-EVO evo:21.4R3-S4-J6-EVO evo:21.4R3-S5-EVO evo:22.3R3-EVO evo:22.3X50-EVO evo:22.3X80-D38-EVO evo:22.3X80-D39-EVO evo:22.4R2-J6-EVO evo:22.4R2-S1-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.4R1-EVO junos:22.4R3 junos:23.1R2 junos:23.2R2
PR Number
Synopsis
Category: Bug and Review Tracking for Segment routing traffic eng
1763406
LDP traffic to destination route might be lost when TI-LFA is configured
Product-Group=evo
On all Junos and Junos OS Evolved platforms, when LDP tunnel over SR-TE route or over RSVP and LFA/rLFA/TI-LFA backup path for the same destination is configured, or if rLFA/LFA with L-ISIS as backup path is configured, the route to the destination is missing. LDP route for the destination is deleted because SR-TE LSP next hop is deleted by processing L-ISIS route with the backup path. Due to this LDP route gets deleted, LDP traffic to destination route is lost.
Resolved In:
evo:21.4R3-S6-EVO evo:22.1R3-S5-EVO evo:22.3R3-S2-EVO evo:22.4R3-EVO evo:23.2R2-EVO evo:23.4R1-EVO evo:23.4R2-EVO evo:24.1R1-EVO junos:21.4R3-S6 junos:22.1R3-S5 junos:22.3R3-S2 junos:22.4R3 junos:23.2R2 junos:23.4R1 junos:23.4R2 junos:24.1R1
PR Number
Synopsis
Category: UI Infrastructure - mgd, DAX API, DDL/ODL
1770643
RPD core seen when groups is activated before corresponding 'apply-groups' in configuration
Product-Group=evo
On all Junos and Junos Evolved platforms, when the group is activated after the corresponding 'apply-groups' statement configuration, rpd core is seen.
Resolved In:
evo:21.2R3-S8-EVO evo:21.4R3-S8-EVO evo:22.2R3-S3-EVO evo:22.2X100-D20-EVO evo:22.3R3-S3-EVO evo:22.3X50-EVO evo:22.3X80-D43-EVO evo:22.3X80-D44-EVO evo:22.4R3-S1-EVO evo:23.2R2-EVO evo:23.4R2-EVO evo:24.1R1-EVO junos:21.2R3-S8 junos:21.2X32-D30 junos:21.4R3-S8 junos:22.2R3-S4 junos:22.3R3-S3 junos:22.4R3-S1 junos:22.4R3-S2 junos:23.2R2 junos:23.4R1-S1 junos:23.4R2 junos:24.1R1
PR Number
Synopsis
Category: Express ZX PFE L3 Features
1711964
The vmcore is observed during the system shutdown
Product-Group=evo
Resolved In:
evo:22.3R3-EVO evo:22.3R3-S3-EVO evo:22.3X50-EVO evo:22.4R2-EVO evo:23.1R1-EVO evo:23.1R2-EVO evo:23.2R1-EVO junos:22.3R3 junos:22.4R2 junos:23.1R2 junos:23.2R1
1732283
Junos OS Evolved: PTX10003 Series: MAC address validation bypass vulnerability (CVE-2023-44189)
Product-Group=evo
An Origin Validation vulnerability in MAC address validation of Juniper Networks Junos OS Evolved on PTX10003 Series allows a network-adjacent attacker to bypass MAC address checking, allowing MAC addresses not intended to reach the adjacent LAN to be forwarded to the downstream network. Due to this issue, the router will start forwarding traffic if a valid route is present in forwarding-table, causing a loop and congestion in the downstream layer-2 domain connected to the device.Please refer to https://supportportal.juniper.net/
JSA73153
[juniper.net]
for more information.
Resolved In:
evo:21.4R3-S4-EVO evo:21.4X1-EVO evo:22.1R3-S3-EVO evo:22.3R2-S2-EVO evo:22.3R3-S1-EVO evo:22.3X50-EVO evo:22.3X80-D35-EVO evo:22.4R2-S1-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.2R2-EVO evo:23.3R1-EVO junos:22.3R2-S2 junos:22.3R3-S1 junos:22.4R2-S1 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.2R1-S1 junos:23.2R2 junos:23.3R1
22.2R3-S4-EVO: Software Release Notification