VMware Deployments Software Installation Guide for

StorageGRID® Webscale 10.4

Software Installation Guide forVMware® Deployments

April 2017 | [email protected]

Contents

Installation overview .................................................................................... 5Planning and preparation ............................................................................ 6

Required materials ....................................................................................................... 6

Downloading and extracting the StorageGRID Webscale installation files ................ 7

Hardware requirements ............................................................................................... 9

Software requirements ................................................................................................. 9

Virtual machine requirements ................................................................................... 10

Networking requirements .......................................................................................... 10

Network model .............................................................................................. 10

Network installation and provisioning .......................................................... 13

Internal grid node communications ............................................................... 14

External client communications .................................................................... 16

Storage requirements ................................................................................................. 16

Web browser requirements ........................................................................................ 17

Deploying grid nodes .................................................................................. 18Deploying virtual machine grid nodes in VMware vSphere Web Client .................. 18

Collecting information about your deployment environment ....................... 18

Deploying the primary Admin Node virtual machine ................................... 20

Deploying additional grid node virtual machines ......................................... 22

Deploying StorageGRID Webscale appliance Storage Nodes .................................. 24

Connecting to the StorageGRID Webscale Appliance Installer .................... 24

Configuring network connections ................................................................. 25

Setting the primary Admin Node IP address ................................................. 33

Installing and monitoring the software installation on the appliance ............ 33

Configuring the grid and completing installation ................................... 36Navigating to the Grid Management Interface .......................................................... 36

Specifying the StorageGRID Webscale license information .................................... 37

Adding sites ............................................................................................................... 37

Specifying Grid Network subnets ............................................................................. 38

Approving pending grid nodes .................................................................................. 39

Specifying Network Time Protocol server information ............................................ 42

Specifying Domain Name System server information .............................................. 42

Specifying the StorageGRID Webscale system passwords ....................................... 43

Reviewing your configuration and completing installation ...................................... 44

Automating the installation ....................................................................... 47Automating grid node deployment in VMware vSphere .......................................... 47

Defining the configuration file for your deployment .................................... 48

Running the Bash script ................................................................................ 54

Automating the configuration of StorageGRID Webscale ........................................ 55

Automating the configuration and installation of appliance Storage Nodes ............. 56

StorageGRID Webscale Installation API overview ................................. 58

Table of Contents | 3

Where to go next ......................................................................................... 59Troubleshooting .......................................................................................... 61

Virtual machine resource reservation requires adjustment ........................................ 61

StorageGRID Webscale Appliance Installer errors ................................................... 61

Failed to download new provisioning progress data ..................................... 61

Storage-related error during software installation ......................................... 62

Glossary ....................................................................................................... 64Copyright information ............................................................................... 71Trademark information ............................................................................. 72How to send comments about documentation and receive update

notifications ............................................................................................ 73Index ............................................................................................................. 74

4 | StorageGRID Webscale 10.4 Software Installation Guide for VMware Deployments

Installation overview

Installing a StorageGRID Webscale system in a VMware deployment includes three primary steps.

1. Preparation: You must make sure you have all of the required materials, installation files,hardware, and networks. See “Planning and preparation” for instructions.

2. Deployment: When you deploy grid nodes, the individual grid nodes are created and connectedto one or more networks. When deploying grid nodes:

a. You deploy the virtual nodes as virtual machines (VMs) in VMware vSphere Web Clientusing a .vmdk file and a set of .ovf file templates. See “Deploying individual grid nodes inVMware vSphere Web Client” for instructions.

b. You deploy any StorageGRID Webscale appliance Storage Nodes, using the StorageGRIDWebscale Appliance Installer. See “Deploying StorageGRID Webscale appliance StorageNodes” for instructions.

3. Configuration: When all nodes have been deployed, you use the StorageGRID Webscale GridManagement Interface to configure the grid and complete the installation. See “Configuring thegrid and completing installation” for instructions.

This document recommends a standard approach for deploying and configuring a StorageGRIDWebscale system in a VMware environment, but it also provides information about these alternativeapproaches:

• Using the deploy-vsphere-ovftool.sh Bash script (provided in the installation package) todeploy grid nodes in VMware vSphere. See “Automating grid node deployment in VMwarevSphere” for more information.

• Configuring the StorageGRID Webscale system with a Python configuration script (provided inthe installation package). See “Automating the configuration of StorageGRID Webscale” formore information.

• Deploying and configuring appliance grid nodes with a second Python configuration script(provided in the installation package). See “Automating the configuration and installation ofappliance Storage Nodes” for more information.

• Using the Installation REST API to automate the configuration and installation of grid nodes. See“StorageGRID Webscale Installation API overview” for more information.

Related concepts

Planning and preparation on page 6

StorageGRID Webscale Installation API overview on page 58

Related tasks

Deploying virtual machine grid nodes in VMware vSphere Web Client on page 18

Deploying StorageGRID Webscale appliance Storage Nodes on page 24

Configuring the grid and completing installation on page 36

Automating grid node deployment in VMware vSphere on page 47

Automating the configuration of StorageGRID Webscale on page 55

Automating the configuration and installation of appliance Storage Nodes on page 56

5

Planning and preparation

Before deploying grid nodes and configuring the StorageGRID Webscale grid, you must be familiarwith the steps and requirements for completing the procedure.

The StorageGRID Webscale deployment and configuration procedures assume that you are familiarwith the architecture and operational functionality of the StorageGRID Webscale system. If theStorageGRID Webscale system includes StorageGRID Webscale appliance Storage Nodes, you mustbe familiar with all steps and requirements necessary to successfully complete the StorageGRIDWebscale appliance installation procedures.

You can deploy a single site or multiple sites at one time; however, all sites must meet the minimumrequirement of having at least three Storage Nodes.

Before starting the node deployment and grid configuration procedure, you must:

• Plan the StorageGRID Webscale deployment.

• Install, connect, and configure all required hardware, including any StorageGRID Webscaleappliances, to specifications.

Note: Hardware-specific installation and integration instructions are not included in theStorageGRID Webscale installation procedure. To learn how to install StorageGRID Webscaleappliances, see the StorageGRID Webscale Appliance Installation and Maintenance Guide.

• Understand the available network options and how each network option should be implementedon grid nodes. See “Networking requirements” for more information.

• Gather all networking information in advance, including the IP addresses to assign to each gridnode, and the IP addresses of the domain name system (DNS) and network time protocol (NTP)servers that will be used.

• Decide which of the available deployment and configuration tools you want to use.

Related concepts

Networking requirements on page 10

Related information

StorageGRID Webscale 10.4 Appliance Installation and Maintenance Guide

Required materialsBefore you install StorageGRID Webscale, you must gather and prepare required materials.

Item Notes

NetApp StorageGRIDWebscale license

You must have a valid, digitally signed NetApp license.

Note: A non-production license, which can be used for testingand proof of concept grids, is included in the StorageGRIDWebscale installation file.

6

https://library.netapp.com/ecm/ecm_download_file/ECMLP2574686

Item Notes

StorageGRID Webscaleinstallation package forVMware

You must download one of the following StorageGRIDWebscale installation packages and extract the files to yourservice laptop.

• StorageGRID-Webscale-version-VMware-SHA.tgz

• StorageGRID-Webscale-version-VMware-SHA.zip

VMware software anddocumentation

During installation, you deploy virtual grid nodes on virtualmachines in VMware vSphere Web Client.

For supported versions, see the NetApp Interoperability MatrixTool.

Service laptop The StorageGRID Webscale system is installed through aservice laptop

The service laptop must have:

• Network port

• SSH client (for example, PuTTY)

• Supported web browser

StorageGRID Webscaledocumentation

• Administrator Guide

• Release Notes

Related tasks

Downloading and extracting the StorageGRID Webscale installation files on page 7

Related references

Web browser requirements on page 17

Related information

NetApp Interoperability Matrix Tool

VMware: Featured Documentation Sets

StorageGRID Webscale 10.4 Administrator Guide

StorageGRID Webscale 10.4 Release Notes

Downloading and extracting the StorageGRID Webscaleinstallation files

You must download the correct StorageGRID Webscale installation package from the NetAppSupport Site.

About this task

You must download one of the following StorageGRID Webscale installation packages and extractthe files to your service laptop.

• StorageGRID-Webscale-version-VMware-SHA.tgz

• StorageGRID-Webscale-version-VMware-SHA.zip

Planning and preparation | 7

http://mysupport.netapp.com/matrix

http://www.vmware.com/support/pubs/



Steps

1. Go to the Software Download page on the NetApp Support Site.

NetApp Downloads: Software

2. If required, sign in using the username and password for your NetApp account.

3. Scroll to StorageGRID Webscale, select All Platforms, and click Go.

Note: Be sure to select StorageGRID Webscale, not StorageGRID.

4. Select the StorageGRID Webscale release, and click View & Download.

5. From the Software Download section of the page, click CONTINUE, and accept the End UserLicense Agreement.

6. Download the appropriate file.

7. Extract the compressed files.

8. Choose the files you need from the following list.

The files you need depend on your planned grid topology and how you will deploy yourStorageGRID Webscale grid.

Filename Description

/vsphere/README A text file that describes all of the filescontained in the StorageGRID Webscaledownload file.

/vsphere/NLF000000.txt A non-production NetApp License File thatyou can use for testing and proof of conceptdeployments.

/vsphere/NetApp-SG-version-

SHA.vmdk

The virtual machine disk file that is used as atemplate for creating grid node virtualmachines.

/vsphere/vsphere-primary-admin.ovf

/vsphere/vsphere-primary-admin.mf

The Open Virtualization Format template file(.ovf) and manifest file (.mf) for deploying theprimary Admin Node.

/vsphere/vsphere-non-primary-

admin.ovf

/vsphere/vsphere-non-primary-

admin.mf

The template file (.ovf) and manifest file (.mf)for deploying non-primary Admin Nodes.

/vsphere/vsphere-archive.ovf

/vsphere/vsphere-archive.mf

The template file (.ovf) and manifest file (.mf)for deploying Archive Nodes.

/vsphere/vsphere-gateway.ovf

/vsphere/vsphere-gateway.mf

The template file (.ovf) and manifest file (.mf)for deploying API Gateway Nodes.

/vsphere/vsphere-storage.ovf

/vsphere/vsphere-storage.mf

The template file (.ovf) and manifest file (.mf)for deploying virtual machine-based StorageNodes.

/vsphere/deploy-vsphere-ovftool.sh A Bash shell script used to automate thedeployment of virtual grid nodes.

/vsphere/deploy-vsphere-ovftool-

sample.ini

A sample configuration file for use with thedeploy-vsphere-ovftool.sh script.


http://mysupport.netapp.com/NOW/cgi-bin/software


/vsphere/configure-sga.py A Python script used to automate theconfiguration of StorageGRID Webscaleappliances.

/vsphere/configure-storagegrid.py A Python script used to automate theconfiguration of a StorageGRID Webscalesystem.

/vsphere/configure-

storagegrid.sample.json

A sample configuration file for use with theconfigure-storagegrid.py script.

/vsphere/configure-

storagegrid.blank.json

A blank configuration file for use with theconfigure-storagegrid.py script.

Hardware requirementsBefore installing StorageGRID Webscale, verify and configure hardware so that it is ready to supportthe StorageGRID Webscale system.

For information about supported servers, see the Interoperability Matrix.

Related information


Software requirementsAll StorageGRID Webscale grid nodes, except for StorageGRID Webscale appliance grid nodes, arehosted by virtual machines. One virtual machine is required for each virtual grid node installed on theVMware server.

VMware vSphere Hypervisor

You must install VMware vSphere Hypervisor on a prepared physical server. The hardware must beconfigured correctly (including firmware versions and BIOS settings) before you install VMwaresoftware.

• Configure networking in the hypervisor as required to support networking for the StorageGRIDWebscale system you are installing.

• Ensure that the datastore is large enough for the virtual machines and virtual disks that arerequired to host the grid nodes.

• If you create more than one datastore, name each datastore so that you can easily identify whichdatastore to use for each grid node when you create virtual machines.

VMware configuration requirements

You must install and configure VMware vSphere and vCenter before deploying StorageGRIDWebscale grid nodes.

For supported versions of VMware vSphere Hypervisor and VMware vCenter Server software, seethe Interoperability Matrix.

For the steps required to install these VMware products, see the VMware documentation.



Related information


VMware: Featured Documentation Sets

Virtual machine requirements

In a production environment, the virtual machines for StorageGRID Webscale grid nodes must meetthe following requirements:

Node Type vCPU RAM Storage

Admin Node 8 24 100 GB OS LUN

200 GB MySQL LUN

200 GB Audit LUN

Storage Node 8 24 100 GB OS LUN

Storage LUNs, as required

API Gateway Node 8 24 100 GB OS LUN

Archive Node 8 24 100 GB OS LUN

Networking requirementsYou must verify that the networking infrastructure and configuration is in place to support yourStorageGRID Webscale system.

For more information on networking configuration and supported network topologies, see theStorageGRID Webscale Grid Primer.

Related information

StorageGRID Webscale 10.4 Grid Primer

Network model

You can configure three networks for use with the StorageGRID Webscale system.

To understand how these three networks are used, consider the three types of network traffic that areprocessed by nodes in a StorageGRID Webscale system:

• Grid traffic: The internal StorageGRID Webscale traffic that travels between all nodes in the grid

• Admin traffic: The traffic used for system administration and maintenance

• Client traffic: The traffic that travels between external client applications and the grid, includingall object storage requests from S3 and Swift clients

