Hewlett Packard Enterprise. SimpliVity OmniStack for vsphere Deployment Guide

Hewlett Packard Enterprise SimpliVity OmniStack for vsphere Deployment Guide Part number: 760-000243 Rev A Published: June 2017

Trademarks, SimpliVity cube logo, SimpliVity The Data Virtualization Company, SimpliVity, 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 SimpliVity Software. Download the SimpliVity software from the Customer Support website for the OmniStack version you use. This includes Deployment Manager and Arbiter. About OmniStack hosts 5

Task Description You can also download SimpliVity Extension for vsphere Web Client, but it is not required to deploy hosts. You use it to manage hosts in the hypervisor. Once you deploy your hosts, you can install SimpliVity Extension for vsphere Web Client as described in the SimpliVity OmniStack for vsphere Administration Guide. Install the SimpliVity software. Install Deployment Manager on the Windows computer you plan to use to deploy OmniStack 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. 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. If the OmniStack hosts are not on the same broadcast domain but are on a reachable network, you must provide the IP address of each host manually. For more information, see "About OmniStack host discovery." 6 Verify the network environment. Check the accounts to ensure access to the applications, verify the network and required ports for OmniStack, and review the deployment checklist. Deploy an OmniStack host. When you first run Deployment Manager, you may want to choose the option to create a configuration file. That way, you can save the network settings in a file to use it as a template. Then, the next time you use Deployment Manager, you can import it when you deploy another OmniStack host. You can make any necessary modifications as you scroll through Deployment Manager. Perform post-deployment tasks. Perform the post-deployment tasks listed in the "Post-deployment Tasks" topic after you successfully deploy an OmniStack host. Deployment tasks summary

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, install the following software from SimpliVity: Deployment Manager: Enables you to use a wizard to deploy the OmniStack hosts. 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. Install Deployment Manager on a supported Window Server or Windows computer. Arbiter: Enables communication between OmniStack and vcenter Server. This communication enables you to deploy and manage OmniStack hosts and related objects. 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. Install Arbiter on the vcenter Server where you want to deploy hosts or a different Windows computer that the OmniStack hosts can access. Download the SimpliVity software To deploy hosts, you need the SimpliVity Deployment Manager and Arbiter software. Download this software from the SimpliVity Customer Support website. Procedure 1. Go to the SimpliVity Customer Support website. 2. Enter your user name and password. 3. Click Product Information > SimpliVity Software.. 4. Click the name of the OmniStack host or OmniStack model that you ordered. 5. Click the version of OmniStack software you ordered. 6. Click Software. 7. Click the name of the software you want to download (SimpliVity Deployment Manager or SimpliVity Arbiter). 8. Save the files in a location you can access. NOTE: You can also download the extension software you need to use to manage hosts in your hypervisor (for example, SimpliVity Extension for vsphere Web Client). But, 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. About SimpliVity software 7

Next steps See the following sections for details on requirements and steps to install the software. About VMware products Before installing the SimpliVity software and deploying OmniStack hosts, verify that your vsphere environment includes one of the following VMware products: vsphere vcenter Server 6.0 or 6.5. vcenter Server Appliance 6.0 or 6.5. Either of the listed products comes with vsphere Web Client. If you do not have these products installed or you need to upgrade them, see the VMware documentation. If you need to download the products or access tools, you need to know your VMware customer account credentials. To access vcenter Server, you need an account with administrator privileges. You can also use Enhanced Link Mode with vcenter Server 6.0 or 6.5 or vcenter Server Appliance 6.0 or 6.5. For more information on setting up Enhanced Link Mode, see the Platform Services Controller instructions in the VMware vcenter Server 6.0 or 6.5 documentation. The OmniStack hosts must use the same hypervisor version of any hosts that reside in the cluster you plan to deploy to. For example, if you use vcenter Server 6.5, you can deploy hosts that use ESXi 6.0 or 6.5. But all the OmniStack hosts in a cluster need to use the same version (all ESXi 6.0 or 6.5). You cannot mix the hypervisor versions in a cluster. 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. Joining multiple vcenter Server systems using vcenter Server Linked Mode enables them to share information. To support a Federation in linked mode using vcenter 6.0 or later, install single sign-on (SSO) using multisite mode (requires an Active Directory [AD] server for authentication). When you deploy OmniStack hosts to a cluster, Deployment Manager displays the SimpliVity Federation Information screen. In this screen, 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). If the OmniStack hosts join a SimpliVity Federation, 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. About Deployment Manager Deployment Manager is a stand-alone Windows application that configures and deploys OmniStack hosts in an existing cluster. With Deployment Manager, you can import data from a previously saved configuration (XML) file or manually enter the network settings to deploy an OmniStack host. If you enter the settings manually, you can save them in a configuration file before you deploy the host. When you import an existing configuration file, Deployment Manager validates the information and 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 a host to a cluster, Deployment Manager creates the virtual switches (vswitches) and port groups for the network connection that you specify. For example, the default vswitch names are vswitch0 and vswitch1 for a 1 Gb/s or 10 Gb/s network. 8 About VMware products

