Alert Type

SRN - Software Release Notification

Product Affected

PTX and QFX series running Junos Evolved

Alert Description

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

unos Software service Release version 20.4R2-S1-EVO is now available.

20.4R2-S1-EVO - List of Fixed issues
PR Number Synopsis Category: EVO RPD agent PRs
1593104 [platform_evo] [rpda] ptx10004 : :: PDT: rpdagent crash seen in master RE @NHTable::insert , comp_nh_rts_handler after 4th GRES with GR enabled
Product-Group=evo 		In a rare race condition with multiple RE switchovers the rpd-agent application might exit with a core. The system will recover automatically from the core.
PR Number Synopsis Category: Category for JET(JUNOS Extension Toolkit) related issues
1592542 GRPC connections stuck on ESTABLISHED with no active collector
Product-Group=evo 		In a lossy network, if the peer end (grpc collector/client) gets closed the TCP sessions are held in established state in the Device. The issue is not seen in a normal network, and the issue seen only where there are high packet drops in the network.
PR Number Synopsis Category: Platform infra to support jvision
1593031 Port related component sensor not getting exported when subscribed to /components/component/state/ path.
Product-Group=evo 		on PTX10008 20.4R2 EVO, Port related component sensors under path /components/component/state/ are not exported when subscribed to /components/component/state/. As a work around, user can subscribe to /components/ path to get these data exported.
PR Number Synopsis Category: PTX10K specific platform PRs
1592004 Power budget test case : FPC went offline after switchover
Product-Group=evo 		If a system has power shortage, then post switchover we can see unexpected FPCs or SIBs going down on the new master. FPCs that were down on the previous master might be ONLINED if they are discovered earlier in the powerManager on the new master.
PR Number Synopsis Category: ZT/YT pfe infra issues
1593083 Low priority host bound traffic may starve or delay processing of high priority host bond traffic.
Product-Group=evo 		Low priority host bound traffic may starve or delay processing of high priority host bond traffic. Issue is applicable only on those FPCs which support AFT.
 

20.4R2-S1-EVO - List of Known issues
PR Number Synopsis Category: EVO RCB software
1592258 For ptx10001-36mr the "Host 0 Voltage Threshold Crossed" alarm will be present.
Product-Group=evo 		For ptx10001-36mr, the software driver reads the voltage threshold erroneously causing the "Host 0 Voltage Threshold Crossed" alarm to present on the device.
PR Number Synopsis Category: Bi Directional Forwarding Detection (BFD)
1586331 "clear bfd session" is not a graceful way to bring down BFD. This can cause the client of the BFD session to go down .
Product-Group=evo 		"clear bfd session" is not a graceful way to bring down BFD. This can cause the client of the BFD session to go down .
PR Number Synopsis Category: Tracking PD specific issues on BRCM platforms running EVO
1577375 QFX5130 and QFX5220 Object anomalies seen with PTP TC config
Product-Group=evo 		On QFX5130 and QFX5220, if PTP is configured and then deleted, an object anomaly will be seen, of an object that is not deleted. With each cycle of PTP delete/create, an additional object will remain, thus leaking memory of that object.
PR Number Synopsis Category: Express BT PFE L3 Features
1593548 Load-balance may not take effect for the L2VPN traffic on the PTX10008 platforms
Product-Group=evo 		On the PTX10008 platforms running 20.4R2 onwards, load-balance may not take effect for the L2VPN traffic on the FPCs after configuring/deleting the knob "no-vlan-tagging".
PR Number Synopsis Category: EVO Services Jflow PRs for defect & enhancement requests
1592901 EVO Syslog errors may be seen on restart of 'msvcsd'
Product-Group=evo 		EVO Syslog errors may be seen on restart of 'msvcsd'
PR Number Synopsis Category: Configd, ffp issues
1534858 The firewall filter for both IPv4 and IPv6 might not work when it is applied through apply-groups.
Product-Group=evo 		On Junos OS Evolved PTX devices, the firewall filter for both IPv4 and IPv6 does not work when it is applied through apply-groups on the subinterface
PR Number Synopsis Category: Express PFE MPLS Features
1586122 Packet loss may be seen during global repair of FRR
Product-Group=evo 		In a high scaled setup with ~23K Unicast Nexthops, ~24K Unilist nexthops, ~75K composite nexthops and ~18K Aggregate nexthops and when majority of the unicast nexthops egress out of one physical port, packet loss is observed during Global repair of FRR events.
PR Number Synopsis Category: Periodic Packet Management Daemon
1576089 Re-anchoring of BFD sessions seamlessly is not supported
Product-Group=evo 		The current design doesn't support re-anchoring the BFD sessions seamlessly. There will be flaps seen when the anchor FPC is restarted. Any BFD session which is having the receive(adj) timers on a particular FPC and that FPC goes down there will be flaps. So if the ask is to do seamless movement of sessions when the fpc is rebooted then it needs to be developed as RLI . Moving sessions from one FPC to another without flap for aggressive intervals needs to be investigated further. This should be developed as RLI .
PR Number Synopsis Category: Resource Reservation Protocol
1575188 after doing restart routing immediately, after DUT recovered and started acting as LSR, seeing transit traffic loss
Product-Group=evo 		there are several issues being tracked with different PRs to fix specific issue, this pr is the aggregator of all of them to track the overall result. there are several configuration changes added to address the scaling requirements to avoid prematurely timing out protocol session, adjacency and routing forwarding plane convergence.
1592893 When restart RPD from cli, you may experience very high Traffic loss (0msec - 16sec) across many node-link Protected LSPs
Product-Group=evo 		When restarting the routing protocol daemon (RPD) from cli, you may experience very high Traffic loss (0msec - 16sec) across many node-link Protected LSPs. This expected since restarting RPD from the cli, for FRR to kick in on adjacent devices, you should expect a delay of the IGP timeout (IS-IS hold = 15sec) + IS-IS variance (~5) for a total of 20 seconds. Hence, for global repair when restarting RPD using cli, we should expect 25 seconds.

Modification History

First publication 2021-05-26