Alert Type

PSN - Product Support Notification
Low/NotificationSoftware Release Notification
Low/NotificationSoftware Release Notification

Product Affected

ACX PTX QFX series running Junos Evolved Software

Alert Description

Junos Software Service Release version 22.2R3-S6-EVO is now available for download from the Junos software download site

Download Junos Software Service Release:

  1. Go to Junos Platforms - Download Software page
  2. Input your product in the "Find a Product" search box
  3. From the Type/OS drop-down menu, select Junos SR
  4. From the Version drop-down menu, select your version
  5. Click the Software tab
  6. Select the Install Package as need and follow the prompts

NOTE: Starting on August 30th, 2024, we include PR's severity with each entry. See KB86335 [juniper.net] for the definition of PR's Severity

Solution

Junos Software service Release version 22.2R3-S6-EVO is now available.

22.2R3-S6-EVO - List of Fixed issues 

PR NumberSynopsisCategory: Border Gateway Protocol
1838490
Minor		BGP_PREFIX_THRESH_EXCEEDED warning message keeps flooding after accepted max prefix limit is reached
Product-Group=evo
Severity=Minor		With this PR fix, BGP_PREFIX_THRESH_EXCEEDED warning message will be stopped after the max prefix limit is reached. The behavior is consitent with prefix-limit feature.
PR NumberSynopsisCategory: PFE L2 forwarding features on BT based platforms
1777003
Major		PTX10001-36MR: epp_epc_intr_shmem_err seen in logs
Product-Group=evo
Severity=Major		On a BT-base PTX platform, you may see the "epp_epc_intr_shmem_err" in its Syslog when a vlan id is missing from an interface.
PR NumberSynopsisCategory: Express BT PFE L3 Features
1856732
Major		Post configuration changes on an AE interface MPLS traffic is discarded for other interfaces/AE interface on a different FPC
Product-Group=evo
Severity=Major		On Junos Evolved PTX10008, PTX10016, PTX10004 platforms having JNP10K-LC1201/LC1202 and multiple FPCs (Flexible PIC (Physical Interface Cards) Concentrators), it is observed that when any of the following configuration changes are performed on a given AE (Aggregate Ethernet) interface, this may cause MPLS (Multiprotocol Label Switching) traffic to be dropped on other interfaces or AE interfaces hosted on other FPCs having the same PIC and port number as the intended AE interface members where no such configuration change is made.* When family MPLS is removed from an AE interface, or* When an AE interface with family MPLS configured is deactivated, or* When the IFD (Interface Device) MTU (Maximum Transmission Unit) is modified on the AE interface that has family MPLS configured, or* When "vlan-tagging" is added or removed on an AE interface that has family MPLS configured, or* When "encapsulation" is added or removed on an AE interface that has family MPLS configured PTX10003, PTX10001-36, PTX10002-36QDD are not exposed.MPLS Traffic drops are recorded as 'normal discard' under "show pfe statistics traffic"
PR NumberSynopsisCategory: Class of Service
1836528
Minor		FC id goes out of sync between the RE and PFE impacting all CoS features using FC id
Product-Group=evo
Severity=Minor		On all Junos and Junos Evolved Platform, forwarding-class (FC) identifier (id) goes out of sync between the Routing Engine (RE) and Packet Forwarding Engine (PFE) when software upgrade is performed. When In Service Software Upgrade (ISSU) is performed, FC id goes out of sync between the RE and PFE impacting all class-of-service (CoS) features using FC id. When manual software upgrade is performed (without using ISSU) , this issue will be seen as a cosmetic display issue where the order in which the FC configurations are displayed will differ.
PR NumberSynopsisCategory: Issues related to debug utilties - objmon, objshell/Dashboard
1838074
Major		Serial Console Stops Working After Cable Reconnection
Product-Group=evo
Severity=Major		On Junos OS Evolved platforms, the serial console may stop functioning, displaying a blank output, after one or more physical disconnections and reconnections of the console cable. The use of intermediate cable adapters or unreliable cables can exacerbate this issue.
PR NumberSynopsisCategory: EVO L2 Control Plane PRs
1710951
Major		[22.4R2]EVPN:qfx5130: Bridged Overlay : some mac addresses are not learnt when "forwarding-profile host-profile" is not configured
Product-Group=evo
Severity=Major		For bridged Overlay, some mac addresses are not learnt when "forwarding-profile host-profile" is not configured
1844623
Major		Stale MAC-IP entries are not cleared in an EVPN-VXLAN scenario when encapsulate-inner-vlan or decapsulate-accept-inner-vlan or both knobs are present
Product-Group=evo
Severity=Major		On all Junos and Junos OS Evolved platforms, when decapsulate-accept-inner-vlan or encapsulate-inner-vlan or both knobs are configured for a VXLAN (Virtual Extensible Local Area Network) and when any action corresponding to MAC-IP entries cleanup takes place, the MAC-IP entries will not be cleaned up from kernel. This will result in anomalies in device and could also lead to a core crash.
PR NumberSynopsisCategory: event/op/commit scripts, SLAX, netconf issues
1836806
Major		Rest API service will not launch on EVO devices when the server address is configured as any interface IP (excluding management interface IP).
Product-Group=evo
Severity=Major		Rest API service will not launch on EVO devices when the server address is configured as any interface IP (excluding management interface IP).
PR NumberSynopsisCategory: mgd, ddl, odl infra issues
1625937
Minor		Configuration archive transfer does not happen via FTP
Product-Group=evo
Severity=Minor		On Junos EVO platforms, configuration archival (transfer-on-commit) over FTP protocol not working.
PR NumberSynopsisCategory: EVPN control plane issues
1839959
Critical		The MAC+IP table and mac-table are not in sync in the EVPN-MPLS active-active multihomed scenario leading to traffic loss
Product-Group=evo
Severity=Critical		On all Junos and Junos OS Evolved platforms that supports ESI lag interface and in an EVPN-MPLS (Ethernet Virtual Private Network - Multi Protocol Label Switching) active-active multihomed scenario, when the multihomed access interfaces are flapped in quick succession, it results in an unresolved destination route for the specific IP host. This is occurred due to race condition within l2ald (Layer 2 Address learning daemon) followed by an interface flap which causes the locally learned MAC to go missing from the mac-table on the other PE router.
PR NumberSynopsisCategory: MX Inline Jflow
1813925
Major		FPC reboots after sensor configuration is removed and readded over a long period on MX and EX9200-15C platforms
Product-Group=evo
Severity=Major		On all MX platforms with MPC10/MPC11/LC9600, MX304 and EX9200-15C platforms, when any sensor configuration on protocols, for example, MPLS LSP, is configured and removed over a long period, the aftd-trio process starts a memory leak and eventually causes FPC to reboot.
PR NumberSynopsisCategory: RPD Interfaces related issues
1795659
Minor		"JTASK_NO_SOCKACCEPT: Process events: no read/accept method for MGMT socket -1" logs may be seen in the messages file or an external syslog server
Product-Group=evo
Severity=Minor		"JTASK_NO_SOCKACCEPT: Process events: no read/accept method for MGMT socket -1" logs may be seen in the messages file or an external syslog server
PR NumberSynopsisCategory: KRT Queue issues within RPD
1817807
Major		Routes for secure tunnel interface interface not installed on forwarding-table on SRX platforms
Product-Group=evo
Severity=Major		On all SRX platforms, after the In-Band Cluster (ICU) upgrade if the system has routes pointing to the secure tunnel interface (st0) interface, or on clearing security IPsec sa on peer router a few routes might have trouble getting installed in forwarding, impacting traffic on the routes that are not installed after the upgrade.
1834859
Major		The RPD crashes after executing "show krt error-statistics errorno X"
Product-Group=evo
Severity=Major		Please do not issue the "show krt error-statistics errorno ..." stanza. This command causes RPD to restart unexpectedly.
PR NumberSynopsisCategory: SNMP Infrastructure (snmpd, mib2d)
1734549
Major		Syslog messages modification for SNMPv3 authentication failure
Product-Group=evo
Severity=Major		On all Junos and Junos Evolved platforms, the syslog message for a wrong auth/privacy and password has been changed to include more information.
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1784818
Major		The non-root user will not be able to copy files
Product-Group=evo
Severity=Major		On all Junos and Junos Evolved platforms, when logged in as a non-root user and trying to copy a file from a remote location, it shows as cannot become non-root username although logged in as a non-root user and an error message is thrown.
1799215
Major		The commit fails error can be seen when configuration is modified after commit prepare
Product-Group=evo
Severity=Major		On all Junos and Junos Evolved platforms, when the user attempts to issue the commit command after modifying the configuration post 'commit prepare', the commit discards the prepared commit cache as it is no longer valid and throws " commit fails" error and proceeds with the regular commit process from scratch.
1799277
Major		The mgd crash is seen on aggregation device and upgrade is halted during upgrade to aggregated satellite switches
Product-Group=evo
Severity=Major		The satellite package is not conforming to the expected junos version format leading to the problem reported. The code which parses this version string has been modified to handle such format incompatibility gracefully.
1842518
Major		The device become unresponsive in a race condition due to maximum process (maxproc) limit
Product-Group=evo
Severity=Major		On all Junos/Junos OS Evolved platforms, the device becomes unresponsive due to management (mgd) processes being stuck in a deadlock. This leads to the piling up of mgd processes, which eventually exhausts the maximum process limit (maxproc) on the device. The impact is that the device will become unusable due to the maxproc limit being reached.
PR NumberSynopsisCategory: Issues related to NETCONF
1792362
Major		RPC request for file copy with routing instances is failing
Product-Group=evo
Severity=Major		On Junos OS and Junos OS Evolved platforms configured with routing instances, RPC (Remote Procedure Call) request for file copy using routing instance fails. There is no service/traffic impact due to this issue.
1796297
Major		Error message not prompted on commit confirmed RPC sent in private mode on all Junos and Junos Evolved platforms
Product-Group=evo
Severity=Major		On all Junos and Junos Evolved platforms, commit confirmed command executed with remote procedure call (RPC) in private configuration mode is being allowed where ideally it should not be.
1831167
Major		Netconf over ssh stop working with "sshd[]: fatal: /etc/ssh/netconf_config line 10: Directive 'Ciphers' is not allowed within a Match block" error
Product-Group=evo
Severity=Major		Day-1 issue affecting all EVO platforms, in some rare conditions, when adding Netconf and SSH cipher configuration or performing a "commit full" (with NETCONF and SSH ciphers config present ) or "load override" (with NETCONF and SSH ciphers config present ) may cause Netconf connections over SSH to fail with the following error message: "sshd[]: fatal: /etc/ssh/netconf_config line 10: Directive 'Ciphers' is not allowed within a Match block"
PR NumberSynopsisCategory: ACX724 timing issues
1833150
Major		Object anomalies seen post deactivate/delete of PTP configurations.
Product-Group=evo
Severity=Major		Object anomalies seen post deactivate/delete of PTP configurations.

 

 

