Hewlett Packard Enterprise. SimpliVity OmniStack for vsphere Upgrade Guide

Transcription

1 Hewlett Packard Enterprise SimpliVity OmniStack for vsphere Upgrade Guide Part number: Rev A Published: June 2017

2 Trademarks Patents Copyright 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. SimpliVity OmniCube and OmniStack products are covered by various United States and foreign patents and pending patent applications. Patents include: AU ; BR PI ; CA 2,776,231; CN ZL ; DE ; DK ; EP ; ES ; FI ; FR ; GB ; IN 679/CHENP/2012; IT ; JP ; NO ; SE ; US 8,478,799; US 9,367,551; US 2016/ ; EP ; HK ; US 2013/ ; AU ; BR ; CA 2,840,178; CN ; EP ; HK ; IN 368/CHENP/2014; JP ; US 9,436,748; US ; AU ; BR ; CA 2,865,240; CN ; EP ; HK ; IN 6929/CHENP/2014; JP ; US 9,032,183; US 2015/ ; AU ; BR ; CA 2,921,039; CN X; EP ; IN ; JP ; US 9,043,576; US ; AU ; BR ; CA WO2016/115219; CN WO2016/115219; EP ; IN ; JP WO2016/115219; US 2016/ ; US 15/280,347 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 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

3 Contents Chapter 1: Overview of the OmniStack upgrade process...4 About OmniStack software upgrades... 4 Upgrade task summary... 4 Determine your current OmniStack software version... 5 Chapter 2: Prerequisites for upgrading the OmniStack software... 6 Check the SimpliVity Federation...7 Move hosts to one cluster per datacenter...8 Verify HA compliance through vsphere Web Client... 9 Verify HA compliance through vsphere Client... 9 Obtain the OmniStack upgrade software...10 Upgrade Arbiter Install SimpliVity Extension for vsphere Web Client Chapter 3: Upgrade the OmniStack software Upload the OmniStack software package...12 Monitor the upgrade...17 Commit the OmniStack upgrade...19 Appendix A: Additional information...21 SimpliVity documentation conventions...21 Reading path SimpliVity terminology Websites Regulatory information Documentation feedback

4 Chapter 1: Overview of the OmniStack upgrade process SimpliVity regularly releases new and updated hardware and software revisions providing feature enhancements and bug fixes as documented in the OmniStack Release Notes. You can also find notifications of available upgrades from the SimpliVity Customer Support web site. About OmniStack software upgrades When you upgrade the OmniStack software on all the OmniStack hosts in a SimpliVity Federation, the upgrade process runs on each host sequentially. For example, with Upgrade Manager, you can upgrade groups of hosts in a single cluster in one datacenter or multiple datacenters. As soon as one host completes the upgrade in one cluster, the next host in the cluster starts. If your Federation contains another datacenter with a cluster of OmniStack hosts, you see the upgrade run at the same time as the one in the other datacenter. They run in parallel. Then the hosts remain in the upgraded state until you commit the upgrade. All your hosts must reside in one cluster per datacenter before you can start the upgrade process. You can use vsphere options to move OmniStack hosts from a datacenter to a cluster within the datacenter. But, you cannot move OmniStack hosts from one datacenter to a cluster in another datacenter. To do that, you need to remove the host from the datacenter and redeploy it to the cluster in the new datacenter. All the OmniStack hosts in a Federation must use the same version of OmniStack software (for example, all 3.6.1). However, during the upgrade procedure, you can see the process creates a mixed environment as it runs through upgrading each host. A software upgrade is not permanent in a Federation until you commit the upgrade. When you commit an upgrade, you irreversibly upgrade all OmniStack systems in a Federation. Therefore, if you do not want to upgrade a host, you can roll back the upgrade to the previous software version as long as you have not committed the upgrade for the host. You cannot perform any further upgrades until you commit the most recent upgrade or roll it back. If you commit the upgrade and need to remove it, you can remove the OmniStack hosts from the Federation. This resets the software version to the factory default version and then redeploy them. Upgrade task summary This chart provides a high-level view of the tasks required to upgrade the OmniStack software on a host: Task Description 1 Ensure that all OmniStack hosts reside in one cluster per datacenter. 2 For configurations with more than one OmniStack host, check that the virtual machines on the hosts are in storage High Availability (HA) compliance. HA compliance ensures that you do not experience data loss during the upgrade process. You do not need to shut down or move virtual machines from the hosts. For one OmniStack host configurations, the virtual machines cannot reach HA compliance. 4 About OmniStack software upgrades

