Search
- Filter results by:
- View attachments
- https://kb.netapp.com/Legacy/NetApp_HCI/OS/Scaling_fails_against_datacenter_with_H615C_hostsApplies to NetApp Deployment Engine (NDE) 1.8 and lower Existing datacenter in VMware with NetApp H615C exclusively NSX is not enabled Cable config is correct Issue When starting the NDE scaler, an er...Applies to NetApp Deployment Engine (NDE) 1.8 and lower Existing datacenter in VMware with NetApp H615C exclusively NSX is not enabled Cable config is correct Issue When starting the NDE scaler, an error is returned when selecting the existing vCenter and datacenter: Your network could not be detected. Ensure that this is the datacenter and cluster associated with your vCenter instance.
- https://kb.netapp.com/Legacy/NetApp_HCI/OS/HCI_node_expansion_failing_with_DNS_error2021-03-02T13:16:56.447798Z | 50346 | 3009319564 | HCI-T125-task:40-ScaleHci | task:536 | ERROR | <class 'sfprime.deploy.errors.ValidationError'>({'error_code': 1, 'errors': ['<INCORRECT_DNS_SERVER>: ...2021-03-02T13:16:56.447798Z | 50346 | 3009319564 | HCI-T125-task:40-ScaleHci | task:536 | ERROR | <class 'sfprime.deploy.errors.ValidationError'>({'error_code': 1, 'errors': ['<INCORRECT_DNS_SERVER>: Invalid DNS server: The DNS operation timed out after 5.003451108932495 seconds'], 'traceback': 'Traceback (most recent call last):\n File "pebble/common.py", line 162, in execute\n File "sfprime/tasks/task.py", line 537, in start\n File "sfprime/tasks/task.py", line 681, in _change_state_error\n F…
- https://kb.netapp.com/data-mgmt/AIQUM/AIQUM_Kbs/AIQUM_data_acquisition_is_unstable_due_to_scale_issuesApplies to ActiveIQ Unified Manager (AIQUM) 9.x OnCommand Unified Manager 9.x AIQUM displays the message Insufficient Historical Data when trying to view the Volume Capacity Used historical charts for...Applies to ActiveIQ Unified Manager (AIQUM) 9.x OnCommand Unified Manager 9.x AIQUM displays the message Insufficient Historical Data when trying to view the Volume Capacity Used historical charts for the 1 week or 1 month time frames. Operation State of some clusters is Failed on Cluster Setup page au.log frequently shows WARN with Data source is already performing a poll of netappfoundation or Data source is already performing a poll of netappstorageperformance. Therefore this poll is skipped.
- https://kb.netapp.com/Legacy/NetApp_HCI/OS/How_is_ESXi_version_selected_when_adding_compute_node_by_NDEIt depends on vCenter Server version when adding the compute node. Installable versions of VMware vSphere in Relase Notes contains the same minor version as vCenter Server: ESXi is installed with the ...It depends on vCenter Server version when adding the compute node. Installable versions of VMware vSphere in Relase Notes contains the same minor version as vCenter Server: ESXi is installed with the same minor version as vCenter Server vCenter Server version is higher than Installable versions of VMware vSphere: ESXi is installed with the highest version in Installable versions of VMware vSphere
- https://kb.netapp.com/Legacy/NetApp_HCI/OS/NetApp_Deployment_Engine_NDE_Scale_shows_errors_but_new_compute_nodes_are_present_in_the_clusterApplies to NetApp Deployment Engine (NDE) Issue NetApp Deployment Engine (NDE) scaling shows below error output when it ends but the cluster is expanded with new compute nodes. The deployment ended wi...Applies to NetApp Deployment Engine (NDE) Issue NetApp Deployment Engine (NDE) scaling shows below error output when it ends but the cluster is expanded with new compute nodes. The deployment ended with the following error: An error occurred while joining existing vCenter. Please download error log details here , and contact your technical support engineer.