22.2R3-S6-EVO - List of Known issues 

PR NumberSynopsisCategory: MX YT-ZF Linecards Interface Software Category
1846164
Major		Continuous logging of alarms during a fiber cut with transport devices
Product-Group=evo		In a scenario where a fiber link has transport devices to amplify the signal, excessive logging of alarms for an interface can occur. The transport devices will amplify the incoming signal, which isn't valid when the fiber has been cut. This causes the router to receive a good signal and Rx power but it contains no valid data. In response, the interface on the router will attempt to link up repeatedly and after failing multiple retries, which is set per platform, the router will attempt to reinitialize the data path. This causes multiple alarms from the optic to get set and then cleared resulting in alarm logs in the system logs. This can become excessive if the link remains down for an extended period of time. To avoid continuous logging to the system log, after a number of retries the logs will be suppressed. The interface will continue to attempt to link up including reinitializing the the data path, but without the logging. This will allow the interface to link up when the physical link is repaired, and at that point the logs will stop being suppressed

Resolved In: evo:23.2R2-S4-EVO evo:23.4R2-S4-EVO evo:24.2R2-EVO evo:24.4R2-EVO evo:25.1R1-EVO evo:25.2R1-EVO junos:23.4R2-S4 junos:24.2R2 junos:24.4R2 junos:25.1R1 junos:25.2R1
PR NumberSynopsisCategory: Border Gateway Protocol
1793435
Major		Route learning process degrades when multipath is enabled
Product-Group=evo		BGP (Border Gateway Protocol) route learning rate shows degradation even if the BGP next hop trace option is disabled.