5 Task Description 3 Download the OmniStack software bundle from the SimpliVity Customer Support web site and save the files in the same directory on the computer that is local to the hosts you want to upgrade (the computer with vcenter Server). 4 Upgrade the Arbiter software (without removing the current version). 5 Run Upgrade Manager to: Upload the OmniStack software to the datastore the hosts use. Upgrade the hosts with the latest OmniStack software. Commit the upgrade to all the hosts. Determine your current OmniStack software version Procedure overview Before you download the OmniStack software bundle from SimpliVity Customer Support and start the upgrade process, do one of the following to determine your current OmniStack software version: For SimpliVity Extension for vsphere Web Client, click SimpliVity Federation from the Home tab and then click Cluster. You can view the OmniStack software version in the Objects tab. For SimpliVity Plug-in for vsphere Client, browse to Home > Inventory > Hosts and Clusters. Expand the datacenter that has the cluster with the hosts you want to upgrade and click the SimpliVity tab. You can view the OmniStack version in the lower-right panel (OmniCube Systems). Determine your current OmniStack software version 5

6 Chapter 2: Prerequisites for upgrading the OmniStack software Before you upgrade, consider the following. Prerequisite Cluster requirements Interoperability Guide Third-party software requirements Scheduling Virtual Machine Operations Policy Backups Description OmniStack hosts must reside in one cluster per datacenter to upgrade the OmniStack software. Read the Interoperability Guide for upgrade information that is specific to the upgrade release. Upgrade Manager requires: Windows 7, 8.1, 10, Windows Server 2008 R2, or Windows Server 2012 R2 Microsoft.NET Framework 4.0 web installer package or later. Schedule the upgrade during a maintenance window or a period when you expect minimal system use. You should also: Upgrade your Production and Disaster Recovery (DR) datacenters separately in order to maintain DR continuity and in case of catastrophic failure or disaster. Avoid times when virtual machine I/O is high. Consider quiescing virtual machines that typically have a high rate of I/O. Make sure that the SimpliVity Federation is in a healthy state and that there are no unacknowledged alarms or events or pending tasks. Maintain the continuity of virtual machines running on standard ESXi hosts that use SimpliVity datastores by migrating their virtual machines to an OmniStack host before you start the upgrade process. For more details on migrating virtual machines, see the VMware documentation. Avoid the following virtual machine operations during upgrades: Backing up virtual machines manually, cloning virtual machines, or creating application consistent backups during the upgrade. Moving virtual machines with the SimpliVity Move Virtual Machine option or VMware vmotion feature. Make sure that your backup schedule is current and that the upgrade does not coincide with a heavy policy backup schedule. Tasks such as policy backups might fail if the backup occurs during a critical time in the upgrade procedure. Examine the virtual machine alarms after an upgrade to check for automated 6

