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.1R1-S1-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.1R1-S1-EVO is now available.

22.1R1-S1-EVO - List of Fixed issues

PR NumberSynopsisCategory: Track PRs in BGP BMP area & is part of BGP inside RPD.
1653130The rpd might crash when BMP rib-out monitoring is configured for flow-spec route
Product-Group=evo		On all Junos and Evolved platforms, rpd crash might be seen when BGP monitoring protocol (BMP) rib-out monitoring is configured for the flow-spec route. Since there is no next-hop for flow-spec route core might be seen while generating rib-out feed. Traffic loss might be seen due to this crash.
PR NumberSynopsisCategory: QFX52xx platforms Interface running EVO
1641583FEC Corrected Errors which are cleared with clear statistics command show up as huge value after ISSU
Product-Group=evo		If FEC errors are present on the interface and the errors are cleared using the Clear statistics cli command and subsequently ISSU is performed, then the FEC error counters show up negative or huge value. Subsequently if the FEC errors surpass the previous value, then The counters will appear non-negative (smaller value).
PR NumberSynopsisCategory: Express BT PFE L3 Features
1651932An error might be seen when the member link on an AE bundle is deleted
Product-Group=evo		On all EVO PTX platforms, gRPC connection between the "evo-aftmand" process and the "cda" process maybe disconnect with the messages "[Error] CDA: exprGrpcAsyncApi: failed cq read", and "GOAWAY with error code ENHANCE_YOUR_CALM". When the disconnection happens, the Junos Evolved system can no longer retrieve status or programs forwarding ASICs. This is a catastrophic failure.
PR NumberSynopsisCategory: EVO Netstack FIB Service Daemon
1653182QFX5220: Change in the output for L3VPN.inet6 route table in "show route forwarding-table summary | display xml" command
Product-Group=evo		For release 22.1R1 only - if routes are installed on an interface and the interface flaps, the summary count for the given routes will not update from the 'ifdn' or 'iddn' states and the "show route forwarding-table summary" command will report stale summary count data. There is no routing or route state functional impact, only the summary display is impacted by this issue.
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1627323Junos Fusion Satellite EX4300 upgrade fails from MX104
Product-Group=evo		Junos Fusion Satelite EX4300 upgrade is performed from MX104 as AD with dual REs. The upgrade may get stuck and not responding.
1643209Commit fails with message "statement does not match patch" due to TOD mismatches between Primary RE and Backup RE
Product-Group=evo		When time-zone for the router is set as EST5EDT and if the TOD (Time-Of-Day) values under "event-options generate-events" are modified in different time zones, that is TOD configurations created on EST time zones are getting modified in EDT time zone, then it can cause commit failures. When such commits happens at different time-zones, internally, it generates a patch file and tries to load the patch at both RE. But due to different time zone, it is not getting excepted by backup RE.
 
 

22.1R1-S1-EVO - List of Known issues

PR NumberSynopsisCategory: PFE COS features on BT based platforms
1656837wrong transmit HW priority for CLI "priority medium-low"
Product-Group=evo		Problem Statement: In PTX10000-36MR, PTX10008, PTX100016, PTX10004, with dual priority scheduler configured, Junos scheduler Priority "medium-low" was wrongly mapped to ASIC priority "low" Ideally, Junos Priority "medium-low" should map to ASIC priority "Medium"
PR NumberSynopsisCategory: Express BT PFE L3 Features
1657532The evo-aftmand-bt crash might be observed on EVO platforms
Product-Group=evo		On all EVO platforms, when the same firewall filter is applied to an ingress as well the egress direction, the evo-aftmand-bt crash might be observed, if the firewall filter is activated or deactivated a few times(4-5 times).
PR NumberSynopsisCategory: mgd, ddl, odl infra issues
1650151The vlan-tagging configuration might cause the blank interface configurations after a system reboot or upgrade
Product-Group=evo		On all EVO platforms, when vlan-tagging is configured on an interface via groups, 'commit' works fine. But, when upgrading to a newer version, the configuration validation fails. After reboot or upgrade, the device may go into a bad state and it might impact traffic as a result of initial configuration failure.
PR NumberSynopsisCategory: ISIS routing protocol
1572441When DUT and non-DUT have different system time, with different active auth keys the ISIS adjacency do not go DOWN.
Product-Group=evo		This scenario happens when we enable ISIS authentication key-chain having multiple keys between routers. The isis adjacency is up since both routers have the same key active. When we manually change the system time in such a way that routers have different keys active in the key chain, the isis adjacency should go down. But that is not happening.
PR NumberSynopsisCategory: PFE infra to support jvision for EVO
1640442[jvision] [jvisiontag] Verification of DB data collection is failing after executing the jvision decoder
Product-Group=evo		The system ID that is exported should be different for UDP and GRPC/GNMI. In the case of UDP, the system name should be appended with the local IP address.
PR NumberSynopsisCategory: QFX EVPN / VxLAN
1658142TOS(DSCP+ECN) bits not getting copied from the Inner L3 header to Outer VXLAN header.
Product-Group=evo		TOS(DSCP+ECN) bits are not getting copied from the Inner L3 header to Outer VXLAN header at the Ingress VTEP. Because of this in the core, ECN marking and DSCP classification are not working.
PR NumberSynopsisCategory: Express ZX PFE L3 Features
1634982MTS-MCAST: [Brackla] Auto RP base verification failed with multiple RPs with same group range
Product-Group=evo		We have found the workaround which is to deactivate/activate auto-rp config on brackla. This is PR is opened since 20.4 and there is no LKWR .We will be fixing it in DCB.

Modification History

First publication 2022-06-29