Resolved In: evo:22.3R3-S3-EVO evo:22.3X50-EVO evo:22.3X80-D43-EVO evo:22.3X80-D44-EVO evo:23.2R2-EVO evo:23.4R2-EVO evo:24.2R1-EVO evo:24.3R1-EVO junos:22.3R3-S3 junos:22.4R3-S3 junos:23.2R2 junos:23.2R2-J14 junos:23.4R2 junos:24.2R1 junos:24.3R1 junos:24.4R1
PR NumberSynopsisCategory: Track PRs in BGP BMP area & is part of BGP inside RPD.
1713444
Major		The rpd process may crash when BMP socket write fails or blocks.
Product-Group=evo		On all Junos and Junos Evolved platforms, the rpd process may crash when BGP Monitoring Protocol (BMP) socket write fails or blocks. This is a special case in BMP operation but can be common for a large scale network. This may cause rpd to restart and affect routing protocols.

Resolved In: evo:21.4X1-EVO evo:22.3X80-D38-EVO evo:22.3X80-D39-EVO junos:21.2R3-S6 junos:21.2R3-S9 junos:21.4R3-S4 junos:22.1R3-S3 junos:22.2R3-S2 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.3R1
PR NumberSynopsisCategory: EVO VXLAN PFE for BCM XGS Platforms
1744725
Major		E/V fabric - local bias/split horizon filter not installed in PFE
Product-Group=evo		Due to the split-horizon filter mis-programming (or lack thereof), BUM packets can loop around between ESI LAG peers, sending multiple copies down to the host.