7 Prerequisite Network Description backup failure and create manual supplemental backups if necessary. Make sure your network is functioning correctly by checking the following: Ports 22, 443, and 9190 are open as documented in the SimpliVity OmniStack for vsphere Deployment Guide. Ports can communicate between the datacenters with the clusters being upgraded and the computer running Upgrade Manager. Do not attempt to upgrade hosts over a WAN. vcenter Server Account Credentials Know the vcenter Server account credentials. SimpliVity Upgrade Manager requires you to log in with administrator credentials as a user or as part of an Administrators group. If you log in to Upgrade Manager with an account that uses a custom role (not administrator), you cannot perform the main upgrade tasks (upgrade, rollback, or commit) even if you have all the available permissions. You can only log in to the application and upload the required.tar file. Health Monitor Script If you plan to commit the upgrade in a Federation with OmniStack hosts in multiple datacenters with single clusters in a ROBO (Remote Office, Branch Office) environment, clear processes that are in a Dead state. If necessary, contact SimpliVity Customer Support and request article KBA_4306. In additon to these considerations, you need to: Check the SimpliVity Federation to ensure your hosts reside in one cluster per datacenter and the virtual machines use storage High Availability (HA). Download the OmniStack upgrade software bundle. Upgrade Arbiter. Upgrade SimpliVity Extension for vsphere Web Client. Check the SimpliVity Federation Procedure overview Before you begin the upgrade process, check the following SimpliVity Federation items: OmniStack hosts reside in one cluster per datacenter Guest virtual machines show a status of "Yes" for Storage High Availability (HA) compliance For configurations with more than one OmniStack host in a cluster, you do not need to shut down or move virtual machines from the hosts. The hosts rely on storage IP failover during the upgrade process. (You Check the SimpliVity Federation 7

8 do not need to rely on vmotion for the guest virtual machines unless the host requires you to restart ESXi after the upgrade.) For configurations with a single OmniStack host in a cluster, the virtual machines cannot reach HA compliance. To ensure a successful upgrade, shut down the virtual machines on the host before you start the upgrade process. But, do not shut down the OmniStack Virtual Controller. It runs the OmniStack software. (The Virtual Controller has the letters "VC" in the virtual machine name.) If you need to upgrade a cluster with one OmniStack host with a hosted vcenter Server, use storage vmotion to move the vcenter virtual machine and any of its components (such as the PSC) off the host using a SimpliVity datastore or the upgrade fails. Move hosts to one cluster per datacenter Procedure overview OmniStack hosts must reside in a single cluster per datacenter for you to upgrade the OmniStack software on the hosts. To create a cluster, use vsphere options. For example, right-click the datacenter where you want to add the cluster and select New Cluster. Follow the prompts to select vsphere cluster features such as vsphere High Availability (HA). If you use OmniStack or later, you can turn on Distributed Resource Scheduler (DRS). But, for OmniStack 3.0.x, you need to enable SimpliVity Enhanced DRS Integration through the svt-edrsi-enable command to ensure efficient load balancing. If you use OmniStack 3.5.x or later, this feature is called SimpliVity Intelligent Workload Optimizer. It is enabled by default to work with DRS. If it was disabled, you can enable it through the svt-iwo-enable command. For more details on creating clusters, see the SimpliVity OmniStack for vsphere Administration Guide, SimpliVity OmniStack for vsphere Command Reference Guide, and VMware documentation. To move OmniStack hosts from a datacenter to a single cluster in the same datacenter, do one of the following: For SimpliVity Extension for vsphere Web Client (OmniStack 3.5.x), use the vsphere Move To (or Move To Cluster) option to move the host from a datacenter to one cluster in the same datacenter. For SimpliVity Plug-In for vsphere Client (OmniStack 3.0.x), expand the datacenter with the hosts you need to move. Then select the host you need to move and drag it to the cluster in the same datacenter. (You can also use the Move host to cluster option instead of using the drag and drop method.) If you need to move an OmniStack host from a cluster to another cluster in the same datacenter, put the host in maintenance mode before moving it. For more details on moving hosts or putting them in Maintenance mode, see the SimpliVity OmniStack for vsphere Administration Guide or VMware documentation. If you want to move OmniStack hosts to a single cluster in another datacenter, you must remove the host from its current datacenter and redeploy it to the appropriate cluster as described in the SimpliVity OmniStack for vsphere Deployment Guide. (For details on removing a host from a Federation, see the SimpliVity OmniStack for vsphere Administration Guide or SimpliVity OmniStack for vsphere Help.) Once you upgrade to OmniStack 3.6.1, you cannot use the vsphere Move options to move hosts to other clusters. You must deploy the hosts directly to the cluster as described in the SimpliVity OmniStack for vsphere Deployment Guide. 8 Check the SimpliVity Federation