After you use Deployment Manager to deploy at least one OmniStack host to a cluster, you can deploy multiple OmniStack hosts to the same cluster (or another cluster in another datacenter). NOTE: Before you can deploy a host, clusters needs to exist in the hypervisor. For example, in vsphere Web Client, you need to create a datacenter and create one or more clusters for the datacenter. OmniStack hosts must reside in one or more clusters. Each cluster can contain up to eight OmniStack hosts. For more information on creating a cluster, see the SimpliVity OmniStack for vsphere Administration Guide or the SimpliVity OmniStack for vsphere Help. Deployment Manager screen icons Deployment 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 start a new deployment as the current one runs, but the cluster must contain at least one previously deployed OmniStack host. The icon also shows the number of deployments in progress. Displays the Settings screen. Use this screen to set a timeout between Deployment Manager and the vcenter Server that is appropriate for your networking environment. The default value is 30 seconds. The maximum value is 120 seconds. Any changes you make in the Settings screen take effect the next time you run Deployment Manager. You can also use the Settings screen to initiate the collection of deployment logs for troubleshooting deployment issues. Displays the version, patents, trademarks, and SimpliVity contact information. Deployment Manager software requirements Only use OmniStack hosts with the same software version in the same cluster. (Do not mix versions.) For example, if your cluster contains hosts with OmniStack 3.5.1, do not deploy hosts with OmniStack 3.5.2 into that cluster. Upgrade the hosts that already reside in the cluster first, then deploy the new hosts with the same OmniStack version. (For more information on upgrading OmniStack software, contact SimpliVity Customer Support). The following software is required to deploy OmniStack hosts using Deployment Manager. Operating System requirements Deployment Manager is supported on these Windows operating systems: Windows Server 2012 R2. Windows Server 2008 R2. Windows 8.1. Windows 7. About Deployment Manager 9

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.0 web installer package or later. NOTE: Install only one version of the third-party software on the Windows computer you are using to deploy OmniStack 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 OmniStack 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 Deployment Manager. Procedure 1. Double-click the simplivity-deployment-manager-n.n.n.n.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)\simplivity \DeploymentManager) or manually enter 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 SimpliVity Deployment Manager. 10 About 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. About Arbiter The SimpliVity Arbiter software runs on the computer hosting a vcenter Server or a different Windows computer that the hosts can access. It is required in every SimpliVity Federation. Arbiter provides the tie-breaking vote when a cluster contains an even number of OmniStack hosts. For example, if a cluster contains two OmniStack hosts and one of those hosts loses connectivity with the cluster, Arbiter acts as the tie breaker. When you run Deployment Manager, you specify the Arbiter location. You can select the vcenter Server or a different Windows computer. For a computer other than the one with vcenter 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 with one or more clusters in a Federation to distribute the workload. For example, if your datacenter includes clusters that run several thousand virtual machines and you already installed Arbiter on vcenter Server, install Arbiter on another Windows computer (separate from the computer with vcenter Server). Then, when you deploy hosts, select the cluster that needs its own Arbiter and enter the IP address of the computer that has it. (Do not install Arbiter on a virtual machine managed within the same cluster it serves.) Arbiter requirements Your version of Arbiter should match the version of OmniStack used by your hosts. Review these requirements before installing Arbiter on the computer hosting a vcenter Server or a different Windows computer. 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. It must run on the computer hosting vcenter Server or on another Windows computer. Do not install it on a virtual machine that resides on an OmniStack host or any host that uses a SimpliVity datastore. Install the latest version of VMware tools on any virtual machine 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. About Arbiter 11

Feature Requirement Persistent storage Minimum of 16 GB (HDD or SDD) NOTE: Set disk caching policy to write-through or write cache disabled. Storage type Storage device capable of 80 IOPS per 128 virtual machines in the arbitration control 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 with a snapshot or backup and restore process or you could corrupt the virtual machine data. Network 1xGigE Supported operating systems Windows Server 2008, 2008R2, 2012, 2012R2, 2016 Install Arbiter Before you begin Before you deploy 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 USB stick that ships with the product or you can download it from Customer Support.) 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 12 About Arbiter

Before uninstalling Arbiter, 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 SimpliVity Arbiter. 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. About Arbiter 13

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, review the following network sections to ensure you deploy the hosts successfully. Refer to the deployment checklist at the end of this section to review the main tasks. About OmniStack user accounts This section describes the user accounts used to deploy and manage OmniStack hosts, including the ESXi root user, vcenter Server single sign-on accounts, or CLI commands. ESXi host root account Use the ESXi host root user account to log on to an OmniStack host. You create the password for the ESXi host root user account when you deploy an OmniStack host using Deployment Manager. For ESXi host password requirements and restrictions, see the VMware documentation for your ESXi host version. vcenter Server single sign-on account vcenter Server single sign-on accounts are controlled-privilege, vcenter Server (Active Directory supported) accounts that can manage a Federation. OmniStack CLI account When your VMware single sign-on account is not available, use the SimpliVity OmniStack CLI account to run SimpliVity CLI commands as described in the SimpliVity OmniStack for vsphere Command Reference Guide. Networking requirements An OmniStack host in a Federation requires three separate networks: Management, Storage, and Federation. During deployment, you assign the OmniStack host, OmniStack Virtual Controller (a virtual machine running OmniStack software), and the VM Kernel port to one or all of the networks. Also do the following: 14 Maintain a separate network for 10 Gb/s storage data traffic between OmniStack hosts in a Federation. Use existing networks (such as a dedicated virtualization management network) if you have appropriate networks in your VMware environment. About deployment environment requirements