To allow you more precise control and security, you can configure one, two, or three networks tomanage these three types of traffic.

Grid network

The Grid network is required. It is used for all internal StorageGRID Webscale traffic. The Gridnetwork provides connectivity between all nodes in the grid, across all sites and subnets. All hosts onthe Grid network must be able to talk to all other hosts. The Grid network can consist of multiplesubnets. Networks containing critical grid services, such as NTP, can also be added as Grid subnets.



http://www.vmware.com/support/pubs/


When the Grid network is the only StorageGRID Webscale network, it is also used for all admintraffic and all client traffic. The Grid network gateway is the node default gateway unless the nodehas the Client network configured.

Admin network

The Admin network is optional. It is a closed network used for system administration andmaintenance. The Admin network is typically a private network and does not need to be routablebetween sites.

Using the Admin network for administrative access allows the Grid network to be isolated andsecure. Typical uses of the Admin network include access to the Grid Management Interface, accessto critical services, such as NTP and DNS, access to audit logs on Admin Nodes, and SSH access toall nodes for maintenance and support. The Admin network is never used for internal grid traffic orfor external client traffic. An Admin network gateway is provided and allows the Admin network tospan multiple subnets. However, the Admin network gateway is never used as the node defaultgateway.

Client network

The Client network is also optional. It is an open network used to provide access to clientapplications, including S3 and Swift. The Client network enables grid nodes to communicate withany subnet reachable through the Client network gateway. The Client network does not becomeoperational until you complete the StorageGRID Webscale configuration steps.

The Client network provides client protocol access to the grid, so the Grid network can be isolatedand secured. Normally, only API Gateway Nodes or Storage Nodes are configured with a Clientnetwork, because these nodes provide S3 and Swift protocol access to the grid. When a Clientnetwork is configured, the Client network gateway is required and becomes the node default gatewayafter the grid has been configured.

Supported networks

The table summarizes the supported networks.

Network Interface IP/Mask Gateway Static routes Default route(0.0.0.0/0)

Grid network(required)

eth0 CIDR forstatic IP

The Gridnetworkgateway mustbe configuredif there aremultiple gridsubnets. TheGrid networkgateway is thenode defaultgateway untilgridconfigurationis complete.

Static routesare generatedautomaticallyfor all nodes toall subnetsconfigured inthe global GridNetworkSubnet List.

The GridnetworkGateway IP isthe defaultgateway. If aClient networkis added, thedefaultgatewayswitches fromthe Gridnetworkgateway to theClient networkgateway whengridconfigurationis complete.


Network Interface IP/Mask Gateway Static routes Default route(0.0.0.0/0)

Adminnetwork(optional)

eth1 CIDR forstatic IP(0.0.0.0 todisable)

The Adminnetworkgateway isrequired ifmultiple adminsubnets aredefined.

Static routesare generatedautomaticallyto each subnetconfigured inthe node'sAdminNetworkSubnet List.

N/A

Client network(optional)

eth2 CIDR forstatic IP(0.0.0.0 todisable)

The Clientnetworkgateway isrequired if theClient networkis configured.The Clientnetworkgatewaybecomes thedefault routefor the gridnode whengridconfigurationis complete.

N/A Added if aClient networkGateway IP isconfigured

When deploying a grid node:

• The node must be attached to the Grid network and must be able to communicate with theprimary Admin Node using the networking configuration you specify when deploying the node.

• At least one NTP server must be reachable by the primary Admin Node, using the networkingconfiguration you specify when deploying the new grid node.

• If you are not ready to configure the optional Admin and Client networks during deployment,note that you can also configure these networks when you approve grid nodes during theconfiguration steps. See “Approving pending grid nodes” for more information.

After completing configuration:

• If DHCP was used to assign IP addresses, you must make the leases assigned by the DHCP serverpermanent.

Note: You can only set up DHCP during the deployment phase. There are no options to set upDHCP during configuration.

• You must configure the Grid Network Subnet List using the Grid Management Interface to enablestatic route generation between subnets on the Grid network.

• You must use the IP address change procedures if you want to change IP addresses, subnet masks,and default gateways for a grid node. For more information, see the “Configuring IP addresses”section in the Maintenance Guide.

• If you make networking configuration changes, including routing and gateway changes, clientconnectivity to the primary Admin Node and other grid nodes might be lost. Depending on thenetworking changes applied, you might need to re-establish these connections.


For more information on the StorageGRID Webscale network model and various ways to use it,review the Grid Primer.

Related tasks

Approving pending grid nodes on page 39

Related information

StorageGRID Webscale 10.4 Maintenance Guide for VMware Deployments


Network installation and provisioning

You must understand how the three networks are used during node deployment and gridconfiguration.

When you first deploy a node, you must attach the node to the Grid network and ensure it has accessto the primary Admin Node. If the Grid network is isolated, you can configure the Admin network onthe primary Admin Node for configuration and installation access from outside the Grid network. Ifthe Grid network has a gateway configured, it is the default gateway for the node during deployment.This allows grid nodes on separate subnets to communicate with the primary Admin Node before thegrid has been configured.

Once the nodes have been deployed, the nodes register themselves with the primary Admin Nodeusing the Grid network. You can then use the Grid Management Interface, the configure-storagegrid.py Python script, or the Installation API to configure the grid and approve theregistered nodes. During grid configuration, you can configure multiple grid subnets. Static routes tothese subnets through the Grid network gateway will be created on each node when you completegrid configuration. If necessary, subnets containing NTP servers or requiring access to the GridManagement Interface or API can also be configured as grid subnets.

During the node approval process, you can configure nodes to use the Admin network, the Clientnetwork, or both as desired. If a node is configured to use the Client network, the default gateway forthat node switches from the Grid network to the Client network when you complete the gridconfiguration steps.

Note: When using the Client network, keep in mind that a node’s default gateway will switch fromthe Grid network to the Client network when you complete the grid configuration steps. For allnodes, you must ensure that the node does not lose access to external NTP servers when thegateway switches. For Admin Nodes, you must also ensure that browsers or API clients do not loseaccess to the Grid Management Interface. To maintain access, perform one of the following steps:

• When configuring the node, route the NTP and Grid Management Interface traffic (AdminNodes only) through the Admin network.

• Add subnets to the Grid Network Subnet List (GNSL) that include the IPs of remote clients andservers that should communicate with the grid over the Grid network.

• Ensure that both the Grid and Client network gateways can route traffic to and from theexternal NTP servers and browsers or other Grid Management Interface API clients.

If you are creating... Behavior Recommended configuration

Grid network only All Grid, Admin, and Clienttraffic flows over the Gridnetwork. The Grid networkgateway is the node defaultgateway.




If you are creating... Behavior Recommended configuration

Grid network and Adminnetwork

Grid and Client traffic flowsover the Grid network.Administrative traffic flowsover the Admin network. TheGrid network gateway is thenode default gateway.

Grid network and Clientnetwork (no Admin network)

When a node is deployed, theGrid network gateway is thenode default gateway. Subnetsproviding access to the GridManagement Interface andNTP servers should beincluded as Grid networksduring configuration. Whenyou complete the gridconfiguration steps, the Clientnetwork gateway becomes thenode default gateway.

Allow NTP and installer clientaccess through both the Gridand Client network gateways.

or

Add the NTP or installer Clientsubnets, or both, as Gridnetworks.

All three networks (Grid,Admin, and Client)

When a node is deployed, theGrid network gateway is thenode default gateway. Subnetsproviding access to the GridManagement Interface andNTP servers should beincluded as Grid networks oras Admin subnets duringconfiguration. When youcomplete the gridconfiguration steps, the Clientnetwork gateway becomes thenode default gateway.


or

Add the NTP or installer clientsubnets, or both, as Gridnetworks (so explicit routeswill be created).

or

Add NTP and installer clientsubnets to the Admin NetworkExternal Subnet List (AESL).

Client network, but at a latertime

Subnets providing access to theGrid Management Interfaceand NTP servers should beincluded as Grid networks oras Admin subnets. The Clientnetwork gateway will becomethe node default gateway


or

Add the NTP or installer clientsubnets, or both, as Gridnetworks (so explicit routeswill be created).

or

Add NTP and installer clientsubnets to the AESL.

Internal grid node communications

The following ports must be accessible to grid nodes on the Grid network. Ensure that the requiredports for the grid node type are open on the server.

Configuration of the following ports is only required if you need to define firewall restrictions thatare external to VMware networking.


Port Description Grid node type

22 (TCP) SSH All

80 (TCP) Used by StorageGRIDWebscale appliance (SGA)Storage Nodes to communicatewith the primary Admin Nodeto start the installation

All SGA Storage Nodes andthe primary Admin Node

123 (UDP) NTP All

443 (TCP) HTTPS Admin Nodes

1139 (TCP) LDR replication Storage Nodes

1501 (TCP) ADC service connection Storage Nodes

1502 (TCP) LDR service connection Storage Nodes

1503 (TCP) CMS service connection Storage Nodes

1504 (TCP) NMS service connection Admin Nodes

1505 (TCP) AMS service connection Admin Nodes

1506 (TCP) SSM service connection All grid node types

1507 (TCP) CLB service connection API Gateway Nodes

1508 (TCP) CMN service connection Admin Nodes

1509 (TCP) ARC service connection Archive Nodes

1511 (TCP) DDS service connection Storage Nodes

2022 (TCP) SSH can optionally beconfigured on this port if 22 isunavailable.

All

5353 (UDP) mDNS, optionally used forprimary Admin Nodediscovery during installationand expansion

All

7001 (TCP) Cassandra SSL inter-nodecluster communication

Storage Nodes

9042 (TCP) Cassandra CQL NativeTransport Port

Storage Nodes

11139 (TCP) ARC replication Archive Nodes

18000 (HTTPS) Account service connectionsfrom Admin Nodes and otherStorage Nodes

Storage Nodes that run theADC service

18001 (HTTPS) Identity service connectionsfrom Admin Nodes and otherStorage Nodes

Storage Nodes that run theADC service

18002 (TCP) Internal HTTP APIconnections from AdminNodes and other StorageNodes

Storage Nodes

18080 (TCP) CDMI Storage Nodes


External client communications

Clients need to communicate with grid nodes and, by extension, the servers that host them in order toingest and retrieve content. The ports used depends on the protocols chosen to ingest and retrievecontent.

The following table shows the ports used for traffic into the nodes.

Port Protocol Allows access to

22 (TCP) SSH Servers being used for software installationand maintenance

80 (TCP) HTTP Admin Nodes (redirects to 443)

161 (TCP/UDP) SNMP Servers that are being monitored throughSNMP

162 (TCP/UDP) snmptrap Servers that are being monitored throughSNMP

443 (TCP) HTTPS Admin Nodes

445 (TCP) SMB Audit logs on Admin Nodes

905 (TCP) NFS statd Audit logs on Admin Nodes

2049 (TCP) NFS Audit logs on Admin Nodes

8080 (TCP) CDMI API Gateway Nodes

8082 (TCP) S3 API Gateway Nodes

8083 (TCP) Swift API Gateway Nodes

18080 (TCP) CDMI Storage Nodes

18082 (TCP) S3 Storage Nodes

18083 (TCP) Swift Storage Nodes

The following table shows the ports used for traffic out of the nodes.

Port Protocol Allows access to

389 (TCP/UDP) LDAP LDAP server from Storage Nodes (ADCservice)

443 (TCP) HTTPS S3 from Archive Node

Storage requirementsYou must ensure that each Storage Node has enough space to support the initial configuration andfuture storage expansion.

Storage Nodes must be provisioned with the appropriate amount of storage space on the first storagevolume to ensure that the Cassandra database has enough space for the initial configuration of theStorage Node and any future storage expansion through the addition of storage volumes. Theminimum size for the first storage volume is 4 TB.


Web browser requirementsYou must use a supported web browser.

Web browser Minimum supported version

Google Chrome 54

Microsoft Internet Explorer 11 (Native Mode)

Mozilla Firefox 50

You should set the browser window to a recommended width.

Browser width Pixels

Minimum 1024

Optimum 1280


Deploying grid nodes

When you deploy grid nodes in a VMware environment, the individual grid nodes are created andconnected to one or more networks.

Steps

1. Deploying virtual machine grid nodes in VMware vSphere Web Client on page 18

2. Deploying StorageGRID Webscale appliance Storage Nodes on page 24

Related tasks

Automating the installation on page 47

Deploying virtual machine grid nodes in VMware vSphereWeb Client

You can use VMware vSphere Web Client to deploy each grid node that will run on a virtualmachine.

Collecting information about your deployment environment

Before deploying grid nodes, you must collect information about your network configuration andVMware environment.

You must access the deployment environment and collect information about the VMwareenvironment; the networks that were created for the Grid, Admin, and Client networks; and thestorage volume types you plan to use for Storage Nodes.

VMware information

You must collect information about your VMware environment, including the following:

• The username and password for a VMware vSphere account that has appropriate permissions tocomplete the deployment.

• Host, datastore, and network configuration information for each StorageGRID Webscale gridnode virtual machine.

Grid network information

You must collect information about the VMware network created for the StorageGRID WebscaleGrid network (required), including:

• The network name.

• The required networking details for each grid node (IP address, gateway, and network mask). Aport with a fixed IP address is added to each grid node by the utility.

Note: The Grid network configuration does not support DHCP.

• The IP address of the primary Admin Node on the Grid network. See “How grid nodes discoverthe primary Admin Node” for more information.

18

