Expanding NetApp HCI compute resources

After deployment, you can expand and configure NetApp HCI compute resources using the NetApp Deployment Engine.

Before you begin


  1. Browse to the management IP address of one of the existing storage nodes:
    http://<storage node management IP address>/
  2. Log in to the NetApp Deployment Engine by providing the NetApp HCI storage cluster administrator credentials.
  3. Click Expand Your Installation.
  4. On the Welcome page, select Yes.
  5. On the End User Licenses page, perform the following actions:
    1. Read the VMware End User License Agreement.
    2. If you accept the terms, click I accept at the end of the agreement text.
    3. Click Continue.
  6. Click Continue.
  7. On the vCenter page, perform the following steps:
    1. Enter a FQDN or IP address and administrator credentials for the vCenter instance associated with your NetApp HCI installation.
    2. Click Continue.
    3. Select a vSphere datacenter to which to add the new compute nodes.
    4. Select a vSphere cluster with which the new compute nodes should be associated.
      Note: If you are adding compute nodes with CPU generations that are different than the CPU generation of the existing compute nodes and Enhanced vMotion Compatibility (EVC) is disabled on the controlling vCenter instance, you must enable EVC before proceeding. This ensures vMotion functionality after expansion is complete.
    5. Click Continue.
  8. On the ESXi Credentials page, create ESXi administrator credentials for the compute node or nodes you are adding.
    You should use the same master credentials that were created during the initial NetApp HCI deployment.
  9. Click Continue.
  10. On the Available Inventory page, select the nodes you want to add to the existing NetApp HCI installation.
    Important: For some compute nodes, you might need to enable EVC at the highest level your vCenter version supports before you can add them to your installation. You need to use the vSphere client to enable EVC for these compute nodes. After you enable it, refresh the Inventory page and try adding the compute nodes again.
  11. Click Continue.
  12. On the Network Settings page:
    1. Verify the information detected from the initial deployment.
    2. Each new compute node is listed by serial number, and you need to assign new network information to it. For each new compute node, perform the following actions:
      • If NetApp HCI detected a naming prefix, copy it from the Detected Naming Prefix field, and insert it as the prefix for the new unique hostname you add in the Hostname field.
      • In the Management IP Address field, enter a management IP address for the compute node that is within the management network subnet.
      • In the vMotion IP Address field, enter a vMotion IP address for the compute node that is within the vMotion network subnet.
      • In the iSCSI A - IP Address field, enter an IP address for the first iSCSI port of the compute node that is within the iSCSI network subnet.
      • In the iSCSI B - IP Address field, enter an IP address for the second iSCSI port of the compute node that is within the iSCSI network subnet.
    3. Click Continue.
  13. On the Review page in the Network Settings section, new nodes are shown in bold text. If you need to make changes to information in any section, perform the following steps:
    1. Click Edit for that section.
    2. When finished making changes, click Continue on any subsequent pages to return to the Review page.
  14. Optional: If you do not want to send cluster statistics and support information to NetApp-hosted SolidFire Active IQ servers, clear the final checkbox.
    This disables real-time health and diagnostic monitoring for NetApp HCI. Disabling this feature removes the ability for NetApp to proactively support and monitor NetApp HCI to detect and resolve problems before production is affected.
  15. Click Add Nodes.
    You can monitor the progress while NetApp HCI adds and configures the resources.
  16. Optional: Verify that any new compute nodes are visible in vCenter.