Deploying the primary Admin Node virtual machine

You deploy the primary Admin Node before deploying other grid nodes.

Before you begin

Note: The open-vm-tools package, an open-source implementation similar to VMware Tools, is included with the StorageGRID Webscale virtual machine. You do not need to install VMware Tools manually.

Steps

  1. Open the VMware vSphere Web Client, and sign in.
  2. Navigate to the appropriate location in the vCenter hierarchy. From there, right-click, select Deploy OVF Template, and select vsphere-primary-admin.ovf and NetApp-SG-version-SHA.vmdk.
    Normally you can navigate to Hosts and Clusters, and deploy the template as a specific user or within a specific resource pool.
  3. Read the information on the End User License Agreement page, and click Accept.
  4. Specify the name of the virtual machine, and select a datastore for the disks.
    The name of the virtual machine is typically the same as the name of the grid node. The best practice is to name the virtual machine during the initial virtual machine deployment instead of changing it later.
  5. In the Network Mapping page, select the networks to use by associating a network port to each network.
    The Grid Network is required. The Admin and Client Networks are optional.
    • If you are going to use the Admin Network, assign the Admin Network adapter to a network in the vSphere environment.
    • If you are going to use the Client Network, assign the Client Network adapter to a network in the vSphere environment
    • If you are not going to use an Admin Network or Client Network, assign their network adapters to the same network as the Grid Network.
      Note: The following warning is displayed, but you can ignore it because you will disable the Admin and Client Networks on the next page.
      Warning: Multiple source networks are mapped to the host network: <Destination Network Name>
  6. Provide the required StorageGRID Webscale information in the Properties page:
    Note: This step is for setting Network IP information. After deploying grid nodes, you use the Grid Manager to configure networks.
    1. Enter the Node Name.
    2. Under the Grid Network (eth0) section, enter the following values:
      • Grid Network IP
      • Grid Network mask
      • Grid Network gateway
    3. In the Admin Network (eth1) section, under Admin Network IP configuration, select STATIC, DHCP, or DISABLED.
      • If you select STATIC, enter the Admin Network IP, Admin Network mask, and Admin Network gateway.
      • If you select DHCP, the Admin Network IP, Admin Network mask, and Admin Network gateway are automatically assigned.
      • If you do not want to use the Admin Network (eth1), select DISABLED and enter 0.0.0.0 for the Admin Network IP. You can leave the other fields blank.
    4. Under the Admin Network (eth1) section, enter the Admin Network external subnet list.
    5. In the Client Network (eth2) section, under Client Network IP configuration, select STATIC, DHCP, or DISABLED.
      • If you select STATIC, enter the Client Network IP, Client Network mask, and Client Network gateway.
      • If you select DHCP, the Client Network IP, Client Network mask, and Client Network gateway are automatically assigned.
      • If you do not want to use the Client Network (eth2), select DISABLED and enter 0.0.0.0 for the Client Network IP. You can leave the other fields blank.
  7. Click Finish.
  8. If you want to remap ports used by the primary Admin Node:
    1. Right-click on the VM, and select Edit Settings.
    2. Select vApp Options.
    3. In the Authoring section, expand Properties and scroll down until you see PORT_REMAP_INBOUND and PORT_REMAP.
      You might need to remap a port if your enterprise networking policies restrict access to one or more ports that is used by StorageGRID Webscale.
    4. To symmetrically map both inbound and outbound communications for a port, select PORT_REMAP and click Edit.
      Enter the port mapping as <network type>/<protocol>/<default port used by grid node>/<new port>, where network type is grid, admin, or client, and protocol is tcp or udp.
      Example
      To remap ssh traffic from port 22 to port 3022, enter the following:
      client/tcp/22/3022

      Click OK.

      Note: If only PORT_REMAP is set, the mapping that you specify applies to both inbound and outbound communications. If PORT_REMAP_INBOUND is also specified, PORT_REMAP applies only to outbound communications.
    5. To specify the port used for inbound communications to the node, select PORT_REMAP_INBOUND and click Edit.
      Enter the port mapping as <network type>/<protocol>/<remapped inbound port>/<default inbound port used by grid node>, where network type is grid, admin, or client, and protocol is tcp or udp.
      Example
      To remap inbound SSH traffic that is sent to port 3022 so that it is received at port 22 by the grid node, enter the following:
      client/tcp/3022/22

      Click OK.

      Note: If you specify PORT_REMAP_INBOUND and do not specify a value for PORT_REMAP, outbound communications for the port are unchanged.
  9. Power on the virtual machine if it is not active.