Admin network information

For nodes that will be connected to the optional StorageGRID Webscale Admin network, you mustcollect information about the VMware network created for this network, including:

• Network name.

• The method used to assign IP addresses, either static or DHCP.

• If you are using static IP addresses, the required networking details for each grid node (IPaddress, gateway, network mask). A port with a fixed IP address is added to each grid node by theutility.

• The external subnet list (ESL) for the Admin network.

Client network information

For nodes that will be connected to the optional StorageGRID Webscale Client network, you mustcollect information about the VMware network created for this network, including:

• Network name.

• The method used to assign IP addresses, either static or DHCP.

• If you are using static IP addresses, the required networking details for each grid node (IPaddress, gateway, network mask). A port with a fixed IP address is added to each grid node by theutility.

Storage volumes for virtual Storage Nodes

You must collect the following information for virtual machine-based Storage Nodes:

• The number and size of storage volumes (rangeDBs) you plan to add. See “Storagerequirements.”

• The names of any volume types you plan to specify. These volumes types must already exist, andthe corresponding block storage must already be configured.

Grid configuration information

You must collect information to configure your grid:

• Grid License

• Network Time Protocol (NTP) server IP addresses

• Domain Name System (DNS) server IP addresses

Related concepts

Storage requirements on page 16

Related references

How grid nodes discover the primary Admin Node on page 20

Deploying grid nodes | 19

How grid nodes discover the primary Admin Node

After a grid node is deployed, it must know how to connect to the grid’s primary Admin Node forconfiguration and management.

To connect to the primary Admin Node, each grid node uses the primary Admin Node’s IP addressfor the Grid network. When you enter the settings used for deployment, you use the ADMIN_IPsetting to provide this value manually.

Grid nodes can also automatically discover the primary Admin Node’s IP address. Automaticdiscovery of the primary Admin Node is accomplished using a multicast Domain Name System(mDNS). When the primary Admin Node first starts up, it publishes its IP address using mDNS.Other nodes on the same subnet can then query for the IP address and acquire it automatically.However, because multicast IP traffic is not normally routable across subnets, nodes on other subnetscannot acquire the primary Admin Node’s IP address directly.

For this reason, you must include the ADMIN_IP setting for at least one grid node on any subnetsthat the primary Admin Node is not directly attached to. This grid node can then publish the primaryAdmin Node’s IP address for other nodes on the subnet to discover.

Deploying the primary Admin Node virtual machine

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

Before you begin

• You must have access to the .ovf and .mf files for the primary Admin Node:

◦ vsphere-primary-admin.ovf

◦ vsphere-primary-admin.mf

• You must have access to the StorageGRID Webscale Virtual Machine Disk (.vmdk) file, and itmust be in the same folder as the .ovf and .mf files:

NetApp-SG-version-SHA.vmdk

• You must be familiar with VMware vSphere Hypervisor and have experience deploying virtualmachines in this environment.

About this task

The VMware tools package is included with the StorageGRID Webscale virtual machine.

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, selectDeploy OVF Template, and select vsphere-primary-admin.ovf.

Normally you can navigate to Hosts and Clusters, and deploy the template as a specific user orwithin 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 bestpractice is to name the virtual machine during the initial virtual machine deployment instead ofchanging it later.


5. In the Network Mapping page, select the networks to use by associating a network port to eachnetwork.

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 inthe vSphere environment.

• If you are going to use the Client network, assign the Client network adapter to a network inthe vSphere environment

• If you are not going to use an Admin network or Client network, assign their respectivenetwork adapters to the same network as the Grid network.

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 theGrid Management Interface to configure networks.

a. Enter the Node Name.

b. Under the Grid Network (eth0) section, enter the following values:

• Grid network IP

• Grid network mask

• Grid network gateway

c. Under the Admin Network (eth1) section, under Admin network IP configuration, selectSTATIC, DHCP, or DISABLED.

d. If you specified STATIC for the Admin network IP configuration, enter the following valuesunder the Admin Network (eth1) section:

• Admin network IP

• Admin network mask

• Admin network gateway

e. Under the Admin Network (eth1) section, enter the Admin network external subnet list.

f. Under the Client Network (eth2) section, under Client network IP configuration, selectSTATIC, DHCP, or DISABLED.

g. If you specified STATIC for the Client network IP configuration, enter the following valuesunder the Client Network (eth2) section:

• Client network IP

• Client network mask

• Client network gateway

7. Click Finish.

8. Power on the virtual machine if it is not active.


Deploying additional grid node virtual machines

After deploying the primary Admin Node, you can deploy the other virtual machine-based grid nodesin your StorageGRID Webscale system.

Before you begin

• You must have access to the .ovf and .mf files for the grid nodes you are deploying:


vsphere-non-primary-admin.ovf

vsphere-non-primary-admin.mf

The template file and manifest file fordeploying non-primary Admin Nodes.

vsphere-archive.ovf

vsphere-archive.mf

The template file and manifest file fordeploying Archive Nodes.

vsphere-gateway.ovf

vsphere-gateway.mf

The template file and manifest file fordeploying API Gateway Nodes.

vsphere-storage.ovf

vsphere-storage.mf

The template file and manifest file fordeploying virtual machine-based StorageNodes.

• You must have access to the StorageGRID Webscale Virtual Machine Disk (.vmdk) file, and itmust be in the same folder as the .ovf and .mf files:

NetApp-SG-version-SHA.vmdk

Note: The same .vmdk file is used for all node types.

About this task

You must deploy all grid nodes before configuring the grid. When deploying a StorageGRIDWebscale virtual machine, ensure that it can connect to the primary Admin Node over the Gridnetwork.

Steps

1. Open VMware vSphere Web Client, and sign in.

2. Navigate to the vApp or resource pool where you want to deploy the StorageGRID Webscalegrid, and select Actions > All vCenter Actions > Deploy OVF Template.

3. Use the Deploy OVF Template dialog box to deploy the .ovf file for the type of grid node youare deploying.

4. Specify the name of the virtual machine, which is typically the name of the grid node.

The best practice is to name the VM during the initial virtual machine deployment instead ofchanging it later.

5. In the Network Mapping page, select the networks to use by associating a network port to eachnetwork. The Grid network is required. The Admin and Client networks are optional. Select theGrid network to use, and then choose the following as applicable:

• If you are going to use the Admin network, assign the Admin network adapter to a network inthe vSphere environment.

• If you are going to use the Client network, assign the Client network adapter to a network inthe vSphere environment


• If you do not intend to use an Admin network or Client network, assign their respectivenetwork adapters to the same network as the Grid network.

6. Provide the required StorageGRID Webscale information in the Properties page, and clickFinish.

a. Enter the Node Name.

b. Enter the Primary Admin IP.

If you omit the primary Admin Node IP address, the IP address will be automaticallydiscovered if the primary Admin Node, or at least one other grid node with ADMIN_IPconfigured, is present on the same subnet. However, it is recommended to set the primaryAdmin Node IP address here.

c. Under the Grid Network (eth0) section, enter the following values:

• Grid network IP

• Grid network mask

• Grid network gateway

d. Under the Admin Network (eth1) section, under Admin network IP configuration, selectSTATIC, DHCP, or DISABLED.

e. If you specified STATIC for the Admin network IP configuration, enter the following valuesunder the Admin Network (eth1) section:

• Admin network IP

• Admin network mask

• Admin network gateway

f. Under the Admin Network (eth1) section, enter the Admin network external subnet list.

g. Under the Client Network (eth2) section, under Client network IP configuration, selectSTATIC, DHCP, or DISABLED.

h. If you specified STATIC for the Client network IP configuration, enter the following valuesunder the Client Network (eth2) section:

• Client network IP

• Client network mask

• Client network gateway

7. Click Next and then Finish to start the upload of the virtual machine.

8. Assign storage to the virtual machine.

Important: For Storage Nodes, you must assign storage to the virtual machine. The StorageNode OVF provided defines several VMDKs for storage. You should remove these and assignappropriate VMDKs for storage before powering up the node.

9. Power on the virtual machine.


Deploying StorageGRID Webscale appliance Storage NodesIf your grid includes StorageGRID Webscale appliances, you deploy them after deploying virtualgrid nodes.

Before you begin

You must have already deployed the primary Admin Node.

About this task

Deploying a Storage Node appliance involves several major tasks.

Note: Optionally, you can use the configure-sga.py script to configure and installStorageGRID Webscale appliance Storage Nodes.

Steps

1. Connecting to the StorageGRID Webscale Appliance Installer on page 24

2. Configuring network connections on page 25

3. Setting the primary Admin Node IP address on page 33

4. Installing and monitoring the software installation on the appliance on page 33

Related tasks

Automating the configuration and installation of appliance Storage Nodes on page 56

Connecting to the StorageGRID Webscale Appliance Installer

To start the appliance software installation, connect to the StorageGRID Webscale ApplianceInstaller. The installer enables you to configure the connections between the appliance and the Adminnetwork, Grid network, and optional Client network. You can also enter the primary Admin Node IPaddress if necessary, and monitor the installation progress.

Steps

1. Open a browser, and enter the IP address that was provisioned during the physical installation forManagement port 1 on the E5600SG controller.

http://Management_Port_IP:8080

This IP address might be displayed on the appliance's seven-segment display if the StorageGRIDWebscale Appliance Installer supports the display of IP addresses.

The StorageGRID Webscale Appliance Installer Home page appears.


Note: This example shows version 1.7 of the StorageGRID Webscale Appliance Installer. Youcan locate the version number in the header bar for all versions later than 1.3.

During the initial setup, the status for procedure steps might be “Not Complete.”

2. Verify the status of these items:

a. Configure Admin network: The Admin network for this StorageGRID Webscale Appliance.To enter or update this information, see “Configuring network connections.”

b. Configure Grid network: The Grid network for this StorageGRID Webscale Appliance. Toenter or update this information, see “Configuring network connections.”

c. Set StorageGRID Installer IP: The primary Admin Node IP address for this StorageGRIDWebscale Appliance. To enter or update this information, see “Setting the primary AdminNode IP address.”

Related tasks

Configuring network connections on page 25

Setting the primary Admin Node IP address on page 33

Configuring network connections

You use the StorageGRID Webscale Appliance Installer to enter networking information for theE5600SG controller in the StorageGRID Webscale appliance.

About this task

When you configure network connections for the StorageGRID Webscale appliance, you specifywhich networks are connected to the E5600SG controller, the IP addresses for the controller's ports,and the routes for each network. If the E5600SG controller includes version 1.7 or later of theStorageGRID Webscale Appliance Installer, you can also specify what type of bonding should beused for the four 10-GbE optical ports on the controller.

Note: To see which version of the Appliance Installer is running, look at the title bar of theAppliance Installer web page. If you want to use a later version, contact technical support.

Steps

1. From the title bar of the StorageGRID Webscale Appliance Installer, click Configure NetworkConnections.


The Configure Network Connections page appears. The version is shown in the header bar.


2. If you are not using a Client network to provide client protocol access to the grid, click theDisable button in the Configure Networks section.

The Client Network section of the page and the Client network settings for the 10-GbE ports areno longer shown. You can click Enable to re-enable these settings.

Related information

NetApp Support

Configuring the 10-GbE ports on the controller

You can use the StorageGRID Webscale Appliance Installer to configure the four 10-GbE opticalports on the E5600SG controller.

Before you begin

If you plan to use Link Aggregation Control Protocol (LACP IEEE 802.3ad), a virtual LAN (VLAN),or both:

• You must be using version 1.7 or later of the StorageGRID Webscale Appliance Installer.

• The 10-GbE optical ports on the E5600SG controller must be connected to switches that cansupport these features.

• You must understand how to configure the switches to use these features.

About this task

The E5600SG controller in the StorageGRID Webscale appliance includes four 10-GbE optical ports,which connect to the Grid network and, optionally, to the Client network. The ports are bondedtogether in groups to provide redundant paths to the controller, as follows:

• By default, and for all versions of the StorageGRID Webscale Appliance Installer, controller ports2 and 4 use active-backup bonding for the Grid network, and ports 1 and 3 use active-backupbonding for the Client network (if used).

In active-backup mode, pairs of ports are bonded together. If the active port fails, its backup portautomatically provides a failover connection to the controller and to the appliance Storage Node.In the default configuration (Fixed Port), port 4 provides a backup path for port 2 (Grid network),and port 3 provides a backup path for port 1 (Client network).

• Starting with version 1.7 of the StorageGRID Webscale Appliance Installer, you can configure thefour ports to use LACP (802.3ad) instead of active-backup mode.

In LACP mode, the ports are grouped together as a single logical channel between the controllerand the network, allowing for higher throughput. In addition, if a port fails, the other ports in theLACP group provide a failover connection to the controller and the appliance Storage Node.

If you have version 1.7 or later of the StorageGRID Webscale Appliance Installer, you can specifyhow the ports should be grouped, as follows:

• Fixed Port Configuration (default) – Ports 2 and 4 control the Grid network, and ports 1 and 3control the Client network, if enabled. The ports can be bonded as pairs in active-backup mode(default) or in LACP mode.

If you do not need redundant connections, you can use only one port for each network.


http://mysupport.netapp.com

Note: If you choose to use one port, be aware that an alarm will be raised in the GridManagement Interface after StorageGRID Webscale is installed, indicating that a cable isunplugged. You can safely acknowledge this alarm to clear it.