Use VLANs to separate management and virtual machine traffic. However, ensure that the Management network and OmniStack host can route to each other through a common VLAN. Open TCP ports 9292 and 9299 on the Management network to deploy OmniStack hosts. You can close these 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 unit For best performance, 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, set the Quality of Service (QoS) MTU attribute to 9216. The MTU size range on the Federation networks is 1000 to 9000 bytes. For a 10 Gb/s network, the MTU on the Management, Storage, and Federation networks must be the same value. For best performance, set the MTU to 9000 for a 10 Gb/s connection. For a 1 Gb/s or 10 Gb/s NIC, the MTU size on the Storage and Federation networks must be the same value. 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. The MTU setting for the Management, Storage, and Federation networks must match the MTU settings used for any OmniStack hosts that already reside in the cluster (if available). For Cisco servers managed through Cisco Integrated Management Controller (CIMC) with an MTU setting greater than 1500, set the MTU for the Storage and Federation networks to 9000 to ensure vmotion functions as expected. The Management network can remain at the default setting of 1500. 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. Requirement Description NTP The Network Time Protocol (NTP) is preconfigured in an OmniStack host using US internet time servers. The default servers are 0.us.pool.ntp.org through 3.us.pool.ntp.org. Record any NTP servers the vcenter Server is using. At least three NTP servers are required for an OmniStack host deployment. Networking requirements 15

Requirement Description 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 OmniStack Virtual Controller, OmniStack host, vcenter Server, vsphere Web Client, and the Windows computer running Deployment Manager. You need a DNS suffix name for each OmniStack host. The host you plan to deploy cannot be a DNS child domain. You need a default DNS suffix to search for a domain. vcenter Server IP address or FQDN The IP address or FQDN for the vcenter Server planned to contain the SimpliVity Federation. Cluster The name of the cluster in vcenter Server where you want to deploy the OmniStack hosts. To create a cluster in a datacenter, see the SimpliVity Extension Help. 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. OmniStack host. Virtual Controller. Storage Network. Virtual Controller. VMkernel Port. Federation Network. Virtual Controller. Ports required for SimpliVity servers OmniCube or OmniStack hosts require these ports to communicate with your network and other hosts. For ports required by: 16 vsphere hypervisor, see the VMware documentation. Your specific platform, such as the IPMI port, see the vendor documentation. Networking requirements

Ports Protocols Networks Sources Destinations 22 TCP All Management Workstation 80 TCP Management Deployment Manager OmniStack For remote host access, using SSH, to the OmniStack server when Virtual the web server Controller is unavailable. OmniStack Deployment host monitoring and Support OmniStack Capture Virtual downloads Controller used by SimpliVity Support. 427 TCP and UDP Management Deployment Manager 443 TCP OmniCube or OmniStack server Deployment Manager Deployment OmniStack Manager Virtual Controller vsphere Web Client 9190 TCP Management Management 9292, 9299 TCP Management Deployment Manager Description OmniStack host Deployment operation and monitoring. vcenter Server SSL ports for vsphere ESXi and vcenter OmniStack Server. host OmniStack host OmniStack CLI or vsphere Client access to the OmniCube or OmniStack server. Deployment Manager access to the host over SSL. This port must be open to deploy the OmniCube or OmniStack server. You can close this port after a deployment is successful. Networking requirements 17

Ports Protocols Networks Sources Destinations Description 9390 TCP Management OmniStack Virtual Controller OmniStack Virtual Controller Event Manager uses this port to manage events between the OmniStack Virtual Controllers on the OmniStack hosts. 22122 UDP and TCP Federation and Management OmniStack Virtual Controller 111, 2049, 32764-32768 UDP and TCP Management and Storage OmniStack host OmniStack Federation Virtual traffic between Controller hosts, Arbiter communication, Arbiter and backups to remote clusters. If communication on the Federation network fails, the Management network is used. OmniStack host Management and Storage traffic between OmniStack hosts or standard hosts that share a SimpliVity datastore. OmniStack host requirements Before deploying an OmniStack host, ensure the following: 18 Install at least two OmniStack hosts on a rack in your data center. Check that they are connected to the power and powered on. To deploy multiple OmniStack hosts to a cluster, the servers must use the same number of CPUs (single or dual) and use similar storage size. For example, you can deploy CN-3400 to a cluster with CN-3000 and CN-3400 already deployed to the same cluster. But, you cannot deploy a CN-3400 (large storage size) to a cluster with CN-1200 and Cisco USC C240 hosts (small storage size). Avoid deploying OmniStack hosts across a wide-area network (WAN). Network disruptions can cause the deployment to fail. OmniStack host requirements

