HPE OmniStack 3.7.7 for vSphere Deployment Guide · Before installing the HPE SimpliVity software and deploying HPE OmniStack hosts, verify that your vSphere environment includes

Hewlett PackardEnterprise

HPE OmniStack 3.7.7 for vSphereDeployment Guide

Part number: P00121-008Published: December 2018

2

© 2018 Hewlett Packard Enterprise Development LP

NoticesThe information contained herein is subject to change without notice. The only warranties for Hewlett PackardEnterprise products and services are set forth in the express warranty statements accompanying such productsand services. Nothing herein should be construed as constituting an additional warranty. Hewlett PackardEnterprise shall not be liable for technical or editorial errors or omissions contained herein.

Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use,or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer SoftwareDocumentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor'sstandard commercial license.

Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett PackardEnterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprisewebsite.

Contents 3

Contents

Chapter 1: HPE OmniStack host deployment overview......................5HPE OmniStack hosts...................................................................................................................5HPE OmniStack host deployment.................................................................................................5Deployment tasks summary..........................................................................................................5

Chapter 2: Install the HPE SimpliVity software....................................7HPE SimpliVity software............................................................................................................... 7

Download the HPE SimpliVity software..............................................................................7VMware products...........................................................................................................................8

Linked Mode and deployment............................................................................................ 9Deployment Manager.................................................................................................................... 9

Deployment Manager screen icons.................................................................................... 9Deployment Manager software requirements...................................................................10Install Deployment Manager............................................................................................. 10Uninstall Deployment Manager.........................................................................................11

Arbiter.......................................................................................................................................... 11Arbiter requirements..........................................................................................................12Install Arbiter..................................................................................................................... 13Uninstall Arbiter................................................................................................................. 13

HPE SimpliVity Plug-in for vSphere............................................................................................14HPE SimpliVity Plug-in requirements............................................................................... 14Install HPE SimpliVity Plug-in on Windows Server.......................................................... 15Uninstall HPE SimpliVity Plug-in from Windows Server................................................... 18Install HPE SimpliVity Plug-in on vCenter Server Appliance............................................18Uninstall HPE SimpliVity Plug-in from vCenter Server Appliance.................................... 20

Chapter 3: Verify the deployment environment................................. 21Deployment environment requirements...................................................................................... 21HPE OmniStack user accounts...................................................................................................21

ESXi host root account..................................................................................................... 21vCenter Server single sign-on account.............................................................................21HPE OmniStack CLI account............................................................................................21

Networking requirements.............................................................................................................21Maximum transmission unit.............................................................................................. 22Network address and vSphere inventory requirements....................................................22Ports required for HPE OmniStack hosts......................................................................... 23

HPE OmniStack host requirements............................................................................................ 25

Contents 4

Deployment checklist...................................................................................................................26

Chapter 4: Deploy OmniStack hosts...................................................28HPE OmniStack host deployment...............................................................................................28Deployment prerequisites............................................................................................................29HPE OmniStack host discovery..................................................................................................29

Connect to a remote management interface.................................................................... 30Optional: Assign a static IP address to an HPE OmniStack host.....................................30

Deploy an HPE OmniStack host.................................................................................................30HPE OmniStack host heartbeats................................................................................................ 45Review post-deployment tasks................................................................................................... 45

Chapter 5: Troubleshooting................................................................. 47Recoverable deployment errors.................................................................................................. 47

Reset HPE OmniStack host discovery state.................................................................... 48Reset the power switch on an HPE SimpliVity 380 Gen9 host........................................ 49Reset the power switch on an HPE SimpliVity 380 Gen10 host...................................... 52

General deployment issues.........................................................................................................54Cannot connect to port 9299............................................................................................54IP address already assigned............................................................................................ 55Disconnected hosts........................................................................................................... 55Network connection timeout..............................................................................................55.NET needs to be upgraded............................................................................................. 55HPE OmniStack software version outdated..................................................................... 56Cannot connect to HPE OmniStack host......................................................................... 56IP address already in use.................................................................................................56IP address associated with failed deployment................................................................. 56

Collect deployment logs.............................................................................................................. 57

Appendix A: Support and other resources........................................ 58Support and other resources...................................................................................................... 58

Accessing Hewlett Packard Enterprise Support............................................................... 58Accessing updates............................................................................................................ 58Customer self repair..........................................................................................................59Remote support.................................................................................................................59Warranty information......................................................................................................... 59Regulatory information...................................................................................................... 60

Documentation feedback.............................................................................................................60

Chapter 1: HPE OmniStack host deployment overview 5

Chapter 1: HPE OmniStack hostdeployment overviewThis section contains the following topics:

• HPE OmniStack hosts

• HPE OmniStack host deployment

• Deployment tasks summary

HPE OmniStack hostsHPE OmniStack, from HPE SimpliVity, is a converged server and storage solution. It provides:

• High availability

• Scalability

• Efficient disaster protection

• Global unified management

Each HPE OmniStack host comes with the following pre-installed software:

• HPE OmniStack

• HPE SimpliVity vStorage APIs for Array Integration (VAAI)-network-attached storage (NAS) plug-in

To enable key functionality such as high availability, dynamic resource sharing, and efficient data movement, youshould deploy HPE OmniStack hosts in sets of two within a cluster. As capacity and performance needs increase,you can add more HPE OmniStack hosts without disruption to users. This network of hosts is called an HPESimpliVity federation.

Once you deploy HPE OmniStack hosts to a cluster, you can manage them and their related virtual objects usingHPE SimpliVity Plug-in for vSphere Web Client.

HPE OmniStack host deploymentYou can deploy multiple HPE OmniStack hosts to a cluster at once using HPE OmniStack Deployment Manager(with up to 16 HPE OmniStack hosts in a cluster). Before you begin using the application, install all the requiredsoftware and verify your network environment.

After you complete the necessary tasks, you can run Deployment Manager and follow the prompts to deploy oneor more hosts to vCenter Server. You can then manage the virtual hosts and related objects using HPE SimpliVityfeatures in HPE SimpliVity Plug-in for vSphere (Flex or HTML5).

Deployment tasks summaryTo deploy HPE OmniStack hosts to an existing cluster in vCenter Server, you need to have the appropriatesoftware installed and know the network details required to run HPE OmniStack Deployment Manager. This chartprovides more details on all the tasks you need to complete in the order shown.

Chapter 1: HPE OmniStack host deployment overview 6

Task Description

Locate or download the HPEOmniStack Software.

Download the HPE SimpliVity software from the Customer Support(support.hpe.com) website for the HPE OmniStack version you use. Thisincludes Deployment Manager and Arbiter.

You can also download HPE SimpliVity Plug-in for vSphere (Flex or HTML5),but it is not required to deploy hosts. (You use it to manage hosts in thehypervisor after you deploy them.)

Install the HPE SimpliVitysoftware.

Install Deployment Manager on the Windows computer you plan to use todeploy HPE OmniStack hosts. Install Arbiter on a Windows vCenter Serverwhere you want to deploy hosts or a different Windows computer that thehosts can access. You can install HPE SimpliVity Plug-in on the vCenterServer before or after you deploy hosts.

NOTE:

The Windows computer and HPE OmniStack hosts must be on thesame broadcast domain for Deployment Manager to discover the hostsautomatically on the network. If the HPE OmniStack hosts are not on thesame broadcast domain but are on a reachable network, you must providethe IP address of each host manually.

For more information, see "HPE OmniStack host discovery."

Verify the network environment. Check the accounts to ensure access to the applications, verify the networkand required ports for HPE OmniStack, and review the deployment checklistprovided in this guide.

Deploy an HPE OmniStack host. When you first run Deployment Manager, you may want to choose the optionto create a configuration file. That way, you can save the network settingsin a file to use it as a template. Then, the next time you use DeploymentManager, you can import it when you deploy another HPE OmniStack host.You can make any necessary modifications as you scroll through DeploymentManager.

Perform post-deployment tasks. Perform the post-deployment tasks listed in the "Post-deployment Tasks"topic after you successfully deploy an HPE OmniStack host.

http://support.hpe.com


Chapter 2: Install the HPE SimpliVity software 7

Chapter 2: Install the HPE SimpliVitysoftwareThis section contains the following topics:

• HPE SimpliVity software

• VMware products

• Deployment Manager

• Arbiter

• HPE SimpliVity Plug-in for vSphere

HPE SimpliVity softwareBefore you deploy HPE OmniStack hosts to a cluster in vCenter Server, install the following software:

• Deployment Manager: Enables you to use a wizard to deploy the HPE OmniStack hosts. You can manuallyenter network information when prompted or import a configuration file (with settings that you saved from anearlier deployment) to automatically populate fields. Install Deployment Manager on a supported WindowServer or Windows computer.

• Arbiter: Enables communication between OmniStack and vCenter Server. This communication enables you todeploy and manage HPE OmniStack hosts and related objects. Arbiter preserves the health of the federationby acting as an independent witness and providing the tie-breaking vote when a federation contains an evennumber of HPE OmniStack hosts. Install Arbiter on the vCenter Server where you want to deploy hosts or on adifferent Windows computer that the hosts can access.

• HPE SimpliVity Plug-in for vSphere (Flex or HTML5): Provides HPE SimpliVity options for you to manage yourhosts and other HPE SimpliVity objects.

Download the HPE SimpliVity softwareTo deploy hosts, you need Deployment Manager and Arbiter software. To manage the hosts and other HPESimpliVity objects, you need to install HPE SimpliVity Plug-in for vSphere. Download this software from the HPESimpliVity Customer Support (support.hpe.com) website.

Procedure

1. Go to the HPE SimpliVity Customer Support website (support.hpe.com).

2. Log in with your HPE account.

3. Enter the OmniStack version you need in the Search field (for example, OmniStack 3.7.7) to list the HPEOmniStack supported platforms (for example, DL380).

NOTE:

For existing federations, the hosts previously deployed to clusters must use HPE OmniStack 3.7.6 or later todeploy multiple hosts at once.

4. Locate the platform model you use from the list and click Drivers and Software.

5. Click the link for the hypervisor you use (for example, HPE OmniStack for vSphere).

6. Click Obtain Software.




7. Log in with your HP Passport account. If you do not have an HPE Passport account, create one.

