Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

20.3R1-S3-EVO: Software Release Notification for JUNOS Software Version 20.3R1-S3-EVO

0

0

Article ID: TSB17990 TECHNICAL_BULLETINS Last Updated: 02 Mar 2021Version: 1.0
Alert Type:
SRN - Software Release Notification
Product Affected:
PTX and QFX series running Junos Evolved
Alert Description:
Junos Software Service Release version 20.3R1-S3-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 20.3R1-S3-EVO is now available.

20.3R1-S3-EVO - List of Fixed issues
PR Number Synopsis Category: EVO RCB software
1567880 User folders are not created when snapshot taken
Product-Group=evo
User folders are not created when snapshot taken.
PR Number Synopsis Category: Express BT PFE L3 Features
1511563 OSPF may flap when line rate traffic is sent at smaller packet sizes
Product-Group=evo
On EVO PTX10001-36MR/PTX10004/PTX10008/PTX10016 platforms, When line rate traffic with smaller packet sizes (64 or 128B) is sent, the OSPF protocol might flap. Sending line rate traffic with smaller size packets may congest the interface and hence control traffic may be lost.
PR Number Synopsis Category: EVO Class of Services
1544531 The cosd may not come up after FPC restart
Product-Group=evo
On Evo platforms, cosd process may not come up after FPC restart. Due to this, the classifier/rewrite/scheduler functionalities may stop working. This issue may be seen during validation check for CNP (Congestion Network Profile) and Drop profile configuration. This issue has a functional impact.
1548014 out of order evl object's Add event even though linkage is present in the config bundle
Product-Group=evo
When configuring Class of Service on a Junos Evolved system, the COSD process may restart unexpectedly.
1566161 cosd crash may be observed with classifier & rewrite bindings
Product-Group=evo
cosd crash may be observed in the following scenarios configs : cos features (classifier & rewrite and corresponding IFL bindings) 1) with deactivate & activate cos configs along with deactivate & activate of interface 2) Daemon restart - class-of-service 3) Router reboot
PR Number Synopsis Category: Firewall related development
1556982 Junos EVO - changing the interface-specific field of the referenced filter in a single commit is not supported.
Product-Group=evo
When changing an interface-specific field of a firewall filter may cause the firewall process to restart. This operation is not supported on the Junos Evolved Software when done with a single commit. You may do this in separate commits.
PR Number Synopsis Category: Issues related to evo operations - libevo infra, typeinfo ..
1540807 PTX10008 JNP10K-LC1202 : savecore.sh is failing to transfer core and journal files from FPCs due to directory create errors
Product-Group=evo
PTX10008 JNP10K-LC1202 : Sometimes, when applications crash on FPCs, these application cores are not transferred to MasterRE as expected. This is because the script that transfers cores from FPC to RE fails to create directory on RE. This happens when a file with the same name exists on the location.
PR Number Synopsis Category: System Management daemon and related issues
1562981 FPC will not be powered on using 'request node power-on fpc'
Product-Group=evo
On PTX10003 and PTX10008 running Junos Evolved, If user does 'request node power-off fpc1' cli to power-off fpc1 and then tries to power it back on using 'request node power-on fpc1', then fpc1 will not be powered on.
PR Number Synopsis Category: Lacp related problems and issues.
1553196 [lacp] [lacptag] PTX10004 lacpd core is obserevd after router reboot
Product-Group=evo
The "lacpd" process may generate a core dump file while a router is shutting down in the following scenarios: a. router reboot b. router upgrade Since the router is shutting down, this won't have an impact on forwarding traffic.
PR Number Synopsis Category: Express PFE FW Features
1540625 PTX10008 : Core generated when combination of hop limit and packet length is configured in filter.
Product-Group=evo
PTX10008 : Core generated when combination of hop limit and packet length is configured in filter.
PR Number Synopsis Category: Interface PR for Lazurite LC
1562471 Interface loopback might not work if there is no optics connected to the port on PTX10000
Product-Group=evo
For retimer ports on PTX10000 platforms, loopback configuration might not work if there is no optics connected to the port.
 

