Alert Type

SRN - Software Release Notification
Low/NotificationSoftware Release Notification
Low/NotificationSoftware Release Notification

Product Affected

ACX, MX, EX, PTX, QFX, vMX, vRR, NFX, SRX, vSRX, JWEB.

Alert Description

Junos Software Service Release version 20.1R1-S3 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 20.1R1-S3 is now available.

20.1R1-S3 - List of Fixed issues

PR NumberSynopsisCategory: MX Platform SW - FRU Management
1489939Support for PSM firmware upgrade in MX2X
Product-Group=junos		Support for upgrading PSMs firmware on the mx2k platforms
PR NumberSynopsisCategory: MX Platform SW - Power Management
1488575Add support for PSM firmware upgrade on MX2K
Product-Group=junos		Supporting PSM firmware upgrades on MX2K platforms
1489967Add support for PSM firmware upgrade in utility
Product-Group=junos		support for upgrading PSM's firmware on the mx2k platforms
1494557Packaging firmware file into jfirmware
Product-Group=junos		Adding the firmware file that needs to packaged in the jfirmware
PR NumberSynopsisCategory: MX Platform SW - UI management
1493045The Delta PSM Firmware upgrade status is incorrectly displayed
Product-Group=junos		fix for displaying the upgrade status
PR NumberSynopsisCategory: MPC11 ULC fabric software related issues.
1483124Link errors may be seen after restarting the FPC or fabric plane
Product-Group=junos		On MPC10/MPC11, if the main PFE is disabled due to the major errors, link errors are observed after the FPC or fabric plane is restarted.
PR NumberSynopsisCategory: MPC11 ULC platform software related issues.
1478243The ukern-platformd process might crash on MX2000 platforms with MPC11
Product-Group=junos		On MX2000 platforms with MPC11, the ukern-platformd process might crash during interrupt handling. Due to this issue, the impacted MPC11 might reboot and traffic loss might happen.
PR NumberSynopsisCategory: Kernel MPLS / Tag / P2MP Infrastructure
1493053Backup RE might crash unexpectedly due to a rare timing issue
Product-Group=junos		The backup Routing Engine might crash unexpectedly due to a rare timing issue during a route churn in the network.
1493431BGP session might keep flapping between two directly connected BGP peers because of the wrong TCP MSS (maximum segment size) in use.
Product-Group=junos		In case the two directly connected BGP peers are established over a one-hop LSP, if the IP layer's MTU is smaller than the MPLS layer's MTU and the BGP packets from the host have the DF bit set, the BGP session might keep flapping because of the wrong TCP MSS in use.
PR NumberSynopsisCategory: Trio pfe qos software
1465870The CoS might not work on MPC10E/MPC11E line cards
Product-Group=junos		On MX platforms with MPC10E/MPC11E line cards used, classifier installation might fail during MPC restart or if interface and CoS classifiers are committed in single commit or deactivate/activate of interface and CoS configs. As a result, traffic might not be forwarded in the scheduled queue. This is a timing issue.
PR NumberSynopsisCategory: ZT pfe firewall software
1484193The traffic rate might not as expected on the AE interface after applying a shared-bandwidth policer
Product-Group=junos		The shared-bandwidth policers for the AE interface might not work if all the child links are not part of the same FPC and same PFE instance.
1493084MPC10/11 linecard might crash if the interface is configured with firewall filter referencing shared-bandwidth policer
Product-Group=junos		On MX platforms with MPC10/11, if the shared-bandwidth policer is referenced by an interface specific firewall filter, and the filter is bound to the interface of the affected linecard, during the linecard reboot, there is a chance that firewall filter information updates come out of order when being sent from Routing Engine (RE) to Packet Forwarding Engine (PFE). Due to handling the out of order update messages, the linecard might crash and get into continuous reboot state.
 

20.1R1-S3 - List of Known issues