• Aggregate Port Configuration – All four ports are grouped in a single LACP bond, allowing allports to be used for Grid network and Client network traffic. Selecting Aggregate PortConfiguration significantly increases the throughout for each network and provides additionalfailover paths. When using Aggregate Port Configuration, you must specify a unique VLAN IDfor each network. This VLAN ID will be added to each network packet to ensure that networktraffic is routed to the correct network.

If you do not need the full bandwidth of four 10-GbE ports, you can use one, two, or three ports,as follows:

◦ If you choose to use one port, use Port 1.

◦ If you choose to use two ports, use Ports 1 and 3.

◦ If you choose to use three ports, use Ports 1, 2, and 3.

This strategy maximizes the chance that some network connectivity will remain available if asingle 10-GbE interface chip fails on the E5600SG controller.

Note: If you choose to use fewer than four ports, be aware that one or more alarms will beraised in the Grid Management Interface after StorageGRID Webscale is installed, indicatingthat cables are unplugged. You can safely acknowledge the alarms to clear them.

The table summarizes the options for configuring the 10-GbE ports. These options are available onlyif the E5600SG controller includes version 1.7 or later of the StorageGRID Webscale ApplianceInstaller. If your controller includes an earlier version, you cannot disable the Client network,configure the ports for LACP mode, or define VLAN IDs. Go to the next section to configure theAdmin, Grid, and Client networks.

Portconfiguration

Type of bond Client network enabled Client network disabled

Fixed(default)

Active-Backup(default)

• Ports 2 and 4 use an active-backup bond for the Gridnetwork.

• Ports 1 and 3 use an active-backup bond for the Clientnetwork.

• VLAN IDs can be specifiedfor both networks for theconvenience of the networkadministrator.

• Ports 2 and 4 use an active-backup bond for the Gridnetwork.

• Ports 1 and 3 are not used.

• A VLAN ID is optional.

LACP(802.3ad)

• Ports 2 and 4 use an LACPbond for the Grid network.

• Ports 1 and 3 use an LACPbond for the Clientnetwork.

• VLAN IDs can be specifiedfor both networks for theconvenience of the networkadministrator.

• Ports 2 and 4 use an LACPbond for the Grid network.

• Ports 1 and 3 are not used.

• A VLAN ID is optional.


Portconfiguration

Type of bond Client network enabled Client network disabled

Aggregate LACP(802.3ad)only

• All four ports use a singleLACP bond. Packets for theGrid network and theClient network use thesame ports.

• The two VLAN IDs allowGrid network packets to besegregated from Clientnetwork packets.

• All four port use a singleLACP bond, and all areused for the Grid network.

• The VLAN ID identifiesGrid network packets.

Steps

1. If the E5600SG controller includes version 1.7 or later of the StorageGRID Webscale ApplianceInstaller, refer to the table and specify how you want to configure the four 10-GbE ports on theE5600SG controller.

This screen shot shows the default setting (Fixed and Active-Backup selected). You canoptionally specify a VLAN ID for either network.

This screen shot shows Aggregate and LACP selected for both networks. You must specify aunique VLAN ID for each network.

VLAN IDs can be integers between 1 and 4094.

2. When you are done configuring the ports and entering VLAN IDs, click Submit.

The Grid Network and Client Network sections of the page are updated. The currentconfiguration for the 10-GbE ports is shown, along with the network's VLAN ID, if entered.These examples show that the Grid and Client networks are using Aggregate Port Configurationwith VLAN IDs of 328 and 332.


Configuring the Admin, Grid, and Client networks

You use the StorageGRID Webscale Appliance Installer to enter networking information for the threetype of networks that can be connected to the appliance.

About this task

Based on how the controller was connected during installation, you might need to configure threenetworks.

• Admin (or management) network: The Admin network allows you to access the StorageGRIDWebscale Appliance Installer, which is included on the E5600SG controller. When you configurethe Admin network, you specify the IP address and routes for Management Port 1 on theE5600SG controller (the leftmost 1-GbE RJ45 port).

• Grid network: During installation, the Grid network allows the appliance to communicate withthe installation API on the primary Admin Node. When installation is complete, the Grid networkallows the appliance to communicate with the grid. You must specify the IP address and routes forthe appliance Storage Node on this network.

• Client network (optional): The Client network provides client protocol access to the grid. If theClient network is enabled, you must specify the IP address and routes for the appliance StorageNode on this network.


Steps

1. If you are using static IP address allocation, complete the following steps:

a. Click Change Static IP/netmask.

The button name changes to Save Changes and a pop-up appears.

b. Enter the IP address for the network, and click Save Changes.

Route information based on the specified IP appears.

c. In the pop-up, click OK.

d. If needed, edit the route, and click Save route.

The default route must be configured on the network connection interface.

2. If you are using DHCP for IP address allocation, click Use DHCP for IP/Netmask.

3. Click Test next to the Ping IP on network text box to verify that the IP address is reachable.

The following message appears for a successful ping:

PING OF "10.223.0.1" SUCCESSFUL.

PING 10.224.1.196 (10.224.1.196) from 10.224.1.92 br1: 56(84) bytes of data.64 bytes from 10.224.1.196: icmp_req=1 ttl=64 time=0.433 ms

--- 10.224.1.196 ping statistics ---1 packets transmitted, 1 received, 0% packet loss, time 0msrrt min/avg/max/mdev = 0.433/0.433/0.433/0.000 ms

The following message appears for a failed ping:

PING OF "10.223.0.1" FAILED.

PING 10.223.0.1 (10.223.0.1) from 10.224.1.92 br1: 56(84) bytes of data.

--- 10.223.0.1 ping statistics ---1 packets transmitted, 0 received, 100% packet loss, time 0ms

4. Click OK to acknowledge the ping message.


Setting the primary Admin Node IP address

You can use the StorageGRID Webscale Appliance Installer to set or correct the IP address of theprimary Admin Node if necessary.

Steps

1. Click Home to navigate to the main StorageGRID Webscale Appliance Installer.

2. Verify that the StorageGRID Installer IP text box shows the IP address of the primary AdminNode.

If this IP address is not shown or should be changed, enter the correct address and click Update.

The Installer IP address will be automatically discovered if the primary Admin Node, or at leastone other grid node with ADMIN_IP configured, is present on the same subnet. If the IP addressin the field was automatically populated, (discovered) appears next to the field as shown in thisexample:

3. Click OK in the confirmation dialog box.

4. Verify that the correct Node Name is shown in the StorageGRID Node Name text box.

To change the name of this Storage Node, enter a new name and click Update.

The Node Name is shown on the Grid Nodes page in the Grid Management Interface, and thename is assigned to the Storage Node in the StorageGRID Webscale system.

Installing and monitoring the software installation on the appliance

The StorageGRID Webscale Appliance Installer provides status until the StorageGRID Webscalesoftware installation is complete.

Before you begin

You must have already entered the network configuration information and entered the primary AdminNode IP address.


About this task

When the software installation is complete, the "Convert installation to bare-metal" step starts. Afterthat step is complete, the appliance reboots itself.

Important: If your grid includes multiple StorageGRID Webscale appliance Storage Nodes, installthe software on no more than five nodes at one time. To avoid bandwidth issues, do not click BeginStorageGRID node install node_name for additional appliances until the first appliances appearin the Grid Management Interface.

Steps

1. From the StorageGRID Webscale Appliance Installer, next to the Set StorageGRID WebscaleInstaller IP option, click Begin StorageGRID node install node_name:

A list of install operations appears. You can review the installation progress as each operationstatus changes from “Not started” to “Completed.” The status refreshes every five seconds.


Note: The Installer ensures that certain tasks completed in a previous install are not re-run. Onthe progress page, any tasks that do not need to be re-run remain in a “Not started” state.

2. To monitor progress, return to the StorageGRID Webscale Appliance Installer.

The Deploy Grid Nodes section shows the installation progress for the Storage Node appliance.

3. Review the installer.

The following occurs:

• When the operating system is being installed, a thumbnail image of the installation screenappears next to the list of operations.

• The StorageGRID Webscale Installer Deploy Grid Nodes status bar changes to blue,indicating a job in progress, and then to green, indicating successful completion.

• The installer shows the last 10 lines of the installation log, which updates every five seconds.

• For new installations, after the last operation, “Boot into StorageGRID” is displayed on thelast line, indicating a status of initiating the reboot.

4. Repeat this process for any additional appliances.

After you finish

The deployment stops while awaiting the node-specific configuration. The system does notautomatically continue the deployment. You must proceed to the next task to trigger it.


Configuring the grid and completing installation

You complete installation by configuring the StorageGRID Webscale grid from the GridManagement Interface on the primary Admin Node.

Steps

1. Navigating to the Grid Management Interface on page 36

2. Specifying the StorageGRID Webscale license information on page 37

3. Adding sites on page 37

4. Specifying Grid Network subnets on page 38

5. Approving pending grid nodes on page 39

6. Specifying Network Time Protocol server information on page 42

7. Specifying Domain Name System server information on page 42

8. Specifying the StorageGRID Webscale system passwords on page 43

9. Reviewing your configuration and completing installation on page 44

Navigating to the Grid Management InterfaceYou use the Grid Management Interface to define all of the information required to configure yourStorageGRID Webscale system on each grid node.

Before you begin

The primary Admin Node must be deployed and have completed the initial startup sequence.

Steps

1. Open your web browser and navigate to the following address:

https://primary_admin_node_ip

Note: This might be the Grid network IP or the Admin network IP, as appropriate for yournetwork configuration.

2. Click Install a StorageGRID Webscale system.

The page used to configure a StorageGRID Webscale grid appears.

36

Specifying the StorageGRID Webscale license informationYou must specify the name for your StorageGRID Webscale system and upload the license fileprovided by NetApp.

Steps

1. On the License page, enter a meaningful name for your StorageGRID Webscale system in GridName.

The name is displayed as the top level in the grid topology tree after installation.

2. Click Browse, locate the NetApp License File (NLFunique_id.txt), and click Open.

The license file is validated, and the serial number and licensed storage capacity are displayed.

Note: A non-production license (NLF00000.txt) is provided and can be used for testing andproof of concept grids. You can update to a production license after installation.

3. Click Next.

Adding sitesYou need to create at least one site when you are installing your StorageGRID Webscale system. Youcan create additional physical sites to increase the reliability and storage capacity of yourStorageGRID Webscale grid.

Steps

1. On the Sites page, enter the Site Name.

2. To add additional sites, click the plus sign next to the last site entry and enter the name in the newSite Name text box.

Add as many additional sites as required for your grid topology. You can add up to 16 sites.

Configuring the grid and completing installation | 37

3. Click Next.

Specifying Grid Network subnetsYou must specify the subnets that are used on the Grid Network.

About this task

The subnet entries include the subnets for the Grid Network for each site in your StorageGRIDWebscale system, along with any subnets that need to be reachable via the Grid Network (forexample, the subnets hosting your NTP servers).

If you have multiple grid subnets, the Grid Network gateway is required. All grid subnets specifiedmust be reachable through this gateway.

Steps

1. Specify the CIDR network address for at least one Grid Network in the Network 1 text box.

2. Click the plus sign next to the last entry to add an additional network entry.

3. Click Next.


Approving pending grid nodesYou must approve each grid node before it joins the StorageGRID Webscale grid.

Before you begin

All virtual and StorageGRID Webscale appliance grid nodes must have been deployed.

Steps

1. Review the Pending Nodes list, and confirm that it shows all of the grid nodes you deployed.

Note: If a grid node is missing, confirm that it was deployed successfully.

2. Select the radio button next to a pending node you want to approve.

3. Click Approve.

4. In General Settings, modify settings for the following properties, as necessary:


• Site: The name of the site the grid node will be associated with.

• Name: The name that will be displayed in the Grid Management Interface

• NTP Role: The grid node's Network Time Protocol (NTP) role. The options are Automatic,Primary, and Client. Selecting Automatic assigns the Primary option to Admin Nodes, thePrimary option to Storage Nodes that have an ADC service, and the Client option to all othergrid node types.

Note: Assign the Primary NTP role to at least two nodes at each site. This providesredundant system access to external timing sources.

• ADC service: For Storage Nodes, whether the selected node will run the AdministrativeDomain Controller service. Select Automatic to have the this option applied automatically bythe system as required, or select Yes or No to explicitly set this option for the grid node. Forexample, you might need to select Yes if you want to have more than three ADC services at asite.

5. In Grid Network, modify settings for the following properties as necessary:

• IPv4 Address (CIDR): The CIDR network address for the eth0 Grid network interface. Forexample: 192.168.0.0/21

• Gateway: The Grid network gateway. This Grid network gateway is used during installationand might be used after installation, unless the Client network is configured. For example:192.168.0.1


Note: The gateway is required if there are multiple grid subnets.

6. If you want to configure the Admin network for the grid node, add or update the settings in theAdmin Network section as necessary.

Enter the destination subnetworks of the routes out of this interface in the Subnets (CIDR) textbox. If there are multiple admin subnets, the admin gateway is required.

Note: If you selected DHCP for the Admin network configuration and you change the valuehere, the new value will be configured as a static address on the node. You must make sure theresulting IP address is not within a DHCP address pool.

7. If you want to configure the Client network for the grid node, add or update the settings in theClient Network section as necessary. If the Client network is configured, the gateway is required,and it becomes the default gateway for the node during installation.

Note: If you selected DHCP for the Client network configuration and you change the valuehere, the new value will be configured as a static address on the node. You must make sure theresulting IP address is not within a DHCP address pool.

8. Click Save.

The grid node entry moves to the Approved Nodes list.

