Support Support Downloads Knowledge Base Juniper Support Portal 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

21.2R2-S1-EVO: Software Release Notification for JUNOS Software Version 21.2R2-S1-EVO

0

0

Article ID: TSB18254 TECHNICAL_BULLETINS Last Updated: 30 Dec 2021Version: 1.0
Alert Type:
SRN - Software Release Notification
Product Affected:
PTX and QFX Series running Junos Evolved Software
Alert Description:
Junos Software Service Release version 21.2R2-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
Risk Risk Description
Low/Notification - No defined time impact to take action Software Release Notification
Impact Impact Description
Low/Notification - Monitor the situation but no action needed Software Release Notification

Solution:

Junos Software service Release version 21.2R2-S1-EVO is now available.

21.2R2-S1-EVO - List of Fixed issues

PR Number Synopsis Category: "agentd" software daemon
1600412 gNMI Telemetry might stop working after RE switchover
Product-Group=evo
In a dual RE (Routing Engine) system with GRES (Graceful Routing Engine Switchover) NSR (Nonstop Active Routing) enabled telemetry might stop working after RE switchover.
PR Number Synopsis Category: EVO platform software
1597999 PTX10001-36MR: Inconsistency in the platform name used in multiple places, version, snmp mibs, etc.
Product-Group=evo
"show snmp mib walk sysDescr" will show ptx10001-36mr
PR Number Synopsis Category: Express BT PFE L3 Features
1616179 [aft] [generic_evo] : Scapa : PDT - SCAPA - after FPC offline, minor cm-errors may occur for ZFI block on other FPCs.
Product-Group=evo
After FPC offline, minor cm-errors may occur for ZFI block on other FPCs. These errors are cleared and should not affect system functionality.
1621037 Incorrect sensor modeling/mapping when using /junos/system/linecard/interface/ native telemetry streaming in EVO based platforms.
Product-Group=evo
On Branch 20.4R3-S1-EVO and 21.2R2-EVO: The interface sensor will export UDP data with either 158 or 58. This is a bug that was fixed in future releases
PR Number Synopsis Category: EVO L2 Control Protocols Support
1570498 If more than 512 OSPF neighbors are configured, all OSPF routes may not be learned unless the MTU of the IRB interface is modified.
Product-Group=evo
On all QFX Evo platforms, if scaled OSPF (Open Shortest Path First) neighbors (e.g 512 neighbors) are formed over IRB (Integrated Routing and Bridging) interfaces with layer 2 interfaces in the interface-mode trunk, the OSPF routes might be not learned from the neighbors. The issue results in traffic loss.
PR Number Synopsis Category: Category to track runtime issues during package install
1618946 EVO:JDI_FT_REGRESSION:ui:ui_change:PTX10001-36MR :: On performing "request system snapshot", the snapshot msg is not captured in /etc/motd file
Product-Group=evo
Snapshot Banner message when booted from snapshot partition is not getting displayed because /etc/motd file is not getting updated. To check if a system is booted from a snapshot partition, then run cli command "show system software list".
PR Number Synopsis Category: Layer2 forwarding on EX/NTF/PTX/QFX
1626714 Broadcast traffic might not be forwarded to LT interface in VPLS routing instance after LT interface is deleted then added back
Product-Group=evo
On MX platforms, when Logical Tunnels (LT) interface is used for VPLS, VPLS broadcast traffic might not be forwarded to LT interface properly after deleting the LT interface adding it back, which might cause LT interface missing from VPLS flood topology and eventually affects VPLS communication.
PR Number Synopsis Category: PTX10K RE EVO Issues
1617720 Unexpected RE switchover might be observed on EVO platforms
Product-Group=evo
On all EVO platforms with dual RE, automatic RE switchover might be observed unexpectedly since the feature "chassis redundancy failover" is enabled by default.
PR Number Synopsis Category: UI Infrastructure - mgd, DAX API, DDL/ODL
1600435 The dfwc and dcd processes may crash when a commit-check is performed after a previously terminated (with ctrl+c) commit-check
Product-Group=evo
During performing commit-check for the firewall and interface related configurations, if an operator uses the ctrl+c to abort it, the dfwc and dcd may crash after performing another commit-check. This issue will happen only with those daemons that follow the message-based commit-check model (such as dfwc, dcd, rdmd and fwa), and has no impact on other daemons.
PR Number Synopsis Category: Express ZX PFE L3 Features
1624629 "show pfe route ip" is getting timeout when route table size is large
Product-Group=evo
When running "show pfe route ip" command on PTX10001 and PTX10003, an internal script will be run to output the data. Since this script stores all the data into a buffer and once completed, it will result the output. When the data size is large, eg collect complete route internet table, it will turn into timeout (15 seconds)
 

21.2R2-S1-EVO - List of Known issues