20.3R1-S3-EVO - List of Known issues
PR Number Synopsis Category: Express BT PFE L3 Features
1530710 "show pfe statistics error" should print counters for meaningful errors
Product-Group=evo
"show pfe statistics error", on Junos Evolved platform, shows only "Error Count: <>" for all errors for all PFEs.
1557444 EVO COS: ~260G of traffic drops are consistently seen on egress AE1 (20x100G), after the Ingress/Egress FPC is restarted
Product-Group=evo
The throughput might fall below the advertised line-rate if multiple traffic flows use the same egress interface. To recover, the traffic flows must be spread across multiple egress interfaces.
1561608 Junos EVO - Traffic loss of around 10 to 12 seconds seen on offline / online FPC
Product-Group=evo
In the JUNOS Evolved version 20.3 release, when an FPC is off-lined, there may be traffic loss for about 10 seconds.
PR Number Synopsis Category: Issues related to EVO interface statistics.
1554370 The output of "show interface queue <>" always show "Forwarding classes: 16 supported, 4 in use" with customized configuration
Product-Group=evo
On a PTX running Junos Evolved software, the output of "show interface queue <>" always show "Forwarding classes: 16 supported, 4 in use" with customized configuration.
PR Number Synopsis Category: System Management daemon and related issues
1552045 request system reboot is taking longer in new release
Product-Group=evo
When you issue the "request system reboot" command, the backup routing engine (backup RE) takes about 1 minute longer to clean up the system's state before it reboots.
PR Number Synopsis Category: EVO linux defects & enhancement requests
1528996 [interface] [interface] ptx10004 : PTX10004 :: The system login banner/ message is not showing up when we telnet to the device.
Product-Group=evo
Standard "issue" message is not displayed for the initial login attempt, but if that login attempt fails for any reason and the user is re-prompted, then the message is displayed. This seems to be an issue common to PTX10004.
PR Number Synopsis Category: AAA, auditd issues
1557052 EVO Vs JUNOS : strict-authorization config option missing under set system tacplus-options.
Product-Group=evo
With this change, when config knob strict-authorization is configured under tacplus-options and authorization fails, user is not allowed to login.
PR Number Synopsis Category: Category for software tracing Infra issues
1556040 Core dump for trace-relay process is seen
Product-Group=evo
If some application spawns too many threads trace-relay daemon may dump core if it reaches the upper cap of memory usage. The trace infra will recover and there will be no impact to service. No action needed from user.
PR Number Synopsis Category: Express PFE CoS Features
1544551 EVO COS GRES: Consistent queue drops on high priority AF4 queue, after back-to-back GRES (by yank-out the RE0 followed by RE1) with 125% over-subs traffic
Product-Group=evo
Consistent queue drops on high priority AF4 queue, after back-to-back GRES (by yank-out the RE0 followed by RE1) with 125% over-subs traffic
1553943 [aft] [generic_evo] ptx10004 : PTX10004 :: - seeing cmerror dp_1_viqm_intr_req_enq_err, not cleared after loading latest 20.4 EVO
Product-Group=evo
In scenario of queue congestion, interface enable/disable or in PFC mode this interrupt can come on this release.
PR Number Synopsis Category: Express PFE FW Features
1499294 On a QFX5220 :: show firewall cli shows error error: communication failure with /re0/evo-pfemand/ when unique filter is applied over all physical interfaces.
Product-Group=evo
show firewall cli shows error error: communication failure with /re0/evo-pfemand/ when unique filter is applied over all physical interfaces.
1554685 Encapsulate and Decapsulate actions are not supported under firewall
Product-Group=evo
Encapsulate and Decapsulate actions are not supported under firewall
PR Number Synopsis Category: ISIS routing protocol
1537300 Traffic loss for few seconds after NSR Re switchover for scale routes
Product-Group=evo
Traffic loss is observed during scale as the remnant routes convergence time is more than the default 180s. Seems to be a day1 evo issue. There is no workaround. Reducing the scale could avoid this issue.
1540400 Traffic loss may be seen after graceful switchover
Product-Group=evo
traffic loss seen after graceful switchover with LSR Core MPLS_DSCP profile configuration
PR Number Synopsis Category: KRT Queue issues within RPD
1542511 PTX10008 JNP10K-LC1201 : rpd core seen @ krt_reset_krtq_op_mcnh with lsr core profile configuration
Product-Group=evo
PTX10008 JNP10K-LC1201 : rpd core seen @ krt_reset_krtq_op_mcnh with lsr core profile configuration
PR Number Synopsis Category: PTX10K RE EVO Issues
1556600 Cleaning up the unsupported knob "set chassis redundancy keepalive-time & failover" from Junos Evolved software
Product-Group=evo
'set chassis redundancy keepalive-time' is not yet supported in EVO. Hence removing the CLI.
PR Number Synopsis Category: Express PFE L2 fwding Features on ZX platforms
1568566 Routes learned via IRB interface might not be reachable in IBGP setup
Product-Group=evo
On Junos EVO based PTX10003/QFX10003 platforms with IBGP setup, the route is not reachable if it is learned via indirect Next Hop, which further points to unicast Next hop and getting resolved through IRB interface. There will be complete traffic for the affected route.
 
Modification History:
First publication 2021-03-02
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search