Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 33 results
    • The mNode reports storage cluster and vCenter unavailable after upgrading the management services
      https://kb.netapp.com/Legacy/NetApp_HCI/OS/The_mNode_reports_storage_cluster_and_vCenter_unavailable_after_upgrading_the_management_services
      Applies to NetApp mNode on Element software 12.0 or 12.2 Upgrade of the management services to 2.15.28 or 2.16.66 Issue After upgrading the management services: HCC dashboard: One or more vCenter inst...Applies to NetApp mNode on Element software 12.0 or 12.2 Upgrade of the management services to 2.15.28 or 2.16.66 Issue After upgrading the management services: HCC dashboard: One or more vCenter instances cannot be reached, causing some information to be unavailable. Storage nodes are not displayed Errors in mnode_logs-svc: | ERROR | Unable to connect to vCenter due to an incorrect user name or password | | DEBUG | No compute controller found for compute host <HOST_NAME> with IP <HOST_IP> in {}
    • Scaling fails against datacenter with H615C hosts
      https://kb.netapp.com/Legacy/NetApp_HCI/OS/Scaling_fails_against_datacenter_with_H615C_hosts
      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 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.
    • What are the phases in the NDE install workflow?
      https://kb.netapp.com/Legacy/NetApp_HCI/OS/What_are_the_phases_in_the_NDE_install_workflow
      NetApp Deployment Engine (NDE) NDE creates the following deployment workflow tasks: They are serially executed until the install is complete. DeployHci – Master task for HCI deployment All nodes excep...NetApp Deployment Engine (NDE) NDE creates the following deployment workflow tasks: They are serially executed until the install is complete. DeployHci – Master task for HCI deployment All nodes except NDE master node renetworked Then NDE master node renetworked Execute DeployComputeNodeEsxi on N-1 nodes (10% - 91%) ~ 900 seconds Execute GetImages on the remaining node to download files to NDE master node (2% – 9%) ~ 160 seconds Create NetApp-HCI access group and add ESXi IQNs
    • HCI node expansion failing with DNS error
      https://kb.netapp.com/Legacy/NetApp_HCI/OS/HCI_node_expansion_failing_with_DNS_error
      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>: ...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…
    • How to troubleshoot HCI Scale using APIPA
      https://kb.netapp.com/Legacy/NetApp_HCI/OS/How_to_troubleshoot_HCI_Scale_using_APIPA
      Applies to NetApp HCI NDE 1.8 and beyond Description While expanding existing HCI cluster with compute nodes configured with two cable option, using APIPA (zeroconf) addressing, the NDE inventory page...Applies to NetApp HCI NDE 1.8 and beyond Description While expanding existing HCI cluster with compute nodes configured with two cable option, using APIPA (zeroconf) addressing, the NDE inventory page displays an error: X node(s) cannot be displayed due to a problem with the network configuration. To deploy the missing node(s), ensure that jumbo frames are enabled on the switch ports connected to the node's virtual machine ports and storage ports. Doesn't discover any compute nodes
    • NetApp Deployment Engine(NDE) or Scale does not allow to select a storage node due to incorrect drive count detected error
      https://kb.netapp.com/Legacy/NetApp_HCI/OS/NetApp_Deployment_Engine_NDE_or_Scale_does_not_allow_to_select_a_storage_node_due_to_incorrect_drive_count_detected_error
      Applies to NetApp Deployment Engine (NDE) NetApp HCI EasyScale Issue Unable to select a storage node to expand an existing HCI cluster. NDE Available Inventory page displays error for Drive count thou...Applies to NetApp Deployment Engine (NDE) NetApp HCI EasyScale Issue Unable to select a storage node to expand an existing HCI cluster. NDE Available Inventory page displays error for Drive count though drives are available in the slots.
    • Will NDE Scale work after changing default vMotion TCP IP stack
      https://kb.netapp.com/Legacy/NetApp_HCI/OS/Will_NDE_Scale_work_after_changing_default_vMotion_TCP_IP_stack
      Applies to You can modify default vMotion TCP/IP stack and NDE Scale will still let you expand existing HCI cluster By using the vMotion TCP/IP stack, vSphere vMotion traffic can be assigned a default...Applies to You can modify default vMotion TCP/IP stack and NDE Scale will still let you expand existing HCI cluster By using the vMotion TCP/IP stack, vSphere vMotion traffic can be assigned a default gateway on its own subnet and can go over layer 3 networks. The vMotion TCP/IP stack is not available in the default vDS vmkernel wizard, and therefore the vmkernel adapter must be created directly on the ESXi hosts. Use this article to create the vMotion TCP/IP stack on the ESXi host
    • HCI - How to add an HCI Compute node when Easy Scale fails
      https://kb.netapp.com/Legacy/NetApp_HCI/OS/HCI_-_How_to_add_an_HCI_Compute_node_when_Easy_Scale_fails
      Applies to NetApp HCI NetApp Deployment Engine (NDE) Easy Scale Description This KB describes how to add an HCI Compute node when Easy Scale fails
    • NetApp Deployment Engine(NDE) or Scale fails to discover new compute and storage nodes
      https://kb.netapp.com/Legacy/NetApp_HCI/OS/NetApp_Deployment_Engine_NDE_or_Scale_fails_to_discover_new_compute_and_storage_nodes
      Applies to NetApp Deployment Engine NetApp HCI EasyScale Issue NetApp Deployment Engine(NDE) fails to discover new compute and storage nodes.
    • HCI Scale Fails with: The deployment cannot start because an operation is in progress on this installation
      https://kb.netapp.com/Legacy/NetApp_HCI/OS/HCI_Scale_Fails_with__The_deployment_cannot_start_because_an_operation_is_in_progress_on_this_installation
      Applies to NetApp HCI NetApp Deployment Engine (NDE) Issue Attempting to expand HCI with NDE (NetApp Deployment Engine) EasyScale fails with error "The deployment cannot start because an operation is ...Applies to NetApp HCI NetApp Deployment Engine (NDE) Issue Attempting to expand HCI with NDE (NetApp Deployment Engine) EasyScale fails with error "The deployment cannot start because an operation is in progress on this installation"
    • NetApp HCI Compute Node Scale fails with network settings error
      https://kb.netapp.com/Legacy/NetApp_HCI/OS/NetApp_HCI_Compute_Node_Scale_fails_with_network_settings_error
      2018-10-12T01:10:09.805160Z | 22709 | 1516248645 | MainProcess-MainThread | inventory_network:338 | INFO | VDS port groups: found 0 HCI port groups out of 4 port groups 2018-10-12T01:10:09.805810Z | 2...2018-10-12T01:10:09.805160Z | 22709 | 1516248645 | MainProcess-MainThread | inventory_network:338 | INFO | VDS port groups: found 0 HCI port groups out of 4 port groups 2018-10-12T01:10:09.805810Z | 22709 | 1516248646 | MainProcess-MainThread | inventory_network:381 | WARNING | VDS port groups: did not find expected HCI port groups 2018-10-12T01:10:09.806402Z | 22709 | 1516248647 | MainProcess-MainThread | inventory_network:618 | INFO | VDS is not HCI or no HCI VDS portgroups found