PR Number Synopsis Category: "agentd" software daemon
1581659 Certain fields in the GNMI extension header and show network-agent statistics cli will have incorrect values if the input subscription path contains a ":" character
Product-Group=evo
For input subscription paths containing a ":" character, the extension header in case of GNMI and certain fields for the "show network-agent statistics" cli will have incorrect values.
1621347 On scaling system, load override and commit of baseline cfg can cause RPD sensors uninstallation to fail
Product-Group=evo
On scaling system, load override and commit of baseline cfg causes RPD to spin high on CPU. As GRPC config is removed aswell, sensors needs to be uninstalled. But RPD is not responding to these telemetry sensors uninstallation requests. So sensors uninstallation fails. Later when GRPC is enabled back on box and same sensor profile( cfg .json file used with jtimon) is requested from collector, RPD is sending pkts with higher sequence numbers(Because sensor was not removed from RPD earlier) and this is considered as drops by collectors which rely on sequence-numbers.
PR Number Synopsis Category: PTX10003 Platform related issues
1600870 In PTX, if the marvd daemon is restarted (due to a crash), the line card will have access issues and reboot.
Product-Group=evo
Should the marvd daemon restart for any reason, the device becomes unreachable because of PCI uncorrectable non-fatal AER errors getting generated on marvd restart and system goes for reboot without any core. This is a rare event that occurs if there marvd crashes.
PR Number Synopsis Category: PFE COS features on BT based platforms
1633850 evo-cda-bt core dump if "show cda qpoll" or get-state used while a PFE is offlined/faulted, then also after PFE restarted
Product-Group=evo
On EVO PTX10001-36MR or PTX10008/-04/-16, using cli-pfe "show cda qpoll ..." or get-state while a PFE is Offlining or Off sets up evo-cda-bt to crash later, if those commands or get-state is used again when that PFE has restarted.
PR Number Synopsis Category: PFE L2 forwarding features on BT based platforms
1602131 Layer 2 host injected packets might not go out of IRB interface for 40G link
Product-Group=evo
On PTX10001-36MR/PTX10004/PTX10008/PTX10016 platforms with Junos OS Evolved, when 40G interface is configured as L2 interface, if by any chance the interface gets stream id as 32 and if that port is where host injected packet over IRB (Integrated Routing and Bridging) interface has to go out, then the packet drop issue might be seen.
PR Number Synopsis Category: Express BT PFE L3 Features
1621689 [aft] [generic_evo] - after changing ae2 config, seeing [Error] Nexthop: Egress NhChain: numOfTags is 2 and srteGlobalIndex is 0 on all 3 FPCs
Product-Group=evo
After changing ae2 config, seeing [Error] Nexthop: Egress NhChain. The change in this PR is to add syslog messages to help identify the issue.
PR Number Synopsis Category: EVO RPD agent PRs
1623601 PTX10008 routing subsystem not running with warm-standby option enabled
Product-Group=evo
After configuring the warm-standby option, please wait for 3 minutes before performing a RE switchover.
PR Number Synopsis Category: SNMP, mib2d issues
1623201 [CCL] EVO SNMP Traps are not getting generated for second trap group
Product-Group=evo
When two trap groups are configured with same trap destination address, snmpd will send trap using only first trap-group (community).
PR Number Synopsis Category: EVPN control plane issues
1622035 EVO: default route in master instance pointing to mgmt interface could result in anomalies with EVPN VXLAN enabled
Product-Group=evo
On a EVO system, with EVPN VXLAN enabled, if there is a default route in master instance pointing to mgmt interface, it could result in anomalies in EVO database.
PR Number Synopsis Category: EVPN Layer-2 Forwarding
1609322 Few ARP/ND/MAC entries for Vlans are missing with MAC-VRF configuration
Product-Group=evo
In all Junos and Evo platforms, in EVPN-VXLAN scenario, with "proxy-macip-advertisement" knob configured, few ARP/ND/MAC entries may get missing.
PR Number Synopsis Category: PTX10K platform specific fabric PRs
1486023 Restarting the fabspoked-pfe application for the line card restarts the line card.
Product-Group=evo
Restarting the fabspoked-pfe application for the line card restarts the line card.
1624765 Interfaces are down after restarting FPC multiple times
Product-Group=evo
On all Junos OS Evolved platforms with Scapa/Lazurite line cards, the CDA application might crash with multiple FPC restarts, resulting in not publishing the PfeE object. Hence, fabricPfeE objects are not created/deleted. This might lead to multiple fabric links going down for the FPC and might impact the traffic throughput.
PR Number Synopsis Category: EVO Services Sflow PRs for defect & enhancement requests
1602448 EVO:: sflow ingress sampling reports oif as 0 and nextHop as 0000:0000:0000:0000:0000:0000:0000:0000 with user ipv6 traffic with ECMP case at last hop router with Ultimate Hop Pop lsp
Product-Group=evo
Sflow ingress sampling reports incorrect OIF and NH with user ipv6 traffic in ECMP scenario at last hop router with Ultimate Hop Pop lsp
 
Modification History:
First publication 2021-12-30
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