Note: To modify the properties of an approved grid node, select its radio button and click Edit.

9. Repeat these steps for each pending grid node you want to approve.

You must approve all nodes that you want in the grid. However, you can return to this page at anytime before you click Install on the Summary page.

10. When you are done approving grid nodes, click Next.


Specifying Network Time Protocol server informationYou must specify the Network Time Protocol (NTP) configuration information for the StorageGRIDWebscale system, so that operations performed on separate servers can be kept synchronized.

About this task

You must specify external NTP servers. The specified NTP servers must use the NTP protocol.

You must specify four NTP server references of Stratum 3 or better to prevent issues with time drift.

Note: Do not use a Windows server running Windows Time Service as an NTP server referencefor a production-level StorageGRID Webscale installation. Windows Time Service does notprovide a sufficiently accurate clock reference for StorageGRID Webscale.

The external NTP servers connect to the nodes to which you previously assigned Primary NTP roles.For this reason, specifying at least two nodes with Primary NTP roles is recommended.

Important: Make sure that at least two nodes at each site can access at least four external NTPsources. If only one node at a site can reach the NTP sources, timing issues will occur if that nodegoes down. In addition, designating two nodes per site as primary NTP sources ensures accuratetiming if a site is network islanded from the rest of the grid.

Steps

1. Specify the IP addresses for at least four NTP servers in the Server 1 to Server 4 text boxes.

2. If necessary, click the plus sign next the last entry to add additional server entries.

3. Click Next.

Specifying Domain Name System server informationYou must specify Domain Name System (DNS) information for your StorageGRID Webscalesystem, so that you can access external servers using hostnames instead of IP addresses.

About this task

Specifying DNS server information allows you to use Fully Qualified Domain Name (FQDN)hostnames rather than IP addresses for email notifications and AutoSupport. Specifying at least twoDNS servers is recommended.


Important: Provide two to six IP addresses for DNS servers. You should select DNS servers thateach site can access locally in the event of network islanding. This is to ensure an islanded sitecontinues to have access to the DNS service. After configuring the grid-wide DNS server list, youcan further customize the DNS server list for each node. For more information, see “Modifying theDNS configuration for a single grid node” in the Maintenance Guide.

If the DNS server information is omitted or incorrectly configured, a DNST alarm is triggered oneach grid node’s SSM service. The alarm clears when DNS is configured correctly and the newserver information has reached all grid nodes.

Steps

1. Specify the IP address for at least one DNS server in the Server 1 text box.

2. If necessary, click the plus sign next to the last entry to add additional server entries.

The best practice is to specify at least two DNS servers. You can specify up to six DNS servers.

3. Click Next.

Specifying the StorageGRID Webscale system passwordsYou need to enter the passwords to use to secure your StorageGRID Webscale system.

Steps

1. In Provisioning Passphrase, enter the provisioning passphase that will be required to makechanges to the grid topology of your StorageGRID Webscale system.

You should record this password in a secure place.

2. In Confirm Provisioning Passphrase, reenter the provisioning passphrase to confirm it.

3. In Grid Management Root User Password, enter the password to use to access the GridManagement Interface as the “root” user.

4. In Confirm Root User Password, reenter the Grid Management password to confirm it.


5. If you are installing a grid for proof of concept or demo purposes, optionally deselect the Createrandom command line passwords check box.

For production deployments, random passwords should always be used for security reasons.Deselect Create random command line passwords only for demo grids if you want to usedefault passwords to access grid nodes from the command line using the “root” account.

Important: You are prompted to download the Recovery Package file (sgws-recovery-package-id-revision.zip) after you click Install on the Summary page. You mustdownload this file to complete the installation. The passwords required to access the system arestored in the Passwords.txt file.

6. Click Next.

Reviewing your configuration and completing installationYou must carefully review the configuration information you have entered to ensure that yourStorageGRID Webscale system installation completes successfully.

Steps

1. View the Summary page.


2. Verify that all of the grid configuration information is correct. Use the Modify links on theSummary page to go back and correct any errors.

3. Click Install.

Note: If a node is configured to use the Client network, the default gateway for that nodeswitches from the Grid network to the Client network when you click Install. If you loseconnectivity, you must ensure that you are accessing the primary Admin Node through anaccessible subnet. See “Network installation and provisioning” for details.

4. Click Download the Recovery Package.

When the installation progresses to the point where the grid topology is defined, you will beprompted to download the Recovery Package file (.zip), and confirm that you can successfullyaccess the contents of this file. You must download the Recovery Package file so that you canrecover the StorageGRID Webscale system in the event that one or more grid nodes fails. Theinstallation continues in the background, but you cannot complete the installation and access theStorageGRID Webscale system until you download and verify this file.

5. Verify that you can extract the contents of the .zip file, and then save it in two safe, secure, andseparate locations.

Important: The Recovery Package file must be secured because it contains encryption keys andpasswords that can be used to obtain data from the StorageGRID Webscale system.

6. Select the I have successfully downloaded and verified the Recovery Package file check box,and click Next.


If the installation is still in progress, the status page is displayed indicating the progress of theinstallation for each grid node.

Once the installation status for all grid nodes reaches 100%, the installation is complete, and thesign-in page for the Grid Management Interface is displayed.

7. Sign in to the Grid Management Interface using the "root" user and the password you specifiedduring the installation.


Automating the installation

You can automate the deployment of VMware virtual grid nodes, the configuration of grid nodes, andthe configuration of StorageGRID Webscale appliances.

Steps

1. Automating grid node deployment in VMware vSphere on page 47

2. Automating the configuration of StorageGRID Webscale on page 55

3. Automating the configuration and installation of appliance Storage Nodes on page 56

Automating grid node deployment in VMware vSphereYou can automate the deployment of StorageGRID Webscale grid nodes in VMware vSphere.

Before you begin

• You have access to a Linux/Unix system with Bash 3.2 or later.

• You have VMware OVF Tool 4.1 installed and correctly configured.

• You know the username and password required to access VMware vSphere using the OVF Tool.

• You know the virtual infrastructure (VI) URL for the location in vSphere where you want todeploy the StorageGRID Webscale virtual machines. This URL will typically be a vApp, orResource Pool. For example: vi://vcenter.example.com/vi/sgws

Note: You can use the VMware ovftool utility to determine this value (see the ovftooldocumentation for details).

Note: If you are deploying to a vApp, the virtual machines will not start automatically the firsttime, and you must power them on manually.

• You have collected all the required information for the configuration file. See “Collectinginformation about your deployment environment” for information.

• You have access to the following files from the VMware installation package for StorageGRIDWebscale:


NetApp-SG-version-SHA.vmdk The virtual machine disk file that is used as atemplate for creating grid node virtualmachines.

Note: This file must be in the same folderas the .ovf and .mf files.

vsphere-primary-admin.ovf

vsphere-primary-admin.mf

The Open Virtualization Format template file(.ovf) and manifest file (.mf) for deploying theprimary Admin Node.

vsphere-non-primary-admin.ovf

vsphere-non-primary-admin.mf

The template file (.ovf) and manifest file (.mf)for deploying non-primary Admin Nodes.

47


vsphere-archive.ovf

vsphere-archive.mf

The template file (.ovf) and manifest file (.mf)for deploying Archive Nodes.

vsphere-gateway.ovf

vsphere-gateway.mf

The template file (.ovf) and manifest file (.mf)for deploying API Gateway Nodes.

vsphere-storage.ovf

vsphere-storage.mf

The template file (.ovf) and manifest file (.mf)for deploying virtual machine-based StorageNodes.

deploy-vsphere-ovftool.sh The Bash shell script used to automate thedeployment of virtual grid nodes.

deploy-vsphere-ovftool-sample.ini The sample configuration file for use with thedeploy-vsphere-ovftool.sh script.

Steps

1. Defining the configuration file for your deployment on page 48

2. Running the Bash script on page 54

Related references

Collecting information about your deployment environment on page 18

Defining the configuration file for your deployment

You specify the information needed to deploy virtual grid nodes for StorageGRID Webscale in aconfiguration file, which is used by the deploy-vsphere-ovftool.sh Bash script. You canmodify a sample configuration file, so that you do not have to create the file from scratch.

Steps

1. Make a copy of the sample configuration file (deploy-vsphere-ovftool.sample.ini). Savethe new file as deploy-vsphere-ovftool.ini in the same directory as deploy-vsphere-ovftool.sh.

2. Open deploy-vsphere-ovftool.ini.

3. Enter all of the information required to deploy VMware virtual grid nodes.

See “Configuration file settings” for information.

4. When you have entered and verified all of the necessary information, save and close the file.

Related concepts

Configuration file settings on page 48

Configuration file settings

The deploy-vsphere-ovftool.ini configuration file contains the settings that are required todeploy virtual grid nodes.

The configuration file first lists global parameters, and then lists node-specific parameters in sectionsdefined by node name. When the file is used:

• Global parameters are applied to all grid nodes.

• Node-specific parameters override global parameters.


Global parameters

Global parameters are applied to all grid nodes, unless they are overridden by settings in individualsections. Place the parameters that apply to multiple nodes in the global parameter section, and thenoverride these settings as necessary in the sections for individual nodes.

• OVFTOOL_ARGUMENTS: You can specify OVFTOOL_ARGUMENTS as global settings, oryou can apply arguments individually to specific nodes. For example:

OVFTOOL_ARGUMENTS = --powerOn --noSSLVerify --diskMode=thin --datastore='datastore_name'

You can use the --powerOffTarget and --overwrite options to shut down and replaceexisting virtual machines.

Important: It is recommended that you deploy nodes to different datastores and specifyOVFTOOL_ARGUMENTS for each node, instead of globally.

• SOURCE: The path to the StorageGRID Webscale virtual machine template (.vmdk) file andthe .ovf and .mf files for individual grid nodes. This defaults to the current directory.

SOURCE = /downloads/StorageGRID-Webscale-version/vsphere

• TARGET: The VMware vSphere virtual infrastructure (vi) URL for the location whereStorageGRID Webscale will be deployed. For example:

TARGET = vi://vcenter.example.com/vm/sgws

• GRID_NETWORK_TARGET: The name of an existing VMware network to use for the Gridnetwork. If all or most of the nodes use the same network name, you can specify it here. You canthen override the global setting by specifying different settings for one or more individual nodes.

For example:

GRID_NETWORK_TARGET = SG-Grid-Network

• GRID_NETWORK_MASK: The network mask for the Grid network. If all or most of the nodesuse the same network mask, you can specify it here. You can then override the global setting byspecifying different settings for one or more individual nodes. For example:

GRID_NETWORK_MASK = 255.255.255.0

• GRID_NETWORK_GATEWAY: The network gateway for the Grid network. If all or most ofthe nodes use the same network gateway, you can specify it here. You can then override the globalsetting by specifying different settings for one or more individual nodes. For example:

GRID_NETWORK_GATEWAY = 10.1.0.1

• GRID_NETWORK_MTU: Optional. The maximum transmission unit (MTU) on the Gridnetwork. If specified, the value must be between 68 and 65535. If omitted, 1400 is used. If all ormost of the nodes use the same MTU for the Grid network, you can specify it here. You can thenoverride the global setting by specifying different settings for one or more individual nodes. Forexample:

GRID_NETWORK_MTU = 8192

Automating the installation | 49

• ADMIN_NETWORK_CONFIG: The method used to acquire IP addresses, either DISABLED,STATIC, or DHCP. The default is DISABLED. If all or most of the nodes use the same methodfor acquiring IP addresses, you can specify that method here. You can then override the globalsetting by specifying different settings for one or more individual nodes. For example:

ADMIN_NETWORK_CONFIG = STATIC

• ADMIN_NETWORK_TARGET: The name of an existing VMware network to use for theAdmin network. This setting is required unless the Admin network is disabled. If all or most ofthe nodes use the same network name, you can specify it here. You can then override the globalsetting by specifying different settings for one or more individual nodes. For example:

ADMIN_NETWORK_TARGET = SG-Admin-Network

• ADMIN_NETWORK_MASK: The network mask for the Admin network. This setting isrequired if you are using static IP addressing. If all or most of the nodes use the same networkmask, you can specify it here. You can then override the global setting by specifying differentsettings for one or more individual nodes. For example:

ADMIN_NETWORK_MASK = 255.255.255.0

• ADMIN_NETWORK_GATEWAY: The network gateway for the Admin network. This settingis required if you are using static IP addressing and you specify external subnets in theADMIN_NETWORK_ESL setting. (That is, it is not required if ADMIN_NETWORK_ESL isempty.) If all or most of the nodes use the same network gateway, you can specify it here. You canthen override the global setting by specifying different settings for one or more individual nodes.For example:

ADMIN_NETWORK_GATEWAY = 10.3.0.1

• ADMIN_NETWORK_ESL: The external subnet list (routes) for the Admin network, specifiedas a comma-separated list of CIDR route destinations. If all or most of the nodes use the samenetwork external subnet list, you can specify it here. You can then override the global setting byspecifying different settings for one or more individual nodes. For example:

ADMIN_NETWORK_ESL = 172.16.0.0/21,172.17.0.0/21

• ADMIN_NETWORK_MTU: Optional. The maximum transmission unit (MTU) on the Adminnetwork. Do not specify if ADMIN_NETWORK_CONFIG = DHCP. If specified, the value mustbe between 68 and 65535. If omitted, 1400 is used. If all or most of the nodes use the same MTUfor the Admin network, you can specify it here. You can then override the global setting byspecifying different settings for one or more individual nodes. For example:

ADMIN_NETWORK_MTU = 8192

• CLIENT_NETWORK_CONFIG: The method used to acquire IP addresses, either DISABLED,STATIC, or DHCP. The default is DISABLED. If all or most of the nodes use the same methodfor acquiring IP addresses, you can specify that method here. You can then override the globalsetting by specifying different settings for one or more individual nodes. For example:

CLIENT_NETWORK_CONFIG = STATIC

• CLIENT_NETWORK_TARGET: The name of an existing VMware network to use for theClient network. This setting is required unless the Client network is disabled. If all or most of the


nodes use the same network name, you can specify it here. You can then override the globalsetting by specifying different settings for one or more individual nodes. For example:

CLIENT_NETWORK_TARGET = SG-Client-Network

• CLIENT_NETWORK_MASK: The network mask for the Client network. This setting isrequired if you are using static IP addressing. If all or most of the nodes use the same networkmask, you can specify it here. You can then override the global setting by specifying differentsettings for one or more individual nodes. For example:

CLIENT_NETWORK_MASK = 255.255.255.0

• CLIENT_NETWORK_GATEWAY: The network gateway for the Client network. This settingis required if you are using static IP addressing. If all or most of the nodes use the same networkgateway, you can specify it here. You can then override the global setting by specifying differentsettings for one or more individual nodes. For example:

CLIENT_NETWORK_GATEWAY = 10.4.0.1

• CLIENT_NETWORK_MTU: Optional. The maximum transmission unit (MTU) on the Clientnetwork. Do not specify if CLIENT_NETWORK_CONFIG = DHCP. If specified, the value mustbe between 68 and 65535. If omitted, 1400 is used. If all or most of the nodes use the same MTUfor the Client network, you can specify it here. You can then override the global setting byspecifying different settings for one or more individual nodes. For example:

CLIENT_NETWORK_MTU = 8192

Node-specific parameters

Each node is in its own section of the configuration file. Each node requires the following settings:

• The section head defines the node name that will be displayed in the Grid Management Interface.You can override that value by specifying the optional NODE_NAME parameter for the node.

• NODE_TYPE: VM_Admin_Node, VM_Storage_Node, VM_Archive_Node, orVM_API_Gateway_Node

• GRID_NETWORK_IP: The IP address for the node on the Grid network.

• ADMIN_NETWORK_IP: The IP address for the node on the Admin network. Required only ifthe node is attached to the Admin network and ADMIN_NETWORK_CONFIG is set to STATIC.

• CLIENT_NETWORK_IP: The IP address for the node on the Client network. Required only ifthe node is attached to the Client network and CLIENT_NETWORK_CONFIG for this node isset to STATIC.

• ADMIN_IP: The IP address for the primary Admin node on the Grid network. Use the value thatyou specify as the GRID_NETWORK_IP for the primary Admin Node. If you omit thisparameter, the node attempts to discover the primary Admin Node IP using mDNS. See “Howgrid nodes discover the primary Admin Node” for more information.

Note: The ADMIN_IP parameter is ignored for the primary Admin Node.

• Any parameters that were not set globally. For example, if a node is attached to the Adminnetwork and you did not specify ADMIN_NETWORK parameters globally, you must specifythem for the node.


Primary Admin Node

The following additional settings are required for the primary Admin Node:

• NODE_TYPE: VM_Admin_Node

• ADMIN_ROLE: Primary

This example entry is for a primary Admin Node that is on all three networks:

[DC1-ADM1] ADMIN_ROLE = Primary NODE_TYPE = VM_Admin_Node GRID_NETWORK_IP = 10.1.0.2 ADMIN_NETWORK_IP = 10.3.0.2 CLIENT_NETWORK_IP = 10.4.0.2

The following additional setting is optional for the primary Admin Node:

• DISK: By default, Admin Nodes are assigned two additional 200 GB hard disks for audit anddatabase use. You can increase these settings using the DISK parameter. For example:

DISK = INSTANCES=2, CAPACITY=300

Note: For Admin nodes, INSTANCES must always equal 2.

Storage Node

The following additional setting is required for Storage Nodes:

• NODE_TYPE: VM_Storage_Node

This example entry is for a Storage Node that is on the Grid and Admin networks, but not on theClient network. This node uses the ADMIN_IP setting to specify the primary Admin Node's IPaddress on the Grid network.

[DC1-S1] NODE_TYPE = VM_Storage_Node

GRID_NETWORK_IP = 10.1.0.3 ADMIN_NETWORK_IP = 10.3.0.3

ADMIN_IP = 10.1.0.2

The following additional setting is optional for Storage Nodes:

• DISK: By default, Storage Nodes are assigned three 4 TB disks for RangeDB use. You canincrease these settings with the DISK parameter.

Archive Node

The following additional setting is required for Archive Nodes:

• NODE_TYPE: VM_Archive_Node

This example entry is for an Archive Node that is on the Grid and Admin networks, but not on theClient network.

[DC1-ARC1] NODE_TYPE = VM_Archive_Node



ADMIN_IP = 10.1.0.2

API Gateway Node

The following additional setting is required for API Gateway Nodes:

• NODE_TYPE: VM_API_Gateway

This example entry is for an example API Gateway node on all three networks. In this example, noClient network parameters were specified in the global section of the configuration file, so they mustbe specified for the node:

[DC1-G1] NODE_TYPE = VM_API_Gateway


CLIENT_NETWORK_CONFIG = STATIC CLIENT_NETWORK_TARGET = SG-Client-Network CLIENT_NETWORK_MASK = 255.255.255.0 CLIENT_NETWORK_GATEWAY = 10.4.0.1 CLIENT_NETWORK_IP = 10.4.0.5

ADMIN_IP = 10.1.0.2

Non-primary Admin Node

The following additional settings are required for non-primary Admin Nodes:

• NODE_TYPE: VM_Admin_Node

• ADMIN_ROLE: Non-Primary

This example entry is for a non-primary Admin Node that is not on the Client network:

[DC2-ADM1] ADMIN_ROLE = Non-Primary NODE_TYPE = VM_Admin_Node

GRID_NETWORK_TARGET = SG-Grid-Network GRID_NETWORK_IP = 10.1.0.6 ADMIN_NETWORK_IP = 10.3.0.6

ADMIN_IP = 10.1.0.2

The following additional setting is optional for non-primary Admin Nodes:

• DISK: By default, Admin Nodes are assigned two additional 200 GB hard disks for audit anddatabase use. You can increase these settings using the DISK parameter. For example:

DISK = INSTANCES=2, CAPACITY=300

Note: For Admin nodes, INSTANCES must always equal 2.

Related references

How grid nodes discover the primary Admin Node on page 20


Running the Bash script

You can use the deploy-vsphere-ovftool.sh Bash script and the deploy-vsphere-ovftool.ini configuration file you modified to automate the deployment of StorageGRIDWebscale grid nodes in VMware vSphere.

Before you begin

• You have created a deploy-vsphere-ovftool.ini configuration file for your environment.

About this task

You can use the help available with the Bash script by entering the help commands (-h/--help). Forexample:

~jsmith/deploy-vsphere-ovftool.sh -h

or

~jsmith/deploy-vsphere-ovftool.sh --help

Steps

1. Log in to the Linux machine you are using to run the Bash script.

2. To deploy all grid nodes, run the Bash script with the appropriate options for your environment.

For example:

~jsmith/deploy-vsphere-ovftool.sh --username=jsmith --password=pwd ~jsmith/deploy-vsphere-ovftool.ini

3. If a grid node failed to deploy because of an error, resolve the error and rerun the Bash script foronly that node.

For example:

~jsmith/deploy-vsphere-ovftool.sh --username=jsmith --password=pwd --single-node="DC1-S3" ~jsmith/deploy-vsphere-ovftool.ini

Result

The deployment is complete when the status for each node is “Passed.”

Deployment Summary+-----------------------------+----------+----------------------+| node | attempts | status |+-----------------------------+----------+----------------------+| DC1-ADM1 | 1 | Passed || DC1-G1 | 1 | Passed || DC1-S1 | 1 | Passed || DC1-S2 | 1 | Passed || DC1-S3 | 1 | Passed |+-----------------------------+----------+----------------------+


Automating the configuration of StorageGRID WebscaleAfter deploying virtual grid nodes and appliance grid nodes, you can automate the configuration ofthe StorageGRID Webscale system.

Before you begin

You must know the location of the following files from the installation package.


configure-storagegrid.py Python script used to automate theconfiguration

configure-storagegrid.sample.json Sample configuration file for use with the script

configure-storagegrid.blank.json Blank configuration file for use with the script

About this task

You can use the configure-storagegrid.py Python script along with a modified version of thesample configuration file (configure-storagegrid.json) to automate the configuration of yourStorageGRID Webscale system.

Note: You can also configure the system using the Grid Management Interface (see “Navigating tothe Grid Management Interface”) or the Installation API (see “StorageGRID Webscale InstallationAPI overview”)

Steps

1. Log in to the Linux machine you are using to run the Python script.

2. Run the Python script with the appropriate options for your environment.

For example:

~jsmith/storagegrid/configure-storagegrid.py ~jsmith/storagegrid/configurestoragegrid.json --start-install

Result

A sgws-recovery-package.zip file is generated during the configuration process anddownloaded to the computer you are using to run the installation and configuration process. You mustback up the Recovery Package file. For example, copy it to a secure, backed up network location andto a secure cloud storage location.

Important: The Recovery Package file must be secured because it contains encryption keys andpasswords that can be used to obtain data from the StorageGRID Webscale system.

If you specified that random passwords should be generated, you need to extract thePasswords.txt file and look for the passwords required to access your StorageGRID Webscalesystem.

########################################################################### The StorageGRID "recovery package" has been downloaded as: ########## ./sgws-recovery-package.zip ########## Safeguard this file as it will be needed in case of a ########## StorageGRID node recovery. ###########################################################################


Your StorageGRID Webscale system is installed and configured when a confirmation message isdisplayed.

StorageGRID has been configured and installed.

Related concepts

StorageGRID Webscale Installation API overview on page 58

Related tasks

Navigating to the Grid Management Interface on page 36

Automating the configuration and installation of applianceStorage Nodes

You can use the configure-sga.py script to configure and install StorageGRID Webscaleappliance Storage Nodes.

Before you begin

• All StorageGRID Webscale appliance networking configuration has been completed using theStorageGRID Webscale Appliance Installer.

• You know the location of the configure-sga.py file from the installation package.

Steps

1. Log in to the Linux machine you are using to run the Python script.

2. For help with the script syntax and to see a list of the available parameters, enter the following:

configure-sga.py --help

The configure-sga.py script uses four subcommands: configure, install, monitor, andreboot. To get help for each subcommand, enter the following:

configure-sga.py subcommand --help

3. To confirm the current configuration of the appliance Storage Node, enter the following:

configure-sga.py configure SGA-INSTALL-IP

The results show current IP information for the appliance, including the IP address of the primaryAdmin Node and information about the Admin, Grid, and Client networks.

4. If you need to change any of the values in the current configuration, use the configuresubcommand to update them. For example, if you want to change the IP address for the primaryAdmin Node to 10.224.2.99, enter the following:

configure-sga.py configure --admin-ip 10.224.2.99 SGA-INSTALL-IP


5. When you are satisfied with the configuration, use the install and monitor subcommands toinstall the appliance:

configure-sga.py install --monitor --monitor-delta SGA-INSTALL-IP

6. If you are experiencing difficulties trying to configure the appliance and want to try rebooting it,enter the following:

configure-sga.py reboot SGA-INSTALL-IP


StorageGRID Webscale Installation API overview

StorageGRID Webscale provides a REST API for performing grid installation tasks.

The Installation API is only available when you are initially configuring your StorageGRIDWebscale system, and in the event that you need to perform a primary Admin Node recovery. TheInstallation API can be accessed over HTTPS from the Grid Management Interface.

StorageGRID Webscale Installation API documentation

The StorageGRID Webscale Installation API uses the Swagger open source API platform to providethe API documentation. Swagger allows both developers and non-developers to interact with the APIin a user interface that illustrates how the API responds to parameters and options. Thisdocumentation assumes that you are familiar with standard web technologies and the JSON(JavaScript Object Notation) data format.

Attention: Any API operations you perform using the Swagger user interface are live operations.Be careful not to create, update, or delete configuration or other data by mistake.

You can access the StorageGRID Webscale Installation API documentation by navigating to theinstallation web page on the primary Admin Node and selecting Help > API Docs in the webapplication header.

API

Each REST API command includes the API's URL, an HTTP action, any required or optional URLparameters, and an expected API response.

The StorageGRID Webscale Installation API includes the following sections:

• config – Operations related to the product release and versions of the API. You can list theproduct release version and the major versions of the API supported by that release.

• grid – Grid-level configuration operations. You can get and update grid settings, including griddetails, Grid Network subnets, grid passwords, and NTP and DNS server IP addresses.

• nodes – Node-level configuration operations. You can retrieve a list of grid nodes, delete a gridnode, configure a grid node, view a grid node, and reset a grid node's configuration.

• provision – Provisioning operations. You can start the provisioning operation and view the statusof the provisioning operation.

• recovery – Primary Admin Node recovery operations. You can reset information, upload theRecover Package, start the recovery, and view the status of the recovery operation.

• recovery-package – Operations to download the Recovery Package.

• sites – Site-level configuration operations. You can create, view, delete, and modify a site.

58

Where to go next

After completing an installation, you must perform a series of integration and configuration steps.Some steps are required; others are optional.

