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.1R3-S2-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.1R3-S2-EVO is now available.
22.1R3-S2-EVO - List of Fixed issues
PR Number
Synopsis
Category: EX2300/3400 platform
1695057
The l2cpd telemetry crash would be observed when the LLDP Netconf notification from external controllers along with Netconf services configuration is present on the device
Product-Group=evo
On all Junos and Junos Evolved platforms, configuring Link Layer Discovery Protocol (LLDP) with "system services netconf notification" enabled will trigger the l2cpd crash. This crash causes the CPU to spike.
PR Number
Synopsis
Category: Border Gateway Protocol
1695062
Traffic blackholing is observed when removing the BGP routes take a long time to get removed from RIB
Product-Group=evo
On Junos platforms, if a BGP (Border Gateway Protocol) peer is going down and stays down and the system might take an extremely long time to complete removing the BGP routes. The issue observed when a BGP peer sends many routes, only a small amount of routes are selected as the active routes in the RIB (Routing Information Base), and if the BGP delete job gets only a small part of the CPU time as other work in the routing process utilize the CPU.
PR Number
Synopsis
Category: Gnats category for dynamic rendering infrastructure
1698192
EVO jkey path changed under protocol/isis. "isis/levels" is missing
Product-Group=evo
When using the proprietary subscribe RPC for telemetry, the "isis/levels" keyword is missing from the jkey output for leaf lists.
PR Number
Synopsis
Category: PRs related to software Agentd daemon on EVO
1697986
The agentd process crash might crash in a telemetry scenario
Product-Group=evo
On all Junos Evolved platforms, the agentd process will crash when the telemetry sensor name is greater than 64 characters. The crash will only impact RPD related telemetry services.
PR Number
Synopsis
Category: EVO L2 Control Plane PRs
1703226
The l2ld process will crash when an IFL is changed to trunk mode and a new VLAN is added
Product-Group=evo
On all Junos Evolved platforms, the Layer 2 address learning daemon (l2ald) process will crash when there is a scaled configuration to commit and a Logical Interface (IFL) mode is changed from access to the trunk and a new Virtual Local Area Network (VLAN) is added to the IFL in a single commit. This issue will impact new MAC learning until the l2ald process recovers.
1713640
On PTX10001-36MR the VXLAN tunnel termination functionality impacted with global configuration not enabled
Product-Group=evo
On Junos Evolved PTX10001-36MR platform, the VXLAN(Virtual Extensible LAN) tunnel termination functionality will be impacted when configuration is not enabled for tunnel termination. As the tunnel will not get terminated this will impact the packet forwarding process.
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: EVPN Layer-2 Forwarding
1712259
The Anycast Gateway stretched across 2 DCs over the seamless MPLS stitching DCI does not have Anycast Gateway MAC information coming from the remote DC when VLAN and VNI ids are different
Product-Group=evo
On all Junos and Junos OS Evolved platforms, the AnyCast Gateway stretched across 2 Data Centres (DC) over the Data Centre Interconnect (DCI) using seamless Multiprotocol Label Switching (MPLS) stitching through Interconnect knob and having different VLAN and Virtual Network Identifier (VNI) ids (e.g., VLAN ID 101 <-- -> VNI 1101), then upon deactivating the Integrated Routing and Bridging (IRB) interface on all the gateways within DC, the AnyCast Gateway MAC information coming from Interconnect-Ethernet Segment Identifier (I-ESI) will not be available in the bridge mac-table and thus, the Inter VLAN/VNI routing will be impacted.
22.1R3-S2-EVO - List of Known issues
PR Number
Synopsis
Category: L2NG RTG feature
1715518
Traffic loss is seen on RTG bound interface
Product-Group=evo
On all Junos and Junos OS Evolved platforms, configuring mac-move with action shutdown can disable the RTG (Redundant Trunk Groups) interface leading to traffic loss bound to that interface.
Resolved In:
evo:22.2R3-EVO evo:22.3R3-EVO evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:21.4R3-S3 junos:22.1R3-S2 junos:22.2R3 junos:22.3R2-S1 junos:22.3R3 junos:22.4R1-S2 junos:22.4R2 junos:22.4R3 junos:23.1R1 junos:23.1R2 junos:23.2R1
PR Number
Synopsis
Category: Gnats category for dynamic rendering infrastructure
1706708
evo-aftmand-zx not responding, ping, arp not working after unsubscribing some telemetry sensors.
Product-Group=evo
After unsubscribing certain telemetry sensors, evo-aftmand-zx becomes unresponsive due to a deadlock problem.
Resolved In:
evo:22.2R3-EVO evo:22.3R2-EVO evo:22.3X80-D32-EVO evo:22.4R2-EVO evo:23.1R2-EVO evo:23.2R1-EVO junos:22.1R3-S2 junos:22.3R3 junos:22.4R1-S2 junos:23.2R1
PR Number
Synopsis
Category: UI Infrastructure - mgd, DAX API, DDL/ODL
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.1R3-S5 junos:21.2R3-S4 junos:21.2X32-D20 junos:21.3R3-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 junos:23.2R1
1708321
MX960 :: CST:RE goes to amnesiac state, when rebooting the DUT -mgd: error: translation script failure
Product-Group=evo
When a toggle attribute with variable is committed under dynamic-profiles hierarchy, upon reboot system will go to amnesiac mode
Resolved In:
evo:21.4R3-S3-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.3R3-EVO evo:22.4R2-EVO evo:23.1R1-EVO evo:23.1R2-EVO evo:23.2R1-EVO junos:21.4R3-S3 junos:22.1R3-S2 junos:22.2R2-S2 junos:22.2R3 junos:22.3R2 junos:22.3R3 junos:22.4R1-S2 junos:22.4R2 junos:23.1R1 junos:23.1R2 junos:23.2R1
PR Number
Synopsis
Category: Issues related to NETCONF
1585855
< ok/> response is getting generated along with < rpc-error>
Product-Group=evo
When maximum-password-length is configured and user tries to configure password whose length exceeds configured maximum-password-length, error is thrown, along with error '' tag is also emitted. (Ideally '' tag should not be emitted in an error scenario.) The configuration does not get committed.
Resolved In:
evo:23.1R1-EVO evo:23.2R1-EVO junos:23.1R1 junos:23.2R1
Modification History
First publication 2023-03-29
22.1R3-S2-EVO: Software Release Notification for JUNOS Evolved Software