9 Verify HA compliance through vsphere Web Client Procedure overview All the virtual machines in the Federation must be in storage High Availability (HA) compliance before you can upgrade the hosts to ensure you do not lose data. To check for HA compliance in SimpliVity Extension for vsphere Web Client (OmniStack or later), see the following steps. If you use SimpliVity Plug-In for vsphere Client, see Verify HA compliance through vsphere Client on page 9 instead of this procedure. Procedure 1. From vsphere Web Client Home, click SimpliVity Federation. 2. Click Virtual Machines to open the Objects tab. 3. Verify that all virtual machines have a Storage HA value of Yes (synchronized). If you see a status of No, you have a single OmniStack host in the cluster. Virtual machines on a single host in a cluster cannot reach HA compliance. You need to shut down the virtual machines to upgrade the software. See Check the SimpliVity Federation on page 7 for more details. Verify HA compliance through vsphere Client Procedure overview All the virtual machines in the Federation must be in storage High Availability (HA) compliance before you can upgrade the hosts to ensure you do not lose data. To check for HA compliance in SimpliVity Plug-In for vsphere Client (OmniStack or 3.0.8), see the following steps. If you use SimpliVity Extension for vsphere Web Client (OmniStack or later), see Verify HA compliance through vsphere Web Client on page 9 instead of this procedure. Procedure 1. In vsphere Client, expand the datacenter with the cluster that has the OmniStack hosts. Click the cluster. 2. Select a virtual machine in the cluster and click the Summary tab. 3. Scroll down to the the Summary panel and check the HA status. To check the HA status of all the virtual machines in the cluster, click the Profile Compliance tab and click Check Compliance Now. See the VMware documentation for more information. 4. Verify that all virtual machines have a Storage HA Compliance value of Yes (synchronized). If you see a status of No, you have a single OmniStack host in the cluster. Virtual machines on a single host in a cluster cannot reach HA compliance. You need to shut down the virtual machines to upgrade the software. See Check the SimpliVity Federation on page 7 for more details. Check the SimpliVity Federation 9

10 Obtain the OmniStack upgrade software Procedure overview This procedure describes how to access the Upgrade Manager software you need to upgrade your OmniStack hosts. Procedure 1. Log in to the SimpliVity Customer Support web site and locate the OmniStack software version you need for the upgrade. For example, click Downloads & Documents, click the image of the server you use, scroll down the page and click SimpliVity Software and Documentation. Click the version of OmniStack software you need. 2. Select the following files: simplivity-arbiter xxx.msi simplivity-upgrade-manager xxx.exe SimpliVity-OmniStack-Software-revA xxx.tar SimpliVityExtensionForvSphereWebClient.exe 3. Select Download from the Item Actions menu. 4. Choose Save File. The files reside in the default Web download location. 5. Proceed to the next procedure to upgrade Arbiter. Upgrade Arbiter Procedure overview To ensure your hosts operate correctly, leave your existing Arbiter version installed when you install the new version. Do not remove your current version of Arbiter before performing the upgrade steps. Procedure 1. Copy the executable named simplivity-arbiter-n.n.n.nnn.msi from the distribution media to the Arbiter host (typically the vcenter Server computer). 2. Double-click the installer icon to open the installer and click Next. 3. Accept the license agreement and click Next to open the Setup Type dialog box. 4. Click Complete, and then Install. No other installation options are valid. 5. If you see a "Files in Use" message stating that some VMware applications are in use and need to be closed, select Do not close applications. A reboot will be required and click OK. Arbiter installs as expected without you needing to restart the computer. 6. Click Finish to complete the installation. 10 Obtain the OmniStack upgrade software

11 Install SimpliVity Extension for vsphere Web Client To manage SimpliVity virtual objects in vsphere Web Client after you complete the OmniStack upgrade, you must install SimpliVity Extension for vsphere Web Client on the vcenter Server that you plan to access. This application plugs into the existing vsphere Web Client interface. You must install it using administrator credentials to successfully register it. If you use Enhanced Linked Mode, you must install the same version of SimpliVity Extension for vsphere Web Client on each server running vcenter Server to access the SimpliVity options. To access the latest version of SimpliVity Extension for vsphere Web Client, download it from the SimpliVity Customer Support web site as described in Obtain the OmniStack upgrade software on page 10. If you have an earlier version installed, remove it before you install the new version. For complete steps on installing or removing the application, see the SimpliVity OmniStack for vsphere Administration Guide. Install SimpliVity Extension for vsphere Web Client 11