Resolved In: evo:22.2R3-S1-J3-EVO evo:22.2R3-S1-J4-EVO evo:22.4R3-EVO evo:23.1R2-EVO
PR NumberSynopsisCategory: Issues related to evo operations - libevo infra, typeinfo ..
1711265
Major		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.2R3-S4-J3-EVO evo:22.2R3-S5-J10-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 evo:24.2R2-EVO junos:22.3R3 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.3R1
PR NumberSynopsisCategory: System Management daemon and related issues
1788276
Major		Memory utilisation monitoring shows cycles of high and low usage
Product-Group=evo		The disk manager clean up logs when the memory usage reaches 85%. This shows very high and sudden low memory usage in devices, which causes concern for customers.

Resolved In: 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.4R1-S1-EVO evo:23.4R2-EVO evo:24.1R1-EVO evo:24.2R1-EVO
PR NumberSynopsisCategory: All Guardian (ACX7509) Platform related issues
1671198
Major		vmcore on new backup RE after switchover due to master FEB power fault
Product-Group=evo		In a Junos Evolved ACX7509 system with dual RE and FEB, when there is a power fault of master FEB, a switchover should happen and backup RE and FEB will take up mastership. Post switchover a VMCore may be generated in the new Backup RE. This failure should not impact the system uptime. Post Vmcore backup RE will reboot and come back online.

Resolved In:
PR NumberSynopsisCategory: Issues related to Junos licensing infrastructure
1751384
Major		License is missing on device on performing upgrade
Product-Group=evo		On all Junos Evolved platforms, under rare scenario, it is seen that license file gets removed on performing upgrade.

Resolved In: evo:21.4R3-S5-EVO evo:22.3X50-EVO evo:22.3X80-D38-EVO evo:22.3X80-D39-EVO evo:22.4R3-EVO evo:23.3R2-EVO evo:23.4R1-EVO evo:24.1R1-EVO junos:23.2R2 junos:23.3R2 junos:23.4R1 junos:24.1R1
PR NumberSynopsisCategory: Multiprotocol Label Switching
1698889
Major		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 NumberSynopsisCategory: Resource Reservation Protocol
1819948
Major		LSP re-optimization issue has been observed
Product-Group=evo		On all Junos and Junos Evolved platforms, the LSP (Label Switched Path) re-optimization issue has been observed. LSP bandwidth change is unsuccessful due to bandwidth unavailable RSVP (Resource Reservation Protocol) PathErr.

Resolved In: evo:22.4R3-S5-EVO evo:23.4R2-S4-EVO evo:24.2R2-EVO evo:24.3R1-EVO evo:24.4R1-EVO junos:20.3X75-D441 junos:20.3X75-D46 junos:21.4R3-S10 junos:22.4R3-S5 junos:23.4R2-S4 junos:24.2R2 junos:24.3R1 junos:24.4R1
PR NumberSynopsisCategory: PTX10K specific platform PRs
1711595
Major		On PTX platform running JUNOS-EVO ungraceful restart of FPC may lead to PFEs on other FPCs to be disabled due to fatal error
Product-Group=evo		On PTX platform running JUNOS-EVO ungraceful restart of FPC may lead to PFEs on other FPCs to be disabled due to fatal error.

