Hewlett Packard Enterprise. HPE OmniStack for vsphere Upgrade Guide

Transcription

1 Hewlett Packard Enterprise HPE OmniStack for vsphere Upgrade Guide Part number: P Published: September 2017

2 2017 Hewlett Packard Enterprise Development LP Notices The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying. Consistent with FAR and , Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise website. 2

3 Contents Chapter 1: Overview of the HPE OmniStack upgrade process... 4 About HPE OmniStack software upgrades...4 Upgrade task summary... 4 Determine your current OmniStack software version... 5 Chapter 2: Prerequisites for upgrading the HPE OmniStack software... 6 Check the HPE SimpliVity federation... 7 Verify HA compliance through vsphere Web Client... 8 Verify HA compliance through vsphere Client... 8 Obtain the HPE OmniStack upgrade software... 9 Upgrade Arbiter... 9 Install HPE SimpliVity Plug-in for vsphere Web Client...10 Chapter 3: Upgrade the HPE OmniStack software Upload the HPE OmniStack software package Monitor the upgrade...17 Commit the upgrade...19 Appendix A: Support and other resources Support and other resources Accessing Hewlett Packard Enterprise Support Accessing updates Customer self repair...23 Remote support...23 Warranty information Regulatory information HPE SimpliVity terminology...24 Documentation feedback...25 Contents 3

