Search
- Filter results by:
- View attachments
- https://kb.netapp.com/on-prem/ontap/mc/MC-KBs/METROCLUSTER_SWITCHBACK_FAILED_-_AutoSupport_MessageNote: The metrocluster operation show output will only report on the last metrocluster operation. If a subsequent metrocluster operation has run since the switchback failure the output will not be rel...Note: The metrocluster operation show output will only report on the last metrocluster operation. If a subsequent metrocluster operation has run since the switchback failure the output will not be relevant to the failure. From the output, identify the operation-uuid of the failed or partially failed operation: Run the metrocluster operation history show command with the identified operation uuid: Errors: Failed to validate the node and cluster components before the switchback operation.
- https://kb.netapp.com/Support/General_Support/NetApp_Authenticated_File_Upload_Release_NotesApplies to NetApp Products Description New features for NetApp Authenticated File Upload releases are discussed on this page. For general guidance on uploading via NetApp Authenticated File Upload, re...Applies to NetApp Products Description New features for NetApp Authenticated File Upload releases are discussed on this page. For general guidance on uploading via NetApp Authenticated File Upload, refer to these instructions.
- https://kb.netapp.com/Support/NSS/Support_Site/How_do_I_subscribe_to_a_BugApplies to NetApp Support Site Bugs Online Dashboard (BOL) Description If you’re interested in a type of Bug that might impact your system, then Bug Subscription Preferences will allow you to track it...Applies to NetApp Support Site Bugs Online Dashboard (BOL) Description If you’re interested in a type of Bug that might impact your system, then Bug Subscription Preferences will allow you to track it. The Bug Subscription service has two options for tracking: Track individual Bugs Track Bugs per product by creating a Profile Both options have the ability enable email, to receive notifications when a Bug has been added to your favorite list or when a Bug's status changes.
- https://kb.netapp.com/data-mgmt/OCI_Kbs/How_to_collect_troubleshooting_logs_for_OnCommand_Insight_Data_WarehouseApplies to OnCommand Insight Data Warehouse (DWH) Description This article outlines how to create "Troubleshooting Report", which is a bundle of logs that are commonly needed by Technical resources to...Applies to OnCommand Insight Data Warehouse (DWH) Description This article outlines how to create "Troubleshooting Report", which is a bundle of logs that are commonly needed by Technical resources to troubleshoot OnCommand Insight Data Warehouse issues.
- https://kb.netapp.com/on-prem/ontap/Perf/Perf-KBs/How_to_collect_a_Perfstat_from_clustered_Data_ONTAP_systems_using_the_Perfstat_GUIThis document provides information about the Perfstat 8.4 GUI tool and the procedure that should be followed to collect performance data using the tool. Run Perfstat from a physical host or a VM not a...This document provides information about the Perfstat 8.4 GUI tool and the procedure that should be followed to collect performance data using the tool. Run Perfstat from a physical host or a VM not associated with the cluster being collected against. Collection host should be on the same network as the cluster, avoid a lot of network hops or latency between host and cluster. The Perfstat application and related output files should only be stored on the local disk of the collection host.
- https://kb.netapp.com/on-prem/E-Series/Hardware-KBs/E-Series_controller_in_lockdown_state_OE_Lt_after_encountering_configuration_issues_during_startupApplies to All E-Series Hardware Platforms All E-Series Controller Firmware Issue Controller is locked down with a 7-segment LED code of OE Lt Alternate controller is typically also in lock down with ...Applies to All E-Series Hardware Platforms All E-Series Controller Firmware Issue Controller is locked down with a 7-segment LED code of OE Lt Alternate controller is typically also in lock down with code of OE LF or OE Lt but may be something else GUI may display alarm for "Storage Array in Recovery Mode'
- https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/How_to_reduce_workload_driven_disk_utilization_in_ONTAP_9cluster1::> qos statistics volume latency show -vserver svm1 -volume vol1 Workload ID Latency Network Cluster Data Disk QoS Max QoS Min NVRAM --------------- ------ ---------- ---------- ---------- --...cluster1::> qos statistics volume latency show -vserver svm1 -volume vol1 Workload ID Latency Network Cluster Data Disk QoS Max QoS Min NVRAM --------------- ------ ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- -total- - 4.71ms 185.00us 7.00us 468.00us 4.04ms 0ms 0ms 11.00us vol1 32140 22.22ms 86.00us 125.00us 904.00us 21.11ms 0ms 0ms 1.00us -total- - 4.58ms 253.00us 7.00us 991.00us 3.32ms 0ms 0ms 11.00us vol1 32140 29.69ms 90.00us 162.00us 2.61ms 26.82…
- https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Bus_Overruns_on_Port_Causing_Cluster_Health_to_be_Degraded[node_name-1: vifmgr: vifmgr.cluscheck.droppedall:alert]: Total packet loss when pinging from cluster lif node_name-1_cluster1 (node node_name-1) to cluster lif node_name-2_cluster1 (node node_name-2)...[node_name-1: vifmgr: vifmgr.cluscheck.droppedall:alert]: Total packet loss when pinging from cluster lif node_name-1_cluster1 (node node_name-1) to cluster lif node_name-2_cluster1 (node node_name-2). [node_name-1: vifmgr: callhome.clus.net.degraded:alert]: Call home for CLUSTER NETWORK DEGRADED: Insufficient L2 Reachability - Insufficient L2 Reachability detected from cluster port e0a on node node_name-1.
- https://kb.netapp.com/on-prem/ontap/mc/MC-KBs/How_to_interpret_the_data_gathered_via_MCDCNetApp MetroCluster Data Collector The NetApp MetroCluster Data Collector is an application bundle to assist in monitoring MetroCluster systems and continuously gather information from all components....NetApp MetroCluster Data Collector The NetApp MetroCluster Data Collector is an application bundle to assist in monitoring MetroCluster systems and continuously gather information from all components. MCDC can be configured for up to 50 MetroCluster systems of the following configurations: Stretched MetroCluster, direct SAS or ATTO attached Note: MCDC is not intended to replace an online monitoring solution. It is designed to assist in verifying the configuration and diagnosing issues.
- https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/e0a_e0b_link_flaps_on_A300_FAS8200_A200_FAS2600_A220_FAS2700_C190_may_cause_a_TakeoverCluster ports e0a/e0b links flap or go down at the same time, with or without a node takeover. This could be caused by hardware failure on one of the nodes. KB article provides steps to identify the a...Cluster ports e0a/e0b links flap or go down at the same time, with or without a node takeover. This could be caused by hardware failure on one of the nodes. KB article provides steps to identify the affected node and resolve the issue.
- https://kb.netapp.com/on-prem/E-Series/Hardware-KBs/E-Series_Controller_tray_component_removed_-_AutoSupport_MessageSANtricity reports one or multiple events for a controller tray component being removed, such as a controller. Confirm the status of the component reporting as removed Verify if there is any maintenan...SANtricity reports one or multiple events for a controller tray component being removed, such as a controller. Confirm the status of the component reporting as removed Verify if there is any maintenance being performed such as hardware reseat or replacement. Verify the status of the component that is being reported as removed. Verify the Event Logs from Support > Event Logs and confirm if any other events may have caused the errors to be reported. One E-Series controller is removed status