PR NumberSynopsisCategory: OAM support on ACX
1483014ACX [bfd] [bfdtag] JDI ACCESS REGRESSION: BFD : When checking the BFD fuctionality over L2VPN Client, BFD session is not coming UP
Product-Group=junos		ACX platforms - BFD over L2VPN/ L2Circuit will not work due to ACX platforms' SDK upgrade to version 6.5.16
PR NumberSynopsisCategory: ACX Services feature
1505089Stateful Firewall (SFW) sessions might not get updated on ms interfaces in ACX500
Product-Group=junos		On ACX500 platforms with CGNAT service, connectivity with Physical Interface Card (PIC) is affected and the SFW session stats are not fetched. This issue happens when the mspmand daemon on the service processor is not initialized properly due to the delay to the state machine.
PR NumberSynopsisCategory: MPC Fusion SW
1491337The ISSU is not supported on NG-MPC cards wherefrom the release is 19.4R1
Product-Group=junos		On the MX platforms with MPC2E-NG/MPC3E-NG installed, when performing ISSU (in-service software upgrade) to 19.4R1 release or later, it may cause NG-MPC cards to crash. When ISSU is done to the builds in which mpc-2e-3e-ng.jbf size greater than 75M (i.e. from 19.4R1 release), the from builds should have the fix of PR 1491337. Otherwise, we would observe crashes on NG-MPC cards/ISSU PREPARE TIMEOUT
PR NumberSynopsisCategory: Bi Directional Forwarding Detection (BFD)
1453705JDI-RCT:M/Mx: BFD session on ISIS flaps during ISSU - FRU upgrade stage (Local diag: CtlExpire Remote diag: None Reason: Detect Timer Expiry) in mx2010
Product-Group=junos		Bfd session flaps during ISSU only in mpc7e card(Bfd sessions from other cards of DUT to peer routers did not flap during ISSU). Issue is not seen frequently.
PR NumberSynopsisCategory: BGP Openconfig and Sensor
1505425The rpd may crash in case of network churn when telemetry streaming is in progress
Product-Group=junos		On all Junos platforms with the JTI (Juniper Telemetry Interface) configured, the rpd may crash when there is telemetry streaming is in progress and meanwhile there is a network churn. This is a timing issue, and the rpd will recover automatically.
PR NumberSynopsisCategory: MX Platform SW - Power Management
1514749[chassisd] [troubleshooting_fru] MX2020 :: Omni MX2K-UNIVERSAL-HV-PSM - PSM is with new firmware (1.7.3) and system available version is 1.4.6 ( new firmware not published )
Product-Group=junos		An MX2020 HV Power Supply Module (PSM) may have a newer firmware version than the firmware bundled with the JUNOS software. There is no impact on system operation.
PR NumberSynopsisCategory: bugs related to esmd daemon
1491513subscriber services's class-of-service shaping rate is not as expected
Product-Group=junos		class-of-service shaping rate is not as expected while verifying interface-set stats
PR NumberSynopsisCategory: Express PFE CoS Features
1502716JDI-RCT:T/PTX : Observed the error message "PFE_ERROR_FAIL_OPERATION: IFD et-1/0/8: RS credits failed to return: init=192 curr=193 chip=5"
Product-Group=junos		During a high traffic load situation, such as during a network convergence, the PTX switching fabric software may use a wrong hi priority fabric queue credit value causing the "RS credits failed to return:" error.
PR NumberSynopsisCategory: jdhcpd daemon
1490907Subscribers do not come up when making connections to a router configured with DHCP ALQ and VRRP
Product-Group=junos		With Active Lease Query (ALQ) and VRRP configurations, DHCP subscribers are not coming up since the DHCP packets are dropped.
PR NumberSynopsisCategory: JSR Infrastructure
1505864The installation fails when upgrading from legacy Junos to specific BSDx based Junos
Product-Group=junos		The installation fails when upgrading from legacy(non-BSDx) Junos to specific BSDx based Junos releases.
PR NumberSynopsisCategory: Label Distribution Protocol
1493969RPD save core file while performing ISSU from 19.3R2 to Junos 20.1R1 or later
Product-Group=junos		RPD may coredump during ISSU 19.3R2 to 20.1R1 or later during stats sync procedure.
PR NumberSynopsisCategory: Multiprotocol Label Switching
1476822PCC might flood event logs to controller
Product-Group=junos		On all Junos platforms, with RSVP-TE based label-switched path (LSP) configured on Path Computation Client (PCC) and PCC connected with Path Computation Element (PCE) using Path Computation Element Protocol (PCEP), PCC might flood event logs (about 20K per minute) to PCE when the LSP having link protection is down without alternative path available. This problem could increase CPU utilization on both PCC and PCE. At the end, device performance will be affected. This is a regression issue.
PR NumberSynopsisCategory: sflow on MX PRs for defect & enhancement requests
1487876Incorrect 'frame length' of 132 bytes might be captured in packet header
Product-Group=junos		On all MX/PTX5k/EX platforms with Trio based line cards, if a packet is send with more than 128 bytes it will always show incorrect "Frame length" of 132 bytes in raw packet header of sflow collector captured data.
PR NumberSynopsisCategory: QFX L2 PFE
1515254On QFX5000 and EX46xx with VXLAN enabled , ARP request may get dropped if storm control is configured
Product-Group=junos		ARP request get dropped on QFX5000 and EX46xx devices when all of the following condition are met. 1.Storm control is enabled on any of the port. 2.VXLAN is enabled 3.Arp-suppression is enabled.
PR NumberSynopsisCategory: MPC7/8/9 Kernel or ukernel SW issues
1471006Syslog message : "fpcX user.notice logrotate: ALERT exited abnormally with [1]" pops at 04:02:01
Product-Group=junosvae		The below "logrotate" ALERT message is logged every day at 04:02:01.000. ``` Oct 15 04:02:01.000 mx-re0 : %PFE-5: fpc8 user.notice logrotate: ALERT exited abnormally with [1] ```
PR NumberSynopsisCategory: RPD Interfaces related issues
1478523The FPC with 'vpn-localization vpn-core-facing-only' configured might be stuck in ready state
Product-Group=junos		On all Junos platform with MVPN scenario, when 'vpn-localization vpn-core-facing-only' is configured, the FPC should be restart when MVPN configuration is changed. But if there is a large-scale configuration that includes "vpn-localization vpn-core-facing-only" and vt-ifl under mvpn instance, when performing configuration removal/restoration(load baseline, commit, rollback 1, commit again), the FPC might be stuck in ready state due to cleanup failure of vt-ifl under MVPN instance.
PR NumberSynopsisCategory: Resource Reservation Protocol
1485985The rpd crash might be seen after back to back GR or GRES
Product-Group=junos		On all platforms, with RSVP LSP configured, after back to back GR or GRES, the rpd crash might be seen.
1498457JDI-RCT: rpd crash observed @rsvp_ing_rt_nh_remove_path, @ rsvp_delete_ing_path, @rsvp_delete_lp_headend_route after performing restart routing
Product-Group=junos		RPD process may dump core while performing "restart routing" if there are LSPs that are unprotected & without secondary paths.
PR NumberSynopsisCategory: MPC7/8/9 Interface Issues
1473280"Failed to complete DFE tuning" syslog messages may appear on MX
Product-Group=junos		Even with the fix for PR 1463015, the "Failed to complete DFE tuning" syslog may appear. This message has no functional impact and can be ignored.
1513321The wavelength configured via CLI might not be set on SFP+-10G-T-DWDM-ZR optics when the optics is used on MPC7E line card
Product-Group=junos		The code change in PR 1410877 (which is fixed in 19.1R1 19.2R1) broke the wavelength configuration for tunable optics on MPC7E line card. After configuring 'interfaces <> optics-options wavelength' for interfaces using SFP+-10G-T-DWDM-ZR optics on MPC7E line card, the wavelength configured might not take effect on these interfaces.
PR NumberSynopsisCategory: Trio pfe bridging, learning, stp, oam, irb software
1493723Traffic loss is observed after ISSU, while enable/disable and activate/deactivate the interface
Product-Group=junos		Traffic loss is observed after ISSU, while enable/disable and activate/deactivate the interface
PR NumberSynopsisCategory: ZT pfe bridging, learning, stp, oam, irb software
1472995Error message "L2:VxLAN Decap flow count:1 L3 RTT context cannot be deleted" may be seen on MPC11E
Product-Group=junos		Following errors may be seen on MPC11E on Junos 20.1R1: aftd-trio: [Error] L2:VxLAN Decap flow count:1 L3 RTT context cannot be deleted for proto:2 L3 RTT Id:0 aftd-trio: [Error] L2:VxLAN Decap flow count:1 L3 RTT context cannot be deleted for proto:6 L3 RTT Id:0
1486158JDI-RCT:-MPC10E@Critical syslog error messages@ fpc3 user.crit aftd-trio: [Critical] Em: Possible out of order deletion of AftNode #012#012#012 AftNode details - AftIndirect token:230791 group:0 nodeMask:0xffffffffffffffff indirect:333988 hwInstall:1#012 "during baseline
Product-Group=junos		Possible out of order deletion of AftNode #012#012#012 AftNode details - AftIndirect token:230791 group:0 nodeMask:0xffffffffffffffff indirect:333988 hwInstall:1#012 "during baseline
PR NumberSynopsisCategory: ZT pfe l3 forwarding issues
1474146JDI-RCT:-MPC10E:- ISIS and micro bfd sessions are not coming up during baseline.
Product-Group=junos		For the MPC10E card line, the IS-IS and micro-BFD sessions do not come up during baseline.
PR NumberSynopsisCategory: ZT pfe multicast software
1499631The heap memory leak might be seen on MPC10/MPC11 linecards
Product-Group=junos		On MPC10/MPC11 linecards, under heavy route churn, the aftd-trio process might slowly leak memory.
 

Modification History

First publication 2020-07-30

01/04/2022: Non-technical changes; formatting modified