4 Chapter 1: Overview of the HPE OmniStack upgrade process Hewlett Packard Enterprise regularly releases new and updated hardware and software revisions providing feature enhancements and bug fixes as documented in the HPE OmniStack Release Notes. You can also find notifications of available upgrades from the Customer Support web site. About HPE OmniStack software upgrades When you upgrade the HPE OmniStack software on all the HPE 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 HPE 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. Your hosts can reside in one or more clusters per datacenter. But, all the HPE OmniStack hosts in a federation must use the same version of HPE OmniStack software (for example, all 3.7.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 HPE OmniStack hosts 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 HPE 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 HPE OmniStack hosts reside in one cluster per datacenter. 2 For configurations with more than one HPE 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 a configuration with one HPE OmniStack host, the virtual machines cannot reach HA compliance. 3 Download the HPE OmniStack software bundle from the 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: Chapter 1: Overview of the HPE OmniStack upgrade process 4

5 Task Description Upload the HPE OmniStack software to the datastore the hosts use. Upgrade the hosts with the latest HPE OmniStack software. Commit the upgrade to all the hosts. Determine your current OmniStack software version Procedure overview Before you download the HPE OmniStack software bundle from Customer Support ( support/hpesc) and start the upgrade process, do one of the following to determine your current HPE OmniStack software version: For HPE SimpliVity Plug-in for vsphere Web Client, click HPE SimpliVity Federation from the Home tab and then click Cluster. You can view the OmniStack software version in the Objects tab. For HPE 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. Chapter 1: Overview of the HPE OmniStack upgrade process 5

6 Chapter 2: Prerequisites for upgrading the HPE OmniStack software Before you upgrade, consider the following. Prerequisite Cluster requirements Interoperability Guide Third-party software requirements Scheduling Virtual Machine Operations Policy Backups Description HPE OmniStack hosts can reside in one or more clusters per datacenter to upgrade the HPE OmniStack software. Read the Interoperability Guide for upgrade information that is specific to the upgrade release. You can find this guide in the documentation section for your release on the Customer Support site. Upgrade Manager requires: Windows 7, 8.1, 10, Windows Server 2008 R2, Windows Server 2012 R2, or Windows Server 2016 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 hosts that use HPE SimpliVitydatastores by migrating their virtual machines to an HPE 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 HPE 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. NOTE: 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 Chapter 2: Prerequisites for upgrading the HPE OmniStack software 6

7 Prerequisite Network Description an upgrade to check for automated 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 HPE OmniStack for vsphere Deployment Guide. Ports can communicate between the datacenters with the clusters being upgraded and the computer running Upgrade Manager. NOTE: Do not attempt to upgrade hosts over a WAN. vcenter Server Account Credentials Know the vcenter Server account credentials. HPE SimpliVity Upgrade Manager requires you to log in with administrator credentials as a user or as part of an Administrators group. NOTE: 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 HPE 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 Customer Support ( and request article KBA_4306. In additon to these considerations, you need to: Check the federation to ensure your hosts reside in one cluster per datacenter and the virtual machines use storage High Availability (HA). Download the HPE OmniStack upgrade software bundle. Upgrade Arbiter. Upgrade HPE SimpliVity Plug-in for vsphere Web Client. Check the HPE SimpliVity federation Procedure overview Before you begin the upgrade process, check the following Hewlett Packard Enterprise federation items: HPE 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 HPE 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 do not Chapter 2: Prerequisites for upgrading the HPE OmniStack software 7

8 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 HPE 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 HPE OmniStack Virtual Controller. It runs the HPE OmniStack software. (The Virtual Controller has the letters "VC" in the virtual machine name.) NOTE: If you need to upgrade a cluster with one HPE 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 an HPE SimpliVity datastore or the upgrade fails. 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 Hewlett Packard Enterprise Extension for vsphere Web Client (HPE 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 8 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). NOTE: If you see a status of No, you have a single HPE 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 HPE 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 Hewlett Packard Enterprise Plug-In for vsphere Client (HPE OmniStack or 3.0.8), see the following steps. If you use SimpliVity Extension for vsphere Web Client (HPE OmniStack or later), see Verify HA compliance through vsphere Web Client on page 8 instead of this procedure. Procedure 1. In vsphere Client, expand the datacenter with the cluster that has the HPE 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. Chapter 2: Prerequisites for upgrading the HPE OmniStack software 8

9 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). NOTE: If you see a status of No, you have a single HPE 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 HPE SimpliVity federation on page 7 for more details. Obtain the HPE OmniStack upgrade software Procedure overview This procedure describes how to access the Upgrade Manager software you need to upgrade your HPE OmniStack hosts. Procedure 1. Log in to the Hewlett Packard Enterprise Customer Support web site and locate the HPE 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 HPE OmniStack software you need. 2. Select the following files: HPEsimplivity-arbiter-x.x.x.msi HPEsimplivity-upgrade-manager-x.x.x.exe HPESimpliVity-OmniStack-Software-revX-x.x.x.tar HPESimpliVity-Plug-in-for-vSphere-Web-Client-windows-x.x.x.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. NOTE: Do not remove your current version of Arbiter before performing the upgrade steps. Procedure 1. Copy the executable named hpesimplivity-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. Chapter 2: Prerequisites for upgrading the HPE OmniStack software 9

10 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. Install HPE SimpliVity Plug-in for vsphere Web Client To manage HPE SimpliVity virtual objects in vsphere Web Client after you complete the HPE OmniStack upgrade, you must install HPE SimpliVity Plug-in 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 HPE SimpliVity Plug-in for vsphere Web Client on each server running vcenter Server to access the HPE SimpliVity options. To access the latest version of HPE SimpliVity Plug-in for vsphere Web Client, download it from the Customer Support web site as described in Obtain the HPE OmniStack upgrade software on page 9. 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 HPE OmniStack for vsphere Administration Guide. Chapter 2: Prerequisites for upgrading the HPE OmniStack software 10

11 Chapter 3: Upgrade the HPE OmniStack software This upgrade procedure uses Upgrade Manager to upgrade the federation on a per-datacenter basis. (All HPE OmniStack hosts reside in one cluster per datacenter.) Upgrade Manager allows you to upload the new software to the HPE 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 HPE 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. Upgrade all single clusters in each datacenter that contain a single HPE OmniStack host before or after upgrading all single clusters in each datacenter with multiple HPE OmniStack hosts. This full upgrade process includes uploading the software to the datastore, monitoring the upgrade process, and committing the upgrade to all the HPE OmniStack hosts. NOTE: If you have HPE SimpliVity Plug-in for vsphere Web Client 3.5.x or later 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 HPE SimpliVity datacenter object view. But, if you use an earlier version of HPE SimpliVity Plug-in (for example, HPE SimpliVity Plug-in for vsphere Web Client or ), do not install HPE SimpliVity Plug-in for vsphere Web Client until you complete the HPE OmniStack upgrade process and commit the upgrade for all the HPE OmniStack hosts in the federation. Upload the HPE OmniStack software package Procedure overview You use Upgrade Manager to upload the HPE 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-x.x.x.exe and SimpliVity-OmniStack-Software-revA-x.x.x.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. Chapter 3: Upgrade the HPE OmniStack software 11

12 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. Chapter 3: Upgrade the HPE OmniStack software 12

13 4. Make sure that you have fulfilled the upgrade prerequisites and are following the best practices. Then, click OK to open the HPE SimpliVity Software Upgrade screen. Chapter 3: Upgrade the HPE OmniStack software 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 Hewlett Packard Enterprise and do not continue. 6. Select HPE SimpliVity Federation, one or more datacenters or clusters, or individual hosts. NOTE: 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. Chapter 3: Upgrade the HPE OmniStack software 14

15 8. Enter the administrator user name and password for the selected hosts. NOTE: 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. Chapter 3: Upgrade the HPE OmniStack software 15

16 10. Do one of the following: 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.) Chapter 3: Upgrade the HPE OmniStack software 16

17 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. 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. Chapter 3: Upgrade the HPE OmniStack software 17