For more information about interoperability requirements, see the Interoperability Guide for your platform available from SimpliVity Support at https://support.simplivity.com. Deployment checklist To ensure a smooth and an efficient deployment, review the following checklist. NOTE: Take an inventory of all the OmniStack hosts you plan to deploy by serial number also. Deployment Manager shows the status of a deployment by serial number only. Step Details Install one or more servers on racks. Ensure that two or more OmniStack servers are installed in each rack and the servers are powered on. Fill in the predeployment forms. Log on to SimpliVity Support at support.simplivity.com. Click My Support. Then click Deployment Planning. Follow the prompts to fill in a predeployment form online or print a PDF version of it. This information allows you to prepare the information you need to enter when you run Deployment Manager to deploy hosts. (If you saved the form online, you can access it again at any time through the Deployment Planning option in the SimpliVity Support Center.) Check that the vcenter Server version is compatible with the ESXi version. To check the hypervisor compatibility, see the Interoperability Matrix on the SimpliVity Support site (support.simplivity.com). (From the Support Home page, click Product Information > SimpliVity Platforms > <name of your server> and scroll down to the link for the Interoperability Guide.) OmniStack UCS only: Requires Cisco UCSM maintenance release (2.0.4) or deploy OmniStack UCS C240 M4SX Verify the UCSM version, if managed only in standalone mode. mode is requested. Check the password complexity. Do not use special characters (for example, asterisk, ampersand, slash) in your OmniStack host password (if prompted to set one during deployment). See your hypervisor documentation and the SimpliVity OmniStack for vsphere Release Notes for details on character limitations. Check that the following is configured: IPMI, CIMC, or UCSM. See the Hardware Installation and Maintenance Guide for your platform for details. Deployment checklist 19

Step Details Verifty that the DNS resolution of IP addresses (IPv4 supported) is identical on the computer with Deployment Manager installed and on the computer with vcenter Server installed. Use the nslookup command at each computer to verify address resolution: Install the correct version of all required SimpliVity software. Download Deployment Manager, Arbiter, and SimpliVity Extension for vsphere Web Client from SimpliVity Customer Support. Check that the OmniStack versions on the hosts are the same. Check that all the hosts you plan to deploy to a cluster use the same version of the OmniStack software. The OmniStack version must also match the version installed on any hosts previously deployed (if you deploy to the same location). Check that you have administrator access to vcenter Server. Obtain the vcenter credentials (if you do not know them already). Check that the firewall is set to allow the specified ports. See "Ports required for SimpliVity servers." Check the IP addresses/network configuration. Verify there are three separate networks: Management, Storage, and Federation. nslookup <ip-address-of-host> Check for duplicate IP addresses. Verify that the MTU size matches that of existing Federation members. Verify the NTP server. 20 Deployment checklist

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, you can deploy one OmniStack host at a time to a cluster. Once you deploy two or more OmniStack hosts, you created a SimpliVity Federation in your hypervisor. You can also use Deployment Manager to import a previously saved configuration file. The configuration file contains store network settings. This helps you deploy hosts faster because you have a template. Just import the file when prompted and make the appropriate modifications to the populated fields as you click through the Deployment Manager wizard. NOTE: OmniStack hosts must reside in one or more clusters in a datacenter. Each cluster can contain up to eight OmniStack hosts. 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. If it detects any issues, you see a message with an appropriate workaround. You can stop and start the tests at any time if you need to make any changes to your settings before you continue. During the deployment of an OmniStack host, Deployment Manager performs a reverse DNS lookup. When an IP address resolves to a host name, the OmniStack host appears in vcenter Server with an assigned host name. When an IP address does not resolve to a host name, the OmniStack 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 deploys the host with the IP address as the name. You can rename a host using the svt-host-rename command as described in the SimpliVity OmniStack for vsphere Command Reference Guide. The renaming process does not impact 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 SimpliVity options in your hypervisor. For more information, 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. About deploying an OmniStack host 21