12 Chapter 3: Upgrade the OmniStack software This upgrade procedure uses the SimpliVity Upgrade Manager to upgrade the Federation on a perdatacenter basis. (All OmniStack hosts reside in one cluster per datacenter.) Upgrade Manager allows you to upload the new software to the SimpliVity datastore. Once uploaded, you can start the upgrade process. Before the upgrade completes, you can rollback or cancel the upgrade. If you allow the upgrade to finish, you must commit it to all the OmniStack hosts in the Federation before you can use the new version. Review these items before you run Upgrade Manager: Do not run the upgrade across a slow network link. Carefully enter your administrative password when prompted during the upgrade. If you enter an incorrect password, you must first delete the incorrect password before entering the correct one. You cannot simply highlight the incorrect password and type in the correct password. Upgrade all single clusters in each datacenter that contain a single OmniStack host before or after upgrading all single clusters in each datacenter with multiple OmniStack hosts. This full upgrade process includes uploading the software to the datastore, monitoring the upgrade process, and committing the upgrade to all the OmniStack hosts. If you have SimpliVity Extension for vsphere Web Client 3.5.x installed in the vcenter Server you plan to upgrade, you can use it to track alerts and alarms during the upgrade and commit process. For example, you can view the upgrade status through the SimpliVity datacenter object view. But, if you use an earlier version of SimpliVity Extension (for example, SimpliVity Plugin for vsphere Client or ), do not install SimpliVity Extension for vsphere Web Client until you complete the OmniStack upgrade process and commit the upgrade for all the OmniStack hosts in the Federation. Upload the OmniStack software package Procedure overview You use SimpliVity Upgrade Manager to upload the OmniStack software package from your Windows client to the datastore used by the hosts you need to upgrade. This procedure also allows you to only upgrade the software to the datastore in case you want to perform the upgrade and commit the software later. Procedure 1. Ensure that the simplivity-upgrade-manager xxx.exe and SimpliVity-OmniStack-Software-revA xxx.tar files reside in the same directory. (If not, place them in the same folder.) 2. Double-click the Upgrade Manager executable to open the login screen. 12 Upload the OmniStack software package

13 3. Enter the vcenter Server IP address, your administrator user name and password, and click Login to open the Upgrade Prerequisites and Best Practices screen. 4. Make sure that you have fulfilled the upgrade prerequisites and are following the best practices. Then, click OK to open the SimpliVity Software Upgrade screen. Upload the OmniStack software package 13

14 5. Ensure that the hosts you want to upgrade have an Upgrade Status of Ready for upgrade. If you previously upgraded some hosts in the cluster, you may see a mix of status settings (for example, Ready for upgrade and Ready for Commit). If you see hosts with the Faulty status, you can check these hosts for any alarms and attempt to resolve the alarm conditions before attempting the upgrade. If you do not see any hosts with the Ready for upgrade status, and you need to upgrade them, contact SimpliVity and do not continue. 6. Select the Federation, one or more datacenters or clusters, or individual hosts. If you cannot see a cluster you recently created, close Upgrade Manager and log back in to the application after a few minutes. You should see the cluster appear on the screen. 7. Click Next to open the Administrator Credentials screen. 14 Upload the OmniStack software package

15 8. Enter the administrator user name and password for the selected hosts. For more than one host, you see Apply credentials for selected. Leave this option selected if all the hosts use the same user name and password. Otherwise, clear it and enter the credentials for each host on each row. 9. Click Next to open the Ready to upgrade screen. 10. Do one of the following: Upload the OmniStack software package 15

16 If you only want to upload the software to the datastore, select Upload only from the bottom of the screen and then click Finish. You can close the application after the upload finishes and continue the upgrade process at a later time. For example, when ready, you can log in to Upgrade Manager again and click Finish at this screen (without selecting Upload only). If you want to upload the software package and start the upgrade process, click Finish. (The process starts, and the button switches to Next during the upgrade process.) 11. Monitor the state of the upload in the Upgrade Status column. The Upgrade status changes from Initiating upload process > Uploading package > Validating uploaded package > Upload completed. Do not close the wizard during the upload process to ensure it finishes. If you want to cancel the upload process for the hosts in a specific cluster in the Uploading Package state, click the menu icon ( ) at the end of the cluster row and select Cancel Upload. For example: 16 Upload the OmniStack software package

