Hewlett PackardEnterprise SimpliVity OmniStack for vSphere Deployment Guide Part number: 760-000243 Rev A Published: June 2017 Trademarks SimpliVity®, ®, SimpliVity cube logo®, SimpliVity The Data Virtualization Company®, OmniCube®, OmniStack®, Global Federated Architecture®, Data Virtualization Platform™, SVT™, and RapidDR™ are trademarks or registered trademarks of SimpliVity® Corporation in the United States and certain other countries. All other trademarks are the property of their respective owners. Patents SimpliVity OmniCube® and OmniStack® products are covered by various United States and foreign patents and pending patent applications. Patents include: AU 2010265954; BR PI1013789-0; CA 2,776,231; CN ZL201080033630.9; DE 2433226; DK 2433226; EP 2433226; ES 2433226; FI 2433226; FR 2433226; GB 2433226; IN 679/CHENP/2012; IT 2433226; JP 5695040; NO 2433226; SE 2433226; US 8,478,799; US 9,367,551; US 2016/0283498; EP 12738334.7; HK 14110213.4; US 2013/0024615; AU 2012273295; BR 112013032706-5; CA 2,840,178; CN 201280036259.0; EP 12732895.3; HK 14110215.2; IN 368/CHENP/2014; JP 6059216; US 9,436,748; US 2016-0371354; AU 2013222325; BR 112014020806-9; CA 2,865,240; CN 201380017261.8; EP 13710149.9; HK 15100889.7; IN 6929/CHENP/2014; JP 5902323; US 9,032,183; US 2015/0242315; AU 2014308938; BR 112016003205-5; CA 2,921,039; CN 201480045910.X; EP 14759406.3; IN 201647008897; JP 2016-536408; US 9,043,576; US 2015-0254256; AU 2016206826; BR 112016028144-6; CA WO2016/115219; CN WO2016/115219; EP 16703395.0; IN 201647041955; JP WO2016/115219; US 2016/0202927; US 15/280,347 Copyright Information in this document is subject to change without notification. Reproduction in any manner whatsoever without the written permission of SimpliVity Corporation is strictly forbidden. © SimpliVity Corporation 2017 Customer support To contact SimpliVity Customer Support, visit https://support.simplivity.com. When contacting a representative, you need to know the serial number of your OmniStack server to verify your service subscription. SimpliVity uses OmniWatch to automatically monitor the health of your OmniStack equipment and have it send us notifications of any alerts or errors. 2 Contents Chapter 1: OmniStack deployment overview.......................................5 About OmniStack hosts.................................................................................................................5 About OminStack host deployment...............................................................................................5 Deployment tasks summary..........................................................................................................5 Chapter 2: Install the SimpliVity software............................................ 7 About SimpliVity software..............................................................................................................7 Download the SimpliVity software...................................................................................... 7 About VMware products................................................................................................................8 Linked Mode and deployment............................................................................................ 8 About Deployment Manager......................................................................................................... 8 Deployment Manager screen icons.................................................................................... 9 Deployment Manager software requirements..................................................................... 9 Install Deployment Manager............................................................................................. 10 Uninstall Deployment Manager.........................................................................................10 About Arbiter................................................................................................................................11 Arbiter requirements..........................................................................................................11 Install Arbiter..................................................................................................................... 12 Uninstall Arbiter................................................................................................................. 12 Chapter 3: Verify the deployment environment................................. 14 About deployment environment requirements............................................................................ 14 About OmniStack user accounts.................................................................................................14 ESXi host root account..................................................................................................... 14 vCenter Server single sign-on account.............................................................................14 OmniStack CLI account.................................................................................................... 14 Networking requirements.............................................................................................................14 Maximum transmission unit.............................................................................................. 15 Network address and vSphere inventory requirements....................................................15 Ports required for SimpliVity servers................................................................................ 16 OmniStack host requirements..................................................................................................... 18 Deployment checklist...................................................................................................................19 Chapter 4: Deploy OmniStack hosts...................................................21 About deploying an OmniStack host.......................................................................................... 21 Deployment prerequisites............................................................................................................22 About OmniStack host discovery................................................................................................ 22 3 Connect to a remote management interface.................................................................... 22 Assign a static IP address to an OmniStack host............................................................ 23 Deploy an OmniStack host......................................................................................................... 23 About OmniStack host heartbeats.............................................................................................. 37 Review post-deployment tasks................................................................................................... 37 Chapter 5: Troubleshooting................................................................. 39 About recoverable deployment errors.........................................................................................39 Retry deployment for errors 1-3..................................................................................................40 Retry deployment for errors 4-6..................................................................................................40 Reset OmniStack host discovery state.............................................................................40 Retry deployment for errors 7-33................................................................................................41 Reset the boot drive on a CN-Series host....................................................................... 41 Reset the installer image on a Cisco C240 M3S or Cisco UCS C240 M4SX host............42 Reset the boot drive on a Lenovo x3650 host................................................................. 42 About general deployment issues...............................................................................................43 Cannot connect to port 9299............................................................................................ 43 IP address already assigned............................................................................................ 43 Disconnected hosts........................................................................................................... 43 Network connection timeout..............................................................................................44 .NET needs to be upgraded............................................................................................. 44 OmniStack software version outdated.............................................................................. 44 Cannot connect to OmniStack host.................................................................................. 44 IP address already in use.................................................................................................45 IP address already in use or not associated with server..................................................45 Disconnected hosts........................................................................................................... 45 IP address associated with failed deployment................................................................. 45 Failed deployment with Cisco UCSM and Cisco M3S or UCS C240 M4SX platforms......46 Collect deployment logs.............................................................................................................. 46 Appendix A: Additional information....................................................48 SimpliVity documentation conventions........................................................................................48 Reading path............................................................................................................................... 49 SimpliVity terminology................................................................................................................. 51 Websites...................................................................................................................................... 53 Regulatory information................................................................................................................ 53 Documentation feedback.............................................................................................................54 4 Chapter 1: OmniStack deployment overview This section contains the following topics: • About OmniStack hosts • About OminStack host deployment • Deployment tasks summary About OmniStack hosts OmniStack from SimpliVity, SimpliVity The Data Virtualization Company, is a converged server and storage solution. It provides: • High availability • Scalability • Efficient disaster protection • Global unified management Each OmniStack host comes with the following pre-installed software: • SimpliVity OmniStack • 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, SimpliVity recommends that you deploy OmniStack hosts in sets of two within a cluster. As capacity and performance needs increase, you can add more OmniStack hosts without disruption to users. This network of hosts is called a SimpliVity Federation. Once you deploy OmniStack hosts to a cluster, you can manage them and their related virtual objects using SimpliVity Extension for vSphere Web Client. About OminStack host deployment You can deploy one OmniStack host at a time to a cluster using SimpliVity Deployment Manager. Before you begin using the application, install all the required software and verify your network environment. After you complete the necessary tasks, you can run Deployment Manager and follow the prompts to deploy a host to vCenter Server. You can then manage the virtual hosts and related objects using SimpliVity features in SimpliVity Extension for vSphere Web Client. Deployment tasks summary To deploy an OmniStack host to an existing cluster in vCenter Server, you need to have the appropriate SimpliVity software installed and know the network details required to run SimpliVity Deployment Manager. This chart provides more details on all the tasks you need to complete in the order shown. Task Description Locate or download the Download the SimpliVity software from the Customer Support website SimpliVity Software. for the OmniStack version you use. This includes Deployment Manager and Arbiter. About OmniStack hosts 5 That way. but it is not required to deploy hosts. Install Arbiter on a Windows vCenter Server where you want to deploy hosts or a different Windows computer that the OmniStack hosts can access. and review the deployment checklist. verify the environment. you may want to choose the option to create a configuration file. Once you deploy your hosts. network and required ports for OmniStack. Task Description You can also download SimpliVity Extension for vSphere Web Client." Verify the network Check the accounts to ensure access to the applications. Install Deployment Manager on the Windows computer you plan to use to deploy OmniStack hosts. If the OmniStack hosts are not on the same broadcast domain but are on a reachable network. Tasks" topic after you successfully deploy an OmniStack host. You use it to manage hosts in the hypervisor. Perform post-deployment Perform the post-deployment tasks listed in the "Post-deployment tasks. you can install SimpliVity Extension for vSphere Web Client as described in the SimpliVity OmniStack for vSphere Administration Guide. NOTE: The Windows computer and OmniStack hosts must be on the same broadcast domain for Deployment Manager to discover the hosts automatically on the network. For more information. When you first run Deployment Manager. You can make any necessary modifications as you scroll through Deployment Manager. you must provide the IP address of each host manually. the next time you use Deployment Manager. you can import it when you deploy another OmniStack host. Then. 6 Deployment tasks summary . see "About OmniStack host discovery. you can save the network settings in a file to use it as a template. Install the SimpliVity software. Deploy an OmniStack host. Download this software from the SimpliVity Customer Support website. But. About SimpliVity software 7 . 8. 7. install the following software from SimpliVity: • Deployment Manager: Enables you to use a wizard to deploy the OmniStack hosts. Install Deployment Manager on a supported Window Server or Windows computer. This communication enables you to deploy and manage OmniStack hosts and related objects. Install Arbiter on the vCenter Server where you want to deploy hosts or a different Windows computer that the OmniStack hosts can access. SimpliVity Extension for vSphere Web Client). You can manually enter network information when prompted or import a configuration file (with settings that you saved from an earlier deployment) to automatically populate fields. Click Software. NOTE: You can also download the extension software you need to use to manage hosts in your hypervisor (for example. Click Product Information > SimpliVity Software.. Arbiter preserves the health of the Federation by acting as an independent witness and providing the tie-breaking vote when a Federation contains an even number of OmniStack hosts. 6.Chapter 2: Install the SimpliVity software This section contains the following topics: • About SimpliVity software • About VMware products • About Deployment Manager • About Arbiter About SimpliVity software Before you deploy OmniStack hosts to a cluster in vCenter Server. Go to the SimpliVity Customer Support website. you do not need to install it until you successfully deploy hosts and want to manage them as desribed in the SimpliVity OmniStack for vSphere Administration Guide. 3. Download the SimpliVity software To deploy hosts. • Arbiter: Enables communication between OmniStack and vCenter Server. you need the SimpliVity Deployment Manager and Arbiter software. Enter your user name and password. Save the files in a location you can access. 5. Click the version of OmniStack software you ordered. 4. 2. Procedure 1. Click the name of the software you want to download (SimpliVity Deployment Manager or SimpliVity Arbiter). Click the name of the OmniStack host or OmniStack model that you ordered. 5.xml. About VMware products Before installing the SimpliVity software and deploying OmniStack hosts. see the VMware documentation. But all the OmniStack hosts in a cluster need to use the same version (all ESXi 6. see the Platform Services Controller instructions in the VMware vCenter Server 6. install single sign-on (SSO) using multisite mode (requires an Active Directory [AD] server for authentication). If the OmniStack hosts join a SimpliVity Federation.0 or 6.5 or vCenter Server Appliance 6.0 or 6. Deployment Manager creates the virtual switches (vSwitches) and port groups for the network connection that you specify.0 or later.5. To access vCenter Server. you can import data from a previously saved configuration (XML) file or manually enter the network settings to deploy an OmniStack host. You cannot mix the hypervisor versions in a cluster. you need to know your VMware customer account credentials. specify the Virtual Controller IP address of an OmniStack host in the existing SimpliVity Federation to ensure that the hosts you plan to deploy locates it.0 or 6. verify that your vSphere environment includes one of the following VMware products: • vSphere vCenter Server 6. you need an account with administrator privileges. About Deployment Manager Deployment Manager is a stand-alone Windows application that configures and deploys OmniStack hosts in an existing cluster. For more information on setting up Enhanced Link Mode.5. If you need to download the products or access tools. you specify if you want the OmniStack hosts to create a SimpliVity Federation in the current vCenter Server or join a SimpliVity Federation in a vCenter Server in Linked Mode (or Enhanced Link Mode).5.0 or 6.0 or 6. Either of the listed products comes with vSphere Web Client. Deployment Manager displays the SimpliVity Federation Information screen.5). The first time you deploy a host to a cluster. you can deploy hosts that use ESXi 6. Next steps See the following sections for details on requirements and steps to install the software. if you use vCenter Server 6. Joining multiple vCenter Server systems using vCenter Server Linked Mode enables them to share information.5 documentation. In this screen. you can save them in a configuration file before you deploy the host.0 or 6. The file name format is: starting_ip_address_timestamp. 8 About VMware products . When you import an existing configuration file. For example. The OmniStack hosts must use the same hypervisor version of any hosts that reside in the cluster you plan to deploy to.5. • vCenter Server Appliance 6. When you deploy OmniStack hosts to a cluster. If you do not have these products installed or you need to upgrade them. For example. To support a Federation in linked mode using vCenter 6.0 or 6. Linked Mode and deployment SimpliVity Federations support VMware vCenter Servers in linked mode and enable access to SimpliVity and VMware virtual objects across all OmniStack hosts. With Deployment Manager. You can also use Enhanced Link Mode with vCenter Server 6. If you enter the settings manually. Deployment Manager validates the information and stores it in an XML file located in your home directory by default. the default vSwitch names are vSwitch0 and vSwitch1 for a 1 Gb/s or 10 Gb/s network. For example. Deployment Manager software requirements Only use OmniStack hosts with the same software version in the same cluster. (For more information on upgrading OmniStack software. patents. • Windows 7. The maximum value is 120 seconds. see the SimpliVity OmniStack for vSphere Administration Guide or the SimpliVity OmniStack for vSphere Help. you can deploy multiple OmniStack hosts to the same cluster (or another cluster in another datacenter). Displays the version. • Windows Server 2008 R2. you need to create a datacenter and create one or more clusters for the datacenter. contact SimpliVity Customer Support).2 into that cluster. Any changes you make in the Settings screen take effect the next time you run Deployment Manager. For more information on creating a cluster. • Windows 8. The following software is required to deploy OmniStack hosts using Deployment Manager. in vSphere Web Client. Upgrade the hosts that already reside in the cluster first. OmniStack hosts must reside in one or more clusters. The default value is 30 seconds. You can start a new deployment as the current one runs. Operating System requirements Deployment Manager is supported on these Windows operating systems: • Windows Server 2012 R2.5. The icon also shows the number of deployments in progress. Deployment Manager screen icons Deployment Manager includes these icons at the top of each screen: Icon Description Blinks when deployment starts. NOTE: Before you can deploy a host. Each cluster can contain up to eight OmniStack hosts. Click it to open the status window. and SimpliVity contact information. About Deployment Manager 9 . do not deploy hosts with OmniStack 3. then deploy the new hosts with the same OmniStack version. if your cluster contains hosts with OmniStack 3. but the cluster must contain at least one previously deployed OmniStack host. After you use Deployment Manager to deploy at least one OmniStack host to a cluster.5. (Do not mix versions. Use this screen to set a timeout between Deployment Manager and the vCenter Server that is appropriate for your networking environment. You can also use the Settings screen to initiate the collection of deployment logs for troubleshooting deployment issues. clusters needs to exist in the hypervisor.1.) For example. Displays the Settings screen. trademarks.1. 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 OmniStack hosts. make sure you have administrator privileges to access the system. Procedure 1. double-click SimpliVity Deployment Manager. • If you want all users to access Deployment Manager or just the current user. 2.8 • Microsoft® . Third-party software requirements Install the following third-party software on every Windows computer running Deployment Manager: • Oracle® Java 1. Procedure 1. click Control Panel > Programs > Uninstall a program.0 web installer package or later." • Verify that you have 127 MB of available disk space on the Windows computer. These credentials are required to log on to Deployment Manager. • Obtain the vCenter Server administrator credentials. 3.n.NET Framework 4.msi file. Click Next to continue through the screens. Uninstall an older version before you install a new version.n.n. Click Run and follow the prompts to accept the license agreement. Click Close to when the install process ends. click Browse. 4. • To change the default location of the installation folder (C:\Program Files (x86)\SimpliVity \DeploymentManager) or manually enter a new path. 2. 5. Uninstall Deployment Manager Before you begin Before uninstalling Deployment Manager. click Disk Cost. See "Deployment Manager requirements. Double-click the simplivity-deployment-manager-n. From the Start menu. • If an older version of Deployment Manager is installed on the Windows computer. NOTE: Install only one version of the third-party software on the Windows computer you are using to deploy OmniStack hosts. On the Select Installation Folder screen. accept the defaults or do any of the following: • If you need to view the space available. From the list of installed programs. leave the default of Everyone. 10 About Deployment Manager . uninstall that version. install Arbiter on another Windows computer (separate from the computer with vCenter Server). For a computer other than the one with vCenter Server. select the cluster that needs its own Arbiter and enter the IP address of the computer that has it. click OK. if your datacenter includes clusters that run several thousand virtual machines and you already installed Arbiter on vCenter Server. if a cluster contains two OmniStack hosts and one of those hosts loses connectivity with the cluster.) Arbiter requirements Your version of Arbiter should match the version of OmniStack used by your hosts. 4. you must specify the IP address to ensure communication with the Federation. (Do not install Arbiter on a virtual machine managed within the same cluster it serves. Wait while the installer removes the software. NOTE: The Arbiter application ensures the resiliency of the Federation by acting as a tie-breaking vote in cluster failure scenarios that include an even number of OmniStack hosts. Review these requirements before installing Arbiter on the computer hosting a vCenter Server or a different Windows computer. Install the latest version of VMware tools on any virtual machine that is hosting Arbiter.000 virtual machines and associate it with one or more clusters in a Federation to distribute the workload. For example. About Arbiter 11 . you specify the Arbiter location. 5. Caution: To ensure the best performance. Then. You can select the vCenter Server or a different Windows computer. It must run on the computer hosting vCenter Server or on another Windows computer. To confirm that you want to delete the extension. Do not install it on a virtual machine that resides on an OmniStack host or any host that uses a SimpliVity datastore. Installing Arbiter on a computer outside the Federation ensures its availability. When you run Deployment Manager. Feature Requirement CPU frequency 1. Arbiter provides the tie-breaking vote when a cluster contains an even number of OmniStack hosts. About Arbiter The SimpliVity Arbiter software runs on the computer hosting a vCenter Server or a different Windows computer that the hosts can access. when you deploy hosts. click Next. install a new Arbiter for every 4. It is required in every SimpliVity Federation.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. Arbiter acts as the tie breaker. click Yes. When finished. For example. 3. To close the information window. ) 2. 2008R2. Network 1xGigE Supported operating Windows Server 2008. 2012R2. Click Run. 4. Select the license acceptance box and click Next.msi file. 3. 2016 systems Install Arbiter Before you begin Before you deploy OmniStack hosts. click Finish.2K RPM HDD for up to 128 virtual machines.n. (This file comes on the USB stick that ships with the product or you can download it from Customer Support. install Arbiter. On the Welcome screen. The Setup Type screen opens. To start the setup wizard. Do not recover the Arbiter storage device to a previous point in time with a snapshot or backup and restore process or you could corrupt the virtual machine data. click Next.n. Uninstall Arbiter Before you begin 12 About Arbiter . For example: • 1 x 7. NOTE: One Arbiter can control up to 4096 virtual machines. 6. click the simplivity-arbiter-n. • 1 x 10K RPM HDD for up to 256 virtual machines. Click Complete and then click Install. • 1 x SSD for up to 4096 virtual machines. 2012. Storage type Storage device capable of 80 IOPS per 128 virtual machines in the arbitration control domain. In the Completed screen. Procedure 1. Feature Requirement Persistent storage Minimum of 16 GB (HDD or SDD) NOTE: Set disk caching policy to write-through or write cache disabled.n. 5. To close the information window. To confirm that you want to delete the extension. double-click SimpliVity Arbiter. click Control Panel > Programs > Uninstall a program. click Next. When finished. click OK. About Arbiter 13 . From the Start menu. click Yes. From the list of installed programs.Before uninstalling Arbiter. 3. 5. 2. Wait while the installer removes the software. Procedure 1. make sure you have administrator privileges to access the system. 4. use the SimpliVity OmniStack CLI account to run SimpliVity CLI commands as described in the SimpliVity OmniStack for vSphere Command Reference Guide. you assign the OmniStack host. vCenter Server (Active Directory supported) accounts that can manage a Federation. 14 About deployment environment requirements . vCenter Server single sign-on accounts. Refer to the deployment checklist at the end of this section to review the main tasks. review the following network sections to ensure you deploy the hosts successfully. Storage. OmniStack Virtual Controller (a virtual machine running OmniStack software). vCenter Server single sign-on account vCenter Server single sign-on accounts are controlled-privilege.Chapter 3: Verify the deployment environment This section contains the following topics: • About deployment environment requirements • About OmniStack user accounts • Networking requirements • OmniStack host requirements • Deployment checklist About deployment environment requirements Before you deploy OmniStack hosts. and Federation. or CLI commands. During deployment. see the VMware documentation for your ESXi host version. About OmniStack user accounts This section describes the user accounts used to deploy and manage OmniStack hosts. including the ESXi root user. OmniStack CLI account When your VMware single sign-on account is not available. ESXi host root account Use the ESXi host root user account to log on to an OmniStack host. For ESXi host password requirements and restrictions. • Use existing networks (such as a dedicated virtualization management network) if you have appropriate networks in your VMware environment. Networking requirements An OmniStack host in a Federation requires three separate networks: Management. Also do the following: • Maintain a separate network for 10 Gb/s storage data traffic between OmniStack hosts in a Federation. You create the password for the ESXi host root user account when you deploy an OmniStack host using Deployment Manager. and the VM Kernel port to one or all of the networks. the MTU on the Management. set the MTU for the Storage and Federation networks to 9000 to ensure vMotion functions as expected. ensure that the Management network and OmniStack host can route to each other through a common VLAN. the MTU size on the Storage and Federation networks must be the same value.pool.org. Record any NTP servers the vCenter Server is using. However. You can close these ports after a deployment is complete. Networking requirements 15 . set the MTU to 9000 for a 10 Gb/s connection. • Use VLANs to separate management and virtual machine traffic. Maximum transmission unit For best performance.us. and Federation networks must be the same value.ntp. The MTU size on the Management network can be any value (1500 is recommended) but the MTU value must be the same on all Management networks on the subnet. enable Service Location Protocol (SLP) for automatic host discovery.org through 3. Storage. NOTE: To deploy a host with Deployment Manager. • The MTU setting for the Management. • The MTU size range on the Federation networks is 1000 to 9000 bytes. For a 10 Gb/s network. Network address and vSphere inventory requirements This table describes the network address requirements and objects required in the vSphere inventory to contain the OmniStack hosts. At least three NTP servers are required for an OmniStack host deployment. For best performance. The default servers are 0. use the following Maximum Transmission Unit (MTU) settings to deploy and manage OmniStack hosts: • When using Cisco UCS Manager to manage OmniStack network interfaces with a MTU greater than 1500.ntp. Storage.us.pool. • Open TCP ports 9292 and 9299 on the Management network to deploy OmniStack hosts. • For a 1 Gb/s or 10 Gb/s NIC. • For Cisco servers managed through Cisco Integrated Management Controller (CIMC) with an MTU setting greater than 1500. Requirement Description NTP The Network Time Protocol (NTP) is preconfigured in an OmniStack host using US internet time servers. and Federation networks must match the MTU settings used for any OmniStack hosts that already reside in the cluster (if available). set the Quality of Service (QoS) MTU attribute to 9216. The Management network can remain at the default setting of 1500. The host you plan to deploy cannot be a DNS child domain. In addition: • The DNS servers must be the same and reachable by the OmniStack Virtual Controller. For ports required by: • vSphere hypervisor. Requirement Description DNS Server The IP address for a primary and optional secondary DNS server. • VMkernel Port. • Virtual Controller. OmniStack IP Addresses There are separate OmniStack IP addresses that you assign to these five interfaces on the OmniStack networks during a deployment: Management Network. see the vendor documentation. OmniStack host. Cluster The name of the cluster in vCenter Server where you want to deploy the OmniStack hosts. Storage Network. see the VMware documentation. • You need a default DNS suffix to search for a domain. vSphere Web Client. vCenter Server IP address The IP address or FQDN for the vCenter Server planned to or FQDN contain the SimpliVity Federation. • Virtual Controller. Federation Network. see the SimpliVity Extension Help. • Your specific platform. such as the IPMI port. • OmniStack host. To create a cluster in a datacenter. 16 Networking requirements . • Virtual Controller. and the Windows computer running Deployment Manager. vCenter Server. Ports required for SimpliVity servers OmniCube or OmniStack hosts require these ports to communicate with your network and other hosts. • You need a DNS suffix name for each OmniStack host. 427 TCP and UDP Management Deployment OmniStack Deployment Manager host operation and monitoring. using SSH. 9292. You can close this port after a deployment is successful. to the • OmniStack server when Virtual the web server Controller is unavailable. host • Deployment Manager 9190 TCP Management • Deployment OmniStack OmniStack Manager Virtual CLI or Controller vSphere Client • vSphere access to the Web Client OmniCube or OmniStack server.Ports Protocols Networks Sources Destinations Description 22 TCP All Management • OmniStack For remote Workstation host access. 443 TCP Management • OmniCube • vCenter SSL ports for or Server vSphere ESXi OmniStack and vCenter • OmniStack server Server. 80 TCP Management Deployment • OmniStack Deployment Manager host monitoring and Support • OmniStack Capture Virtual downloads Controller used by SimpliVity Support. Networking requirements 17 . 9299 TCP Management Deployment OmniStack Deployment Manager host Manager access to the host over SSL. This port must be open to deploy the OmniCube or OmniStack server. 18 OmniStack host requirements . If communication on the Federation network fails. Arbiter communication. ensure the following: • Install at least two OmniStack hosts on a rack in your data center. • Avoid deploying OmniStack hosts across a wide-area network (WAN). But. OmniStack host requirements Before deploying an OmniStack host. 2049. you cannot deploy a CN-3400 (large storage size) to a cluster with CN-1200 and Cisco USC C240 hosts (small storage size). Check that they are connected to the power and powered on. • To deploy multiple OmniStack hosts to a cluster. Ports Protocols Networks Sources Destinations Description 9390 TCP Management OmniStack OmniStack Event Virtual Virtual Manager Controller Controller uses this port to manage events between the OmniStack Virtual Controllers on the OmniStack hosts. 22122 UDP and TCP Federation • OmniStack • OmniStack Federation and Virtual Virtual traffic between Management Controller Controller hosts. the servers must use the same number of CPUs (single or dual) and use similar storage size. the Management network is used. • Arbiter and backups to remote clusters. you can deploy CN-3400 to a cluster with CN-3000 and CN-3400 already deployed to the same cluster. Network disruptions can cause the deployment to fail. 111. UDP and TCP Management OmniStack OmniStack Management 32764-32768 and Storage host host and Storage traffic between OmniStack hosts or standard hosts that share a SimpliVity datastore. For example. 0.) OmniStack UCS only: Requires Cisco UCSM maintenance release (2. if managed only in standalone mode. NOTE: Take an inventory of all the OmniStack hosts you plan to deploy by serial number also.4) or deploy OmniStack UCS C240 M4SX Verify the UCSM version. For more information about interoperability requirements. Check the password complexity. slash) in your OmniStack host password (if prompted to set one during deployment). Log on to SimpliVity Support at support. Deployment checklist To ensure a smooth and an efficient deployment. review the following checklist. (If you saved the form online. see the Interoperability Guide for your platform available from SimpliVity Support at https://support. mode is requested.com. Check that the following is See the Hardware Installation and Maintenance configured: IPMI.com). ampersand.simplivity. Fill in the predeployment forms. Do not use special characters (for example. Click My Support.) Check that the vCenter Server To check the hypervisor compatibility.simplivity. Ensure that two or more OmniStack servers are installed in each rack and the servers are powered on.simplivity. or UCSM. Follow the prompts to fill in a predeployment form online or print a PDF version of it. click Product Information > SimpliVity Platforms > <name of your server> and scroll down to the link for the Interoperability Guide. Deployment Manager shows the status of a deployment by serial number only. site (support. Then click Deployment Planning. √ Step Details Install one or more servers on racks. you can access it again at any time through the Deployment Planning option in the SimpliVity Support Center. see the version is compatible with the ESXi Interoperability Matrix on the SimpliVity Support version. asterisk. (From the Support Home page.com. See your hypervisor documentation and the SimpliVity OmniStack for vSphere Release Notes for details on character limitations. Guide for your platform for details. This information allows you to prepare the information you need to enter when you run Deployment Manager to deploy hosts. CIMC. Deployment checklist 19 . Arbiter. Verify the NTP server. Install the correct version of all Download Deployment Manager. Check for duplicate IP addresses. The OmniStack version must also match the version installed on any hosts previously deployed (if you deploy to the same location). Storage." the specified ports. and Federation. Management. and required SimpliVity software. them already). 20 Deployment checklist . SimpliVity Extension for vSphere Web Client from SimpliVity Customer Support. cluster use the same version of the OmniStack software. Check that you have administrator Obtain the vCenter credentials (if you do not know access to vCenter Server. Check the IP addresses/network Verify there are three separate networks: configuration. √ Step Details Verifty that the DNS resolution of Use the nslookup command at each computer IP addresses (IPv4 supported) to verify address resolution: is identical on the computer with nslookup <ip-address-of-host> Deployment Manager installed and on the computer with vCenter Server installed. Verify that the MTU size matches that of existing Federation members. Check that the firewall is set to allow See "Ports required for SimpliVity servers. Check that the OmniStack versions Check that all the hosts you plan to deploy to a on the hosts are the same. During the deployment of an OmniStack host. Once you deploy your hosts. You can rename a host using the svt-host-rename command as described in the SimpliVity OmniStack for vSphere Command Reference Guide.Chapter 4: Deploy OmniStack hosts This section contains the following topics: • About deploying an OmniStack host • Deployment prerequisites • About OmniStack host discovery • Deploy an OmniStack host • About OmniStack host heartbeats • Review post-deployment tasks About deploying an OmniStack host With Deployment Manager. This helps you deploy hosts faster because you have a template. Before you can deploy the host. you see a message with an appropriate workaround. the OmniStack host appears in vCenter Server with an assigned IP address. If it detects any issues. Deployment Manager performs a reverse DNS lookup. For example. port group name. The configuration file contains store network settings. Just import the file when prompted and make the appropriate modifications to the populated fields as you click through the Deployment Manager wizard. Network Interface Card (NIC) speed and connection. NOTE: If Deployment Manager cannot determine the host name associated with the IP address of a host. About deploying an OmniStack host 21 . Deployment Manager runs a series of validation tests on the network settings. When an IP address does not resolve to a host name. it checks the IP address. Once you deploy two or more OmniStack hosts. NOTE: OmniStack hosts must reside in one or more clusters in a datacenter. see "Post-deployment tasks." NOTE: You can deploy OmniStack hosts using the procedures in this document or see the SimpliVity OmniStack for vSphere Command Reference Guide for details on using deployment commands. it deploys the host with the IP address as the name. You can also use Deployment Manager to import a previously saved configuration file. Each cluster can contain up to eight OmniStack hosts. you can deploy one OmniStack host at a time to a cluster. The renaming process does not impact the I/O performance of the virtual machines residing on the host. When an IP address resolves to a host name. You can stop and start the tests at any time if you need to make any changes to your settings before you continue. For more information. the OmniStack host appears in vCenter Server with an assigned host name. you can manage them and their associated virtual objects through SimpliVity options in your hypervisor. you created a SimpliVity Federation in your hypervisor. (With vSphere HA. virtual machines on one failed host can restart on a healthy OmniStack host if one is available. use Deployment Manager 3. netmask. an OmniStack host may not acquire a temporary IP address automatically. • If deploying a single OmniStack host. OmniStack hosts must reside in one or more clusters in a datacenter. you must manually obtain an IP address for the OmniStack host. For more information. connect the OmniStack server to a Windows computer. • Only IPv4 addresses are supported. You do not have enough OmniStack hosts. For example. If the Windows computer and an OmniStack host are not on the same network.Deployment prerequisites Before you begin using Deployment Manager.) About OmniStack host discovery When you power on an OmniStack host. This requires that you manually assign a static IP address. ESXi 6." • Open TCP ports 9292 and 9299 on the Management network to deploy an OmniStack host. • Check that the OmniStack hosts in the same cluster are the same model types with the same number of CPUs (single or dual).1. • Know the hypervisor version used (for example. • All OmniStack hosts you plan to deploy use the same OmniStack software version. such as model type and serial number. and launch the virtual console or KVM console before you can assign a static IP address. • Check that your version of Deployment Manager is the same version as the OmniStack version of your hosts or later. Connect to a remote management interface If you need to assign a static IP address to the host you want to deploy because the host could not obtain one automatically. do not enable vSphere High Availability (HA).0 or 6. • Verify the Windows computer you are using to deploy an OmniStack host is not configured to enter hibernation or sleep mode during the deployment. The temporary IP address connects to an installer and collects the properties of an OmniStack host. You can close these ports after the deployment is successful. and gateway to the OmniStack host during the deployment process.6. In certain situations.1 or later. The temporary IP address allows the Deployment Manager client to communicate with the OmniStack host. For example. see "About OmniStack discovery. Procedure 22 Deployment prerequisites . if your hosts use OmniStack 3. it obtains a temporary IP address from a DHCP server.6. • The Windows computer and OmniStack hosts you plan to deploy must be on the same network. The Deployment Manager client uses the Service Location Protocol (SLP) to discover the OmniStack host. Do not mix OmniStack versions in the same cluster.5) on each OmniStack host you plan to deploy. connect to the remote management interface for your server (for example. the cluster you plan to deploy to has CN-5000 and CN-5400 dual CPU server models and you plan to deploy two more CN-5400 dual CPU models. IDRAC). review the following list to ensure that you successfully deploy the OmniStack hosts: • You created a cluster under the datacenter where you want to deploy the OmniStack hosts. Each cluster can contain up to eight OmniStack hosts with a maximum of 32 OmniStack hosts in a Federation. Press Tab to select Enable NIC and press Enter. when the status is Waiting to be discovered. Connect to the remote management interface and launch the virtual console or KVM console for your platform. specify the IP address on the Select OmniStack Host screen. Connect an Ethernet cable from the Windows computer to the Ethernet management port on the rear of the OmniStack host. Configure the remote management interface for your platform. 7. You can only deploy one host at a time. Deploy an OmniStack host Procedure overview Follow the steps in this procedure to deploy an OmniStack host to a cluster. In Deployment Manager. press Ctrl+N . Press Tab to Apply and press Enter. and gateway for the OmniStack host. you can manually enter the host settings or import a previously saved configuration file to automatically populate fields. 2. 3. 4. Determine the network interface for the connection you are planning to use on the Management network to deploy the OmniStack host. see the Hardware Installation and Maintenance Guide for your platform. Assign a static IP address to an OmniStack host Procedure 1. 5. On the SimpliVity Installer screen. indicate the VLAN for the network interface as follows: Use the Tab key to select Add VLAN and press Enter. 2. Deploy an OmniStack host 23 . The SimpliVity Installer screen opens. netmask. However. b) Enter the VLAN ID for the network interface.) Procedure 1. To deploy a host. Open Deployment Manager on the Windows computer you want to use to deploy the OmniStack hosts. after you deploy the first host. For more information. 1. Then use the Tab key to select OK and press Enter. 3. 6. a) Use the Tab key to select Add VLAN and press Enter. If the Management network and network interface are on different VLANs. Press Tab to specify the IP address. (You can save the settings you enter in Deployment Manager before you deploy a host. Press Tab to select Done and press Enter. you can start the deployment of another host while another host deploys. enter the vCenter Server IP address and administrator credentials. 2. Leave the hypervisor set to VMware vSphere. 24 Deploy an OmniStack host . Then. Do one of the following: • If you selected a cluster with existing OmniStack hosts. Expand a datacenter and select a cluster for deployment. Each cluster can contain up to eight OmniStack hosts. Click Refresh Inventory to update the contents if necessary. For example: 3.) Click Login to open the Select Deploy Location screen. NOTE: OmniStack hosts must reside in one or more clusters in a datacenter. skip to step 7. (Do not try to log on to the local host or use the loopback address. 4. you cannot continue to this screen until that first host completes the deployment process. You can check the progress through the deployment icon ( ). But. Deploy an OmniStack host 25 . the cluster you selected does not have any existing hosts. NOTE: If you only see the "SimpliVity Arbiter Information" section to specify the location of Arbiter. This ensures that Deployment Manager can locate the correct vCenter Server you want to use.) 6. select one of the following to define the Arbiter information: • SimpliVity Arbiter is installed on this vCenter • SimpliVity Arbiter is installed on a different Windows computer In the IP address of the Windows server running the SimpliVity Arbiter field. enter the management IP address of a Virtual Controller in the Federation. enter the Windows server IP address. • Join an existing SimpliVity Federation: You plan to deploy an OmniStack host to a Federation with vCenter Server in Linked Mode or Enhanced Link Mode. If you recently deployed your first host to a cluster. 7. Arbiter. Click Next to open the Select Method screen. (The management IP address is part of the Virtual Controller name. click Next to open the Define Settings for Federation. Skip to step 6 if you only see Arbiter options. or Both screen. 5. If shown. • If you selected a cluster without existing OmniStack hosts. you logged into a vCenter Server with previously deployed OmniStack hosts in the Federation. Select one of the following: • Create a SimpliVity Federation: You plan to deploy an OmniStack host to create a new Federation in vCenter Server. In the Existing SimpliVity Federation Virtual Controller management IP address field. Click Scan to automatically discover hosts on the broadcast domain and populate the table. Click Next to open the Select an OmniStack Host screen. Click Browse to select the configuration file (XML) you want to import. If you do not see the host you want to deploy. For example. your screen populates with details similar to this (IP not shown in example): 26 Deploy an OmniStack host . By default. • Import configuration (XML) file: Select this option to import data from an existing configuration file and automatically populate some network fields. Deployment Manager stores configuration files to the C:\Users\<user name>\My Documents directory. Do one of the following: • Manually enter settings: Leave this option selected to manually enter the network information to deploy a host. 10. You can modify the data at any time during the deployment. enter the IP address in the Add host IP address field and click Add. (You need Read privileges to import the file.) 9. 8. Deploy an OmniStack host 27 . Click the NIC Details icon ( ) to see the supported hypervisors and Network Interface Cards (NICs) used on each host.x).11. maximum link speed (1 gigabit per second [Gb/s] or 10 Gb/s). check the physical server.510. or switch.com. and link (connection) status. port. NOTE: Click the X icon to close the details. Once you select a hypervisor version in the Select Hypervisor Version field. contact SimpliVity Support at support. model name and number. 13. To update the Installer application on the host.x or all 6. A host may come equipped with many NICs (for example. if you use vCenter Server 6. three to 10).5. Or. Select the hosts you want to deploy and click Next to open the Select Network Interface Cards screen. 12. Expand the network adapter name to review the interface. These details help you determine what NIC to use for the networks.0 or 6. the version of the SimpliVity Installer application on the host may be older than the Deployment Manager version. Select the desired hypervisor version from the Select Hypervisor Version drop-down menu. MAC address (physical address and unique port identifier). vendor. For example. But. card. You may have a faulty cable. each host in a cluster must use the same hypervisor version (all 5.simplivity. Deployment Manager prevents you from selecting any OmniStack hosts that do not support this hypervisor version. If you do not see any NIC details for a host or a NIC appears disconnected. you can select ESXi 6. 14. In addition. 28 Deploy an OmniStack host . But. select the NIC you want to use for each network from the chart that opens in the drop-down lists. In the Management NIC and Storage and Federation NIC fields. For example: NOTE: You can use the same NIC for the each network. select NICs with the same link speed combination for each host (for example. 15. all 1 Gb/s and 10 Gb/s or all 10 Gb/s and 10 Gb/s). use a NIC with a link speed of at least 1 Gb/s for the Management network and 10 Gb/s for the Storage and Federation network. Click Next to open the Set OmniStack Passwords screen. Your selections must also match the link speed combination of any OmniStack hosts that already reside in the cluster (if available). Click Next to open the Configure Management Network Settings screen. enter the following Management network information for the management connection.) Then enter the Command Line Interface (CLI) password and confirm it for command line access. 17. • Host Netmask. 18. and Paste options. Enter a value between 0 to 4094.16. Enter the password for the root user account to log on to the OmniStack host and confirm it. Deploy an OmniStack host 29 . If deploying hosts to a cluster with existing OmniStack hosts. On the Network Settings tab. NOTE: You can right-click some fields to access Cut. (Use the password requirements of the hypervisor. • Host VLAN ID. Virtual Controller. and host: • Host Gateway. Copy. you see some of the fields populate with default responses that provide limited options for changes or must remain as shown. you cannot change the default name. If you selected two NICs. you cannot change the default name. • Host Port Group Name. 21. If performing a new deployment. Select the name from the drop-down list. NOTE: If you selected one NIC for the Management and Storage and Federation networks. • Management vSwitch Name. However. 20. Deployment Manager accesses the vSwitch names from vCenter Server. If performing a new deployment. you can select one vSwitch for the Management network and another vSwitch for the Storage and Federation networks. you cannot change the default vSwitch name. Enter the host and Virtual Controller IP addresses for each host you plan to deploy. If performing a new deployment. • Virtual Controller Port Group Name. Click Next to open the Configure Storage Network Settings screen. 19. Select the name from the drop-down list. Select the name from the drop-down list (if more than one vSwitch is available). the Storage and Federation networks should use the same vSwitch because they use the same NIC. • MTU. • Virtual Controller Netmask. Enter a value between 0 to 4094. Click the IP Addresses tab. Enter a value between 1000-9000. • Host Controller VLAN ID. 30 Deploy an OmniStack host . • Virtual Controller Gateway. The MTU setting must match the MTU settings used for the Management network of any OmniStack hosts that already reside in the cluster (if available). select the same vSwitch for all the networks (for example. all vSwitch0). • Virtual Controller Gateway. you cannot change the default name. If performing a new deployment. • Host Port Group Name. you can select one vSwitch for the Management network and another vSwitch for the Storage and Federation networks. • Host VLAN ID. the Storage and Federation networks should use the same vSwitch because they use the same NIC. The MTU setting must match the MTU settings used for the Storage network of any OmniStack hosts that already reside in the cluster (if available). • Virtual Controller Port Group Name. • Host Netmask. select the same vSwitch for all the networks. • Virtual Controller Netmask. this field defaults to the name used for the Management network and you cannot change it. If you selected two NICs. • Virtual Controller VLAN ID. • MTU. NOTE: If you selected one NIC for the Management and Storage and Federation networks. If performing a new deployment. Select the name from the drop-down list. If you selected the same NIC link speed for the networks of a new deployment. Enter a value between 0 to 4094. On the Network Settings tab. Virtual Controller. 23. you cannot change the default name. Select the name from the drop-down list (if more than one vSwitch is available). and host: • Host Gateway. • Storage vSwitch Name. enter the following Storage network information for the storage connection. Enter a value between 0 to 4094. Click the IP Addresses tab. However. Enter a value between 1000-9000.22. Select the name from the drop-down list. Deploy an OmniStack host 31 . • Virtual Controller Netmask. 24. enter the following Federation network information for the connection and Virtual Controller: • Virtual Controller Gateway. If you selected the same NIC link speed for the networks of a new deployment. • Virtual Controller VLAN ID. On the Network Settings tab. If you selected two NICs. Select the name from the drop-down list (if more than one vSwitch is available). 25. Click Next to open the Configure Federation Network Settings screen. Enter the host and Virtual Controller IP addresses for each host you plan to deploy. select the same vSwitch for all the networks. you can select 32 Deploy an OmniStack host . • Federation vSwitch Name. this field defaults 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. 26. Enter a value between 0 to 4094. 28. 30. Enter the domain name (with a DNS suffix). Deploy an OmniStack host 33 . 29. • Virtual Controller Port Group Name. However. Enter the Virtual Controller IP address for each host you plan to deploy. you cannot change the default name. If performing a new deployment. Select the name from the drop-down list. Enter a value between 1000-9000. Click Next to open the Configure Host DNS Settings screen. the Storage and Federation networks should use the same vSwitch because they use the same NIC. • MTU. Enter the following host DNS information: • Domain. 27. The MTU setting must match the MTU settings used for the Federation network of any OmniStack hosts that already reside in the cluster (if available). • Search Domain. one vSwitch for the Management network and another vSwitch for the Storage and Federation networks. Click the IP Addresses tab. ntp. • Find and register the host by domain name. You can scroll down the screen to see all of the settings. For example: 34 Deploy an OmniStack host . The default servers are: • 0. • Secondary Server. Click Up or Down to change the priority order of the NTP servers.pool. Leave this option selected for DNS to perform a lookup for the hostname and register it in vCenter with that name.org • 1.org • 2. 31.org You can add an IP address or DNS name for an alternate NTP server in the Alternate Server field and then click Add. If it cannot find the name. Deployment Manager still deploys the host to vCenter with the IP address.ntp. • Primary Server.org • 3.pool. see the SimpliVity OmniStack for vSphere Command Reference Guide.us.pool. 33. For more details on using this command.us.ntp. Select at least three NTP servers and click Add. Click Next to open the Select NTP Servers for Host screen. Click Next to review the information in the Review Deployment Details screen.us. 32. You can change the name at any time after deployment using the svt-host-rename command.ntp.us.pool. NOTE: If some tests fail. Once the tests pass. If Deployment Manager detects any issues. the network. you can make changes to physical hardware. Click Next to open the Test Host Settings screen. or click Back and change settings. When ready. Deploy an OmniStack host 35 . you can continue. the Start Test button toggles to Rerun Test. 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. 34. For example. click Rerun Test. This gives you time to make corrections. You can toggle between starting and rerunning the test as needed through the Start/Rerun Test button. you see the messages with any necessary troubleshooting tips in the Test Details section. Click Start Test when ready to test the host settings. Use the legend to review the status as the test runs. NOTE: If you need to make corrections. 35. • Select Save settings in a configuration file to save the settings in a configuration file that you can import as a template for later deployments. Do one of the following: • Select both options to deploy the OmniStack hosts and create a configuration file. • Select Start deployment to deploy the OmniStack hosts. click Next to open the Start Deployment. Then. 38. click Save As and browse to a directory. Specify the desired filename for the configuration file and click Save. 36. Next steps 36 Deploy an OmniStack host . When all the tests pass and you see a success message in the Test Details section. Click Finish. 37. If you chose to deploy the OmniStack hosts. Deployment Manager displays the Monitor Deployment screen. or Both screen. You do not deploy any hosts at this time if you only select this option. Save Settings. ◦ Create datastores. ◦ Set the time zone for all the clusters (defaults to Coordinated Universal Time [UTC]). create or migrate virtual machines. See the SimpliVity Extension for vSphere Web Client Help for information about monitoring events and alarms. complete these tasks for each OmniStack host. ◦ Assign backup policies to the virtual machines.) • Complete the following tasks as described in the SimpliVity OmniStack for vSphere Administration Guide or the SimpliVity OmniStack for vSphere Help: ◦ (Optional) Configure NIC teaming on the standard or distributed port groups.com. Review post-deployment tasks After a successful deployment. On any Deployment Manager screen. This deployment status icon shows the number of deployments in progress. you can monitor and maintain their connections through two heartbeat functions. SimpliVity also supports the VMware vSphere HA datastore heartbeat if it is configured in your environment. For example. ◦ Set up your virtual environment. You can also find steps to restart Arbiter (if necessary).simplivity.com/support/pubs/ • Install SimpliVity Extension for vSphere Web Client on the computer where the vCenter Server is installed. To start a new deployment from the Monitor Deployment screen. ◦ Add rules to the backup policies. If this heartbeat stops. If the Arbiter heartbeat stops. ) at the top of the screen to display the deployment status. click New Deployment. • Configure the VMware license settings for vCenter Server and the ESXi hosts. go to support. (To download the application. ◦ Create backup policies. You can start a new deployment while the current one runs. For more information. you can clear it from the list by clicking Clear Completed. Once a host successfully completes the deployment. you can click the square deployment status icon (for example. About OmniStack host heartbeats Once you deploy hosts to a Federation. vCenter Server displays the following error message: SimpliVity Accelerator Firmware Unresponsive. • The Arbiter application provides a connection heartbeat between the OmniStack hosts within a Federation. see the VMware documentation at: https://www. About OmniStack host heartbeats 37 .vmware. • The Accelerator Firmware also provides a heartbeat. vCenter Server displays the following error message: Lost contact with the Arbiter at ip-address. ◦ Install SimpliVity Extension for vSphere Web Client on the computer where the vCenter Server is installed. it deploys the host with the IP address as the name. But. you can rename a host using the svt-host-rename command as described in the SimpliVity OmniStack for vSphere Command Reference Guide. NOTE: If Deployment Manager could not determine the host name associated with the IP address of a host. The renaming process does not impact the I/O performance of the virtual machines residing on the host. 38 Review post-deployment tasks . To view status messages when a deployment is in progress. • Deployment Manager did not locate the OmniStack host during discovery. For example: The point when a deployment fails determines the action you can take to retry the deployment. • For errors between steps 4-6. ). About recoverable deployment errors 39 . click the blinking deployment icon at the top of the screen (for example.Chapter 5: Troubleshooting This section contains the following topics: • About recoverable deployment errors • Retry deployment for errors 1-3 • Retry deployment for errors 4-6 • Retry deployment for errors 7-33 • About general deployment issues • Collect deployment logs About recoverable deployment errors An OmniStack host deployment can fail when these conditions occur: • There is a temporary network interruption. • For errors between steps 1-3. Deployment Manager displays an error message with the serial number of the OmniStack host. make any necessary changes on the screens and retry the deployment. reset the OmniStack host discovery state as described in this guide and try the deployment again. When a deployment fails. review the error message. Retry deployment for errors 4-6 When a deployment fails between steps 4-6.com. (For example.com. reset the boot drive or installer image as described in this guide and retry the deployment. If deployment continues to fail between steps 4-6. Reset OmniStack host discovery state Before you begin Verify an active instance of Deployment Manager is not currently discovering or deploying the OmniStack host where you are resetting the discovery state. • Connect an Ethernet cable from the Windows computer to the Ethernet management port on the rear of the OmniStack host. 40 Retry deployment for errors 1-3 . Log in with your account and click the appropriate options to launch the virtual console and open the SimpliVity Installer screen. reset the OmniStack host discovery state using the SimpliVity Installer software and retry the deployment.simplivity. or Intelligent Baseboard Management Controller [iBMC] for Huawei servers.) See the section that applies to your error to troubleshoot the issue. If the procedures fail. Retry deployment for errors 1-3 When a deployment fails between steps 1-3. open Intelligent Platform Management Interface [IPMI] for CN servers. Do one of the following. press Ctrl+R when the status is Discovered. On the SimpliVity Installer screen.com. Integrated Management Module [IMM] for Lenovo. The following messages may appear during the reset process: a) Press Enter to continue if OmniStack displays the following message. Procedure 1.simplivity. contact SimpliVity Customer Support at support. contact SimpliVity Customer Support at support. 2. (The procedure you follow depends on your server type. Configure and connect the remote management interface for your server and launch the virtual console and open the SimpliVity Installer screen. See the following section for details. Cisco Integrated Management Controller [CIMC] for Cisco servers. retry the deployment. • For errors between steps 7-33. If it continues to fail between steps 1-3. depending on your internal network: • Open a supported browser and open the remote management interface for your server. contact SimpliVity Customer Support at support.simplivity. Retry the deployment using Deployment Manager. Reset the boot drive on a CN-Series host Use this procedure to retry an OmniStack host deployment on a CN-Series platform. b) Press Tab to make a selection. If deployment continues to fail between steps 7-33. • Select Cancel if deployment of this OmniStack host is in progress. If the deployment fails. Then clear the error in Deployment Manager and retry the deployment. contact SimpliVity Customer Support at support. See the following sections for details. Retry deployment for errors 7-33 41 . Retry deployment for errors 7-33 When a deployment fails between steps 7-33. • This message indicates that an instance of Deployment Manager has discovered this OmniStack host and is in the process of deploying it. Lenovo server.simplivity. reset the boot drive on a CN-series server. you reset the installer image instead. • Select OK to prepare this OmniStack host for deployment. This message indicates that the OmniStack host is available and is ready for redeployment. or Huawei server. Press Enter if OmniStack displays the following message. contact Customer Support. For a Cisco server.com. 3. The SimpliVity Installer screen opens. depending on your internal network: • Open a supported browser and enter the URL with the IP address or domain name of the Integrated Management Module (IMM) of the affected host. Then click Tools > Power > Cycle and click Yes to confirm. depending on your internal network: • Open a supported browser and enter the URL with the IP address or domain name of the Intelligent Platform Management Interface (IPMI) of the affected host. 5. On the GNU GRUB screen. Do one of the following. Procedure Contact Customer Support. Select Java Client and click Start remote control in single-user mode. Log in with your account and select Remote Control from the main screen. Click Yes when prompted to confirm the reset. • Connect an Ethernet cable from the Windows computer to the Ethernet management port on the rear of the OmniStack host. Configure and connect the remote management interface for your server and launch the virtual console. Reset the installer image on a Cisco C240 M3S or Cisco UCS C240 M4SX host Retrying an OmniStack host deployment on a Cisco UCS C240 M3S or Cisco UCS C240 M4SX requires a factory reset of the deploy installer image. To open the device selection menu. contact Customer Support. Clear the error in Deployment Manager and deploy the OmniStack host using Deployment Manager. select * Hard drive C:. you need to manually enter it in the SimpliVity Installer main screen. If the address appears blank. 4. Select SD Card: Internal Dual SD and press Enter. The SimpliVity Installer screen opens. select Next Boot > Local SD Card. The host boots into the SD card in the SimpliVity Installer. The OmniStack host reboots and receives a new IP address. use the up or down arrow key to select Deploy and press Enter. From the Properties tab. 2. Procedure 1. 42 Retry deployment for errors 7-33 . click Launch from the Virtual Console Preview panel and click Confirm and Run to launch the virtual console. 8. The SimpliVity Installer screen opens. 3. NOTE: If SD Card: Internal Dual SD does not appear in the BIOS Boot Menu screen. Select Power > Reset System (warmboot) from the Power drop-down menu. 6. 7. Log in with your account and select This SimpliVity IDRAC from the Domain drop-down menu. Reset the boot drive on a Lenovo x3650 host Use this procedure to retry an OmniStack host deployment on a Lenovo platform. In the virtual console. Procedure 1. Do one of the following. deploying to an IP address already in use or having the network connection timeout. The SimpliVity Installer screen opens. Configure and connect the remote management interface for your server and launch the virtual console. Select another resource to continue. An unexpected internal error occurred. • Open port 9299 on the Management network and redeploy the OmniStack host. press F12 to open the Boot Device Selection menu when prompted.n. select Embedded Hypervisor and press Enter. Procedure About general deployment issues 43 . In the Power menu.n port 9299 Procedure • Verify that the specified IP address is not in use by another OmniStack host. use the up or down arrow key to select Deploy and press Enter. 6. select Restart Option. In the Boot Device Selection Menu. • Connect an Ethernet cable from the Windows computer to the Ethernet management port on the rear of the OmniStack host. Deployment Manager displays this message when you navigate from the Select Deployment Location for Hosts screen to the SimpliVity Federation Information screen: Cannot connect to selected resource. 3. Clear the error in Deployment Manager and deploy the OmniStack host using Deployment Manager. Disconnected hosts The cluster you selected in the Select Deployment Location for Hosts screen might contain OmniStack hosts in the Federation that are disconnected or unavailable for any reason (such as a network outage). The IP address is assigned to another OmniStack host. 5.n. 4. 2. The OmniStack host reboots and receives a new IP address. Procedure • Assign an IP address to the OmniStack host that is not in use by another OmniStack host. • Verify that the firewall rules on a switch or network router do not prevent access to port 9299. In the GNU GRUB screen. During the server boot-up process. Cannot connect to port 9299 Deployment Manager displays this message: Error connecting to address n.) This section contains a list of general errors and possible solutions. you might have a general deployment error (such as. IP address already assigned Deployment Manager displays a message that an IP address is already in use on a network. About general deployment issues If you do not need to reset the boot drive or reset the installer image. Contact Customer Support.Timeout while waiting for hypervisor to boot. Deployment Manager displays this message during a deployment: Interface error from Installer Procedure • Reboot the OmniStack hosts.0 is not installed on the Windows computer or the . see the Hardware Installation and Maintenance Guide for your platform. Please install the . For more information. if you have 3. redeploy the OmniStack hosts when network traffic is low.NET Framework 4.0.0. Deployment Manager displays this message: This setup requires the . Verify that the IP address for the OmniStack host is correct. OmniStack software version outdated The current version of the OmniStack software is running on a later release of an OmniStack host. Verify that the OmniStack host you are deploying are on the same subnet. Would you like to do this now? Procedure • Click Yes in the message to install .NET needs to be upgraded Microsoft™ . Deployment Manager displays this message during a deployment: ERROR: step 1 of 33 .Failed to create a session to HMS. • After the reboot is successful. Network connection timeout A network connection timeout occurred between Deployment Manager and the OmniStack hosts you are deploying.0. Procedure 1.NET Framework and run the setup again.8 systems.7 systems and then purchase 3. 2. use Deployment Manager 3. • Verify the power and network cables are connected to the OmniStack host. .0. Deployment Manager displays this message during a deployment on a CN-Series platform: ERROR: step 8 of 33 .NET Framework version installed on the Windows computer is an older version. Procedure • Use the latest version of Deployment Manager when deploying systems of different OmniStack versions.8.0 or a later release on the Windows computer you are using to deploy the OmniStack hosts. Check the network configuration settings. Cannot connect to OmniStack host Deployment Manager cannot connect to the OmniStack host . The .NET Framework 4. 3. 44 About general deployment issues . For example.NET Framework version 4.NET Framework can be obtained from the web. Deployment Manager displays this message: Deployment is already in process for the OmniStack host. Procedure • Check the network configuration settings (for example. Procedure • Verify the IP addresses that are available using the following command: svt-ippool. In the Deployment Status window. Make sure each host has unique IP address information. Deployment Manager displays the following message: The IP address is not associated with an OmniCube system to be deployed or is already in use by an OmniCube system. The Windows computer on which you are running Deployment Manager has Java 1. IP address associated with failed deployment The IP address entered in the Select OmniStack Host screen is associated with an OmniStack host that exists as a failed deployment. Select another resource to continue. IP address already in use The IP address you are using to deploy an OmniStack host is in use by an OmniStack host. click the X icon for the error message associated with the OmniStack host to clear the message. When you retry a deployment and enter the IP address for the OmniStack host. About general deployment issues 45 . see the Hardware Installation and Maintenance Guide for your platform.show --pool all IP address already in use or not associated with server When using Deployment Manager to deploy OmniStack hosts running OmniStack version 3.7 or later. Procedure • Verify the power and network cables are connected to the OmniStack host.0.8 or later installed. Procedure 1. Disconnected hosts The cluster you selected in the Select Deployment Location for Hosts screen might contain OmniStack hosts in the Federation that are disconnected or unavailable for any reason (such as a network outage). IP addresses) that you used for the hosts you want to deploy. For more information.A task error occurred adding host to port group. Retry the deployment. Deployment Manager displays this message during a deployment: ERROR: step 14 of 33 . If necessary. 4. Deployment Manager displays this message when you navigate from the Select Deployment Location for Hosts screen to the SimpliVity Federation Information screen: Cannot connect to selected resource. make changes and redeploy. click the Settings icon ( ) to open the Settings screen. 2. Retry the deployment using Deployment Manager and select 10 Gb/s NICs when prompted. Failed deployment with Cisco UCSM and Cisco M3S or UCS C240 M4SX platforms An OmniStack host deployment fails when using Cisco UCSM on an OmniStack Integrated Solution with Cisco C240 M3S or Cisco UCS C240 M4SX platform. Enter the IP address of the OmniStack host in the appropriate field of the Select OmniStack Hosts screen. Procedure 1. A UCS-Managed Server contains 10GbE interfaces only. Check with your UCSM administrator about the current pinning setting. Click Collect to open the Browse For Folder dialog. IfUCSM Dynamic Pinning (or Not Pinned) might not allow full network connectivity for the duration of the deployment and can cause a network connectivity issue during deployment. To collect deployment logs: Procedure 1. The 10GbE interface used for a deployment must carry the VLANs for the Management. and Federation networks. you can collect the relevant deployment logs. 3. These logs can help you and SimpliVity Customer Support analyze the deployment failure and determine the appropriate resolution. 2. In Deployment Manager. SimpliVity recommends using a 10GbE Only (Switched) connection. Check with your UCSM administrator if the 10GbE interface is not carrying these VLANs. 2. Verify network connectivity between the Windows computer running Deployment Manager and the UCSM Managed Server running the SimpliVity Installer. Storage. 46 Collect deployment logs . Collect deployment logs Procedure overview If an OmniStack host deployment fails. 3. Navigate to the folder in which you want to save the deployment logs. Click OK to save the collected deployment logs to the location that you have specified. Type a name for the new folder and press Enter. click Make New Folder. Results Deployment Manager saves the deployment logs in a date/time-stamped folder in the location that you have specified. Collect deployment logs 47 . To save the logs to a new folder. 4. system output. damage to hardware or software. or configuration. • --option is a command option and should be typed exactly as shown.Appendix A: Additional information This section contains the following topics: • SimpliVity documentation conventions • Reading path • SimpliVity terminology • Websites • Regulatory information • Documentation feedback SimpliVity documentation conventions SimpliVity documentation uses the following conventions to assist your reading. General formatting Monospace font represents a command line syntax. • variable is an option variable and should be replaced with the required value. Italic font represents a user-defined name or variable. Bold font represents a user interface element. Command Line formatting SimpliVity documentation uses the following format for CLI commands: command --option variable where • command is the name of the command and should be typed exactly as shown. file path. 48 SimpliVity documentation conventions . such as a button or tab. Caution: Alerts you to the risk of data unavailability or possible issues with regard to security. NOTE: Indicates information that is supplemental or that may require additional attention. Informational Alerts WARNING: Alerts you to the risk of bodily injury. loss of warranty. or similar code. performance. with which a user interacts. or loss of data. 760-000246 Rev A SimpliVity OmniStack Solution with HPE Explains installation.simplivity. 760-000241 Rev A Read this document first. Get started with OmniStack software. The following reading path lists the documentation for this release. cabling.com for this guide. Document Description SimpliVity OmniStack for vSphere Release Explains new features. and known Notes issues in this release. Learn about this OmniStack release. Tip: Provides helpful information such as best practices. Note that the information in these Release Notes may supersede information in other OmniStack publications in this documentation set. Document Description Getting Started With OmniStack for vSphere Introduces you to the SimpliVity hyperconverged infrastructure and steps you 760-000258 Rev A through performing common management tasks on deployed OmniStack hosts using the SimpliVity Extension for vSphere Web Client. 760-000247 Rev A Reading path 49 . Install and configure hardware. Document Description HPE SimpliVity 380 Hardware Installation Quick Explains installation and integration steps for Start OmniStack Solution with HPE ProLiant DL380 Gen9 hardware. fixed issues. See gettingstarted. Reading path SimpliVity provides a comprehensive documentation set for this release of the OmniStack software. and configuration ProLiant DL380 Gen9 Hardware Installation procedures for OmniStack Solution with HPE and Maintenance Guide ProLiant DL380 Gen9 hardware. and Maintenance Guide CN-3000. and CN-5400 Series Hardware procedures for OmniCube CN-1400. cabling. Document Description SimpliVity OmniStack for vSphere Deployment Explains deployment steps for all platforms. 760-000252 Rev A SimpliVity OmniStack Solution with Lenovo Explains installation and integration steps for x3650 M5 Hardware Installation Quick Start OmniStack Solution with Lenovo x3650 M5 hardware. CN-2200. and CN-5000 Hardware Installation procedures for OmniCube CN-2000. Explains installation. CN-2200. 760-0002250 Rev A SimpliVity OmniStack Integrated Solution with Explains installation and integration steps for Cisco UCS C240 M4SX Hardware Installation OmniStack Integrated Solution with Cisco UCS Quick Start C240 M4SX hardware. cabling. and configuration x3650 M5 Hardware Installation and procedures for OmniStack Solution with Lenovo Maintenance Guide x3650 M5 hardware. 760-000248 Rev A SimpliVity OmniCube CN-1400. 760-000249 Rev A SimpliVity OmniCube CN-2000. Explains installation. 760-000251 Rev A SimpliVity OmniStack Integrated Solution with Explains installation. CN-2400. Document Description SimpliVity OmniCube CN-Series Hardware Explains installation and integration steps for Installation Quick Start OmniCube CN-Series hardware. 760-000253 Rev A SimpliVity OmniStack Solution with Lenovo Explains installation. CN-2400. 760-000243 Rev A 50 Reading path . and configuration CN-3400. and configuration Cisco UCS C240 M4SX Hardware Installation procedures for OmniStack Integrated Solution and Maintenance Guide with Cisco UCS C240 M4SX hardware. Quick Start 760-000242 Rev A SimpliVity OmniStack for vSphere Deployment Explains how to use Deployment Manager to Guide deploy all platforms. cabling. and CN-5400 Series hardware. and CN-5000 hardware. Installation and Maintenance Guide CN-3400. 760-000254 Rev A Deploy the OmniStack Software on your platform. and configuration CN-3000. cabling. SimpliVity OmniStack for vSphere Command Explains OmniStack command line interface Reference Guide (CLI) commands. 760-000257 Rev A See api. SimpliVity OmniStack REST API Getting Explains how to use the OmniStack REST API Started Guide to administer OmniStack hosts. SimpliVity Extension for vSphere Web Client includes this Help system. 760-000259 Rev A SimpliVity OmniStack for vSphere Help Explains procedures for administering OmniStack hosts using OmniStack for vSphere 760-000244 Rev A Web Client. It is required in every SimpliVity Federation. Document Description SimpliVity OmniStack for vSphere Explains procedures for administering Administration Guide OmniStack hosts using OmniStack for vSphere Web Client. Document Description SimpliVity OmniStack for vSphere Events Explains SimpliVity-specific alarms and events. 760-000255 Rev A Monitor your Federations. if a cluster contains two OmniStack hosts and one of those SimpliVity terminology 51 .simplivity. For example. Document Description SimpliVity OmniStack for vSphere Upgrade Explains upgrade procedures for OmniStack Guide Software. 760-0002245 Rev A Administer your Federations.com for this guide. Reference Guide 760-000256 Rev A SimpliVity terminology The following table contains SimpliVity terms and definitions. Term Definition Arbiter SimpliVity software that runs on the computer hosting the hypervisor management server or a different Windows computer that the OmniStack hosts can access. The arbiter provides the tie-breaking vote when a cluster contains an even number of OmniStack hosts. its peer ensures that host services continue. This software in turn communicates with the OmniStack Accelerator card inside the host. failure domain A collection of OmniStack hosts that serve as potential high availability failover targets for each other for purposes of high availability and disaster recovery. An OmniStack host uses a dedicated virtual machine called the OmniStack Virtual Controller. OmniStack host A host (server) containing an OmniStack Accelerator card that communicates with the OmniStack software and some supported virtualization software. based on more sources of telemetry data (adding data location to CPU and memory usage) to (IWO) intelligently configure workloads. the arbiter acts as the tie breaker. which you define as being likely to go offline together due to external forces. Federation A collection of SimpliVity OmniStack hosts and clusters managed in a single globally-unified management domain. OmniStack Accelerator A SimpliVity PCI card that provides non-volatile memory.) OmniStack software The SimpliVity software running on the OmniStack Virtual Controller. (Previously referred to as OmniCube software. Intelligent Workload A feature that works with vSphere Distributed Resource Scheduler (DRS) Optimizer to optimize the location of virtual machines within a cluster. (Previously referred to as an OmniCube host. For more information.) (OVC) 52 SimpliVity terminology . OmniCube host See OmniStack host. (Note that an arbiter must not run on any host within a cluster for which it is acting as a tie breaker. system host A generic term referring to either an OmniStack host or a standard host.) OmniStack Virtual A virtual machine dedicated to the OmniStack host that runs the OmniStack Controller software. guest operating The operating system that runs inside a virtual machine.) availability zone Physically co-located collections of OmniStack hosts. and cryptographic hashing. accelerated compression. Term Definition OmniStack hosts loses connectivity with the cluster. including compute and storage resources. datastore A container for virtual machine files.) (Previously referred to as an OmniCube Arbiter. which runs the OmniStack software. The Accelerator card communicates with the OmniStack software. (Previously referred to as an OmniCube Virtual Controller. refer to your hypervisor documentation. If an availability zone goes offline. cluster A collection of OmniStack hosts that share resources and provide high availability and load-balancing services. com/info/insightremotesupport/docs Regulatory information To view the regulatory information for your product.com/info/reach Websites 53 .hpe. A chemical information report for this product can be found at: http://www. view the Safety and Compliance Information for Server. Websites General websites • Hewlett Packard Enterprise Information Library: http://www. to prevent data loss following the loss of a single availability zone.hpe.com/support/Safety-Compliance-EnterpriseProducts Additional regulatory information Hewlett Packard Enterprise is committed to providing our customers with information about the chemical substances in our products as needed to comply with legal requirements such as REACH (Regulation EC No 1907/2006 of the European Parliament and the Council). standard ESXi host An ESXi host that does not contain OmniStack software. Multiple virtual machines can operate (VM) concurrently on the same physical host machine.com/storage/spock • Storage white papers and analyst reports: http://www. virtual machine A virtual computer environment that runs a guest operating system and associated application software.com/storage/whitepapers • Customer Self Repair: http://www. Term Definition SimpliVity Arbiter See Arbiter.hpe. Networking. Stretched Cluster An OmniStack software host configuration using an equal number of OmniStack hosts within two availability zones. Storage.hpe. and Rack Products.com/support/selfrepair • Insight Remote Support: http://www.hpe. standard host A host that does not contain OmniStack software. Power. available at the Hewlett Packard Enterprise Support Center: http://www. and leveraging a third-site arbiter.com/info/EIL • Single Point of Connectivity Knowledge (SPOCK) Storage compatibility matrix: http://www.hpe.hpe. or comments to Documentation Feedback (mailto:
[email protected]). suggestions. see: http://www. edition. and energy efficiency. and publication date located on the legal notices page. product recycling. product version. and publication date located on the front cover of the document.com/info/environment Documentation feedback Hewlett Packard Enterprise is committed to providing documentation that meets your needs. see: http://www. part number. include the product name. help edition. including company programs. send any errors. For online help content. 54 Documentation feedback . To help us improve the documentation.hpe.com/info/ecodata For Hewlett Packard Enterprise environmental information. include the document title. including RoHS and REACH. When submitting your feedback.hpe. For Hewlett Packard Enterprise product environmental and safety information and compliance data.