Deployment prerequisites Before you begin using Deployment Manager, 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. OmniStack hosts must reside in one or more clusters in a datacenter. Each cluster can contain up to eight OmniStack hosts with a maximum of 32 OmniStack hosts in a Federation. All OmniStack hosts you plan to deploy use the same OmniStack software version. Do not mix OmniStack versions in the same cluster. Check that the OmniStack hosts in the same cluster are the same model types with the same number of CPUs (single or dual). 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. Check that your version of Deployment Manager is the same version as the OmniStack version of your hosts or later. For example, if your hosts use OmniStack 3.6.1, use Deployment Manager 3.6.1 or later. Only IPv4 addresses are supported. The Windows computer and OmniStack hosts you plan to deploy must be on the same network. If the Windows computer and an OmniStack host are not on the same network, you must manually obtain an IP address for the OmniStack host. For more information, see "About OmniStack discovery." Open TCP ports 9292 and 9299 on the Management network to deploy an OmniStack host. You can close these ports after the deployment is successful. Know the hypervisor version used (for example, ESXi 6.0 or 6.5) on each OmniStack host you plan to deploy. Verify the Windows computer you are using to deploy an OmniStack host is not configured to enter hibernation or sleep mode during the deployment. If deploying a single OmniStack host, do not enable vsphere High Availability (HA). You do not have enough OmniStack hosts. (With vsphere HA, virtual machines on one failed host can restart on a healthy OmniStack host if one is available.) About OmniStack host discovery When you power on an OmniStack host, it obtains a temporary IP address from a DHCP server. The temporary IP address allows the Deployment Manager client to communicate with the OmniStack host. The Deployment Manager client uses the Service Location Protocol (SLP) to discover the OmniStack host. The temporary IP address connects to an installer and collects the properties of an OmniStack host, such as model type and serial number. In certain situations, an OmniStack host may not acquire a temporary IP address automatically. This requires that you manually assign a static IP address, netmask, and gateway to the OmniStack host during the deployment process. 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, connect the OmniStack server to a Windows computer, connect to the remote management interface for your server (for example, IDRAC), and launch the virtual console or KVM console before you can assign a static IP address. Procedure 22 Deployment prerequisites

1. Connect an Ethernet cable from the Windows computer to the Ethernet management port on the rear of the OmniStack host. 2. Configure the remote management interface for your platform. 3. Connect to the remote management interface and launch the virtual console or KVM console for your platform. The SimpliVity Installer screen opens. For more information, see the Hardware Installation and Maintenance Guide for your platform. Assign a static IP address to an OmniStack host Procedure 1. On the 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 to deploy the OmniStack host. If the Management network and network interface are on different VLANs, indicate the VLAN for the network interface as follows: Use the Tab key to select Add VLAN and press Enter. 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 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 OmniStack Host screen. Deploy an OmniStack host Procedure overview Follow the steps in this procedure to deploy an OmniStack host to a cluster. You can only deploy one host at a time. However, after you deploy the first host, you can start the deployment of another host while another host deploys. To deploy a host, you can manually enter the host settings or import a previously saved configuration file to automatically populate fields. (You can save the settings you enter in Deployment Manager before you deploy a host.) Procedure 1. Open Deployment Manager on the Windows computer you want to use to deploy the OmniStack hosts. Deploy an OmniStack host 23

2. Leave the hypervisor set to VMware vsphere. Then, enter the vcenter Server IP address and administrator credentials. (Do not try to log on to the local host or use the loopback address.) Click Login to 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 if necessary. NOTE: OmniStack hosts must reside in one or more clusters in a datacenter. Each cluster can contain up to eight OmniStack hosts. 4. Do one of the following: 24 If you selected a cluster with existing OmniStack hosts, skip to step 7. Deploy an OmniStack host

If you selected a cluster without existing OmniStack hosts, click Next to open the Define Settings for Federation, Arbiter, or Both screen. NOTE: If you only see the "SimpliVity Arbiter Information" section to specify the location of Arbiter, you logged into a vcenter Server with previously deployed OmniStack hosts in the Federation. But, the cluster you selected does not have any existing hosts. Skip to step 6 if you only see Arbiter options. 5. 6. Select one of the following: Create a SimpliVity Federation: You plan to deploy an OmniStack host to create a new Federation in vcenter Server. 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. In the Existing SimpliVity Federation Virtual Controller management IP address field, enter the management IP address of a Virtual Controller in the Federation. This ensures that Deployment Manager can locate the correct vcenter Server you want to use. (The management IP address is part of the Virtual Controller name.) If shown, 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 Windows server IP address. 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 host completes the deployment process. You can check the progress through the deployment icon ( ). Deploy an OmniStack host 25

8. 9. Do one of the following: Manually enter settings: Leave this option selected to manually enter the network information to deploy a host. Import configuration (XML) file: Select this option to import data from an existing configuration file and automatically 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 Manager stores configuration files to the C:\Users\<user name>\my Documents directory. (You need Read privileges to import the file.) Click Next to open the Select an OmniStack Host screen. 10. Click Scan to automatically discover hosts on the broadcast domain and populate the table. If you do not see the host you want to deploy, enter the IP address in the Add host IP address field and click Add. For example, your screen populates with details similar to this (IP not shown in example): 26 Deploy an OmniStack host