Resolved In: evo:22.3R2-S1-EVO evo:22.3R3-EVO evo:22.3X50-EVO evo:22.3X80-D40-EVO evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R1-S1-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.2R2-EVO evo:23.3R1-EVO junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
PR NumberSynopsisCategory: Issues related to control plane security
1719603
Critical		EVO devices may lose remote access in certain scenarios
Product-Group=evo		In Junos OS Evolved, the xinetd config file was not updated correctly. This could lead to a situation where external login services (such as SSH, NETCONF over SSH, or Telnet) were not accessible. Due to a software defect, an internal function deleted the files required for SSH based services, eg "xinetd-external.conf". Thus services like SSH or Netconf will stop working In some cases when a box was booting, the "xinetd-external.service" came up before the initial boot-time MGD commit would create the file. This caused the service to come up without a config file. Since remote login over may be disabled: SSH Telnet NETCONF over SSH NETCONF over TLS so you may need to log in via the serial console. Following error will be observed in the system: xinetd[6588]: open( /etc/xinetd-external.conf ) failed: No such file or directory (errno = 2) xinetd[6588]: 6588 {init_services} couldn't get configuration. Exiting... xinetd[7537]: xinetd Version 2.3.15 started with libwrap options compiled in. xinetd[7537]: Started working: 2 available services

Resolved In: evo:20.4X6-EVO evo:21.2R3-S5-EVO evo:21.3R3-S5-EVO evo:21.4R3-S4-EVO evo:21.4X1-EVO evo:22.2R3-S1-EVO evo:22.3R2-S2-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.4R2-S1-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.2R1-S1-EVO evo:23.3R1-EVO evo:23.4R1-EVO evo:24.1R1-EVO junos:22.3R3 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.3R1
PR NumberSynopsisCategory: Configuration mgmt, ffp, load-action, commit processing
1818692
Major		Configuration commit fails due to mustd process crash
Product-Group=evo		Core dumps in mustd seen commiting a change to a large prefix-list used by BGP

Resolved In: evo:22.3R3-S4-EVO evo:22.3X50-EVO evo:22.3X80-D47-EVO evo:22.3X80-D49-EVO evo:22.4R3-S5-EVO evo:23.2R2-S3-EVO evo:23.4R2-S3-EVO evo:23.4X100-D20-EVO evo:24.2R2-EVO evo:24.4R1-EVO junos:21.2R3-S9 junos:21.2X32-D30 junos:21.4R3-S9 junos:22.2R3-S5 junos:22.3R3-S4 junos:22.4R3-S5 junos:23.2R2-S3 junos:23.4R2-S3 junos:24.2R1-S1 junos:24.2R2 junos:24.4R1
PR NumberSynopsisCategory: Issues related to NETCONF
1819656
Major		In all Junos and Junos OS Evolved platforms, with Multinode High Availability configured, node configuration on primary might differ from backup due to configuration synchronization failure at the time of commit
Product-Group=evo		In all Junos and Junos OS Evolved platforms with MNHA (Multinode High Availability) supported and "set system commit peers-synchronize" is configured in a local primary node of the HA, when the "commit" command is issued, a synchronization warning message is displayed informing that session to peer (backup) has failed and configuration is committed only in the local primary device. Under the same configuration, if the command "commit peers-synchronize" is used instead of "commit", then the synchronization error will cause the configuration to not be committed on any of the high availability nodes. This issue does not affect network services. The synchronization error is caused by a TACACS authentication failure when primary node attempts to access the secondary backup node.

Resolved In: evo:21.4R3-S9-EVO evo:22.3R3-S4-EVO evo:22.3X50-EVO evo:22.4R0-J0-EVO evo:23.2R2-S2-EVO evo:23.4R2-S3-EVO evo:23.4X100-D20-EVO evo:24.2R2-EVO evo:24.3R1-EVO evo:24.4R1-EVO junos:21.4R3-S9 junos:22.2R3-S5 junos:22.3R3-S4 junos:22.4R3-S4 junos:22.4R3-S5 junos:23.2R2-S3 junos:23.4R2-S3 junos:24.2R1-S1 junos:24.2R2 junos:24.4R1
PR NumberSynopsisCategory: Issues related to YANG Data Models
1725934
Major		ODL controller is throwing unavailable capabilities error for few of the Openconfig Yang modules
Product-Group=evo		ODL controller is throwing unavailable capabilities error for few of the Openconfig Yang modules

Resolved In: evo:22.3X50-EVO evo:22.4R3-EVO evo:23.2R1-EVO evo:23.3R1-EVO evo:23.4R1-EVO evo:24.1R1-EVO evo:24.2R1-EVO junos:21.4R3-S6 junos:22.2R3-S6 junos:23.2R2

 

Modification History

First publication 2025-03-06