8. Enter your Service Agreement Identification (SAID) number or select it from the Select an SAID drop-downlist.

NOTE:

The HPE Support agreement you received after purchasing your HPE product outlines your Supportcoverage. The agreement also lists your 12-digit SAID number. If you need assistance locating your SAIDnumber, contact your Hewlett Packard Enterprise representative.

9. From the Get Software tab, enter the name of the product you need to download in the Search field (forexample, HPE OmniStack software). The available downloads for your product appear in the Downloads list.(If necessary, you can also search for the download you need.)

10. Select the products from the Downloads list (for example, Deployment Manager, Arbiter, and HPE SimpliVityPlug-in for vSphere) and click Download.

NOTE:

You do not need to install the HPE SimpliVity Plug-in for vSphere software to install to deploy hosts. You useit to manage the hosts in the vSphere Client (Flex or HTML5) after you deploy hosts. But, you can also installit before you deploy hosts to check the status of the cluster as you deploy hosts.

11. Save the files in a location you can access.

NOTE:

The software includes a deploy installer image (IMG) file that you may need to use if you experienceissues deploying your host (for example, reset the power) and need to try the deployment more thanonce. To ensure you can use the image file with your server, write the raw image to a USB stick using anapplication such as Etcher (https://etcher.io/), Win32 Disk Imager (https://sourceforge.net/projects/win32diskimager/), Rufus (https://rufus.akeo.ie/), or the data duplicator (dd) command on Linux or Macoperating system after you download it. Then store it in a secure place in case you need it.

Next steps

See the following sections for details on requirements and steps to install the software.

VMware productsBefore installing the HPE SimpliVity software and deploying HPE OmniStack hosts, verify that your vSphereenvironment includes one of the following VMware products:

• vSphere vCenter Server 6.5 or 6.7.

• vCenter Server Appliance 6.5 or 6.7.

Either of the listed products comes with vSphere Web Client (Flex) or vSphere Client (HTML5).

If you do not have these products installed or you need to upgrade them, see the VMware documentation. If youneed to download the products or access tools, you need to know your VMware customer account credentials. Toaccess vCenter Server, you need an account with administrator privileges.

You can also use Enhanced Link Mode with vCenter Server (6.5 or 6.7) or vCenter Server Appliance (6.5 or 6.7).For more information on setting up Enhanced Link Mode, see the Platform Services Controller instructions in theVMware vCenter Server 6.5 or 6.7 documentation.

The HPE OmniStack hosts you want to deploy must use the same hypervisor version in the cluster. For example,if you use vCenter Server 6.7, you can deploy hosts that use ESXi 6.5 or 6.7. But all the HPE OmniStack hosts ina cluster need to use the same version (all ESXi 6.5 or 6.7).

https://etcher.io/

https://sourceforge.net/projects/win32diskimager/

https://sourceforge.net/projects/win32diskimager/

https://rufus.akeo.ie/


Linked Mode and deploymentAn HPE SimpliVity federation supports VMware vCenter Servers in Linked Mode and enables access to HPESimpliVity and VMware virtual objects.

Joining multiple vCenter Server systems using vCenter Server Linked Mode enables them to share information.To support a federation in linked mode using vCenter Server 6.5 or later, install single sign-on (SSO) usingmultisite mode (requires an Active Directory [AD] server for authentication). (HPE OmniStack supports up to fivelinked vCenter Servers.)

When you deploy HPE OmniStack hosts to a cluster, Deployment Manager displays the HPE SimpliVityfederation Information screen. In this screen, you specify if you want the hosts to create a federation in thecurrent vCenter Server or join an HPE SimpliVity federation in a vCenter Server in Linked Mode (or EnhancedLink Mode). If the HPE OmniStack hosts join a federation, specify the Virtual Controller IP address of an HPEOmniStack host in the existing federation to ensure that the hosts you plan to deploy locates it.

Deployment ManagerDeployment Manager is a stand-alone Windows application that configures and deploys HPE OmniStack hosts inan existing cluster.

With Deployment Manager, you can import data from a previously saved configuration (XML) file or manuallyenter the network settings to deploy an HPE OmniStack hosts. If you enter the settings manually, you can savethem in a configuration file before you deploy the host.

When you import an existing configuration file, Deployment Manager validates the informationand stores it in an XML file located in your home directory by default. The file name format is:starting_ip_address_timestamp.xml.

The first time you deploy hosts to a cluster, Deployment Manager creates the virtual switches (vSwitches) andport groups for the network connection that you specify. For example, the default vSwitch names are vSwitch0and vSwitch1 for a 1 Gb/s or 10 Gb/s network.

After you use Deployment Manager to deploy at least one HPE OmniStack host to a cluster, you can deploymultiple HPE OmniStack hosts to another cluster (if necessary).

NOTE:

Before you can deploy hosts, clusters need to exist in the hypervisor. For example, in vSphere Web Client, youneed to create a datacenter and create one or more clusters for the datacenter. HPE OmniStack hosts mustreside in one to 16 clusters. Each cluster can contain up to 16 HPE OmniStack hosts. For more information oncreating a cluster, see the HPE OmniStack for vSphere Administration Guide or the HPE SimpliVity Plug-in forvSphere Help.

Deployment Manager screen iconsDeployment Manager includes these icons at the top of each screen:

Icon Description

Blinks when deployment starts. Click it to open the status window. You can starta new deployment as the current one runs, but the cluster must contain at leastone previously deployed HPE OmniStack host. The icon also shows the number ofdeployments in progress.

Displays the Settings screen. Use this screen to set a timeout between DeploymentManager and the vCenter Server that is appropriate for your networking environment.


Icon Description

The default value is 30 seconds. The maximum value is 120 seconds. Any changesyou make in the Settings screen take effect the next time you run DeploymentManager.

You can also use the Settings screen to initiate the collection of deployment logs fortroubleshooting deployment issues.

Displays the version, patents, trademarks, and Hewlett Packard Enterprise contactinformation.

Deployment Manager software requirementsOnly use HPE OmniStack hosts with the same HPE OmniStack software version in the same cluster. (Do not mixversions.) For example, if your cluster contains hosts with HPE OmniStack 3.5.2, do not deploy hosts with HPEOmniStack 3.7.7 into that cluster. Upgrade the hosts that already reside in the cluster first, then deploy the newhosts with the same HPE OmniStack version. For more information on upgrading HPE OmniStack software, seethe HPE OmniStack for vSphere Upgrade Guide.

The following software is required to deploy HPE OmniStack hosts using Deployment Manager.

Operating System requirements

Deployment Manager is supported on these Windows operating systems:

• Windows Server 2016.

• Windows Server 2012 R2.

• Windows Server 2008 R2.

• Windows 8.1.

• Windows 7.

NOTE:

Check the .NET Framework version used on the computer you plan to use to deploy the HPE OmniStack hosts.Deployment Manager supports .Net Framework 4.7.1 or later. If necessary, upgrade .NET Framework to thatversion before you deploy hosts.

Third-party software requirements

Install the following third-party software on every Windows computer running Deployment Manager:

• Oracle® Java 1.8

• Microsoft® .NET Framework 4.7.1 web installer package or later.

NOTE:

Install only one version of the third-party software on the Windows computer you are using to deploy HPEOmniStack hosts. Uninstall an older version before you install a new version.

Install Deployment Manager

Before you begin

Before you install Deployment Manager on a supported Windows computer:


• Verify the required third-party software is installed on the Windows computer you are using to deploy the HPEOmniStack hosts. See "Deployment Manager requirements."

• Verify that you have 127 MB of available disk space on the Windows computer.

• If an older version of Deployment Manager is installed on the Windows computer, uninstall that version.

• Obtain the vCenter Server administrator credentials. These credentials are required to log on to DeploymentManager.

Procedure

1. Double-click the simplivity-deployment-manager-3.7.7.XXX.msi file.

2. Click Run and follow the prompts to accept the license agreement.

3. On the Select Installation Folder screen, accept the defaults or do any of the following:

• If you need to view the space available, click Disk Cost.

• To change the default location of the installation folder(C:\Program Files (x86)\Hewlett Packard Enterprise\DeploymentManager) or manuallyenter a new path, click Browse.

• If you want all users to access Deployment Manager or just the current user, leave the default of Everyone.

4. Click Next to continue through the screens.

5. Click Close to when the install process ends.

Uninstall Deployment Manager

Before you begin

Before uninstalling Deployment Manager, make sure you have administrator privileges to access the system.

Procedure

1. From the Start menu, click Control Panel > Programs > Uninstall a program.

2. From the list of installed programs, double-click HPE SimpliVity Deployment Manager.

3. To confirm that you want to delete the extension, click Yes.

4. Wait while the installer removes the software. When finished, click Next.

5. To close the information window, click OK.

ArbiterThe Arbiter software runs on the computer hosting a vCenter Server or on a different Windows computer that thehosts can access. It is required in every HPE SimpliVity federation.

Arbiter provides the tie-breaking vote when a cluster contains an even number of HPE OmniStack hosts. Forexample, if a cluster contains two HPE OmniStack hosts and one of those hosts loses connectivity with thecluster, Arbiter acts as the tie breaker.

When you run Deployment Manager, you specify the Arbiter location. For a computer other than the one withvCenter Server, you must specify the IP address to ensure communication with the federation.


Caution:

To ensure the best performance, install a new Arbiter for every 4,000 virtual machines and associate it withone or more clusters in a federation to distribute the workload.

For example, if your datacenter includes clusters that run several thousand virtual machines and youalready installed Arbiter on vCenter Server, install Arbiter on another Windows computer (separate from thecomputer with vCenter Server). Then, when you deploy hosts, select the cluster that needs its own Arbiterand enter the IP address of the computer that has it. (Do not install Arbiter on a virtual machine managedwithin the same cluster it serves.)

Arbiter requirementsYour version of Arbiter should match the version of HPE OmniStack used by your hosts. Review theserequirements before installing Arbiter on the computer with vCenter Server. (You can also install it on a differentWindows computer as long as the hosts in your federation can access it.)

NOTE:

The Arbiter application ensures the resiliency of the federation by acting as a tie-breaking vote in cluster failurescenarios that include an even number of HPE OmniStack hosts. It must run on the computer hosting vCenterServer or on another Windows computer. Do not install it on a virtual machine that resides on an HPE OmniStackhost or any host that uses an HPE SimpliVity datastore. Install the latest version of VMware tools on any virtualmachine that is hosting Arbiter. Installing Arbiter on a computer outside the federation ensures its availability.

Feature Requirement

CPU frequency 1.0 GHz or higher

Number of cores Single core/dual thread or better

Memory 1 GB (for Arbiter application)

NOTE:

Consult Microsoft documentation for OS memory requirements.

Persistent storage Minimum of 16 GB (HDD or SDD)

NOTE:

Set disk caching policy to write-through or write cache disabled.


Feature Requirement

Storage type Storage device capable of 80 IOPS per 128 virtual machines in the arbitrationcontrol domain. For example:

• 1 x 7.2K RPM HDD for up to 128 virtual machines.

• 1 x 10K RPM HDD for up to 256 virtual machines.

• 1 x SSD for up to 4096 virtual machines.

NOTE:

One Arbiter can control up to 4096 virtual machines.

Do not recover the Arbiter storage device to a previous point in time witha snapshot or backup and restore process or you could corrupt the virtualmachine data.

Network 1xGigE

Supported operating systems Windows Server 2008, 2008R2, 2012, 2012R2, 2016

Install Arbiter

Before you begin

Before you deploy HPE OmniStack hosts, install Arbiter.

Procedure

1. To start the setup wizard, click the simplivity-arbiter-n.n.n.n.msi file. (This file comes on the USBstick that ships with the product or you can download it from Customer Support (support.hpe.com).)

2. Click Run.

3. On the Welcome screen, click Next.

4. Select the license acceptance box and click Next.

The Setup Type screen opens.

5. Click Complete and then click Install.

6. In the Completed screen, click Finish.

Uninstall Arbiter

Before you begin

Before uninstalling Arbiter, make sure you have administrator privileges to access the system.

Procedure


2. From the list of installed programs, double-click HPE SimpliVity Arbiter.

3. To confirm that you want to delete the extension, click Yes.




5. To close the information window, click OK.

HPE SimpliVity Plug-in for vSphereThe HPE SimpliVity Plug-in for vSphere (Web Client [Flex] or Client [HTML5]) application allows you to manageyour HPE SimpliVity virtual inventory objects across the entire HPE SimpliVity federation using HPE SimpliVityfeatures. For example, you can access links to manage HPE SimpliVity clusters, hosts, backup policies,datastores, and virtual machines. After you deploy hosts, you can create HPE SimpliVity datastores, policies, andperform numerous tasks on virtual machines. For more details, see the Help that comes with the Plug-in.

HPE SimpliVity Plug-in requirements

Supported software

HPE SimpliVity Plug-in for vSphere (Web Client [Flex] or Client [HTML5]) supports the following:

Item Description

Software • VMware vSphere 6.7 Update 1 and 6.5 Update 2c

◦ For vSphere 6.7 Update 1: vCenter Server or vCenter Server Appliance withvSphere Web Client (Flex) or vSphere Client (HTML5)

◦ For vSphere 6.5 Update 2c: vCenter Server or vCenter Server Appliance withvSphere Web Client (Flex) or vSphere Client (HTML5)

HPE SimpliVity Plug-in supports Enhanced Link Mode with vCenter Server 6.7Update 1 and 6.5 Update 2c or with vCenter Server Appliance 6.7 Update 1 or 6.5Update 2c. For details on setting up Enhanced Link Mode, see the VMware vSpheredocumentation.

NOTE:

For the best performance when using Enhanced Link Mode, ensure that eachconnected vCenter Server contains at least one HPE OmniStack host. Do not use aconfiguration that has some linked vCenter Servers with HPE OmniStack hosts andother vCenter Servers without them.

Operating System • Windows Server 2008 R2 or Windows Server 2012 R2 or 2016 (64-bit)

• VMware vCenter Server Appliance (a preconfigured Linux virtual machine, 64-bit,optimized to run vCenter Server)


Item Description

Browsers Windows:

• Internet Explorer 11.0.96 or later

• Mozilla Firefox (latest available)

• Google Chrome (latest available)

Macintosh or Linux:

• Mozilla Firefox (latest available)

• Google Chrome (latest available)

NOTE:

There is a known Firefox and Chrome browser issue with Adobe Shockwave Flash27.0.0.170 that affects all versions of vSphere Web Client where Flash crashes and youcannot access the Client. For more details, see the VMware Knowledge Base article:Shockwave Flash crashes with vSphere Web Client 6.X (2151945).

Configuration requirements

For details on hardware requirements and how to use Enhanced Linked Mode with multiple vCenter Servers orvCenter Server Appliance systems, see the VMware vSphere documentation.

Hypervisor upgrade requirements

If you upgrade the ESXi version of your previously deployed HPE OmniStack hosts after you installed HPESimpliVity Plug-in on vCenter Server, the HPE SimpliVity options may no longer function as expected. Forexample, some options may not appear in the All HPE SimpliVity Actions menu.

To ensure all the options function as expected, log out of vSphere Web Client or Client and log back in afterupgrading the hypervisor on a host. For more details on upgrading your hypervisor, see the HPE OmniStack forvSphere Upgrade Guide or the VMware documentation.

Install HPE SimpliVity Plug-in on Windows Server

Before you begin

If you have an earlier version of HPE SimpliVity Plug-in for vSphere Web Client installed, remove it before youinstall a later version.

Procedure overview

To manage HPE SimpliVity virtual objects in vSphere Web Client (Flex) or Client (HTML5), you must installHPE SimpliVity Plug-in on the vCenter Server that you plan to access. This application plugs into the existingvSphere Web Client (Flex) and Client (HTML5) interface. You must also enter administrator credentials during theinstallation process to successfully register it.

If you plan to use Enhanced Linked Mode, you must install the same version of HPE SimpliVity Plug-in on eachserver running vCenter Server to access the HPE SimpliVity options.

Procedure

1. Log on to the Windows computer that has VMware vSphere with vCenter Server using administratorprivileges.

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2151945

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2151945


2. Download the executable (HPESimpliVity-Plug-in-for-vSphere-Web-Client-windows-x.x.x.exe) and double-click it to open the Setup wizard.

3. Click Next to open the License Agreement

4. Select I accept the agreement and click Next to open the Installation Directory screen.


5. Specify the directory you want to use for the plug-in. The default location isC:\Program Files\Hewlett Packard Enterprise\HPESimpliVityPluginForVSphereWebClient.Then click Next to open the VMware vCenter Server Credentials screen.

6. Enter your vSphere administrator credentials in the User Name and Password fields. In the E-mail field,enter the email address of an administrator responsible for HPE SimpliVity Plug-in for vSphere Web Client sothis person can receive alerts. Then click Next.

7. Click Next when ready to install.

8. Wait while the Setup wizard installs the application. The progression bar shows the progress. When done,click Next to finish the installation.


9. Review the steps to log out of vSphere Web Client (if logged in) to ensure that you can see the HPESimpliVity Plug-in options the next time you access vSphere Web Client or Client. If you do not need to logout, select Launch VMware vSphere Web Client.

10. Leave Restart VMware "vsphere-ui" service (required to activate the Plug-in) option selected toautomatically restart the service. Otherwise, you need to manually stop and start the service to activate thePlug-in.

11. Click Finish.

Uninstall HPE SimpliVity Plug-in from Windows Server

Before you begin

Before uninstalling the HPE SimpliVity Plug-in for vSphere Web Client, make sure you have administratorprivileges to access the system.

Procedure


2. From the list of installed programs, double-click HPE SimpliVity Plug-in for vSphere Web Client.

3. Click Yes to confirm that you want to delete the plug-in.


5. Click OK to close the information window. HPE SimpliVity Plug-in automatically restarts the vsphere-client (forFlex) and vsphere-ui (for HTML5) services. It may take a few minutes to restart it.

Install HPE SimpliVity Plug-in on vCenter Server Appliance


Before you begin

If you have an earlier version of HPE SimpliVity Plug-in for vSphere Web Client installed, remove it before youinstall a later version.

Procedure overview

To manage HPE SimpliVity virtual objects in vSphere Web Client (Flex) or Client (HTML5), you must installHPE SimpliVity Plug-in on the vCenter Server that you plan to access. This application plugs into the existingvSphere Web Client (Flex) and Client (HTML5) interface. You must also enter administrator credentials during theinstallation process to successfully register it.

If you plan to use Enhanced Linked Mode, you must install the same version of HPE SimpliVity Plug-in on eachserver running vCenter Server to access the HPE SimpliVity options.

Procedure

1. Open a command line to log on to vCenter Server Appliance using root privileges. For example, run PuTTYto specify the host IP address you need to access. Then log in as root and enter the root password whenprompted.

2. If you do not see the bash prompt (#), enter:

• shell

3. Place the HPE SimpliVity Plug-in application file (for example,HPE-SimpliVity-Plug-in-for-vSphere-Web-Client-linux-x64-x.x.x.run) on the Linux virtualmachine. You may want to use shell commands scp, curl, or wget to access the file to run the installer.

NOTE:

To access a secure file transfer protocol (sftp), enter: chsh -s /bin/bash root

4. Set the executable bit by entering:

chmod +x <HPE-SimpliVity-Plug-in-for-vSphere-Web-Client-linux-x.x.x.run>

5. Enter the following to run the installer:

./<HPE-SimpliVity-Plug-in-for-vSphere-Web-Client.x.x.x.run>

The installer opens with a prompt to read the License Agreement.

6. Press Enter to scroll through the License Agreement and read it.

7. When prompted to accept the agreement, enter y to continue the installation and open the prompt to specifythe directory for the HPE SimpliVity Plug-in.

8. Press to Enter to accept the default path for the installer or specifiy another path and then press Enter. Thisopens the VMware vCenter Server Credentials prompt.

9. Enter your vSphere administrator credentials in the User Name and Password fields. In the E-mail field,enter the e-mail address of an administrator responsible for HPE SimpliVity Plug-in for vSphere Web Clientso this person can receive alerts.

10. Enter y when prompted to continue the installation

11. Wait while the Setup program installs the application. When done, you see a "Finish" message.

12. Review the steps to log out of vSphere Web Client or Client (if logged in) to ensure that you can see theHPE SimpliVity Plug-in options the next time you access vSphere Web Client. If you do not need to log outof vSphere Web Client or Client, log in with the administrator credentials you used during the installationprocess.


13. Leave the Restart VMware "vsphere-ui" service (required to activate the Plug-in)? prompt set to Y (yes)to automatically restart the service. Otherwise, you need to manually stop and start the service to activate thePlug-in.

Uninstall HPE SimpliVity Plug-in from vCenter Server Appliance

Procedure overview

You can remove the HPE SimpliVity Plug-in from vCenter Server Appliance at any time.

Procedure

1. Open a command prompt to log in to vCenter Server Appliance using root privileges. For example, run PuTTYto specify the host IP address you need to access. Then log in as root and enter the root password whenprompted.

2. If you do not see the bash prompt (#), enter:

• shell

3. Enter the following command with your appropriate path information. For example:

cd /opt/Hewlett Packard Enterprise/HPESimpliVityPluginForVSphereWebClient-x.x.x/./uninstall

4. Press Enter when prompted. You see a message to confirm the uninstall process.

5. Enter y to continue.

6. Wait while the Setup program removes the application. You see an "uninstall status complete" message whendone. HPE SimpliVity Plug-in automatically restarts the vsphere-client (for Flex) and vsphere-ui (for HTML5)services. It may take a few minutes to restart it.

Chapter 3: Verify the deployment environment 21

Chapter 3: Verify the deploymentenvironmentThis section contains the following topics:

• Deployment environment requirements

• HPE OmniStack user accounts

• Networking requirements

• HPE OmniStack host requirements

• Deployment checklist

Deployment environment requirementsBefore you deploy hosts, review the following network sections to ensure you deploy the hosts successfully. Referto the deployment checklist at the end of this section to review the main tasks.

HPE OmniStack user accountsThis section describes the user accounts used to deploy and manage HPE OmniStack hosts, including the ESXiroot user, vCenter Server single sign-on accounts, or CLI commands.

ESXi host root accountUse the ESXi host root user account to log on to an HPE OmniStack host. You create the password for the ESXihost root user account when you deploy an HPE OmniStack host using Deployment Manager. For ESXi hostpassword requirements and restrictions, see the VMware documentation for your version of ESXi.

vCenter Server single sign-on accountvCenter Server single sign-on accounts are controlled-privilege, vCenter Server (Active Directory supported)accounts that can manage a federation.

HPE OmniStack CLI accountWhen your VMware single sign-on account is not available, use the HPE OmniStack CLI account to run CLIcommands as described in the HPE OmniStack for vSphere Command Reference Guide.

Networking requirementsAn HPE OmniStack host in a federation requires three separate networks: Management, Storage, andFederation. During deployment, you assign the HPE OmniStack host, Virtual Controller (a virtual machine runningHPE OmniStack software), and the VM Kernel port to one or all of the networks.

Also do the following:

• Maintain a separate network for 10 Gb/s storage data traffic between HPE OmniStack hosts in a federation.

• Use existing networks (such as a dedicated virtualization management network) if you have appropriatenetworks in your VMware environment.


• Use VLANs to separate management and virtual machine traffic. However, ensure that the Managementnetwork and HPE OmniStack hosts can route to each other through a common VLAN.

• Open TCP ports 9292 and 9299 on the Management network to deploy HPE OmniStack hosts. You can closethese ports after a deployment is complete.

NOTE:

To deploy a host with Deployment Manager, enable Service Location Protocol (SLP) for automatic host discovery.

Maximum transmission unitFor best performance, use the following Maximum Transmission Unit (MTU) settings to deploy and manage HPEOmniStack hosts:

• For one 10 Gb/s Network Interface Card (NIC), the Management, Storage, and Federation networks must usethe same MTU settings. The MTU setting can range from 1000 to 9000 bytes. But, best practices recommendsthat you use an MTU setting of 9000 for each network.

• For two NICs (both 1 Gb/s, both 10 Gb/s, or one 1Gb/s and one 10 Gb/s), the Management, Storage,and Federation network can use any MTU setting between 1000 to 9000 bytes. However, best practicesrecommends an MTU setting of 1500 for the Management network and 9000 for the Storage and Federationnetworks.

• The physical switches connected to the NICs must have their MTU set properly. For example, the MTU settingfor the physical switch connected to the Management NIC must be equal to or more than the MTU settingyou chose for the Management network. The MTU setting for physical switch connected to the Storage andFederation NIC must be equal to or more than the MTU settings of the Storage and Federation networks.

• The MTU setting for the Management, Storage, and Federation networks must match the MTU settings usedfor any HPE OmniStack hosts that already reside in the cluster (if any).

Network address and vSphere inventory requirementsThis table describes the network address requirements and objects required in the vSphere inventory to containthe HPE OmniStack hosts.

Requirement Description

NTP The Network Time Protocol (NTP) is preconfigured in an HPEOmniStack host using US internet time servers. The default servers are0.us.pool.ntp.org through 3.us.pool.ntp.org.

Record any NTP servers the vCenter Server is using. At least three NTPservers are required for host deployment.

DNS Server The IP address for a primary and optional secondary DNS server. In addition:

• The DNS servers must be the same and reachable by the VirtualController, HPE OmniStack host, vCenter Server, vSphere Web Client,and the Windows computer running Deployment Manager.

• You need a DNS suffix name for each HPE OmniStack host. The host youplan to deploy cannot be a DNS child domain.

• You need a default DNS suffix to search for a domain.


Requirement Description

vCenter Server IP address orFQDN

The IP address or FQDN for the vCenter Server planned to contain the HPESimpliVity federation.

Cluster The name of the cluster in vCenter Server where you want to deploy the HPEOmniStack hosts. To create a cluster in a datacenter, see the HPE SimpliVityPlug-in for vSphere Help.

HPE OmniStack IP Addresses There are separate HPE OmniStack IP addresses that you assign to thesefive interfaces on the HPE OmniStack networks during a deployment:

Management Network.

• HPE OmniStack host.

• Virtual Controller.

Storage Network.


• VMkernel Port.

Federation Network.


Ports required for HPE OmniStack hostsHPE OmniStack hosts require specific ports to communicate with your network and other hosts in the HPESimpliVity federation.

The following chart does not include standard ports required to use the vSphere hypervisor or the remote consolefor your server.

For a complete list of ports required to use vSphere, see the VMware documentation (https://www.vmware.com/support/pubs/) or VMware Knowledge Base (https://kb.vmware.com/selfservice/microsites/microsite.do)and search for "required ports."

For details on the remote management console ports (such as Integrated Lights Out [iLO]), see thedocumentation that came with the server.

NOTE:

Deployment Manager uses the TLSv1.2 protocol to increase privacy of the information communicated over thenetwork. For more details on the TLSv1.2 protocol, see the VMware Knowledge Base (https://kb.vmware.com/selfservice/microsites/microsite.do) and search for "Status of TLSv1.1/1.2 Enablement and TLSv1.0Disablement across VMware products (2145796)."

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


https://kb.vmware.com/selfservice/microsites/microsite.do



https://kb.vmware.com/s/article/2145796



Ports Protocols Networks Sources Destinations Description

22 TCP All ManagementWorkstation

• HPEOmniStackhost

• VirtualController

For remoteaccess, usingSSH, to theserver when theweb server isunavailable.

53 UDP Management DNS server • HPEOmniStackhost


Used for DNSresolution.

80 TCP Management DeploymentManager



Deploymentmonitoring andSupport Capturedownloads usedby CustomerSupport.

427 TCP and UDP Management DeploymentManager

HPE OmniStackhost

Deploymentoperation andmonitoring.

443 TCP Management • VirtualController

• DeploymentManager

• vSphere WebClient

• vCenterServer



SSL port forvSphere ESXiand vCenterServer.

9090, 9190 TCP Management • DeploymentManager

• vSphere WebClient

Virtual Controller HPE OmniStackCLI or vSphereClient accessto the VirtualController.

9292, 9299 TCP Management DeploymentManager

HPE OmniStackhost

DeploymentManager accessto the host overSSL. This portmust be open todeploy the HPEOmniStack host.You can closethis port after adeployment issuccessful.


Ports Protocols Networks Sources Destinations Description

9390 TCP Management Virtual Controller Virtual Controller Event Manageruses this portto manageevents betweenthe VirtualControllerson the HPEOmniStackhosts.

22122 UDP and TCP Federation andManagement



• Arbiter

Federationtraffic betweenhosts, Arbitercommunication,and backups toremote clusters.If communicationon the federationnetwork fails, theManagementnetwork is used.

111, 2049,32764-32768

UDP and TCP Management andStorage

HPE OmniStackhost

HPE OmniStackhost

Management andStorage trafficbetween HPEOmniStack hostsor standard hoststhat share anHPE OmniStackdatastore.

HPE OmniStack host requirementsBefore deploying an HPE OmniStack host, ensure the following:

• Install at least two HPE OmniStack hosts on a rack in your data center. Verify that they are connected to thepower and powered on.

• To ensure the best performance, clusters that contain multiple HPE OmniStack hosts should be the samemodel. If the cluster contains different models with different CPU counts, you may notice a difference inperformance. For example, if some hosts have 2 CPUs and some have 1 CPU, the hosts in the cluster canonly perform as fast as the slowest host. If you want to deploy hosts to a cluster with a mix of models or CPUcounts, Deployment Manager displays a message for you to confirm the host selection. You can confirm themessage and continue the deployment. But, you may notice a difference in performance. For more details, seeVMware Knowledge Base article: EVC and CPU Compatibility FAQ (1005764).

NOTE:

If you use HPE SimpliVity 2600 Gen10 Family of Servers, you must deploy them to a cluster that does notcontain any other type of HPE OmniStack host (for example, other HPE SimpliVity models, or Dell, Cisco, orLenovo models). HPE SimpliVity 2600 Gen10 Family of Servers do not use an Accelerator card and cannot



reside in the same cluster as hosts that do. But, all models of HPE OmniStack hosts can reside in the samefederation.

• Avoid deploying HPE OmniStack hosts across a wide-area network (WAN). Network disruptions can cause thedeployment to fail.

• For security purposes, configure isolated vLANS for the Omnistack federation before deploying the HPEOmniStack hosts. This protects federation interfaces and data from external discovery or malicious attacks.

Best Practice:

Configure the ports on the physical switches that an HPE OmniStack host connects to as trunk ports. Thisconfiguration allows the hypervisor to manage the VLAN configuration. In addition, you can add VLAN IDs to awhitelist. This limits which VLANs are allowed to communicate on the trunk ports. In this scenario, the whitelistcontains the VLAN IDs that you plan to use for the Storage and Federation networks. In Deployment Manager,when specifying the network settings for the Storage and Federation networks, enter the VLAN IDs from thewhitelist in the appropriate fields. For example, you enter the Host VLAN ID and Virtual Controller VLAN ID forStorage Network Settings and the Virtual Controller VLAN ID field for the Federation network.

NOTE:

For details on interoperability requirements, see the Interoperability Guide for your platform available throughCustomer Support (support.hpe.com).

Deployment checklistTo ensure a smooth and efficient deployment, review the following checklist.

NOTE:

Take an inventory of all the HPE OmniStack hosts you plan to deploy by serial number. Deployment Managershows the status of a deployment by serial number only.

√ Step Details

Install one or more servers on racks. Ensure that two or more HPE OmniStack servers areinstalled in each rack and the servers are powered on.

Check that the vCenter Server version iscompatible with the ESXi version of thehosts.

To check the hypervisor compatibility, see theInteroperability Matrix in the Interoperability Guidefor your server model on the Customer Support(support.hpe.com) site.

Check the password complexity. Do not use special characters (for example, asterisk,ampersand, slash) in your HPE OmniStack host password(if prompted to set one during deployment). See yourhypervisor documentation and the HPE OmniStackfor vSphere Release Notes for details on characterlimitations.

Check that the remote managementsystem for your server is configured.

See the Hardware Installation and Maintenance Guide foryour platform for details.





√ Step Details

Verify that the DNS resolution of IPaddresses (IPv4 supported) is identical onthe computer with Deployment Managerinstalled and on the computer with vCenterServer installed.

Use the nslookup command at each computer to verifyaddress resolution:

nslookup <ip-address-of-host>

Install the correct version of all requiredHPE SimpliVity software.

Download Deployment Manager, Arbiter, and HPESimpliVity Plug-in for vSphere Web Client from CustomerSupport (support.hpe.com).

Check that the HPE OmniStack versions onthe hosts are the same.

Check that all the hosts you plan to deploy to a clusteruse the same version of the HPE OmniStack software.The version must also match the HPE OmniStacksoftware version installed on any hosts previouslydeployed (if you deploy to the same location).

Check that you have administrator accessto vCenter Server.

Obtain the vCenter Server credentials (if you do not knowthem already).

Check that the firewall is set to allow thespecified ports.

See "Ports required for HPE OmniStack hosts."

Verify there are three separate networks: Management,Storage, and Federation.

Check for duplicate IP addresses.

Verify that the MTU size matches that of existingfederation members.

Check the IP addresses/networkconfiguration.

Verify the NTP server.



Chapter 4: Deploy OmniStack hosts 28

Chapter 4: Deploy OmniStack hostsThis section contains the following topics:

• HPE OmniStack host deployment

• Deployment prerequisites

• HPE OmniStack host discovery

• Deploy an HPE OmniStack host

• HPE OmniStack host heartbeats

• Review post-deployment tasks

HPE OmniStack host deploymentWith Deployment Manager, you can deploy multiple HPE OmniStack hosts at a time to a cluster. Once you deploytwo or more hosts, you created an HPE SimpliVity federation in your hypervisor.

You can also use Deployment Manager to import a previously saved configuration file. The configuration filecontains store network settings. This helps you deploy hosts faster because you have a template. Just importthe file when prompted and make the appropriate modifications to the populated fields as you click through theDeployment Manager wizard.

NOTE:

HPE OmniStack hosts must reside in one to 16 clusters in a federation. A cluster can contain up to 16 HPEOmniStack hosts with up to 720 virtual machines. A single vCenter Server can contain a maximum of 32HPE OmniStack hosts. If linking vCenter Servers with Enhanced Linked Mode, you can deploy up to 96 HPEOmniStack hosts in a federation.

Before you can deploy the host, Deployment Manager runs a series of validation tests on the network settings.For example, it checks the IP address, port group name, Network Interface Card (NIC) speed and connection. Ifit detects any issues, you see a message with an appropriate workaround. You can stop and start the tests at anytime if you need to make any changes to your settings before you continue.

During the deployment of an HPE OmniStack host, Deployment Manager performs a reverse DNS lookup. Whenan IP address resolves to a host name, the host appears in vCenter Server with an assigned host name. Whenan IP address does not resolve to a host name, the host appears in vCenter Server with an assigned IP address.

NOTE:

If Deployment Manager cannot determine the host name associated with the IP address of a host, it deploysthe host with the IP address as the name. You can rename a host using the svt-host-rename command asdescribed in the HPE OmniStack for vSphere Command Reference Guide. The renaming process does notimpact the I/O performance of the virtual machines residing on the host.

Once you deploy your hosts, you can manage them and their associated virtual objects through the HPESimpliVity options in your hypervisor. For more information, see Review post-deployment tasks on page 45.

NOTE:

If you want to deploy hosts using commands instead of using Deployment Manager as described in thisdocument, see the HPE OmniStack for vSphere Command Reference Guide.


Deployment prerequisitesBefore you begin using Deployment Manager, review the following list to ensure that you successfully deploy theHPE OmniStack hosts:

• You created a cluster under the datacenter where you want to deploy the hosts. HPE OmniStack hosts mustreside in one to 16 clusters in a federation. A cluster can contain up to 16 HPE OmniStack hosts with up to720 virtual machines. A single vCenter Server can contain a maximum of 32 HPE OmniStack hosts. If linkingvCenter Servers with Enhanced Linked Mode, you can deploy up to 96 HPE OmniStack hosts in a federation(with up to five linked vCenter Servers).

• All HPE OmniStack hosts you plan to deploy use the same HPE OmniStack software version. Do not mix HPEOmniStack versions in the same cluster.

• Verify that your version of Deployment Manager is the same version as the HPE OmniStack version of yourhosts or later. For example, if your hosts use HPE OmniStack 3.7.7, use Deployment Manager 3.7.7.

• If you plan to deploy hosts to a cluster that contains previously deployed HPE OmniStack hosts, verify thatthe previously deployed hosts are in a healthy state. For example, use the HPE SimpliVity Plug-in for vSphereoptions to verify the state of the hosts and their Virtual Controllers before you deploy new hosts. If necessary,make modifications to the network and power. You cannot deploy HPE OmniStack hosts to a cluster thatcontains unresponsive hosts.

• Only IPv4 addresses are supported.

• The Windows computer and HPE OmniStack hosts you plan to deploy must be on the same network. If theWindows computer and an HPE OmniStack host are not on the same network, you must manually obtain anIP address for the HPE OmniStack host. For more information, see "HPE OmniStack host discovery."

• Open TCP ports 9292 and 9299 on the Management network to deploy an HPE OmniStack host. You canclose these ports after the deployment is successful.

• Know the hypervisor version used (for example, ESXi 6.5 or 6.7) on each HPE OmniStack host you plan todeploy.

• Verify the Windows computer you are using to deploy an HPE OmniStack host is not configured to enterhibernation or sleep mode during the deployment.

• If deploying a single HPE OmniStack host, do not enable vSphere High Availability (HA). You do not haveenough HPE OmniStack hosts. (With vSphere HA, virtual machines on one failed host can restart on a healthyHPE OmniStack host if one is available.)

HPE OmniStack host discoveryWhen you power on an HPE OmniStack host, it obtains a temporary IP address from a DHCP server. Thetemporary IP address allows the Deployment Manager client to communicate with the HPE OmniStack host.

Deployment Manager uses the Service Location Protocol (SLP) to discover the HPE OmniStack host.Deployment Manager connects to the HPE OmniStack host and collects its properties, such as model type andserial number.

In certain situations, for example, when you do not have a DHCP server on the network, an HPE OmniStackhost cannot acquire a temporary IP address automatically. In this case, you need to manually assign a staticIP address, netmask, and gateway to the HPE OmniStack host as described in Optional: Assign a static IPaddress to an HPE OmniStack host on page 30. (If the host is not on the network and you cannot open abrowser to access the HPE SimpliVity Installer console, you also need to follow the steps in Connect to a remotemanagement interface on page 30.)


Connect to a remote management interfaceIf you need to assign a static IP address to the host you want to deploy because it cannot obtain oneautomatically, you need to know the host can access the HPE SimpliVity Installer console first. For example, ifthe host is not on the network and you cannot access a browser, you cannot connect to the remote managementinterface for your server (iLO 4 or 5) and launch the HPE SimpliVity Installer console. This procedure describeshow to connect to the remote manage system and access the console. If the host is on the network, skip toOptional: Assign a static IP address to an HPE OmniStack host on page 30.

Procedure

1. Connect an Ethernet cable from the Windows computer to the Ethernet management port ( iLO port) on therear of the HPE OmniStack host.

2. Configure the remote management interface for your platform.

3. Connect to the remote management interface and launch the HPE SimpliVity Installer console. For moreinformation on the console, see the Hardware Installation and Maintenance Guide for your platform.

4. Follow the steps in Optional: Assign a static IP address to an HPE OmniStack host on page 30.

Optional: Assign a static IP address to an HPE OmniStack hostIf you do not have a DHCP server on the network, an HPE OmniStack host cannot acquire a temporary IPaddress automatically. Follow these steps to manually assign an IP address. Then Deployment Manager candetect the IP address automatically.

Procedure

1. On the HPE SimpliVity Installer screen, when the status is Waiting to be discovered, press Ctrl+N .

2. Determine the network interface for the connection you are planning to use on the Management network todeploy the HPE OmniStack host. If the Management network and network interface are on different VLANs,indicate the VLAN for the network interface as follows:

a) Use the Tab key to select Add VLAN and press Enter.

b) Enter the VLAN ID for the network interface. Then use the Tab key to select OK and press Enter.

3. Press Tab to select Enable NIC and press Enter.

4. Press Tab to specify the IP address, netmask, and gateway for the HPE OmniStack host.

5. Press Tab to Apply and press Enter.

6. Press Tab to select Done and press Enter.

7. In Deployment Manager, specify the IP address on the Select an HPE OmniStack Host screen.

Deploy an HPE OmniStack hostProcedure overview

Follow the steps in this procedure to deploy HPE OmniStack hosts to a cluster. You can only deploy hosts to onecluster at a time. However, after you start the deployment of hosts to one cluster, you can start the deployment ofhosts to another cluster.

To deploy HPE OmniStack hosts, you can manually enter the host settings or import a previously savedconfiguration file to automatically populate fields. (You can save the settings you enter in Deployment Managerbefore you deploy hosts.)


Procedure

1. Open Deployment Manager on the Windows computer you want to use to deploy the HPE OmniStack hosts.

2. Leave the Hypervisor set to VMware vSphere. Then, enter the vCenter Server IP address and administratorcredentials. (Do not try to log on to the local host or use the loopback address.) Click Login.

Deployment Manager retrieves the VMware certificate to access vCenter Server. Click Accept to accept thecertificate and open the Select Deploy Location screen. For example:

3. Expand a datacenter and select a cluster for deployment. Click Refresh Inventory to update the contents ifnecessary.


NOTE:

HPE OmniStack hosts must reside in one to 16 clusters in a federation. A cluster can contain up to 16 HPEOmniStack hosts with up to 720 virtual machines. A single vCenter Server can contain a maximum of 32HPE OmniStack hosts. If linking vCenter Servers with Enhanced Linked Mode, you can deploy up to 96 HPEOmniStack hosts in a federation.

4. Do one of the following:

• If you selected a cluster with existing HPE OmniStack hosts, skip to step 7.

• If you selected a cluster without existing HPE OmniStack hosts, click Next to open the Define Settings forFederation, Arbiter, or Both screen.

NOTE:

If you only see the "HPE SimpliVity Arbiter Information" section to specify the location of Arbiter, you loggedinto a vCenter Server with previously deployed HPE OmniStack hosts in the federation. But, the cluster youselected does not have any existing hosts. Skip to step 6 if you only see Arbiter options.

5. Select one of the following:

• Create an HPE SimpliVity Federation: You plan to deploy hosts to create a new federation in vCenterServer.

• Join an existing HPE SimpliVity Federation: You plan to deploy hosts to a federation with vCenterServer in Linked Mode (or Enhanced Link Mode). In the Existing HPE SimpliVity Federation VirtualController management IP address field, enter the management IP address of a Virtual Controller inthe federation. This ensures that Deployment Manager can locate the correct vCenter Server you want touse. (The management IP address is part of the Virtual Controller name.)

6. If shown, select one of the following to define the Arbiter information:

• HPE SimpliVity Arbiter is installed on this vCenter

• HPE SimpliVity Arbiter is installed on a different Windows computer

In the IP address of the Windows server running the Arbiter field, enter the Windows server IPaddress.


7. Click Next to open the Select Method screen.

If you recently deployed your first host to a cluster, you cannot continue to this screen until that first hostcompletes the deployment process. You can check the progress through the deployment icon ( ).


• Manually enter settings: Leave this option selected to manually enter the network information to deploya host.

• Import configuration (XML) file: Select this option to import data from an existing configuration file andautomatically populate some network fields. You can modify the data at any time during the deployment.Click Browse to select the configuration file (XML) you want to import. By default, Deployment Managerstores configuration files to the C:\Users\<user name>\My Documents directory. (You need Readprivileges to import the file.)

9. Click Next to open the Select an HPE OmniStack Host screen.


10. Click Scan to automatically discover hosts on the broadcast domain and populate the table. If you do notsee the host you want to deploy, enter the IP address in the Add host IP address field and click Add. Forexample, your screen populates with details similar to this (IP not shown in example):

11. Click the NIC Details icon ( ) to see the supported hypervisors and Network Interface Cards (NICs) usedon each host. Expand the network adapter name to review the interface, MAC address (physical addressand unique port identifier), vendor, model name and number, maximum link speed (1 gigabit per second [Gb/s] or 10 Gb/s), and link (connection) status. A host may come equipped with many NICs (for example, threeto 10). These details help you determine what NIC to use for the networks.

NOTE:

Click the X icon to close the details. If you do not see any NIC details for a host or a NIC appearsdisconnected, check the physical server. You may have a faulty cable, port, card, or switch. Or, the version ofthe HPE SimpliVity Installer application on the host may be older than the Deployment Manager version. Toupdate the Installer application on the host, contact Customer Support (support.hpe.com).

12. Select the desired hypervisor version from the Select Hypervisor Version drop-down menu (only shownwhen deploying hosts to an empty cluster).

For example, if you use vCenter Server 6.7, you can select ESXi 6.5 or 6.7. But, each host in a cluster mustuse the same hypervisor version (all 6.x).

Once you select a hypervisor version, you no longer see the Select Hypervisor Version field for subsequentdeployments to the same cluster. You also cannot deploy HPE OmniStack hosts to the same cluster unless ituses a supported hypervisor.

13. Leave the default language of US English in the Locale field or select another language from the drop-downmenu (US English or Japanese only).

14. Select the hosts you want to deploy and click Next to open the Select Network Interface Cards screen.

NOTE:

If you select hosts with a mix of vendor models or CPU counts (or the cluster contains different hosts), yousee a prompt to confirm your host selection in case you want to change it or deploy hosts to another cluster.Best practices recommends that you use the same host models and CPU counts in a cluster for the bestperformance.



15. In the Management NIC and Storage and Federation NIC fields, select the NIC you want to use for eachnetwork from the chart that opens in the drop-down lists. For example:

NOTE:

You can use the same NIC for the each network. But, use a NIC with a link speed of at least 1 Gb/s for theManagement network and 10 Gb/s for the Storage and Federation network. In addition, select NICs with thesame link speed combination for each host (for example, all 1 Gb/s and 10 Gb/s or all 10 Gb/s and 10 Gb/s).Your selections must also match the link speed combination of any HPE OmniStack hosts that already residein the cluster (if available).

16. Click Next to open the Set HPE OmniStack Passwords screen.


17. Enter the password for the root user account to log on to the HPE OmniStack host and confirm it. (Use thepassword requirements of the hypervisor.) Then enter the Command Line Interface (CLI) password andconfirm it for command line access.

18. Click Next to open the Configure Management Network Settings screen.

NOTE:

You can right-click some fields to access Cut, Copy, and Paste options. If deploying hosts to a cluster withexisting HPE OmniStack hosts, you see some of the fields populate with default responses that providelimited options for changes or must remain as shown.

19. On the Network Settings tab, enter the following Management network information for the managementconnection, Virtual Controller, and host:

• Host Gateway.


• Host Netmask.

• Host VLAN ID. Enter a value between 0 to 4094.

• Virtual Controller Gateway.

• Virtual Controller Netmask.

• Host Controller VLAN ID. Enter a value between 0 to 4094.

• Management vSwitch Name. Select the name from the drop-down list (if more than one vSwitch isavailable). Deployment Manager accesses the vSwitch names from vCenter Server. If performing a newdeployment, you cannot change the default vSwitch name.

NOTE:

If you selected one NIC for the Management and Storage and federation networks, select the samevSwitch for all the networks (for example, all vSwitch0). If you selected two NICs, you can select onevSwitch for the Management network and another vSwitch for the Storage and federation networks.However, the Storage and federation networks should use the same vSwitch because they use the sameNIC.

• Host Port Group Name. Select the name from the drop-down list. If performing a new deployment, youcannot change the default name.

• MTU. Enter a value between 1000-9000. The MTU setting must match the MTU settings used for theManagement network of any HPE OmniStack hosts that already reside in the cluster (if available).

• Virtual Controller Port Group Name. Select the name from the drop-down list. If performing a newdeployment, you cannot change the default name.

20. Click the IP Addresses tab.

21. Enter the host and Virtual Controller IP addresses for each host you plan to deploy.

22. Click Next to open the Configure Storage Network Settings screen.


23. On the Network Settings tab, enter the following Storage network information for the storage connection,Virtual Controller, and host:

• Host Gateway.

• Host Netmask.

• Host VLAN ID. Enter a value between 0 to 4094.



• Virtual Controller VLAN ID. Enter a value between 0 to 4094.

• Storage vSwitch Name. Select the name from the drop-down list (if more than one vSwitch is available).If you selected the same NIC link speed for the networks of a new deployment, this field defaults to thename used for the Management network and you cannot change it.

NOTE:

If you selected one NIC for the Management and Storage and federation networks, select the samevSwitch for all the networks. If you selected two NICs, you can select one vSwitch for the Managementnetwork and another vSwitch for the Storage and federation networks. However, the Storage andfederation networks should use the same vSwitch because they use the same NIC.

• Host Port Group Name. Select the name from the drop-down list. If performing a new deployment, youcannot change the default name.

• MTU. Enter a value between 1000-9000. The MTU setting must match the MTU settings used for theStorage network of any HPE OmniStack hosts that already reside in the cluster (if available).




25. Enter the host and Virtual Controller IP addresses for each host you plan to deploy.

26. Click Next to open the Configure Federation Network Settings screen.

27. On the Network Settings tab, enter the following federation network information for the connection and VirtualController:



• Virtual Controller VLAN ID. Enter a value between 0 to 4094.

• Federation vSwitch Name. Select the name from the drop-down list (if more than one vSwitch isavailable). If you selected the same NIC link speed for the networks of a new deployment, this fielddefaults to the name used for the Management network and you cannot change it.


NOTE:

If you selected one NIC for the Management and Storage and federation networks, select the samevSwitch for all the networks. If you selected two NICs, you can select one vSwitch for the Managementnetwork and another vSwitch for the Storage and federation networks. However, the Storage andFederation networks should use the same vSwitch because they use the same NIC.


• MTU. Enter a value between 1000-9000. The MTU setting must match the MTU settings used for thefederation network of any HPE OmniStack hosts that already reside in the cluster (if available).


29. Enter the Virtual Controller IP address for each host you plan to deploy.

30. Click Next to open the Configure Host DNS Settings screen.


31. Enter the following host DNS information:

• Domain. Enter the domain name (with a DNS suffix).

• Search Domain.

• Primary Server.

• Secondary Server.

• Find and register the host by domain name. Leave this option selected for DNS to perform a lookupfor the hostname and register it in vCenter Server with that name. If it cannot find the name, DeploymentManager still deploys the host to vCenter Server with the IP address. You can change the name at anytime after deployment using the svt-host-rename command. For more details on using this command, seethe HPE OmniStack for vSphere Command Reference Guide.

32. Click Next to open the Select NTP Servers for Host screen.


33. Select at least three NTP servers and click Add.

The default servers are:

• 0.us.pool.ntp.org




You can add an IP address or DNS name for an alternate NTP server in the Alternate Server field and thenclick Add. Click Up or Down to change the priority order of the NTP servers.

34. Click Next to review the information in the Review Deployment Details screen. You can scroll down thescreen to see all of the settings. For example:

NOTE:

If you need to make corrections, click Back to return to the screen where you need to make the change.Click Next until you return to the Review Deployment Details screen.

35. Click Next to open the Test Host Settings screen.


36. Click Start Test when ready to test the host settings. Use the legend to review the status as the test runs. IfDeployment Manager detects any issues, you see the messages with any necessary troubleshooting tips inthe Test Details section. You can toggle between starting and rerunning the test as needed through the Start/Rerun Test button.

NOTE:

If some tests fail, the Start Test button toggles to Rerun Test. This gives you time to make corrections. Forexample, you can make changes to physical hardware, the network, or click Back and change settings.When ready, click Rerun Test. Once the tests pass, you can continue.

37. When all the tests pass and you see a success message in the Test Details section, click Next to open theStart Deployment, Save Settings, or Both screen.


• Select both options to deploy the HPE OmniStack hosts and create a configuration file.


• Select Start deployment to deploy the HPE OmniStack hosts.

• Select Save settings in a configuration file to save the settings in a configuration file that you canimport as a template for later deployments. Then, click Save As and browse to a directory. Specify thedesired filename for the configuration file and click Save. You do not deploy any hosts at this time if youonly select this option.

39.

Click Finish.

If you chose to deploy the HPE OmniStack hosts, Deployment Manager displays the Monitor Deploymentscreen.

Next steps

You can start a new deployment while the current one runs. To start a new deployment from the MonitorDeployment screen, click New Deployment.

On any Deployment Manager screen, you can click the square deployment status icon (for example, )at the top of the screen to display the deployment status. This deployment status icon shows the number ofdeployments in progress. For example:


Click OK to close it. Or, once hosts successfully complete their deployment, you can clear them from the list byclicking Clear Completed.

HPE OmniStack host heartbeatsOnce you deploy hosts to a federation, you can monitor and maintain their connections through two heartbeatfunctions.

• The Arbiter application provides a connection heartbeat between the HPE OmniStack host within a federation.If the Arbiter heartbeat stops, vCenter Server displays the following error message:

Lost contact with the Arbiter at ip-address.

• The Accelerator Firmware also provides a heartbeat. If this heartbeat stops, vCenter Server displays thefollowing error message:

HPE SimpliVity Accelerator Firmware Unresponsive.

HPE SimpliVity also supports the VMware vSphere HA datastore heartbeat if it is configured in your environment.

See the HPE SimpliVity Plug-in for vSphere Web Client Help for information about monitoring events and alarms.You can also find steps to restart Arbiter (if necessary).

Review post-deployment tasksAfter a successful deployment, complete these tasks for each HPE OmniStack host.

• Configure the VMware license settings for vCenter Server and the ESXi hosts. For more information, see theVMware documentation at:


• If not done already, install HPE SimpliVity Plug-in for vSphere on the computer where the vCenter Server isinstalled as described in this document. (To download the application, go to support.hpe.com and log in withyour account.)

• Complete the following tasks as described in the HPE OmniStack for vSphere Administration Guide or theHPE SimpliVity Plug-in for vSphere Help:

◦ (Optional) Configure NIC teaming on the standard or distributed port groups.




◦ Install HPE SimpliVity Plug-in for vSphere Web Client on the computer where the vCenter Server isinstalled.

◦ Set the time zone for all the clusters (defaults to Coordinated Universal Time [UTC]).

◦ Create backup policies.

◦ Create datastores.

◦ Set up your virtual environment. For example, create or migrate virtual machines.

◦ Assign backup policies to the virtual machines.

◦ Add rules to the backup policies.

NOTE:

If Deployment Manager could not determine the host name associated with the IP address of a host, itdeploys the host with the IP address as the name. But, you can rename a host using the svt-host-renamecommand as described in the HPE OmniStack for vSphere Command Reference Guide. The renamingprocess does not impact the I/O performance of the virtual machines residing on the host.

Chapter 5: Troubleshooting 47

Chapter 5: TroubleshootingThis section contains the following topics:

• Recoverable deployment errors

• General deployment issues

• Collect deployment logs

Recoverable deployment errorsAn HPE OmniStack host deployment can fail when there is a temporary network interruption or DeploymentManager could not discover the host.

As described in the deployment procedure, you can view status messages during deployment by clicking the

blinking deployment icon at the top of the screen ( ). The icon shows the number of hosts deploying. When adeployment fails, Deployment Manager displays a failure message and the host serial number.

The point where the deployment fails determines the action you need to take to resolve it. For example, you mayneed to retry the deployment, reset the discovery state, or reset the power on the server.

To check what you need to do to resolve the error, log in to the Integrated Lights Out (iLO) remote managementinterface (iLO 4 for HPE SimpliVity 380 Gen9 servers or iLO 5 for HPE SimpliVity Gen10 servers [HPE SimpliVity380 Gen10 or HPE SimpliVity 2600 Gen10]) and launch the HPE SimpliVity Installer remote console. (Forexample, you can log in to iLO, click the Overview tab, and click .NET or Java Web Start from the IntegratedRemote Console field. Then click Run when prompted.)

The status that appears on the screen determines how you resolve the error. For example, you may see one ofthe following HPE SimpliVity Installer screens depending on the deployment issue:

• If you see a Waiting to be discovered status message, clear the error in Deployment Manager and trythe deployment again. For example, your screen may look like this:

• If you see a Discovered status message, reset the discovery state. For example, your screen may look likethis:


• If you see a SimpliVity ESXi message, reset the power switch. For example, your screen may look likethis:

See one of the following procedures if you need to reset the discovery state or reset the power switch. If youcontinue to encounter deployment issues, contact Customer Support (support.hpe.com).

Reset HPE OmniStack host discovery state

Before you begin

Verify an active instance of Deployment Manager is not currently discovering or deploying the HPE OmniStackhost where you are resetting the discovery state.

Procedure

1. If not done already, log in to the Integrated Lights Out (iLO) remote management interface (iLO 4 for HPESimpliVity 380 Gen9 servers or iLO 5 for HPE SimpliVity Gen10 servers [HPE SimpliVity 380 Gen10 or HPESimpliVity 2600 Gen10]). From the main screen, launch the HPE SimpliVity Installer remote console. The HPESimpliVity Installer screen shows the Discovered status. For example:



2. Press Ctrl+R. You see a warning message. For example:

3. Press Tab to select OK. Then press Enter to reset the deployment state to Waiting to be discovered.

4. Retry the deployment using Deployment Manager. If the deployment fails, contact Customer Support(support.hpe.com).

Reset the power switch on an HPE SimpliVity 380 Gen9 hostUse this procedure to reset the power switch of an HPE SimpliVity 380 Gen9 server when the deployment failsand the HPE SimpliVity Installer showed a "SimpliVity ESXi" status message. (If the deployment failed for an HPESimpliVity Gen10 server [HPE SimpliVity 380 Gen10 or HPE SimpliVity 2600 Gen10], see the following procedureinstead.)

Procedure

1. If not done already, log in to the Integrated Lights Out (iLO 4) remote management interface. From the mainscreen, launch the HPE SimpliVity Installer remote console. The HPE SimpliVity Installer screen shows theSimpliVity ESXi status. For example:




2. Insert the USB stick with the deploy installer image (IMG) file. This file came with the HPE SimpliVity softwareyou downloaded. For more details on this file, see Download the HPE SimpliVity software on page 7 in thisguide.

3. Click Power Switch > Reset. The host goes through the intialization process. Once the host initializes, yousee the HPE Proliant screen. For example:

4. Press F11 and press Enter twice to open the boot options screen. For example:


5. Select option 2, One Time Boot to USB DriveKey, and press Enter to open the deploy or factory resetscreen. For example:

6. Leave the default of Deploy and press Enter.

7. Once you see the screen show a status of Waiting to be discovered, retry the deployment usingDeployment Manager. For example:


Reset the power switch on an HPE SimpliVity 380 Gen10 hostUse this procedure to reset the power switch of an HPE SimpliVity Gen10 server [HPE SimpliVity 380 Gen10 orHPE SimpliVity 2600 Gen10] when the deployment fails and the HPE SimpliVity Installer showed a "SimpliVityESXi" status message. If deployment failed for an HPE SimpliVity 380 Gen9 server, see the previous procedureinstead.

Procedure

1. If not done already, log in to the Integrated Lights Out (iLO 5) remote management interface. From the mainscreen, launch the HPE SimpliVity Installer remote console. The HPE SimpliVity Installer screen shows theSimpliVity ESXi status. For example:


• Plug in the USB stick that has the deploy installer image (IMG) file. This file came with the HPE SimpliVitysoftware you downloaded. For more details on this file, see Download the HPE SimpliVity software onpage 7 in this guide.


• If you moved the deploy installer image file from the USB stick to another location, select Image FileRemovable Media from the Virtual Drives menu. Then browse to the deploy installer image file and clickOpen.

3. Click Power Switch > Reset. The host goes through the intialization process. Once the host initializes, yousee the HPE Proliant screen. For example:

4. Press F11 and press Enter twice to open the boot options screen.

5. Do one of the following, depending on what action you took at step 2:

• If you inserted a USB flash drive, select the Generic USB Boot option.

• If you selected Image File Removable Media, select the iLO Virtual USB 4 : iLO Virtual USB Key optionas shown:

6. Press Enter to open the deploy or factory reset screen. For example:


7. Leave the default of Deploy and press Enter.

8. Once you see the screen show a status of Waiting to be discovered, retry the deployment usingDeployment Manager. For example:

General deployment issuesIf you do not need to reset the boot drive or reset the installer image, you might have a general deployment error(such as, deploying to an IP address already in use or having the network connection timeout).

This section contains a list of general errors and possible solutions.

Cannot connect to port 9299Deployment Manager displays this message:

Error connecting to address n.n.n.n port 9299

Procedure


• Verify that the specified IP address is not in use by another HPE OmniStack host.

• Verify that the firewall rules on a switch or network router do not prevent access to port 9299.

• Open port 9299 on the Management network and redeploy the HPE OmniStack host.

IP address already assignedDeployment Manager displays a message that an IP address is already in use on a network.

The IP address is assigned to another HPE OmniStack host. An unexpected internal error occurred.

Procedure

• Assign an IP address to the HPE OmniStack host that is not in use by another HPE OmniStack host.

Disconnected hostsThe cluster you selected in the Select Deployment Location for Hosts screen might contain HPE OmniStack hostsin the federation that are disconnected or unavailable for any reason (such as a network outage). DeploymentManager displays this message when you navigate from the Select Deploy Location screen to the ConfigureFederation Network Settings screen:

Cannot connect to selected resource. Select another resource to continue.

Procedure

• Verify the power and network cables are connected to the HPE OmniStack host. For more information, see theHardware Installation and Maintenance Guide for your platform.

Network connection timeoutA network connection timeout occurred between Deployment Manager and the HPE OmniStack hosts you aredeploying. Deployment Manager displays this message during a deployment:

Interface error from Installer

Procedure

• Reboot the HPE OmniStack host. Contact Customer Support (support.hpe.com).

• After the reboot is successful, redeploy the HPE OmniStack hosts when network traffic is low.

.NET needs to be upgradedIf Microsoft™ .NET Framework 4.7.1 is not installed on the Windows computer or the .NET Framework versioninstalled on the Windows computer is an older version, you see one of two error messages while installingDeployment Manager. For example, you may see the "Error 1001 Unknown error" message or you may see:

This setup requires the .NET Framework version 4.7.1. Please install the .NET Framework and run the setup again. The .NET Framework can be obtained from the web. Would you like to do this now?

Procedure

• If you see the "Unknown error" message, click OK and close Deployment Manager. Upgrade .NET Frameworkto version 4.7.1 or later.



• If you see the second message (with details on requiring a new version of .NET Framework), click Yes in themessage to install .NET Framework 4.7.1 or a later release on the Windows computer you are using to deploythe HPE OmniStack hosts.

HPE OmniStack software version outdatedThe current version of the HPE OmniStack software is running on a later release of an HPE OmniStack host.Deployment Manager displays this message during a deployment:

ERROR: step 1 of 33 - Failed to create a session to HMS.

Procedure

• Use the latest version of Deployment Manager when deploying systems that use different HPE OmniStackversions. For example, if you have 3.6.1 systems and then purchase 3.7.1 systems, use Deployment Manager3.7.1.

Cannot connect to HPE OmniStack hostDeployment Manager cannot connect to the HPE OmniStack host. Deployment Manager displays this messageduring a deployment on a CN-Series platform:

ERROR: step 8 of 33 - Timeout while waiting for hypervisor to boot.

Procedure

1. Verify that the IP address for the HPE OmniStack host is correct.

2. Verify that the HPE OmniStack host you are deploying are on the same subnet.

3. Check the network configuration settings.

4. Retry the deployment.

IP address already in useThe IP address you are using to deploy a host is already in use by a different HPE OmniStack host. DeploymentManager displays this message during a deployment:

ERROR: step 14 of 33 - A task error occurred adding host to port group.

Procedure

• Verify the IP addresses that are available using the following command:

svt-ippool-show --pool all

IP address associated with failed deploymentThe IP address entered in the Select HPE OmniStack Host screen is associated with an HPE OmniStack hostthat exists as a failed deployment. When you retry a deployment and enter the IP address for the HPE OmniStackhost, Deployment Manager displays this message:

Deployment is already in process for the HPE OmniStack host.

Procedure

1. In the Deployment Status window, click the X icon for the error message associated with the HPE OmniStackhost to clear the message.


2. Enter the IP address of the HPE OmniStack host in the appropriate field of the Select HPE OmniStack Hostsscreen.

Collect deployment logsProcedure overview

If a deployment fails, you can collect the relevant deployment logs. These logs can help you and Hewlett PackardEnterprise Customer Support (support.hpe.com) analyze the deployment failure and determine the appropriateresolution.

To collect deployment logs:

Procedure

1. In Deployment Manager, click the Settings icon ( ) to open the Settings screen.

2. Click Collect to open the Browse For Folder dialog.

3. Navigate to the folder where you want to save the deployment logs.

To save the logs to a new folder, click Make New Folder. Enter a name for the new folder and press Enter.

4. Click OK to save the collected deployment logs to the location that you have specified.

Results

Deployment Manager saves the deployment logs in a date/time-stamped folder in the location that you havespecified.


Appendix A: Support and other resources 58

Appendix A: Support and other resourcesThis section contains the following topics:

• Support and other resources

• Documentation feedback

Support and other resources

Accessing Hewlett Packard Enterprise Support• For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website:

http://www.hpe.com/assistance

• To access documentation and support services, go to the Hewlett Packard Enterprise Support Center website:

support.hpe.com

Information to collect

• Technical support registration number (if applicable)

• Product name, model or version, and serial number

• Operating system name and version

• Firmware version

• Error messages

• Product-specific reports and logs

• Add-on products or components

• Third-party products or components

Accessing updates• Some software products provide a mechanism for accessing software updates through the product interface.

Review your product documentation to identify the recommended software update method.

• To download product updates:

◦ Hewlett Packard Enterprise Support Center

support.hpe.com

◦ Hewlett Packard Enterprise Support Center: Software downloads

http://www.hpe.com/support/downloads

◦ Software Depot

http://www.hpe.com/support/softwaredepot

• To subscribe to eNewsletters and alerts:

http://www.hpe.com/support/e-updates

http://www.hpe.com/assistance



http://www.hpe.com/support/downloads

http://www.hpe.com/support/softwaredepot

http://www.hpe.com/support/e-updates


• To view and update your entitlements, and to link your contracts and warranties with your profile, go to theHewlett Packard Enterprise Support Center More Information on Access to Support Materials page:

http://www.hpe.com/support/AccessToSupportMaterials

NOTE:

Access to some updates might require product entitlement when accessed through the Hewlett PackardEnterprise Support Center. You must have an HPE Passport set up with relevant entitlements.

Customer self repairHewlett Packard Enterprise customer self repair (CSR) programs allow you to repair your product. If a CSR partneeds to be replaced, it will be shipped directly to you so that you can install it at your convenience. Some partsdo not qualify for CSR. Your Hewlett Packard Enterprise authorized service provider will determine whether arepair can be accomplished by CSR.

For more information about CSR, contact your local service provider or go to the CSR website:

http://www.hpe.com/support/selfrepair

Remote supportRemote support is available with supported devices as part of your warranty or contractual support agreement.It provides intelligent event diagnosis, and automatic, secure submission of hardware event notifications toHewlett Packard Enterprise, which will initiate a fast and accurate resolution based on your product's servicelevel. Hewlett Packard Enterprise strongly recommends that you register your device for remote support.

If your product includes additional remote support details, use search to locate that information.

Remote support and Proactive Care information

HPE Get Connected http://www.hpe.com/services/getconnected

HPE Proactive Care services http://www.hpe.com/services/proactivecare

HPE Proactive Care service:Supported products list

http://www.hpe.com/services/proactivecaresupportedproducts

HPE Proactive Care advancedservice: Supported productslist

http://www.hpe.com/services/proactivecareadvancedsupportedproducts

Proactive Care customer information

Proactive Care central http://www.hpe.com/services/proactivecarecentral

Proactive Care serviceactivation

http://www.hpe.com/services/proactivecarecentralgetstarted

Warranty informationTo view the warranty information for your product, see the links below:

HPE ProLiant and IA-32Servers and Options

http://www.hpe.com/support/ProLiantServers-Warranties

HPE Enterprise and CloudlineServers

http://www.hpe.com/support/EnterpriseServers-Warranties

http://www.hpe.com/support/AccessToSupportMaterials

http://www.hpe.com/support/selfrepair

http://www.hpe.com/services/getconnected

http://www.hpe.com/services/proactivecare

http://www.hpe.com/services/proactivecaresupportedproducts

http://www.hpe.com/services/proactivecareadvancedsupportedproducts

http://www.hpe.com/services/proactivecarecentral

http://www.hpe.com/services/proactivecarecentralgetstarted

http://www.hpe.com/support/ProLiantServers-Warranties

http://www.hpe.com/support/EnterpriseServers-Warranties


HPE Storage Products http://www.hpe.com/support/Storage-Warranties

HPE Networking Products http://www.hpe.com/support/Networking-Warranties

Regulatory informationTo view the regulatory information for your product, view the Safety and Compliance Information for Server,Storage, Power, Networking, and Rack Products, available at the Hewlett Packard Enterprise Support Center:

http://www.hpe.com/support/Safety-Compliance-EnterpriseProducts

Additional regulatory information

Hewlett Packard Enterprise is committed to providing our customers with information about the chemicalsubstances in our products as needed to comply with legal requirements such as REACH (Regulation EC No1907/2006 of the European Parliament and the Council). A chemical information report for this product can befound at:

http://www.hpe.com/info/reach

For Hewlett Packard Enterprise product environmental and safety information and compliance data, includingRoHS and REACH, see:

http://www.hpe.com/info/ecodata

For Hewlett Packard Enterprise environmental information, including company programs, product recycling, andenergy efficiency, see:

http://www.hpe.com/info/environment

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs. To help usimprove the documentation, send any errors, suggestions, or comments to Documentation Feedback(mailto:[email protected]). When submitting your feedback, include the document title, part number,edition, and publication date located on the front cover of the document. For online help content, include theproduct name, product version, help edition, and publication date located on the legal notices page.

http://www.hpe.com/support/Storage-Warranties

http://www.hpe.com/support/Networking-Warranties

http://www.hpe.com/support/Safety-Compliance-EnterpriseProducts

http://www.hpe.com/info/reach

http://www.hpe.com/info/ecodata

http://www.hpe.com/info/environment

mailto:[email protected]