11. Click the NIC Details icon ( ) to see the supported hypervisors and Network Interface Cards (NICs) used on each host. Expand the network adapter name to review the interface, MAC address (physical address and 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, three to 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 appears disconnected, check the physical server. You may have a faulty cable, port, card, or switch. Or, the version of the SimpliVity Installer application on the host may be older than the Deployment Manager version. To update the Installer application on the host, contact SimpliVity Support at support.simplivity.com. 12. Select the desired hypervisor version from the Select Hypervisor Version drop-down menu. For example, if you use vcenter Server 6.5, you can select ESXi 6.0 or 6.510. But, each host in a cluster must use the same hypervisor version (all 5.x or all 6.x). Once you select a hypervisor version in the Select Hypervisor Version field, Deployment Manager prevents you from selecting any OmniStack hosts that do not support this hypervisor version. 13. Select the hosts you want to deploy and click Next to open the Select Network Interface Cards screen. Deploy an OmniStack host 27

14. In the Management NIC and Storage and Federation NIC fields, select the NIC you want to use for each network 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 the Management network and 10 Gb/s for the Storage and Federation network. In addition, select NICs with the same 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 OmniStack hosts that already reside in the cluster (if available). 15. Click Next to open the Set OmniStack Passwords screen. 28 Deploy an OmniStack host

16. Enter the password for the root user account to log on to the OmniStack host and confirm it. (Use the password requirements of the hypervisor.) Then enter the Command Line Interface (CLI) password and confirm it for command line access. 17. 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 with existing OmniStack hosts, you see some of the fields populate with default responses that provide limited options for changes or must remain as shown. 18. On the Network Settings tab, enter the following Management network information for the management connection, Virtual Controller, and host: Host Gateway. Host Netmask. Host VLAN ID. Enter a value between 0 to 4094. Deploy an OmniStack host 29

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 is available). Deployment Manager accesses the vswitch names from vcenter Server. If performing a new deployment, you cannot change the default vswitch name. NOTE: If you selected one NIC for the Management and Storage and Federation networks, select the same vswitch for all the networks (for example, all vswitch0). If you selected two NICs, you can select one vswitch 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 same NIC. Host Port Group Name. Select the name from the drop-down list. If performing a new deployment, you cannot change the default name. MTU. Enter a value between 1000-9000. 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). Virtual Controller Port Group Name. Select the name from the drop-down list. If performing a new deployment, you cannot change the default name. 19. Click the IP Addresses tab. 20. Enter the host and Virtual Controller IP addresses for each host you plan to deploy. 21. Click Next to open the Configure Storage Network Settings screen. 30 Deploy an OmniStack host

22. 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 Gateway. Virtual Controller Netmask. 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 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 same vswitch for all the networks. If you selected two NICs, you can select one vswitch 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 same NIC. Host Port Group Name. Select the name from the drop-down list. If performing a new deployment, you cannot change the default name. MTU. Enter a value between 1000-9000. 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. Select the name from the drop-down list. If performing a new deployment, you cannot change the default name. 23. Click the IP Addresses tab. Deploy an OmniStack host 31

24. Enter the host and Virtual Controller IP addresses for each host you plan to deploy. 25. Click Next to open the Configure Federation Network Settings screen. 26. On the Network Settings tab, enter the following Federation network information for the connection and Virtual Controller: Virtual Controller Gateway. Virtual Controller Netmask. 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 is available). If you selected the same NIC link speed for the networks of a new deployment, 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, select the same vswitch for all the networks. If you selected two NICs, you can select 32 Deploy an OmniStack host

one vswitch 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 same NIC. Virtual Controller Port Group Name. Select the name from the drop-down list. If performing a new deployment, you cannot change the default name. MTU. Enter a value between 1000-9000. 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). 27. Click the IP Addresses tab. 28. Enter the Virtual Controller IP address for each host you plan to deploy. 29. Click Next to open the Configure Host DNS Settings screen. 30. Enter the following host DNS information: Domain. Enter the domain name (with a DNS suffix). Search Domain. Deploy an OmniStack host 33

Primary Server. Secondary Server. Find and register the host by domain name. Leave this option selected for DNS to perform a lookup for the hostname and register it in vcenter with that name. If it cannot find the name, Deployment Manager still deploys the host to vcenter with the IP address. You can change the name at any time after deployment using the svt-host-rename command. For more details on using this command, see the SimpliVity OmniStack for vsphere Command Reference Guide. 31. Click Next to open the Select NTP Servers for Host screen. 32. Select at least three NTP servers and click Add. The default servers are: 0.us.pool.ntp.org 1.us.pool.ntp.org 2.us.pool.ntp.org 3.us.pool.ntp.org You can add an IP address or DNS name for an alternate NTP server in the Alternate Server field and then click Add. Click Up or Down to change the priority order of the NTP servers. 33. Click Next to review the information in the Review Deployment Details screen. You can scroll down the screen to see all of the settings. For example: 34 Deploy an OmniStack host

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. 34. Click Next to open the Test Host Settings screen. 35. Click Start Test when ready to test the host settings. Use the legend to review the status as the test runs. If Deployment Manager detects any issues, you see the messages with any necessary troubleshooting tips in the 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. For example, 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. Deploy an OmniStack host 35

36. When all the tests pass and you see a success message in the Test Details section, click Next to open the Start Deployment, Save Settings, or Both screen. 37. 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. 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. Then, click Save As and browse to a directory. Specify the desired filename for the configuration file and click Save. You do not deploy any hosts at this time if you only select this option. 38. Click Finish. If you chose to deploy the OmniStack hosts, Deployment Manager displays the Monitor Deployment screen. Next steps 36 Deploy an OmniStack host