Required tasks

• Configure VMware vSphere Hypervisor for automatic restart.

You must configure the hypervisor to restart the virtual machines when the server restarts.Without an automatic restart, the virtual machines and grid nodes remain shut down after theserver restarts. For details, see the VMware vSphere Hypervisor documentation.

• Configure the StorageGRID Webscale system’s information lifecycle management (ILM) policy.

For information on defining and setting up an appropriate ILM policy, see “Understandinginformation lifecycle management” and “Configuring information lifecycle management” in theAdministrator Guide.

• Create accounts for users and administrators.

You need to set up accounts with the appropriate permissions for any other users that will accessthe system. For more information, see “Managing Accounts” in the Administrator Guide.

• Configure Archive Nodes

◦ If your StorageGRID Webscale system includes any Archive Nodes, you must configure theArchive Node's connection to the target external archival storage system. For moreinformation, see the Administrator Guide.

◦ If any Archive Nodes will use Tivoli Storage Manager as the external archival storage system,you must configure Tivoli Storage Manager. For more information, see the "Integrating TivoliStorage Manager" section in the Administrator Guide.

• Integrate and test API client applications with your StorageGRID Webscale system.

You need to configure the API client applications you use to upload objects to your StorageGRIDWebscale system. For more information, see the appropriate guide for the API you will be using:

◦ If you are using the S3 API, see the Simple Storage Service Implementation Guide.

◦ If you are using the Swift API, see the Swift Implementation Guide.

◦ If you are using the CDMI API, see Cloud Data Management Interface ImplementationGuide.

• If your installation includes StorageGRID Webscale appliance Storage Nodes, use SANtricityStorage Manager to complete the following tasks:

◦ Connect to each StorageGRID Webscale appliance.

◦ Verify receipt of AutoSupport data.

For details, see the StorageGRID Webscale and SANtricity Storage Manager documentation onthe NetApp Support Site.

Optional tasks

• Configure email notifications.

You can configure the mailing lists and contents of notification emails for system alarms andservice status changes. For more information, see the “Configuring notifications” section in theAdministrator Guide.

59

• Configure SNMP monitoring.

You can configure the settings for the Simple Network Management Protocol (SNMP) agent usedto monitor system status. For more information, see the “Configure SNMP monitoring” section inthe Administrator Guide.

• Reconfigure IP addresses.

If any of the grid node IP addresses have changed since you planned your deployment (andgenerated the SAID package), you need to updated them. For details, see the “Change IPAddresses” section in the Maintenance Guide.

• Configure storage encryption.

You can turn on encryption for stored objects, if required. For more information, see the“Configure stored object encryption” section in the Administrator Guide.

• Configure storage compression.

You can turn on compression to reduce the size of stored objects, if required. For moreinformation, see the “Configure stored object compression” section in the Administrator Guide.

• Configure access to audit shares.

You can configure access to the system for auditing purposes, either through a Common InternetFile System (CIFS) or NFS (Network File System) file share. For more information, see“Configuring audit client access” in the Administrator Guide.

Related information

StorageGRID Webscale 10.4 Administrator Guide

StorageGRID Webscale 10.4 Audit Message Reference


StorageGRID Webscale 10.4 Maintenance Guide for VMware Deployments

StorageGRID Webscale 10.4 Release Notes

StorageGRID Webscale 10.4 S3 (Simple Storage Service) Implementation Guide

StorageGRID Webscale 10.4 Swift Implementation Guide

StorageGRID Webscale 10.3 Cloud Data Management Interface Implementation Guide

StorageGRID Webscale 10.4 Troubleshooting Guide

NetApp Documentation: SANtricity Storage Manager

StorageGRID Webscale NAS Bridge 2.0.2 Installation and Setup Guide

StorageGRID Webscale NAS Bridge 2.0.2 Administration Guide











http://mysupport.netapp.com/documentation/productlibrary/index.html?productID=61197



Troubleshooting

This section includes troubleshooting topics to help you identify and solve problems that might occurwhile installing your StorageGRID Webscale system.

If problems persist, contact technical support. The following are the main installation log files:

• /var/local/log/install.log (found on all grid nodes)

• /var/local/log/gdu-console.log (found on the primary Admin Node)

Virtual machine resource reservation requires adjustmentOVF files include a resource reservation designed to ensure that each grid node has sufficient RAMand CPU to operate efficiently. If you create virtual machines by deploying these OVF files onVMware and the predefined number of resources are not available, the virtual machines will not start.

About this task

If you are certain that the VM host has sufficient resources for each grid node, manually adjust theresources allocated for each virtual machine, and then try starting the virtual machines.

Steps

1. In the VMware vSphere Hypervisor client tree, select the virtual machine that is not started.

2. Right‐click the virtual machine, and select Edit Settings.

3. From the Virtual Machines Properties window, select the Resources tab.

4. Adjust the resources allocated to the virtual machine:

a. Select CPU, and then use the Reservation slider to adjust the MHz reserved for this virtualmachine.

b. Select Memory, and then use the Reservation slider to adjust the MB reserved for this virtualmachine.

5. Click OK.

6. Repeat as required for other virtual machines hosted on the same VM host.

StorageGRID Webscale Appliance Installer errorsIf you encounter issues during the StorageGRID Webscale appliance installation, you might find ithelpful to review troubleshooting information.

Failed to download new provisioning progress data

Issue

This message occurs when the installation cannot obtain provisioning data.

Cause

This could occur if the installation encounters a system or power failure.

61

Corrective action

1. Check the StorageGRID Webscale Appliance Installation web page:

a. Browse to the following URL: http://Management_Port_IP:8080

Management_Port_IP is the IP address of Management Port 1 on the E5600SGcontroller (determined during the physical installation).

The StorageGRID Webscale Appliance Installation Home web page appears:

After you install the appliance, the status for each of the procedures on the webpage indicates that the procedure is complete.

b. Refresh the appliance installation web page.

2. Check the StorageGRID Webscale Installer web page:

a. Open a browser and enter the IP address configured when deploying StorageGRIDWebscale.

The StorageGRID Webscale installation page is displayed, listing the status of thegrid node installation.

b. Click Modify an existing system.

c. Note the completion percentage.

3. Check for hardware errors in SANtricity Storage Manager.

4. If hardware errors appear in SANtricity Storage Manager, fix them and reboot theappliance.

5. If hardware errors do not appear in SANtricity Storage Manager, obtain the installationlogs.

For details about logs, see the Troubleshooting Guide.

6. If you cannot resolve the issue, contact technical support.

Related information

StorageGRID Webscale 10.4 Troubleshooting Guide

NetApp Support

Storage-related error during software installation

Issue

The StorageGRID Webscale Appliance Installer issues a storage-related error message,such as Cannot create volume group.




Cause

This could occur due to several possible reasons, including that the appliance is not cabledcorrectly, an installation file is missing or corrupt, or a power failure occurred.

Corrective action

1. Ping the appliance:

ping E2700_controller_IP.

2. Check the logs on the E2700 controller.

3. In SANtricity Storage Manager, look at the status of the E2700 controller.

4. Check the StorageGRID Webscale Appliance Installation web page:

a. Browse to the following URL: http://Management_Port_IP:8080

Management_Port_IP is the IP address of Management Port 1 on the E5600SGcontroller (determined during the physical installation).

The StorageGRID Webscale Appliance Installation Home web page appears:

b. Click Reboot to reboot the appliance. If the Reboot button does not appear, go tohttp://ip:8080/reboot.

5. If this does not resolve the connection issue, contact technical support.

Related information

NetApp Support

Troubleshooting | 63


Glossary

ACL

Access control list. Specifies which users or groups of users are allowed to access anobject and what operations are permitted, for example, read, write, and execute.

active-backup mode

A method for bonding two physical ports together for redundancy.

ADC service

Administrative Domain Controller. The ADC service maintains topology information,provides authentication services, and responds to queries from the LDR, CMN, and CLBservices. The ADC service is present on each of the first three Storage Nodes installed at asite.

ADE

Asynchronous Distributed Environment. Proprietary development environment used as aframework for services within the StorageGRID Webscale system.

Admin Node

The Admin Node provides services for the web interface, system configuration, and auditlogs. See also, primary Admin Node.

Amazon S3

Proprietary web service from Amazon for the storage and retrieval of data.

AMS service

Audit Management System. The AMS service monitors and logs all audited system eventsand transactions to a text log file. The AMS service is present on the Admin Node.

API Gateway Node

An API Gateway Node provides load balancing functionality to the StorageGRIDWebscale system and is used to distribute the workload when multiple client applicationsare performing ingest and retrieval operations. API Gateway Nodes include a ConnectionLoad Balancer (CLB) service.

ARC service

Archive. The ARC service provides the management interface with which you configureconnections to external archival storage such as the cloud through an S3 interface or tapethrough TSM middleware. The ARC service is present on the Archive Node.

Archive Node

The Archive Node manages the archiving of object data to an external archival storagesystem.

atom

Atoms are the lowest level component of the container data structure, and generallyencode a single piece of information.

audit message

Information about an event occurring in the StorageGRID Webscale system that iscaptured and logged to a file.

Base64

A standardized data encoding algorithm that enables 8-bit data to be converted into aformat that uses a smaller character set, enabling it to safely pass through legacy systems

64

that can process only basic (low order) ASCII text excluding control characters. See RFC2045 for more details.

bundle

A structured collection of configuration information used internally by variouscomponents of the StorageGRID Webscale system. Bundles are structured in containerformat.

Cassandra

An open-source database that is scalable and distributed, provides high availability, andhandles large amounts of data across multiple servers.

CBID

Content Block Identifier. A unique internal identifier of a piece of content within theStorageGRID Webscale system.

CDMI

Cloud Data Management Interface. An industry-standard defined by SNIA that includes aRESTful interface for object storage. For more information, see www.snia.org/cdmi.

CIDR

Classless Inter‐Domain Routing. A notation used to compactly describe a subnet maskused to define a range of IP addresses. In CIDR notation, the subnet mask is expressed asan IP address in dotted decimal notation, followed by a slash and the number of bits in thesubnet. For example, 192.0.2.0/24.

CLB service

Connection Load Balancer. The CLB service provides a gateway into the StorageGRIDWebscale system for client applications connecting through HTTP. The CLB service ispart of the API Gateway Node.

Cloud Data Management Interface

See CDMI.

CMN service

Configuration Management Node. The CMN service manages system‐wide configurationsand grid tasks. The CMN service is present on the primary Admin Node.

CMS service

Content Management System. The CMS service carries out the operations of the activeILM policy’s ILM rules, determining how object data is protected over time. The CMSservice is present on the Storage Node.

command

In HTTP, an instruction in the request header such as GET, HEAD, DELETE, OPTIONS,POST, or PUT. Also known as an HTTP method.

container

Created when an object is split into segments. A container object lists the headerinformation for all segments of the split object and is used by the LDR service to assemblethe segmented object when it is retrieved by a client application.

content block ID

See CBID.

content handle

See UUID.

CSTR

Null‐terminated, variable-length string.

Glossary | 65

http://www.snia.org/cdmi

DC

Data Center site.

DDS service

Distributed Data Store. The DDS service interfaces with the distributed key-value storeand manages object metadata. It distributes metadata copies to multiple instances of thedistributed key-value store so that metadata is always protected against loss.

distributed key value store

Data storage and retrieval that unlike a traditional relational database manages data acrossgrid nodes.

DNS

Domain Name System.

enablement layer

Used during installation to customize the Linux operating system installed on each gridnode. Only the packages needed to support the services hosted on the grid node areretained, which minimizes the overall footprint occupied by the operating system andmaximizes the security of each grid node.

Fibre Channel

A networking technology primarily used for storage.

Grid ID signed text block

A Base64 encoded block of cryptographically signed data that contains the grid ID. Seealso, provisioning.

grid node

The basic software building block for the StorageGRID Webscale system, for example,Admin Node or Storage Node. Each grid node type consists of a set of services thatperform a specialized set of tasks.

grid task

System-wide scripts used to trigger various actions that implement specific changes to theStorageGRID Webscale system. For example, most maintenance and expansionprocedures involve running grid tasks. Grid tasks are typically long-term operations thatspan many entities within the StorageGRID Webscale system. See also, Task Signed TextBlock.

ILM

Information Lifecycle Management. A process of managing content storage location andduration based on content value, cost of storage, performance access, regulatorycompliance, and other factors. See also, Admin Node and storage pool.

LACP

Link Aggregation Control Protocol. A method for bundling two or more physical portstogether to form a single logical channel.

LAN

Local Area Network. A network of interconnected computers that is restricted to a smallarea, such as a building or campus. A LAN can be considered a node to the Internet orother wide area network.

latency

Time duration for processing a transaction or transmitting a unit of data from end to end.When evaluating system performance, both throughput and latency need to be considered.See also, throughput.


LDR service

Local Distribution Router. The LDR service manages the storage and transfer of contentwithin the StorageGRID Webscale system. The LDR service is present on the StorageNode.

LUN

See object store.

mDNS

Multicast Domain Name System. A system for resolving IP addresses in a small networkwhere no DNS server has been installed.

metadata

Information related to or describing an object stored in the StorageGRID Webscalesystem; for example, ingest time.

MLAG

Multi-Chassis Link Aggregation Group. A type of link aggregation group that uses two(and sometimes more) switches to provide redundancy in case one of the switches fails.

MTU

Maximum transmission unit. The largest size packet or frame that can be sent in anytransmission.

