Alert Type

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

Product Affected

ACX PTX QFX running Junos Evolved software

Alert Description

Junos Software Service Release version 22.2R2-S2-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

Solution

Junos Software service Release version 22.2R2-S2-EVO is now available.

22.2R2-S2-EVO - List of Fixed issues

PR NumberSynopsisCategory: Issues related to Junos licensing infrastructure
1685433license-check might core dump on MX routers
Product-Group=evo		An intermittent license check daemon core dump might happen. The license service will auto restart and recover.
PR NumberSynopsisCategory: RPD Next-hop issues including indirect, CNH, and MCNH
1698516On Junos platforms MPLS resolving over IPV6 route traffic drop is seen
Product-Group=evo		On Junos platforms error messages seen with traffic drops on labelled route present in mpls.0 resolving over a IPV6 prefix.
PR NumberSynopsisCategory: Configuration management, ffp, load action
1671112Test 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.
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1679413Configuration 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.
1699245The mgd process might crash during commit synchronize
Product-Group=evo		On all Junos OS and Evolved OS platforms with dual RE (Routing Engine) during commit script synchronize, backup RE mgd get crash once the memory leak reaches to 65K due to which commit configuration will fail which are performed through Master RE.
 
 

22.2R2-S2-EVO - List of Known issues

PR NumberSynopsisCategory: software upgrade infra issues
1699699The 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:
PR NumberSynopsisCategory: Express PFE FW Features
1709204Lo0 filter change might trigger parity error, when filter is changed from ISF to Non ISF or vice versa
Product-Group=evo		Lo0 filter change might trigger parity error, when filter is changed from ISF to Non ISF or vice versa

Resolved In:
PR NumberSynopsisCategory: Platform infra to support jvision
1683559Picd coredump is seen on Junos Evolved platforms
Product-Group=evo		On Junos Evolved platforms, Picd coredump is seen when the netconf notification is enabled with the config system services netconf notification. This config should be disabled to avoid this picd core.

Resolved In: evo:22.1R3-EVO evo:22.2R3-EVO evo:22.3R2-EVO junos:22.1R3 junos:22.2R2 junos:22.2R3 junos:22.3R1 junos:22.3R2 junos:22.4R1
PR NumberSynopsisCategory: QFX5K EVO Platform Interface
1680009400G DAC link not coming up Broadcom shell shows as speed as 12.4G instead of 400g
Product-Group=evo		The links are not coming up between two TD4 devices when Auto-negotiation is enabled for DAC cables. We are following up on this issue with the vendor(BCM). Available Work-around for this issue is to configure the below-set cli command on both sides of the links. set interfaces ether-options no-auto-negotiation Thanks.

Resolved In: evo:22.4R2-EVO evo:23.1R1-EVO
 

Modification History

First publication 2023-02-13