You can start a new deployment while the current one runs. To start a new deployment from the Monitor Deployment 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 of deployments in progress. Once a host successfully completes the deployment, you can clear it from the list by clicking Clear Completed. About OmniStack host heartbeats Once you deploy hosts to a Federation, you can monitor and maintain their connections through two heartbeat functions. The Arbiter application provides a connection heartbeat between the OmniStack hosts 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 the following error message: SimpliVity Accelerator Firmware Unresponsive. SimpliVity also supports the VMware vsphere HA datastore heartbeat if it is configured in your environment. See the SimpliVity Extension 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 tasks After a successful deployment, complete these tasks for each OmniStack host. Configure the VMware license settings for vcenter Server and the ESXi hosts. For more information, see the VMware documentation at: https://www.vmware.com/support/pubs/ Install SimpliVity Extension for vsphere Web Client on the computer where the vcenter Server is installed. (To download the application, go to support.simplivity.com.) 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. Install SimpliVity Extension for vsphere Web Client on the computer where the vcenter Server is installed. 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. About OmniStack host heartbeats 37

NOTE: If Deployment Manager could not determine the host name associated with the IP address of a host, 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. The renaming process does not impact the I/O performance of the virtual machines residing on the host. 38 Review post-deployment tasks

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. Deployment Manager did not locate the OmniStack host during discovery. To view status messages when a deployment is in progress, click the blinking deployment icon at the top of the screen (for example, ). When a deployment fails, Deployment Manager displays an error message with the serial number of the OmniStack host. For example: The point when a deployment fails determines the action you can take to retry the deployment. For errors between steps 1-3, review the error message, make any necessary changes on the screens and retry the deployment. For errors between steps 4-6, reset the OmniStack host discovery state as described in this guide and try the deployment again. About recoverable deployment errors 39

For errors between steps 7-33, reset the boot drive or installer image as described in this guide and retry the deployment. (The procedure you follow depends on your server type.) See the section that applies to your error to troubleshoot the issue. If the procedures fail, contact SimpliVity Customer Support at support.simplivity.com. Retry deployment for errors 1-3 When a deployment fails between steps 1-3, retry the deployment. If it continues to fail between steps 1-3, contact SimpliVity Customer Support at support.simplivity.com. Retry deployment for errors 4-6 When a deployment fails between steps 4-6, reset the OmniStack host discovery state using the SimpliVity Installer software and retry the deployment. See the following section for details. If deployment continues to fail between steps 4-6, contact SimpliVity Customer Support at support.simplivity.com. 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. Procedure 1. Do one of the following, depending on your internal network: Open a supported browser and open the remote management interface for your server. (For example, open Intelligent Platform Management Interface [IPMI] for CN servers, Cisco Integrated Management Controller [CIMC] for Cisco servers, Integrated Management Module [IMM] for Lenovo, or Intelligent Baseboard Management Controller [ibmc] for Huawei servers. Log in with your account and click the appropriate options to launch the virtual console and open the SimpliVity Installer screen. 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 and open the SimpliVity Installer screen. 2. On the SimpliVity Installer screen, press Ctrl+R when the status is Discovered. The following messages may appear during the reset process: a) Press Enter to continue if OmniStack displays the following message. 40 Retry deployment for errors 1-3

b) Press Tab to make a selection. Press Enter if OmniStack displays the following message. This message indicates that the OmniStack host is available and is ready for redeployment. This message indicates that an instance of Deployment Manager has discovered this OmniStack host and is in the process of deploying it. Select Cancel if deployment of this OmniStack host is in progress. Select OK to prepare this OmniStack host for deployment. 3. Retry the deployment using Deployment Manager. If the deployment fails, contact Customer Support. Retry deployment for errors 7-33 When a deployment fails between steps 7-33, reset the boot drive on a CN-series server, Lenovo server, or Huawei server. For a Cisco server, you reset the installer image instead. Then clear the error in Deployment Manager and retry the deployment. See the following sections for details. If deployment continues to fail between steps 7-33, contact SimpliVity Customer Support at support.simplivity.com. Reset the boot drive on a CN-Series host Use this procedure to retry an OmniStack host deployment on a CN-Series platform. Retry deployment for errors 7-33 41