17 12. If you selected Upload only, you can close the application when the uploads finish and log back in when ready to upgrade the hosts (or select another datacenter). Or, if you did not select Upload only, proceed to Monitor the upgrade on page 17. Monitor the upgrade After Upgrade Manager uploads the software package, it starts the upgrade process that you can monitor. Procedure overview During the upgrade process, you can click the menu icon ( ) in the Upgrade Status column and select Cancel Upgrade to cancel the upgrade for all the hosts in the cluster or individual hosts. Or, you can roll back the upgrade for individual hosts. However, the status of the upgrade impacts what you can or cannot do through the icon. For example, you can: Click Cancel Upgrade to cancel the upgrade for all the hosts in a cluster or individual hosts if the upgrade status appears as Upgrade in progress. Click Rollback to roll back the upgrade of the host to the previous version if the status appears as Ready for commit. If you attempt to upgrade more than one host in a cluster and cancel the upgrade process for one of the hosts, you see the host appear under the datacenter object instead of the cluster the next time you open Upgrade Manager. This can occur when your OmniStack hosts use different versions of OmniStack software. (For example, one host uses OmniStack 3.0.8, and another uses ) Once you upgrade the host you previously cancelled, you see it appear under the correct cluster object. Procedure 1. If you closed Upgrade Manager, open it and log in again. Monitor the upgrade 17

18 2. Monitor the upgrade progress. If it takes longer than expected, you can close Upgrade Manager and reopen it at any time to check the upgrade status. For example, if it takes more than 15 minutes, you can close it. Then, later, you can open it, and you may see a host restart (reboot) after an upgrade or see the upgrade start for the next host in the cluster. To ensure you do not experience any data loss, Upgrade Manager checks the storage High Availability (HA) status of all the virtual machines on each host to ensure they are protected. If all the virtual machines on a host are HA protected, the upgrade begins. If not, you see a message indicating how many virtual machines are not protected. A virtual machine may become unprotected in a problematic Federation, for example, when network issues cause a host to lose connectivity. The upgrade process for a host cannot start until all its virtual machines are HA protected. (You can check the storage HA status through the Virtual Machines object in your hypervisor.) 3. Verify that the Upgrade Status column shows Upgrade in progress for all datacenters or that all hosts display a status of Ready for commit. Use vsphere Web Client (or vsphere Client) to monitor alarms and events in conjunction with Upgrade Manager. During the upgrade, a reboot occurs automatically after the upgrade and before the commit process. However, you may see an alarm stating that you must reboot due to a change in the passthru.map settings. If you see this message, wait until after all systems are upgraded and the Federation successfully committed before rebooting these systems. Once all hosts in the Federation are in a Ready for commit state, the Next button switches to Commit. 4. Proceed to Commit the OmniStack upgrade on page Monitor the upgrade

19 Commit the OmniStack upgrade Before you begin You cannot access new features in the latest OmniStack software upgrade until you commit the upgrade to all OmniStack systems in the Federation. A commit operation irreversibly modifies the Federation OmniStack hosts. You cannot cancel or rollback the software upgrade once you commit it. If you decide not to commit the upgrade, you can roll back individual systems to the previously installed software revision to defer the upgrade to a later time. Procedure overview Once the Upgrade Status appears as "Ready for commit," you can commit the OmniStack software upgrade to all the hosts in the Federation. Procedure 1. If you previously closed Upgrade Manager, open it and log in with your administrator account. 2. Ensure that all hosts show the same version of OmniStack software and the Upgrade Status shows as Ready for commit. For example: 3. Click Commit. 4. Click Yes to confirm the commit. You cannot reverse the upgrade once you commit it. If you need to roll back the upgrade, click No. Then click the striped icon ( ) in the Upgrade Status column to select the Rollback option. The hosts reverts to the last OmniStack version it had installed. You may need to roll back the upgrade on all the hosts to try the upgrade again and ensure all the hosts use the same OmniStack version. Commit the OmniStack upgrade 19

20 5. Verify that the correct OmniStack version appears in the Current Software Version column. You should also see an upgrade status of Completed. 6. Click Close. 7. Click Yes to confirm the close. Next steps See the Install SimpliVity Extension for vsphere Web Client on page 11 section for details on installing the latest version of SimpliVity Extension. If you use vsphere 6.5 with OmniStack or later, you may experience a slight decrease in storage performance when OmniStack hosts run heavy workloads. If this occurs, contact SimpliVity Customer Support or visit for details on resolving this issue. 20 Commit the OmniStack upgrade