namespace

A set whose elements are unique names. There is no guarantee that a name in onenamespace is not repeated in a different namespace.

nearline

A term describing data storage that is neither “online” (implying that it is instantlyavailable, like spinning disk) nor “offline” (which can include offsite storage media). Anexample of a nearline data storage location is a tape that is loaded in a tape library, but isnot mounted.

NFS

Network File System. A protocol (developed by SUN Microsystems) that enables accessto network files as if they were on local disks.

NMS service

Network Management System. The NMS service provides a web-based interface formanaging and monitoring the StorageGRID Webscale system. The NMS service is presenton the Admin Node. See also, Admin Node.

node ID

An identification number assigned to a service within the StorageGRID Webscale system.Each service (such as an NMS service or ADC service) must have a unique node ID. Thenumber is set during system configuration and tied to authentication certificates.

NTP

Network Time Protocol. A protocol used to synchronize distributed clocks over a variablelatency network, such as the Internet.

object

An artificial construct used to describe a system that divides content into data andmetadata.

object segmentation

A StorageGRID Webscale process that splits a large object into a collection of smallobjects (segments) and creates a segment container to track the collection. The segmentcontainer contains the UUID for the collection of small objects as well as the header

Glossary | 67

information for each small object in the collection. All of the small objects in thecollection are the same size. See also, segment container.

object storage

An approach to storing data where the data is accessed by unique identifiers and not by auser-defined hierarchy of directories and files. Each object has both data (for example, apicture) and metadata (for example, the date the picture was taken). Object storageoperations act on entire objects as opposed to reading and writing bytes as is commonlydone with files, and provided via APIs or HTTP instead of NAS (CIFS/NFS) or blockprotocols (iSCSI/ FC/FCOE).

object store

A configured file system on a disk volume. The configuration includes a specific directorystructure and resources initialized at system installation.

OID

Object Identifier. The unique identifier of an object.

primary Admin Node

Admin Node that hosts the CMN service. Each StorageGRID Webscale system has onlyone primary Admin Node. See also, Admin Node.

provisioning

The process of generating a new or updated Recovery Package and GPT repository. Seealso, SAID.

quorum

A simple majority: 50% + 1. Some system functionality requires a quorum of the totalnumber of a particular service type.

Recovery Package

A .zip file containing deployment-specific files and software needed to install, expand,upgrade, and maintain a StorageGRID Webscale system. The package also containssystem-specific configuration and integration information, including server hostnames andIP addresses, and highly confidential passwords needed during system maintenance,upgrade, and expansion. See also, SAID.

SAID

Software Activation and Integration Data. The component in the Recovery Package thatincludes the Passwords.txt file.

SATA

Serial Advanced Technology Attachment. A connection technology used to connect serverand storage devices.

SCSI

Small Computer System Interface. A connection technology used to connect servers andperipheral devices, such as storage systems.

segment container

An object created by the StorageGRID Webscale system during the segmentation process.Object segmentation splits a large object into a collection of small objects (segments) andcreates a segment container to track the collection. A segment container contains theUUID for the collection of segmented objects as well as the header information for eachsegment in the collection. When assembled, the collection of segments creates the originalobject. See also, object segmentation.

server

Used when specifically referring to hardware. Might also refer to a virtual machine.


service

A unit of the StorageGRID Webscale system, such as the ADC service, NMS service, orSSM service. Each service performs unique tasks critical to the normal operations of aStorageGRID Webscale system.

SQL

Structured Query Language. An industry-standard interface language for managingrelational databases. An SQL database is one that supports the SQL interface.

ssh

Secure Shell. A UNIX shell program and supporting protocols used to log in to a remotecomputer and run commands over an authenticated and encrypted channel.

SSL

Secure Socket Layer. The original cryptographic protocol used to enable securecommunications over the Internet. See also, TLS.

SSM service

Server Status Monitor. A component of the StorageGRID Webscale software that monitorshardware conditions and reports to the NMS service. Every grid node runs an instance ofthe SSM service.

Storage Node

The Storage Node provides storage capacity and services to store, move, verify, andretrieve objects stored on disks.

storage pool

The element of an ILM rule that determines the location where an object is stored.

storage volume

See object store

StorageGRID

A registered trademark of NetApp, Inc., used for an object storage grid architecture andsoftware system.

Task Signed Text Block

A Base64 encoded block of cryptographically signed data that provides the set ofinstructions that define a grid task.

TCP/IP

Transmission Control Protocol/Internet Protocol. A process of encapsulating andtransmitting packet data over a network. It includes positive acknowledgment oftransmissions.

throughput

The amount of data that can be transmitted or the number of transactions that can beprocessed by a system or subsystem in a given period of time. See also, latency.

Tivoli Storage Manager

IBM storage middleware product that manages storage and retrieval of data fromremovable storage resources.

TLS

Transport Layer Security. A cryptographic protocol used to enable secure communicationsover the Internet. See RFC 2246 for more details.

transfer syntax

The parameters, such as the byte order and compression method, needed to exchange databetween systems.

Glossary | 69

URI

Universal Resource Identifier. A generic set of all names or addresses used to refer toresources that can be served from a computer system. These addresses are represented asshort text strings.

UTC

A language-independent international abbreviation, UTC is neither English nor French. Itmeans both “Coordinated Universal Time” and “Temps Universel Coordonné.” UTCrefers to the standard time common to every place in the world.

UUID

Universally Unique Identifier. Unique identifier for each piece of content in theStorageGRID Webscale system. UUIDs provide client applications with a content handlethat permits them to access content in a way that does not interfere with the StorageGRIDWebscale system’s management of that same content. A 128-bit number that is guaranteedto be unique. See RFC 4122 for more details.

virtual machine (VM)

A software platform that enables the installation of an operating system and software,substituting for a physical server and permitting the sharing of physical server resourcesamong several virtual servers.

VLAN

Virtual local area network (or virtual LAN). A group of devices that are located ondifferent LAN segments but are configured to communicate as if they were attached to thesame network switch.

WAN

Wide area network. A network of interconnected computers that covers a large geographicarea, such as a country.

XFS

A scalable, high-performance journaled file system originally developed by SiliconGraphics.

XML

Extensible Markup Language. A text format for the extensible representation of structuredinformation; classified by type and managed like a database. XML has the advantages ofbeing verifiable, human readable, and easily interchangeable between different systems.


Copyright information

Copyright © 1994–2017 NetApp, Inc. All rights reserved. Printed in the U.S.

No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical, including photocopying, recording, taping, or storage in anelectronic retrieval system—without prior written permission of the copyright owner.

Software derived from copyrighted NetApp material is subject to the following license anddisclaimer:

THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS ORIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE,WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANYDIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIALDAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTEGOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING INANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THEPOSSIBILITY OF SUCH DAMAGE.

NetApp reserves the right to change any products described herein at any time, and without notice.NetApp assumes no responsibility or liability arising from the use of products described herein,except as expressly agreed to in writing by NetApp. The use or purchase of this product does notconvey a license under any patent rights, trademark rights, or any other intellectual property rights ofNetApp.

The product described in this manual may be protected by one or more U.S. patents, foreign patents,or pending applications.

RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject torestrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and ComputerSoftware clause at DFARS 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).

71

Trademark information

Active IQ, AltaVault, Arch Design, ASUP, AutoSupport, Campaign Express, Clustered Data ONTAP,Customer Fitness, Data ONTAP, DataMotion, Element, Fitness, Flash Accel, Flash Cache, FlashPool, FlexArray, FlexCache, FlexClone, FlexPod, FlexScale, FlexShare, FlexVol, FPolicy, Fueled bySolidFire, GetSuccessful, Helix Design, LockVault, Manage ONTAP, MetroCluster, MultiStore,NetApp, NetApp Insight, OnCommand, ONTAP, ONTAPI, RAID DP, RAID-TEC, SANscreen,SANshare, SANtricity, SecureShare, Simplicity, Simulate ONTAP, Snap Creator, SnapCenter,SnapCopy, SnapDrive, SnapIntegrator, SnapLock, SnapManager, SnapMirror, SnapMover,SnapProtect, SnapRestore, Snapshot, SnapValidator, SnapVault, SolidFire, SolidFire Helix,StorageGRID, SyncMirror, Tech OnTap, Unbound Cloud, and WAFL and other names aretrademarks or registered trademarks of NetApp, Inc., in the United States, and/or other countries. Allother brands or products are trademarks or registered trademarks of their respective holders andshould be treated as such. A current list of NetApp trademarks is available on the web.

http://www.netapp.com/us/legal/netapptmlist.aspx

72

http://www.netapp.com/us/legal/netapptmlist.aspx

How to send comments about documentation andreceive update notifications

You can help us to improve the quality of our documentation by sending us your feedback. You canreceive automatic notification when production-level (GA/FCS) documentation is initially released orimportant changes are made to existing production-level documents.

If you have suggestions for improving this document, send us your comments by email.

[email protected]

To help us direct your comments to the correct division, include in the subject line the product name,version, and operating system.

If you want to be notified automatically when production-level documentation is released orimportant changes are made to existing production-level documents, follow Twitter account@NetAppDoc.

You can also contact us in the following ways:

• NetApp, Inc., 495 East Java Drive, Sunnyvale, CA 94089 U.S.

• Telephone: +1 (408) 822-6000

• Fax: +1 (408) 822-4501

• Support telephone: +1 (888) 463-8277

73

mailto:[email protected]

Index

10-GbE portsconfiguring on controller 28

A

active-backup mode10-GbE controller ports 28

Admin networkdescription 10during deployment and configuration 13

Admin Nodeconfiguration file settings 48deploying 22virtual machine requirements 10

APIinstallation 58

API client applicationstesting and integrating 59

API Gateway Nodeconfiguration file settings 48deploying 22virtual machine requirements 10

applianceconfiguring 10-GbE ports 28connecting to the StorageGRID Webscale ApplianceInstaller 24deploying 24installing 33

approving grid nodesdescribed 39

Archive Nodeconfiguration file settings 48configuring external connection 59deploying 22virtual machine requirements 10

audit sharesconfiguring access to 59

automatedconfiguration 55, 56deployment of grid nodes 47

B

browserssupported 17

C

Cassandra databasestorage requirements for 16

Client networkdescription 10during deployment and configuration 13

clientsports required for communication 16

commentshow to send feedback about documentation 73

configuration

automating 55grid information 37overview 5, 36reviewing 44

configuration fileediting 48

connectivityconfiguring networks 25, 31

controller portsconfiguring 28

D

default gatewayduring deployment and configuration 13

deploy-vsphere-ovftool.iniediting 48

deploy-vsphere-ovftool.shediting configuration file for 48using to deploy grid nodes 54

deployingappliance Storage Nodes 24

deploymentBash script for 54description of 18information to gather about your environment 18overview 5planning 6tools 5virtual machine 20

documentationhow to receive automatic notification of changes to73how to send feedback about 73

downloading softwaresteps for 7

E

E5600SG controllertroubleshooting installation 61

email notificationsconfiguring 59

F

feedbackhow to send comments about documentation 73

G

gatewayduring deployment and configuration 13

gridconfiguring 37

Grid Management Interfacenavigating to 36

Grid network


description 10during deployment and configuration 13specifying subnets for 38

grid nodesapproving 39automated deployment 47, 54deploying 18deploying in VMware vSphere Hypervisor 22ports required for communication 14

H

hardware requirementsdescribed 9

I

ILM policyconfiguring 59

informationhow to send feedback about improvingdocumentation 73

installationadding sites 37automated configuration of appliance Storage Node56downloading software 7overview 5planning 6required materials 6setting IP address 33summary information for 44troubleshooting 61

installation APIoverview 58

installerconfiguring 10-GbE ports 28

IP addresseschanging 59

L

LACP mode10-GbE ports 28

licensinggrid configuration 37

N

network connectionsconfiguring 25, 31

networksdescription 10requirements for 10use during deployment and configuration 13

nodesdefault gateways 13deploying 18deploying with StorageGRID Webscale ApplianceInstaller 24

P

passwordsfor StorageGRID Webscale system 43

portsexternal client communications 16internal grid node communications 14

prerequisitesdeployment 18

primary Admin Nodeconfiguration file settings 48deploying 20IP address 20

provisioningtroubleshooting 61

R

required materialsinstallation 6

requirementsnetworking 10ports 14, 16virtual machines 10

resource reservationsadjusting for virtual machines 61

S

SANtricitytroubleshooting hardware errors 61

sitesadding to your StorageGRID Webscale system 37

SNMPconfiguring 59

softwarenetwork connections 25, 31setting installer IP address 33

software requirementsStorageGRID Webscale 9

SSH access pointcustomizing 59

storageconfiguring compression 59configuring encryption 59requirements for 16

Storage Nodeautomated configuration for appliance 56configuration file settings 48deploying 22, 24virtual machine requirements 10

StorageGRID Webscale Appliance Installerconnecting to 24

StorageGRID Webscale systempasswords 43software requirements for 9

suggestionshow to send feedback about documentation 73

T

troubleshooting

Index | 75

failure to download new provisioning progress data61installation 61storage-related error 62

Twitterhow to receive automatic notification ofdocumentation changes 73

V

virtual machinesadjusting resource reservations for 61

deploying and starting 20requirements 10

VLAN support10-GbE controller ports 28

VMware vSphere Hypervisordeploying grid nodes in 22

W

web browserssupported 17


VMware Deployments Software Installation Guide for

Documents

Transcript of VMware Deployments Software Installation Guide for