Procedure 1. Do one of the following, 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. Log in with your account and select This SimpliVity IDRAC from the Domain drop-down menu. From the Properties tab, click Launch from the Virtual Console Preview panel and click Confirm and Run to launch the virtual console. The SimpliVity Installer screen opens. 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. The SimpliVity Installer screen opens. 2. In the virtual console, select Next Boot > Local SD Card. 3. Select Power > Reset System (warmboot) from the Power drop-down menu. 4. Click Yes when prompted to confirm the reset. The host boots into the SD card in the SimpliVity Installer. 5. To open the device selection menu, select * Hard drive C:. 6. Select SD Card: Internal Dual SD and press Enter. NOTE: If SD Card: Internal Dual SD does not appear in the BIOS Boot Menu screen, contact Customer Support. 7. On the GNU GRUB screen, use the up or down arrow key to select Deploy and press Enter. The OmniStack host reboots and receives a new IP address. If the address appears blank, you need to manually enter it in the SimpliVity Installer main screen. 8. Clear the error in Deployment Manager and deploy the OmniStack host using Deployment Manager. 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. Procedure Contact Customer Support. Reset the boot drive on a Lenovo x3650 host Use this procedure to retry an OmniStack host deployment on a Lenovo platform. Procedure 1. Do one of the following, depending on your internal network: 42 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. Log in with your account and select Remote Control from the main screen. Select Java Client and click Start remote control in single-user mode. Then click Tools > Power > Cycle and click Yes to confirm. The SimpliVity Installer screen opens. Retry deployment for errors 7-33

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. The SimpliVity Installer screen opens. 2. In the Power menu, select Restart Option. 3. During the server boot-up process, press F12 to open the Boot Device Selection menu when prompted. 4. In the Boot Device Selection Menu, select Embedded Hypervisor and press Enter. 5. In the GNU GRUB screen, use the up or down arrow key to select Deploy and press Enter. The OmniStack host reboots and receives a new IP address. 6. Clear the error in Deployment Manager and deploy the OmniStack host using Deployment Manager. About general deployment issues If 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 9299 Deployment 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 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 OmniStack host. IP address already assigned Deployment Manager displays a message that an IP address is already in use on a network. The IP address is assigned to another OmniStack host. An unexpected internal error occurred. Procedure Assign an IP address to the OmniStack host that is not in use by another OmniStack host. 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). 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. Select another resource to continue. Procedure About general deployment issues 43

Verify the power and network cables are connected to the OmniStack host. For more information, see the Hardware Installation and Maintenance Guide for your platform. Network connection timeout A network connection timeout occurred between Deployment Manager and the OmniStack hosts you are deploying. Deployment Manager displays this message during a deployment: Interface error from Installer Procedure Reboot the OmniStack hosts. Contact Customer Support. After the reboot is successful, redeploy the OmniStack hosts when network traffic is low..net needs to be upgraded Microsoft.NET Framework 4.0 is not installed on the Windows computer or the.net Framework version installed on the Windows computer is an older version. Deployment Manager displays this message: This setup requires the.net Framework version 4.0. 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 Click Yes in the message to install.net Framework 4.0 or a later release on the Windows computer you are using to deploy the OmniStack hosts. OmniStack software version outdated The current version of the OmniStack software is running on a later release of an 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 of different OmniStack versions. For example, if you have 3.0.7 systems and then purchase 3.0.8 systems, use Deployment Manager 3.0.8. Cannot connect to OmniStack host Deployment Manager cannot connect to the OmniStack host. Deployment Manager displays this message during 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 OmniStack host is correct. 2. Verify that the OmniStack host you are deploying are on the same subnet. 3. Check the network configuration settings. 44 About general deployment issues

4. Retry the deployment. IP address already in use The IP address you are using to deploy an OmniStack host is in use by an OmniStack host. Deployment Manager 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 already in use or not associated with server When using Deployment Manager to deploy OmniStack hosts running OmniStack version 3.0.7 or later, 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.8 or later installed. Procedure Check the network configuration settings (for example, IP addresses) that you used for the hosts you want to deploy. Make sure each host has unique IP address information. If necessary, make changes and redeploy. 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). 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. Select another resource to continue. Procedure Verify the power and network cables are connected to the OmniStack host. For more information, see the Hardware Installation and Maintenance Guide for your platform. 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. When you retry a deployment and enter the IP address for the OmniStack host, Deployment Manager displays this message: Deployment is already in process for the OmniStack host. Procedure 1. In the Deployment Status window, click the X icon for the error message associated with the OmniStack host to clear the message. About general deployment issues 45

2. Enter the IP address of the OmniStack host in the appropriate field of the Select OmniStack Hosts screen. 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. Procedure 1. Verify network connectivity between the Windows computer running Deployment Manager and the UCSM Managed Server running the SimpliVity Installer. 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. 2. Check with your UCSM administrator about the current pinning setting. A UCS-Managed Server contains 10GbE interfaces only. SimpliVity recommends using a 10GbE Only (Switched) connection. 3. Retry the deployment using Deployment Manager and select 10 Gb/s NICs when prompted. The 10GbE interface used for a deployment must carry the VLANs for the Management, Storage, and Federation networks. Check with your UCSM administrator if the 10GbE interface is not carrying these VLANs. Collect deployment logs Procedure overview If an OmniStack host deployment fails, you can collect the relevant deployment logs. These logs can help you and SimpliVity Customer Support analyze the deployment failure and determine the appropriate resolution. To collect deployment logs: Procedure 1. In Deployment Manager, click the Settings icon ( 2. Click Collect to open the Browse For Folder dialog. 46 Collect deployment logs ) to open the Settings screen.

3. Navigate to the folder in which you want to save the deployment logs. To save the logs to a new folder, click Make New Folder. Type 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 have specified. Collect deployment logs 47