Search

Cluster port down in a Switchless configuration
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Cluster_port_down_in_a_Switchless_configuration
Wed Nov 15 18:20:39 +0900 [Node01: vifmgr: vifmgr.portdown:debug]: A link down event was received on node Node01, port e0b. Wed Nov 15 18:20:39 +0900 [Node01: vifmgr: vifmgr.clus.linkdown:debug]: The ...Wed Nov 15 18:20:39 +0900 [Node01: vifmgr: vifmgr.portdown:debug]: A link down event was received on node Node01, port e0b. Wed Nov 15 18:20:39 +0900 [Node01: vifmgr: vifmgr.clus.linkdown:debug]: The cluster port e0b on node Node01 has gone down unexpectedly. Wed Nov 15 18:25:34 +0900 [Node01: vifmgr: vifmgr.portdown:debug]: A link down event was received on node Node01, port e0b.
A250 boot failure after ONTAP upgrade
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/A250_boot_failure_after_ONTAP_upgrade
Applies to A250 ONTAP 9 Issue One node of A250 boot failure after ONTAP upgrade. It has show below info then reboot. Version 2.20.1271. Copyright (C) 2023 American Megatrends, Inc. BIOS Date: 08/25/20...Applies to A250 ONTAP 9 Issue One node of A250 boot failure after ONTAP upgrade. It has show below info then reboot. Version 2.20.1271. Copyright (C) 2023 American Megatrends, Inc. BIOS Date: 08/25/2023 11:49:53 Ver: 17.10 BIOS boot from Primary SPI Boot Loader version 8.1.1 Copyright (C) 2000-2003 Broadcom Corporation. Portions Copyright (C) 2002-2023 NetApp, Inc. All Rights Reserved. ACPI RSDP Found at 0x68539000 Returning back to BIOS flash0a Copyright(c) 2021 American Megatrends, Inc.
Service-Processor degraded caused by stuck/stale SPAutoUpgradeFailedMajorAlert
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Service-Processor_degraded_caused_by_stuck_stale_SPAutoUpgradeFailedMajorAlert
Service Processor auto-upgrade fails, node reports: SPAutoUpgradeFailedMajorAlert
Aggr degraded then recovery when ONTAP upgrade
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Aggr_degraded_then_recovery_when_ONTAP_upgrade
Applies to ONTAP 9.8P12 FAS 9000 Issue Aggr degraded then recovery when ontap upgrade from ONTAP 9.7p8 to 9.8P12
Call home for DISK REDUNDANCY FAILED alert after takeover
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Call_home_for_DISK_REDUNDANCY_FAILED_alert_after_takeover
[?] Sun Jul 25 09:59:00 CST [Node_B: dsa_disc: callhome.dsk.redun.fault:error]: Call home for DISK REDUNDANCY FAILED [?] Sun Jul 25 09:44:02 CST [Node_B: pmcsas_timeout_0: sas.adapter.debug:info]: par...[?] Sun Jul 25 09:59:00 CST [Node_B: dsa_disc: callhome.dsk.redun.fault:error]: Call home for DISK REDUNDANCY FAILED [?] Sun Jul 25 09:44:02 CST [Node_B: pmcsas_timeout_0: sas.adapter.debug:info]: params: {'debug_string': 'Link down too long ... offlining', 'adapterName': '0b'} [?] Sun Jul 25 09:44:02 CST [Node_B: pmcsas_timeout_0: sas.link.error:error]: Could not recover link on SAS adapter 0b after 45 seconds.
Upgrade ONTAP failed with "Error: command failed: Validation checks failed with errors."
https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Upgrade_ONTAP_failed_with_Error__command_failed__Validation_checks_failed_with_errors
Refer to the Upgrade Advisor Plan or "Performing manual checks before an automated cluster upgrade" section in the "Clustered Data ONTAP Upgrade Express Guide" for the remaining manual validation chec...Refer to the Upgrade Advisor Plan or "Performing manual checks before an automated cluster upgrade" section in the "Clustered Data ONTAP Upgrade Express Guide" for the remaining manual validation checks that need to be performed before update. Action: Refer to the Upgrade Advisor Plan or "Performing manual checks before an automated cluster upgrade" section in the "Clustered Data ONTAP Upgrade Express Guide" for the remaining validation checks that need to be performed before update.
Upgrade ONTAP failed with one node boot failure
https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Upgrade_ONTAP_failed_with_one_node_boot_failure
Upgrade ONTAP from 9.3P6 to 9.5P19. One node Node02 boot failed after ONTAP upgraded. node01 node02 false Connected to node02,partial giveback,takeover is not possible: The node02 node01 - Waiting for...Upgrade ONTAP from 9.3P6 to 9.5P19. One node Node02 boot failed after ONTAP upgraded. node01 node02 false Connected to node02,partial giveback,takeover is not possible: The node02 node01 - Waiting for Cluster application to come onlie on the local node Node01 is active and run ONTAP 9.3 Ssh to node02 system console ,node02 run ONTAP 9.5 but many service do not start. ::> cluster ring show can not find partner node in both node system console.
Any impact for non zeroed spare disk
https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Any_impact_for_non_zeroed_spare_disk
The same is true for Sick Disk Copy (SDC) that will copy the entire content of the disk, which on current versions of Data ONTAP is the preferred method of disk replacement (by avoiding reconstruction...The same is true for Sick Disk Copy (SDC) that will copy the entire content of the disk, which on current versions of Data ONTAP is the preferred method of disk replacement (by avoiding reconstruction). The only case where a zeroed disk is required is when a new aggregate is being built or a new disk added to increase the size of an existing aggregate.
Call home for CLUSTER NETWORK DEGRADED Frequent Link Flapping
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Call_home_for_CLUSTER_NETWORK_DEGRADED_Frequent_Link_Flapping
The cluster port link is flapping causing the cluster network to be degraded and the following events are reported in the system: [Node-02: vifmgr: callhome.clus.net.degraded:alert]: Call home for CLU...The cluster port link is flapping causing the cluster network to be degraded and the following events are reported in the system: [Node-02: vifmgr: callhome.clus.net.degraded:alert]: Call home for CLUSTER NETWORK DEGRADED: Frequent Link Flapping - Cluster port e0a on node Node-02 has experienced multiple link down notifications. The below alert is reported in the event logs when the link between the cluster port and cluster switch goes down:
ONTAP boot sequence fails with Error Failed to determine the board type
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Boot_failed_with_Error_Failed_to_determine_the_board_type_Contact_technical_support_for_assistance
Post ONTAP upgrade, reboot fails with Error: Failed to determine the board type. Contact technical support for assistance
ASUP send alert emails without seeing any recent errors
https://kb.netapp.com/on-prem/E-Series/Management-Apps-KBs/ASUP_send_alert_emails_without_seeing_any_recent_errors
A few alert mails from ASUP, but check from GUI and support bundle, could not find any recent errors Below is an AutoSupport note that would normally be sent to a NetApp Technical Support Engineer or ...A few alert mails from ASUP, but check from GUI and support bundle, could not find any recent errors Below is an AutoSupport note that would normally be sent to a NetApp Technical Support Engineer or a NetApp Customer as a troubleshooting Guideline in response to an AutoSupport received by NetApp. NetApp has received an AutoSupport from the following system: This AutoSupport message indicates there has been problem with your system. A case is being opened to help address the issue.