21 Appendix A: Additional information SimpliVity documentation conventions SimpliVity documentation uses the following conventions to assist your reading. General formatting Monospace font represents a command line syntax, file path, system output, or similar code. Italic font represents a user-defined name or variable. Bold font represents a user interface element, such as a button or tab, with which a user interacts. 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. --option is a command option and should be typed exactly as shown. variable is an option variable and should be replaced with the required value. Informational Alerts WARNING: Alerts you to the risk of bodily injury, damage to hardware or software, loss of warranty, or loss of data. Caution: Alerts you to the risk of data unavailability or possible issues with regard to security, performance, or configuration. Indicates information that is supplemental or that may require additional attention. Tip: Provides helpful information such as best practices. Reading path SimpliVity provides a comprehensive documentation set for this release of the OmniStack software. The following reading path lists the documentation for this release. SimpliVity documentation conventions 21

22 Learn about this OmniStack release. Document SimpliVity OmniStack for vsphere Release Notes Rev A Description Explains new features, fixed issues, and known issues in this release. Read this document first. Note that the information in these Release Notes may supersede information in other OmniStack publications in this documentation set. Get started with OmniStack software. Document Getting Started With OmniStack for vsphere Rev A Description Introduces you to the SimpliVity hyperconverged infrastructure and steps you through performing common management tasks on deployed OmniStack hosts using the SimpliVity Extension for vsphere Web Client. See gettingstarted.simplivity.com for this guide. Install and configure hardware. Document HPE SimpliVity 380 Hardware Installation Quick Start Rev A SimpliVity OmniStack Solution with HPE ProLiant DL380 Gen9 Hardware Installation and Maintenance Guide Rev A SimpliVity OmniCube CN-Series Hardware Installation Quick Start Rev A SimpliVity OmniCube CN-1400, CN-2400, CN-3400, and CN-5400 Series Hardware Installation and Maintenance Guide Rev A Description Explains installation and integration steps for OmniStack Solution with HPE ProLiant DL380 Gen9 hardware. Explains installation, cabling, and configuration procedures for OmniStack Solution with HPE ProLiant DL380 Gen9 hardware. Explains installation and integration steps for OmniCube CN-Series hardware. Explains installation, cabling, and configuration procedures for OmniCube CN-1400, CN-2400, CN-3400, and CN-5400 Series hardware. 22 Reading path

23 Document SimpliVity OmniCube CN-2000, CN-2200, CN-3000, and CN-5000 Hardware Installation and Maintenance Guide Rev A SimpliVity OmniStack Integrated Solution with Cisco UCS C240 M4SX Hardware Installation Quick Start Rev A SimpliVity OmniStack Integrated Solution with Cisco UCS C240 M4SX Hardware Installation and Maintenance Guide Rev A SimpliVity OmniStack Solution with Lenovo x3650 M5 Hardware Installation Quick Start Rev A SimpliVity OmniStack Solution with Lenovo x3650 M5 Hardware Installation and Maintenance Guide Rev A Description Explains installation, cabling, and configuration procedures for OmniCube CN-2000, CN-2200, CN-3000, and CN-5000 hardware. Explains installation and integration steps for OmniStack Integrated Solution with Cisco UCS C240 M4SX hardware. Explains installation, cabling, and configuration procedures for OmniStack Integrated Solution with Cisco UCS C240 M4SX hardware. Explains installation and integration steps for OmniStack Solution with Lenovo x3650 M5 hardware. Explains installation, cabling, and configuration procedures for OmniStack Solution with Lenovo x3650 M5 hardware. Deploy the OmniStack Software on your platform. Document SimpliVity OmniStack for vsphere Deployment Quick Start Rev A SimpliVity OmniStack for vsphere Deployment Guide Rev A SimpliVity OmniStack for vsphere Upgrade Guide Rev A Description Explains deployment steps for all platforms. Explains how to use Deployment Manager to deploy all platforms. Explains upgrade procedures for OmniStack Software. Reading path 23