18 NOTE: 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 HPE OmniStack hosts use different versions of HPE OmniStack software. (For example, one host uses HPE 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. 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. NOTE: 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. Chapter 3: Upgrade the HPE OmniStack software 18

19 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 upgrade on page 19. Commit the upgrade Before you begin You cannot access new features in the latest HPE OmniStack software upgrade until you commit the upgrade to all HPE OmniStack systems in the federation. A commit operation irreversibly modifies the HPE OmniStack hosts in the federation. 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 HPE 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 HPE OmniStack software and the Upgrade Status shows as Ready for commit. For example: Chapter 3: Upgrade the HPE OmniStack software 19

20 3. Click Commit. 4. Click Yes to confirm the commit. NOTE: You cannot reverse the upgrade once you commit it. If you need to roll back the upgrade, click No. Then click the striped menu icon ( ) in the Upgrade Status column to select the Rollback option. The hosts reverts to the last HPE 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 HPE OmniStack version. 5. Verify that the correct HPE OmniStack version appears in the Current Software Version column. You should also see an upgrade status of Completed. Chapter 3: Upgrade the HPE OmniStack software 20

21 6. Click Close. 7. Click Yes to confirm the close. Next steps See the Install HPE SimpliVity Plug-in for vsphere Web Client on page 10 section for details on installing the latest version of SimpliVity Extension. NOTE: If you use vsphere 6.5 with HPE OmniStack or later, you may experience a slight decrease in storage performance when HPE OmniStack hosts run heavy workloads. If this occurs, contact Customer Support for details on resolving this issue. Chapter 3: Upgrade the HPE OmniStack software 21

22 Appendix A: Support and other resources Support and other resources Accessing Hewlett Packard Enterprise Support For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website: To access documentation and support services, go to the Hewlett Packard Enterprise Support Center website: Information to collect Technical support registration number (if applicable) Product name, model or version, and serial number Operating system name and version Firmware version Error messages Product-specific reports and logs Add-on products or components Third-party products or components Accessing updates Some software products provide a mechanism for accessing software updates through the product interface. Review your product documentation to identify the recommended software update method. To download product updates: Hewlett Packard Enterprise Support Center Hewlett Packard Enterprise Support Center: Software downloads Software Depot To subscribe to enewsletters and alerts: To view and update your entitlements, and to link your contracts and warranties with your profile, go to the Hewlett Packard Enterprise Support Center page titled "More Information on Access to Support Materials": Appendix A: Support and other resources 22

23 NOTE: Access to some updates might require product entitlement when accessed through the Hewlett Packard Enterprise Support Center. You must have an HP Passport set up with relevant entitlements. Customer self repair Hewlett Packard Enterprise customer self repair (CSR) programs allow you to repair your product. If a CSR part needs to be replaced, it will be shipped directly to you so that you can install it at your convenience. Some parts do not qualify for CSR. Your Hewlett Packard Enterprise authorized service provider will determine whether a repair can be accomplished by CSR. For more information about CSR, contact your local service provider or go to the CSR website: Remote support Remote support is available with supported devices as part of your warranty or contractual support agreement. It provides intelligent event diagnosis, and automatic, secure submission of hardware event notifications to Hewlett Packard Enterprise, which will initiate a fast and accurate resolution based on your product's service level. Hewlett Packard Enterprise strongly recommends that you register your device for remote support. If your product includes additional remote support details, use search to locate that information. Remote support and Proactive Care information HPE Get Connected HPE Proactive Care services HPE Proactive Care service: Supported products list HPE Proactive Care advanced service: Supported products list Proactive Care customer information Proactive Care central Proactive Care service activation Warranty information To view the warranty for your product, see the Safety and Compliance Information for Server, Storage, Power, Networking, and Rack Products document, available at the Hewlett Packard Enterprise Support Center: Additional warranty information HPE ProLiant and x86 Servers and Options HPE Enterprise Servers Appendix A: Support and other resources 23

24 HPE Storage Products HPE Networking Products 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: For Hewlett Packard Enterprise environmental information, including company programs, product recycling, and energy efficiency, see: HPE SimpliVity terminology The following table contains HPE SimpliVity terms and definitions. Term Accelerator Arbiter Availability Zone cluster Definition A custom PCI card that provides non-volatile memory, accelerated compression, and cryptographic hashing. The Accelerator card communicates with the HPE OmniStack software. HPE OmniStack software that runs on the computer hosting the hypervisor management server or a different Windows computer that the HPE OmniStack hosts can access. It is required in every federation. The Arbiter provides the tie-breaking vote when a cluster contains an even number of HPE OmniStack hosts. For example, if a cluster contains two HPE OmniStack hosts and one of those HPE 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.) Physically co-located collections of HPE 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 HPE OmniStack hosts that share resources and provide high availability and load-balancing services. Appendix A: Support and other resources 24

25 Term datastore failure domain {internal} federation guest operating system Definition A container for virtual machine files, including compute and storage resources. For more information, refer to your hypervisor documentation. A collection of HPE OmniStack hosts that serve as potential high availability failover targets for each other for purposes of high availability and disaster recovery. A collection of HPE OmniStack hosts 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 HPE OmniStack host or a standard host. HPE OmniStack host HPE OmniStack software A host (server) containing an Accelerator card that communicates with the HPE OmniStack software and some supported virtualization software. An OmniStack host uses a dedicated virtual machine called the Virtual Controller, which runs the HPE OmniStack software. The software running on the Virtual Controller. 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 HPE OmniStack host. standard host A host with VMware ESXi host. It does not contain HPE OmniStack software. Stretched Cluster Virtual Controller virtual machine (VM) An HPE SimpliVity configuration using an equal number of HPE 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 machine dedicated to the HPE OmniStack host that runs the HPE OmniStack software. 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. 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 (mailto:docsfeedback@hpe.com). When submitting your feedback, include the document title, part number, Appendix A: Support and other resources 25

26 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. Appendix A: Support and other resources 26