24 Administer your Federations. Document SimpliVity OmniStack for vsphere Administration Guide Rev A SimpliVity OmniStack for vsphere Help Rev A SimpliVity OmniStack REST API Getting Started Guide Rev A SimpliVity OmniStack for vsphere Command Reference Guide Rev A Description Explains procedures for administering OmniStack hosts using OmniStack for vsphere Web Client. Explains procedures for administering OmniStack hosts using OmniStack for vsphere Web Client. SimpliVity Extension for vsphere Web Client includes this Help system. Explains how to use the OmniStack REST API to administer OmniStack hosts. See api.simplivity.com for this guide. Explains OmniStack command line interface (CLI) commands. Monitor your Federations. Document SimpliVity OmniStack for vsphere Events Reference Guide Rev A Description Explains SimpliVity-specific alarms and events. SimpliVity terminology The following table contains SimpliVity terms and definitions. Term Arbiter Definition SimpliVity software that runs on the computer hosting the hypervisor management server or a different Windows computer that the OmniStack hosts can access. It is required in every SimpliVity Federation. The 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 OmniStack hosts loses connectivity with the cluster, the arbiter acts as the tie breaker. (Note that an arbiter must not run on any host within a cluster for which it is acting as a tie breaker.) (Previously referred to as an OmniCube Arbiter.) 24 SimpliVity terminology

25 Term availability zone cluster datastore failure domain Federation guest operating system Definition Physically co-located collections of OmniStack hosts, which you define as being likely to go offline together due to external forces. If an availability zone goes offline, its peer ensures that host services continue. A collection of OmniStack hosts that share resources and provide high availability and load-balancing services. A container for virtual machine files, including compute and storage resources. For more information, refer to your hypervisor documentation. A collection of OmniStack hosts that serve as potential high availability failover targets for each other for purposes of high availability and disaster recovery. A collection of SimpliVity OmniStack hosts and clusters managed in a single globally-unified management domain. The operating system that runs inside a virtual machine. host A generic term referring to either an OmniStack host or a standard host. Intelligent Workload Optimizer (IWO) OmniCube host A feature that works with vsphere Distributed Resource Scheduler (DRS) to optimize the location of virtual machines within a cluster, based on more sources of telemetry data (adding data location to CPU and memory usage) to intelligently configure workloads. See OmniStack host. OmniStack Accelerator A SimpliVity PCI card that provides non-volatile memory, accelerated compression, and cryptographic hashing. The Accelerator card communicates with the OmniStack software. OmniStack host OmniStack software OmniStack Virtual Controller (OVC) SimpliVity Arbiter A host (server) containing an OmniStack Accelerator card that communicates with the OmniStack software and some supported virtualization software. An OmniStack host uses a dedicated virtual machine called the OmniStack Virtual Controller, which runs the OmniStack software. (Previously referred to as an OmniCube host.) The SimpliVity software running on the OmniStack Virtual Controller. (Previously referred to as OmniCube software.) A virtual machine dedicated to the OmniStack host that runs the OmniStack software. This software in turn communicates with the OmniStack Accelerator card inside the host. (Previously referred to as an OmniCube Virtual Controller.) See Arbiter. standard ESXi host An ESXi host that does not contain OmniStack software. SimpliVity terminology 25

26 Term Definition standard host A host that does not contain OmniStack software. Stretched Cluster virtual machine (VM) An OmniStack software host configuration using an equal number of OmniStack hosts within two availability zones, and leveraging a third-site arbiter, to prevent data loss following the loss of a single availability zone. A virtual computer environment that runs a guest operating system and associated application software. Multiple virtual machines can operate concurrently on the same physical host machine. Websites General websites Hewlett Packard Enterprise Information Library: Single Point of Connectivity Knowledge (SPOCK) Storage compatibility matrix: Storage white papers and analyst reports: Customer Self Repair: Insight Remote Support: Regulatory information To view the regulatory information for your product, view the Safety and Compliance Information for Server, Storage, Power, Networking, and Rack Products, available at the Hewlett Packard Enterprise Support Center: 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). A chemical information report for this product can be found at: For Hewlett Packard Enterprise product environmental and safety information and compliance data, including RoHS and REACH, see: 26 Websites

27 For Hewlett Packard Enterprise environmental information, including company programs, product recycling, and energy efficiency, see: Documentation feedback Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback When submitting your feedback, include the document title, part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page. Documentation feedback 27