12.8 HPE StoreVirtual Storage VSA Installation and Configuration Guide-A00090616en - Us
12.8 HPE StoreVirtual Storage VSA Installation and Configuration Guide-A00090616en - Us
12.8 HPE StoreVirtual Storage VSA Installation and Configuration Guide-A00090616en - Us
Configuration Guide
Abstract
This guide provides information about installing and configuring the HPE StoreVirtual VSA for vSphere, the HPE
StoreVirtual VSA for Hyper-V, and the HPE StoreVirtual VSA for KVM. Included are network configuration best
practices to ensure the best performance for the SAN using the StoreVirtual VSAs. The intended audience is
system administrators responsible for managing HPE StoreVirtual Storage using StoreVirtual VSAs.
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 12.211 and 12.212, 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.
Acknowledgments
Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in the United States and
other countries.
Microsoft® and Windows® are either registered trademarks or trademarks of Microsoft Corporation in the United States
and/or other countries.
Java® and Oracle® are registered trademarks of Oracle and/or its affiliates.
Revision history
Part Number Publication date Edition Summary of changes
TA768-96337 October 2019 13 • Added support for Windows Server 2019
• Added procedure to update the virtual hardware version
on vSphere
TA768-96335 July 2017 12 Added configuration information for the StoreVirtual VSA for
Hyper-V for Windows Server 2016
Table Continued
Part Number Publication date Edition Summary of changes
TA688-63133 August 2015 9 • Updated with the new StoreVirtual VSA for KVM
• Updated for the LeftHand OS 12.5 software release
• Removed the StoreVirtual VSA laptop demo chapter
• Additional edits and troubleshooting added
TA688-63129 January 2015 8 Updated with new StoreVirtual VSA and LeftHand OS 12.0
functionality, including new CPU requirements and the
addition of duration to the licensing requirements
TA688-96141 September 2013 7 Updated with the new StoreVirtual VSA and LeftHand OS
11.0 functionality, including tiered storage, updated memory
requirements, licensing options, and number and size of disks
supported
TA688-96138 March 2013 6 Updated with new product branding for the LeftHand OS
software 10.5 release
TA688-96129 November 2012 5 • Updated for the SAN/iQ software 10.0 release
• Updated memory requirements
• Removed Jumbo Frames and 10 Gb/s as being not
supported with virtual NICs
• Increased virtual CPU prerequisite for VSA for Hyper-V
installation from one to two
AX696-96153 December 2011 4 Updated with changes for the installer for VSA to vSphere
Server for the SAN/iQ software 9.5 release
TA688-96120 September 2011 3 Updated with changes for the SAN/iQ software 9.5 release,
including new installer for VSA for vSphere Server
TA688-96111 November 2010 2 Updated with changes for the SAN/iQ software 9.0 release
TA688-96017 September 2010 1 Updated with changes for the SAN/iQ 8.5 software release
Contents
4
Installing the StoreVirtual VSA for KVM..........................................................................37
Supported versions of Linux.............................................................................................................................................................................................37
Configuration requirements for the StoreVirtual VSA for KVM.................................................................................................................. 37
Preparing the storage configuration............................................................................................................................................................................37
Storage pool..............................................................................................................................................................................................................37
Creating a directory pool................................................................................................................................................................. 38
Raw devices...............................................................................................................................................................................................................39
LVM logical volumes...........................................................................................................................................................................39
Best practices for StoreVirtual VSA for KVM..........................................................................................................................................................40
Unsupported configurations for StoreVirtual VSA for KVM..........................................................................................................................40
Installing the StoreVirtual VSA for KVM....................................................................................................................................................................40
Adding memory, vCPUs and disks to the StoreVirtual VSA for KVM.......................................................................................................43
Adding memory and a vCPU...........................................................................................................................................................................43
Adding disks to the StoreVirtual VSA for KVM................................................................................................................................... 43
Uninstalling the StoreVirtual VSA for KVM............................................................................................................................................................. 45
Troubleshooting the StoreVirtual VSA for KVM...................................................................................................................................................45
Websites................................................................................................................................. 53
5
Installation Planning Checklists
Verify the prerequisites for the virtual network, the virtual storage pool, and the StoreVirtual VSAs before you begin
installation.
Procedure
◦ IP address #1:
◦ IP address #2:
◦ IP address #3:
Subnet mask:
Default gateway:
Mail server:
Time server:
DNS servers:
Set the server time correctly to ensure that StoreVirtual VSA licenses remain valid.
Prepared VMDK or RDM datastores with up to 64TB per disk on internal disk storage, or any block storage that is on the
VMware HCL: internal, external, and shared. The LeftHand OS software consumes a small amount of the available space.
Disks must be configured as independent and persistent to prevent VM snapshots from affecting them.
VMFS datastores for the StoreVirtual VSA that are not shared with any other VMs.
vCenter servers properly licensed before connecting to them using the StoreVirtual VSA for vSphere installer.
When installing StoreVirtual VSAs that use more than 8 TB of datastores, increase the maximum addressable space.
More information
Configuration requirements for the StoreVirtual VSA for vSphere on page 17
Virtual disks with 5 GB - 50 TB (up to 50 TB for Windows Server 2016 or later) of space per disk on internal disk storage,
or direct attached storage that is not accessible from more than one physical server. (The StoreVirtual/LeftHand OS
software consumes a small amount of the available space.)
Defined install paths for the Hyper-V virtual machine and the virtual hard disks.
If using physical disks for the StoreVirtual VSA for Hyper-V, ensure that:
◦ The disks are completely clean of any partitions or any other remnants prior to running the StoreVirtual VSA for Hyper-
V installer.
◦ The disks are connected, but offline in Windows Disk Manager before starting the installer.
More information
Configuration requirements for the StoreVirtual VSA for Hyper-V on page 31
Checklist: Planning the KVM configuration for the StoreVirtual VSA for
KVM
Procedure
The server CPU must support hardware virtualization, and it must be enabled in the BIOS settings.
Install the virtualization packages when you install the host OS:
◦
If you choose the "Virtualization Host" Role during OS installation, all required KVM-related packages to deploy the
StoreVirtual VSA for KVM are installed.
◦ If the host OS is already installed on the server, install the following packages:
kvm libvirt qemu-kvm
◦ The installer for the StoreVirtual VSA for KVM also requires
– virtinst/virt-install
32 GB of space on the OS disk, which will be a separate .img file from the data disks, as with other virtual platforms.
If multiple virtual machines are running, set autostart only for the StoreVirtual VSA for KVM. The default
installation configuration for the StoreVirtual VSA for KVM is set to start automatically if it was running when the server
shut down.
In KVM, storage pools are created to hold virtual machine (VM) disks. The StoreVirtual VSA for KVM requires at least one
storage pool on the KVM host for the OS image file.
More information
Configuration requirements for the StoreVirtual VSA for KVM on page 37
Figure 1: Example of software-defined storage on HPE ProLiant servers with the StoreVirtual VSA
Careful planning of the virtual network configuration, the StoreVirtual VSA configuration, and the configuration of the HPE
StoreVirtual management groups, clusters, and volumes for data storage ensures that you can take full advantage of the
features and benefits of the StoreVirtual Storage.
Planning the virtual network configuration
Before you install the StoreVirtual VSA on the network, plan the virtual network configuration, including the following areas:
SFF SAS Up to 10 TB 2
SFF SAS Up to 30 TB 3
SFF SAS Up to 50 TB 4
• Disks must be configured to be persistent. Upgrading existing StoreVirtual VSAs requires that the disks are configured to
be persistent. If necessary, follow the instructions in Troubleshooting the StoreVirtual VSA for vSphere to enable the
persistent disk identifiers for each disk before upgrading.
• Reserved memory based on total disk capacity, as listed in Memory requirements for StoreVirtual VSA disks.
IMPORTANT: There are increased memory requirements for the StoreVirtual VSA in Version 11.x and later, as listed
in Memory requirements for StoreVirtual VSA disks. Make sure that you increase the memory in existing
StoreVirtual VSAs before performing an upgrade.
Total virtualized capacity Total memory requirement in GB Total Adaptive Optimization and
Space Reclamation memory
requirements in GB
<= 500 MB 4 4
500 MB – 4 TB 5 5
Table Continued
4 TB – 10 TB 7 8
10 TB – 20 TB 9 12
20 TB – 30 TB 12 17
30 TB – 40 TB 15 21
40 TB – 50 TB 18 26
• Licensed capacity and duration. Plan the capacity and duration you intend to configure on the StoreVirtual VSA. The
StoreVirtual VSA requires a license for the capacity and the duration for use beyond the 60–day evaluation period.
Licenses are available in the capacities and durations listed in the table, StoreVirtual VSA license capacity, two of which
apply to tiered storage on the StoreVirtual VSA. For more information about licensing, see the HPE StoreVirtual Storage
User Guide.
1 TB 3 years 3 No
4 TB ◦ 3 years 3 No
◦ 5 years
• Virtual network environment with 1 GbE connectivity or higher, including the following:
More information
Configuration requirements for the StoreVirtual VSA for Hyper-V on page 31
Configuration requirements for the StoreVirtual VSA for vSphere on page 17
Configuration requirements for the StoreVirtual VSA for KVM on page 37
• Disable drive write caches on systems that are running the StoreVirtual VSA to prevent data loss in the event of a power
failure.
• Each StoreVirtual VSA should meet the following conditions, if possible.
◦ Have a virtual switch or virtual network comprised of dual Gigabit Ethernet or more. Providing network redundancy and
greater bandwidth improves both performance and reliability.
◦ Use redundant RAID for the underlying storage of a StoreVirtual VSA in each server to prevent single disk failures from
causing StoreVirtual VSA system failure. Do not use RAID 0.
NOTE: See the HPE StoreVirtual Storage User Guide for detailed information about using RAID for individual storage
system data protection.
More information
Best practices for StoreVirtual VSA for vSphere on page 18
Best practices for StoreVirtual VSA for Hyper-V on page 31
Best practices for StoreVirtual VSA for KVM on page 40
• The virtual NICs on the StoreVirtual VSA do not support flow control setting modifications or TCP off-load. The physical
NICs on the host server can be configured with these features. (NIC bonding is a best practice in the host server.)
• The hot removal of virtual hard disks is not supported. See the Microsoft Linux Integration Services user guide.
More information
Unsupported configurations for StoreVirtual VSA for vSphere on page 18
Unsupported configurations for StoreVirtual VSA for Hyper-V on page 31
Unsupported configurations for StoreVirtual VSA for KVM on page 40
• When using hard drives, use as many drives as the platform will allow and that have faster rotation speeds. The more hard
drives and the faster their rotation speed, the more IOPs, and better performance.
• If using Adaptive Optimization, use SSD drives for 10 percent of the storage capacity.
• Select controllers with protected write cache and ensure that the write cache is enabled.
• Do not enable disk caching on servers that host StoreVirtual VSAs.
• Every virtual disk should be RAID-protected and not configured with RAID 0.
Network adapters
The number of network adapters available in a platform affects your options for configuring virtual switches. Platforms that
will host only StoreVirtual VSAs only need two ethernet (minimum 1 GbE) network adapters. Platforms that will host
Sample configurations
The sample configurations illustrate some of the recommended best practices for redundancy and availability.
Two-storage system configuration
A two-system configuration is the smallest possible redundant configuration. Automatic failover between storage systems
requires a Failover Manager or Quorum Witness. A two-storage system configuration contains the following elements.
NOTE: For more information, see “Failover Manager Overview” in the HPE StoreVirtual Storage User Guide, available on
the following website:
http://www.hpe.com/support/StoreVirtualManuals
Technical videos
Videos that illustrate installing the StoreVirtual VSA are available at the following website:
https://www.youtube.com/playlist?list=PLZ_dk9GbLIdsaoT3WzfRMkxCd1kcYgiDh
Beginning with ESXi 5.5, when installing StoreVirtual VSAs that use more than 8 TB of datastores, increase the maximum
addressable space. In ESXi 5.5 or later, managing large VMDK open files total addressable space is done using
MaxAddressableSpaceTB and MinAddressableSpaceTB. The following table lists the values for these settings.
Version/build Minimum heap value Maximum heap value Maximum open VMDK
storage per host
Table Continued
More information
StoreVirtual VSA and added storage capacity on page 50
To install the StoreVirtual VSA for vSphere OVF version, see Installing the StoreVirtual VSA OVF version.
After the installation is complete, install the Centralized Management Console (CMC) and find the StoreVirtual VSAs as storage
systems in the CMC, as described in CMC Installation. The CMC software is included with the StoreVirtual VSA download. You
can then set up the clustered storage for the SAN, using the Management Groups, Clusters, and Volumes wizard.
NOTE:
If a prior version CMC is installed on a management computer on the network, the StoreVirtual VSA for vSphere installer
updates the CMC to the current version in the same location. The user-specified location entered in the installer wizard is
ignored.
1. Download the StoreVirtual VSA for vSphere from the Hewlett Packard Enterprise website:
http://www.hpe.com/info/StoreVirtualDownloads
NOTE: If you selected the GUI installation, the GUI installer window opens again and you click Install VSA for VMware for
vSphere again to begin the wizard.
4. If necessary, enter the login credentials to allow the installer to configure the StoreVirtual VSA for vSphere on the vSphere
server, and click Yes.
5. Accept the terms of the License Agreement.
6. Complete the wizard to configure the parameters of the virtual machine on the network, including the hard drives.
7. (Optional) Configure another StoreVirtual VSA for vSphere using the same parameters as appropriate.
8. Finish the installation, reviewing the configuration summary, and click Deploy.
When the installer is finished, the StoreVirtual VSA for vSphere is started on the vSphere hosts and is discoverable in the
Centralized Management Console (CMC).
More information
Getting started with CMC on page 47
Updating virtual hardware version for vSphere on page 19
Installation wizard parameters for the StoreVirtual VSA for vSphere on page 21
CMC Installation on page 47
ESXi 6.7 U2 Create, Edit, Run. Create, Edit, Run. Create, Edit, Run. Create, Edit, Run. Create, Edit, Run.
ESXi 6.7 Create, Edit, Run. Create, Edit, Run. Create, Edit, Run. Create, Edit, Run. Create, Edit, Run.
ESXi 6.5 Create, Edit, Run. Create, Edit, Run. Create, Edit, Run. Create, Edit, Run. Create, Edit, Run.
ESXi 6.0 Create, Edit, Run. Create, Edit, Run. Create, Edit, Run. Create, Edit, Run. Create, Edit, Run.
ESXi 5.5 Not Supported Create, Edit, Run. Create, Edit, Run. Create, Edit, Run. Create, Edit, Run.
ESXi 5.1 Not Supported Not Supported Create, Edit, Run. Create, Edit, Run. Create, Edit, Run.
ESXi 5.0 Not Supported Not Supported Not Supported Create, Edit, Run. Create, Edit, Run.
Procedure
4. Choose option ESXi 6.0 virtual machine from the drop-down, to configure VM compatibility.
NOTE: VMware ESXi 5.5 should not be updated to VM version 7 as it disables Edit settings option for the VSA/FOM.
Parameter Definition
Host Setup vCenter Server that will host the StoreVirtual VSA. Enter
either the IP address or host name of the server.
Table Continued
• DNS name for the StoreVirtual VSA. The name for the
StoreVirtual VSA must be 80 characters or less. Valid
characters include a-z (case insensitive), 0–9, and –.
• NIC to configure. Available NICs are eth0 and eth1. The
StoreVirtual VSA for vSphere can support up to two NICs.
◦ IP address
A reserved IP address is recommended. Enter the IP
address, subnet mask, and gateway.
DHCP is supported. If you use DHCP, be sure to
reserve statically assigned IP addresses for all storage
systems on the DHCP server.
◦ The virtual network designated for the StoreVirtual
VSA. Select the appropriate virtual network from the
list.
Table Continued
Virtual Machine Information for creating the virtual machine, including the
following:
• Maximum of 7 drives
• Minimum size: 5 GB
• Maximum size: 64 TB in vSphere 5.5, 6.0, 6.5 and 6.7.
IMPORTANT:
• The raw disk size can be greater than 2 TB in
VMware. However, the total amount of configured
storage on the StoreVirtual VSA cannot exceed 50
TB or the RAID Stripe configuration will fail.
• Be sure to plan the disk capacity in conjunction
with the licensing for the StoreVirtual VSA.
Storage capacity can be added but not removed.
The purchased license controls the amount of
storage that can be used regardless of the disk
capacity.
• Every virtual disk should be RAID-protected and
not configured with RAID 0. The RAID Stripe that
is configured on the StoreVirtual VSA operates like
RAID 0, and creates a pool of storage that has no
redundancy across the drives.
iSCSI rescan
During the ESXi boot process, the iSCSI daemon in the hypervisor starts and scans for available iSCSI targets in an attempt to
establish iSCSI sessions to these targets. If known targets are not available at boot time, ESXi will not automatically discover
these targets once they become available after the system is booted. To discover the targets requires manually triggering a
storage rescan to restart the iSCSI target rescan.
The problem is exacerbated in environments where the iSCSI target is the HPE StoreVirtual VSA that is hosted on the same
ESXi server that is using the HPE StoreVirtual VSA storage. In such configurations, the hypervisor has not brought the HPE
StoreVirtual VSAs online yet, making the StoreVirtual iSCSI devices unavailable. Therefore, ESXi fails to connect and mount
StoreVirtual VSA iSCSI storage volumes automatically upon reboot.
To remedy this issue, HPE recommends obtaining and installing the HPE iSCSI Rescan software.
The ignite script is one of the last scripts executed when the system starts, and it invokes the rescan program.
The software logs activity in the file /var/log/hp-iscsi-rescan.log, which can be examined when troubleshooting
discovery issues. The log retains only the rescan activity for the most recent system reboot.
Default settings
• Rescan interval – 30 seconds. This variable controls how often the script scans for iSCSI targets.
• Rescan duration – 20 minutes. This variable controls how long the script continues scanning for iSCSI targets.
• Debug flag – OFF. This flag enables extended debug logging to help troubleshoot issues.
Prerequisites
Download the HPE iSCSI Rescan software for your ESXi version from http://vibsdepot.hpe.com/hpe/HPE-StoreVirtual/.
Procedure
VIBs Removed:
VIBs Skipped:
Installing the iSCSI Rescan software with the VMware Update Manager
Procedure
Use the VMware Update Manager (VUM) instructions to install the HPE iSCSI Rescan VIB offline bundle.
VUM documentation can be found on the VMware support website at https://www.vmware.com/support/.
Prerequisites
The iSCSI rescan must not be running.
Procedure
3. Uninstall hp-iscsi-rescan:
~ # esxcli software vib remove -n hp-iscsi-rescan
The following messages indicate a successful uninstall:
VIBs Installed
VIBs Skipped:
Uninstalling the iSCSI Rescan software with the VMware Update Manager
Procedure
Use the VMware Update Manager (VUM) instructions to uninstall the HPE iSCSI Rescan VIB offline bundle.
VUM documentation can be found on the VMware support website at https://www.vmware.com/support/.
Procedure
More information
Configuration requirements on page 11
CAUTION: Selecting anything other than SCSI 1:0 for the first disk causes RAID to be unconfigurable later.
Powering on the StoreVirtual VSA and setting the IP address and host name
Procedure
1. In the Inventory Panel, select the new StoreVirtual VSA for vSphere and power it on.
2. Select the Console tab and wait for the StoreVirtual VSA for vSphere to boot.
3. When the StoreVirtual VSA for vSphere finishes booting, enter Start and press Enter to log in to the Configuration
Interface.
4. On the Configuration Interface main menu, press Tab to select Network TCP/IP Settings and press Enter.
5. On the Available Network Devices window, press Tab to select the applicable network interface and press Enter.
6. On the Network Settings window, press Tab to select the Hostname box and enter a host name for the StoreVirtual VSA.
Use backspace to erase an entry if necessary.
This host name displays in the CMC only. It does not change the name of the original .vmx file or the name of the virtual
machine in the VMware interface.
7. Press Tab to select the method for setting the IP address.
If you are entering a static IP address, Gateway is a required field. If you do not have a gateway, enter 0.0.0.0.
NOTE: If VMware Tools show out of date or Unmanaged, then they are running correctly. These statuses are not
a problem, because the tools are available and running. VMware tools are updated with each LeftHand OS software
upgrade.
15. Next, install the CMC, described in Getting started with StoreVirtual Storage.
The installer may take a few minutes to complete, depending upon the underlying hardware.
16. Use the Find function in the CMC to discover the StoreVirtual VSA for vSphere.
The Find Systems window opens automatically the first time you open the CMC.
Issue Description
You want to reinstall the StoreVirtual VSA. 1. Close your CMC session.
2. In the vSphere Client, power off the StoreVirtual VSA.
3. Right-click and select Delete from Disk.
4. Copy fresh files into the virtual machine folder from the
downloaded .zip file.
5. Open VMware and begin again.
You cannot find the StoreVirtual VSA for vSphere with the In the VMware Console, open the Configuration Interface.
CMC, and cannot recall its IP address. Navigate to the Network Settings window to verify the IP
address.
You cannot configure RAID. Verify that the StoreVirtual VSA for vSphere has a virtual disk
configured on SCSI 1:0. StoreVirtual VSAs use SCSI 0:0 for
operating system disks. They use the disk configured for SCSI
1:0 for SAN data storage. If no SCSI disk is configured for
SCSI 1:0 then RAID cannot be configured on the appliance.
You cannot run concurrent StoreVirtual VSA Installers and The best practice is to use a unique name for each instance of
use the same name for the StoreVirtual VSAs on the same the StoreVirtual VSA that you create.
host you are creating.
Table Continued
LeftHand OS upgrades fail because persistent disk identifiers Follow these steps to enable the persistent disk identifiers for
are not enabled. each StoreVirtual VSA for vSphere:
1. From the CMC, power off the StoreVirtual VSA.
2. Open the VMware vSphere Client, and log into a
vCenter Server or ESX Server.
3. Verify that the virtual machine is powered off.
4. Right-click the virtual machine and select Edit Settings.
5. Click the Options tab and select the General entry in
the settings column (under the Advanced entry).
6. Click Configuration Parameters.
7. Click Add Row.
8. In the Name column, enter disk.Enable UUID.
9. In the Value column, enter True.
10. Click OK and then click Save.
11. Power on the virtual machine in the vSphere Client.
The StoreVirtual VSA installer creates StoreVirtual VSA for The following error occurs:
vSphere with no data disks.
Reconfigure virtual machine “name” A
general system error occurred: Failed
to create journal file provider: Failed
to open "/var/log/vmware/journal/
1379975011.25" for write: No such file
or directory
In Windows
The Installation wizard freezes. Reset the Hardware Acceleration in Windows:
In Linux
Table Continued
again.
In vSphere Client
Mouse and keyboard are not responding or are "trapped" in If your cursor is missing, you are in console mode. Press Ctrl-
the StoreVirtual VSA. Alt to regain the cursor. If your keyboard is missing, move the
mouse to the console window and click once.
You want to see your StoreVirtual VSA for vSphere, but the • You are in the Console view of the guest window. Change
window is black. to the Summary view.
• Your Console window has timed out. Click in the window
with the mouse and then press Backspace.
Cause
The iSCSI rescan script relies on the output of the ESXCLI command localcli iscsi adapter target list.
This command retrieves the list of known iSCSI targets from the iSCSI database in /etc/vmware/vmkiscsid/
vmkiscsid.db. The iSCSI database remembers targets that were previously accessed by the ESXi server. When targets are
permanently removed but the discovery address remains, the targets remain in the database and are included in the iSCSI
rescan.
The rescan script expects iSCSI sessions to be established to those stale targets. The script continues rescanning until a
session to all targets is established or the rescan duration expires.
Action
1. The error messages can be safely ignored in this situation. However HPE recommends that you access vCenter to validate
that all expected resources are present.
2. To view stale targets, use the iSCSI subcommand of the ESXCLI.
The vCenter iSCSI configuration menus will not show any of the stale targets.
NOTE: One or more Microsoft hotfixes may be required on your system before you can install the StoreVirtual VSA for Hyper-
V. If so, before the installer actually begins, a window opens that notifies you of the required hotfixes and provides links to the
appropriate site to download the hotfix.
Procedure
1. Download and install the StoreVirtual VSA for Hyper-V from the Hewlett Packard Enterprise website: http://
www.hpe.com/info/StoreVirtualDownloads
2. Double-click the downloaded executable to start the installation.
3. Accept the terms of the License Agreement.
4. Configure the parameters of the virtual machine on the network, including the hard drives.
NOTE: You can run the wizard again to configure another StoreVirtual VSA for Hyper-V using the same parameters as
appropriate.
5. Finish the installation, reviewing the configuration summary. When the installer is finished, the StoreVirtual VSA for Hyper-
V is ready to be used in StoreVirtual Storage.
More information
Getting started with CMC on page 47
CMC Installation on page 47
Installation wizard parameters for the StoreVirtual VSA for Hyper-V on page 32
Hotfix required One or more Microsoft hotfixes that must be installed before installing the StoreVirtual VSA for Hyper-
V.
Type The type of virtual machine to install. Choices include the StoreVirtual VSA or the Failover Manager
(FOM). The Failover Manager is a specialized version of the LeftHand OS software designed to operate
as a manager and provide automated failover capability. See the HPE StoreVirtual Storage User Guide
for information about installing the Failover Manager.
If choosing the StoreVirtual VSA, you can also choose whether the StoreVirtual VSA should be Adaptive
Optimization-capable and use multiple tiers of storage.
Destination Locations for the virtual machine and the virtual disks.
Table Continued
NOTE: The installer for the StoreVirtual VSA for Hyper-V only configures one virtual network
interface. However, an additional virtual network interface can be added manually through the virtual
machine settings.
Table Continued
Virtual machine Information for creating the virtual machine, including the following:
One of two windows opens, depending on which type of drives were selected in the Virtual machine
window.
IMPORTANT:
• The total amount of configured storage on the StoreVirtual VSA for Hyper-V cannot exceed
50 TB or RAID Stripe will fail.
• Be sure to plan the disk capacity in conjunction with the licensing for the StoreVirtual VSA.
Storage capacity can be added but not removed. The purchased license controls the amount
of storage that can be used regardless of the disk capacity. See StoreVirtual VSA license
capacity.
• Every virtual disk should be RAID-protected and not configured with RAID 0. The RAID
Stripe that is configured on the StoreVirtual VSA operates like RAID 0, and creates a pool of
storage that has no redundancy across the drives.
5. Set the following registry keys as described in the Microsoft Knowledge Base article entitled Tuning Windows for TCP/IP
performance which can be found at www.kb.globalscape.com/KnowledgebaseArticle10438.aspx.
a. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip
\Parameters\Interfaces\{Interface GUID}*.
b. Create DWORD 32 bit TcpAckFrequency with value 1 for all GUID interfaces entries.
c. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TCPIP
\Parameters.
6. Set the following registry setting as described in the Microsoft TechNet blog post entitled Increase VMBus buffer sizes to
increase network throughput to guest VMs, which can be found at www.blogs.technet.microsoft.com/
winserverperformance/2010/02/02/increase-vmbus-buffer-sizes-to-increase-network-throughput-to-guest-vms/.
a. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{GUID}\
{index}.
b. Create two new DWORD values, entitled ReceiveBufferSize and SendBufferSize and set the values to
0x800.
1. Install the Hyper-V role on Windows Server from the link https://docs.microsoft.com/en-us/windows-server/
virtualization/hyper-v/get-started/install-the-hyper-v-role-on-windows-server.
2. In Server Manager, on the Manage menu, click Add Roles and Features.
3. Verify the destination server and network environment. Click Next.
4. Select Role-based or Feature-based installation and click Next.
5. Select a server from the server pool. Click Next.
6. Select Hyper-V, on the Select server roles page.
7. To add the tools that you use to create and manage virtual machines, choose Add Features. Click Next.
8. Select the appropriate options, on Create Virtual Switches page, Virtual Machine Migration page, and Default Stores page.
9. Select Restart the destination server automatically if required, on the Confirm installation selections page. Click Install.
10. When installation is completed, verify that Hyper-V is installed.
11. Open all the Servers page in Server Manager and select a server on which you installed Hyper-V. Check the Roles and
Features tile on the page for the selected server.
Issue Description
While installing the StoreVirtual VSA for Hyper-V, you do not 1. Close the installer.
see the physical disks you prepared.
2. Verify that the disks are offline.
3. Start the installer again.
StoreVirtual VSA for Hyper-V reboot fails if the physical disk Do not use an iSCSI volume on a SAN as the physical disk for
of the StoreVirtual VSA for Hyper-V is an iSCSI mounted a StoreVirtual VSA.
volume
You want to reinstall the StoreVirtual VSA for Hyper-V. Using the Hyper-V Manager:
5. Rerun the .exe file and reinstall the StoreVirtual VSA for
Hyper-V.
6. Open the Hyper-V Manager and begin again.
You cannot find the StoreVirtual VSA for Hyper-V with the Open the Configuration Interface. Navigate to the Network
CMC, and cannot recall its IP address. Settings window to verify the IP address.
Windows event viewer event ID 4010 reports an unsupported You can ignore this warning message. This configuration has
configuration of the Hyper-V Linux Integration Services (LIS) been thoroughly tested by HPE Storage.
in the StoreVirtual VSA 2014.
The StoreVirtual VSA for Hyper-V installer does not block the Verify available disks prior to installation and select only
selection of disks already in use. available disks.
Hyper-V reports Linux Integration Services (LIS) tools are out For StoreVirtual VSAs and Failover Managers running on
of date. Hyper-V, the Networking Tab of the Hyper-V Manager will
show that the network status is
Degraded (Integration services upgrade
required)
◦ If you choose the "Virtualization Host" Role during OS installation, all KVM-related packages needed to deploy the
StoreVirtual VSA for KVM are installed.
◦ If the host OS is already installed on the server, install the packages:
kvm libvirt qemu-kvm.
◦ The installer for the StoreVirtual VSA for KVM also requires
virtinst/virt-install.
CAUTION:
To use a raw device for the StoreVirtual VSA for KVM, it cannot be used by the host Linux system. If you specify a raw
device that is used by the host system, the data on that disk or partition will be erased. It can also result in an
unbootable system.
Procedure
Raw devices
The StoreVirtual VSA for KVM supports using raw device access for the data devices, similar to RDMs on ESX and
PhysicalDisks on Hyper-V. This shouldn’t require any preparation. Supported raw devices include direct /dev/attach (for
example, /dev/sdc, /dev/sdd) and LVM Logical Volumes.
CAUTION:
To use a raw device for the StoreVirtual VSA, it cannot be used by the host Linux system. If you specify a raw device
that is used by the host system, the data on that disk or partition will be erased. It can also result in an unbootable
system.
Procedure
This creates a 100Gb raw device as /dev/vg-1TB-pool/raw-vol1-lv100g that the StoreVirtual VSA can use.
Multiple lv raw devices can be created within a single vg.
1. Download the StoreVirtual VSA for KVM bundle from the Hewlett Packard Enterprise website:
http://www.hpe.com/info/StoreVirtualDownloads
2. Extract the bundle in the target location using the following command:
tar –xvf HPE_StoreVirtual_VSA_Installer_for_Linux_KVM-<version >.tgz
This input file tells the installer how to configure the virtual machine. Create additional configurations using different
parameters with the standard template command.
• Enable additional disks with the -disks parameter. For example, the following syntax creates a configuration with
two disks.
./StoreVirtual_VSA_for_KVM_Installer-xx.x.xx.xxxx -create-default-json -
disks 2
• Configure Adaptive Optimization (AO) using the-tiering parameter. AO requires a minimum of two disks.
./StoreVirtual_VSA_for_KVM_Installer-xx.x.xx.xxxx -create-default-json -
disks 2 -tiering
• Create additional NICs with the -nics parameter. The following syntax creates a configuration with two NICs.
./StoreVirtual_VSA_for_KVM_Installer-xx.x.xx.xxxx -create-default-json -
nics 2
4. Edit the JSON file with the values necessary to create the virtual machine according to your planned configuration. See
the following example input file.
Table 8: Values required for the StoreVirtual VSA for KVM JSON file
Table Continued
Networks Add a network section to the JSON file for each NIC you are configuring.
• To assign a Static IP for the virtual machine, enter 0 for DHCP and complete the IP
address, Subnet, and Gateway fields.
• To assign a dynamic IP address, enter 1 for DHCP and leave the other fields empty.
• NetworkInterface must match the fields available in virsh net-list --
all.
Disks Disk location can be a storage pool, as found in virsh pool-list or a raw device. A
storage pool can be created and started using the following virsh commands: virsh
pool-define, virsh pool-autostart, virsh pool-start
NOTE: If you selected FOM for Personality, Disks will not display.
Disk subfields Location—Either the name of a KVM pool if using .img files for the data disks, for example,
vm-storage, or the path to a raw device (/dev/sdc, /dev/vg01/lv01).
Size —The size of the data disk. If using a raw device, leave this field blank to allow the
StoreVirtual VSA for KVM to claim the whole device.
Tier—An optional value to enable AO during installation. The field can contain either "Tier
0" or "Tier 1". Note the space between the word Tier and the number.
5. Install the StoreVirtual VSA for KVM by running the following command:
./StoreVirtual_VSA_Installer_for_KVM_<version> <JSON file> KVM-VSA-
<version>.img
NOTE: During installation, the OS image file is unpacked to its full size (32 GB), which can take several minutes.
Additionally, the virtual machine (VM) created during installation is rebooted before installation is complete. There is no
progress indicator for the installation, which may make it appear that nothing is happening. Wait for the installation to
complete.
The CLI commands virt-tools or virsh cannot be used to deploy the StoreVirtual VSA for KVM. You must use the
installer.
8. Verify the IP address and host name by entering the following command:
9. Next, install the CMC, described in Getting started with StoreVirtual Storage.
The installer may take a few minutes to complete, depending upon the underlying hardware.
10. Use the Find function in the CMC to discover the StoreVirtual VSA for vSphere.
The Find Systems window opens automatically the first time you open the CMC.
Adding memory, vCPUs and disks to the StoreVirtual VSA for KVM
The CLI utility, virsh, uses libvirt to manage KVM virtual machines. You can also use virt-manager to perform
management operations (including editing memory, CPU, or storage), but virt-manager requires GNOME or a GUI
equivalent to be installed on the host system.
1. Shut down the StoreVirtual VSA for KVM with the command:
virsh shutdown <vsa>
2. Edit the memory and vCPU configuration directly for the StoreVirtual VSA for KVM VM using the command:
virsh edit <vsa>
1. Run the following command on the host path, preferably in the storage pool that is already deployed:
server-name@/data/pools/vm-storage/# qemu-img create -f raw demo-disk 10G
2. Use the dumpxml command to create a copy of the StoreVirtual VSA configuration and save it to a file:
#virsh dumpxml srvr-1231-demo-1 > srvr-1231-demo-1.xml
3. Open the file and locate the current disk definitions (<disk> </disk>).
The file contents will differ slightly:
• If you are using a file disk, you will see <disk type='file'> and <source file=>
<disk type='file' device='disk'>
<driver name='qemu' type='raw'/>
<source file='/data/pools/vm-storage/srvr-1231-demo-1_disk1.img'/>
<backingStore/>
<target dev='vdc' bus='virtio'/>
<alias name='virtio-disk2'/>
• If you are using a raw device, you will see <disk type='block'> and <source dev=>
<disk type='block' device='disk'>
<driver name='qemu' type='raw'/>
<source dev='/dev/sdd'/> <backingStore/>
<target dev='vdc' bus='virtio'/>
<alias name='virtio-disk2'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
</disk>
4. Edit the <disk> </disk> section in the newly created demo-disk.xml file as follows:
• For <source file=>, enter the file name you created with qemu-img
• For <source dev=> , enter the raw device you want to add
c. Increment <target dev=> to the next letter (for example, dev='vdc' becomes dev='vdd').
d. Increment <alias name=> to the next value (for example, alias name=’virtio-disk2’ becomes
alias name=’virtio-disk3’).
The file should look similar to the following for a file disk:
<disk type='file' device='disk'>
<driver name='qemu' type='raw'/>
<source file='/data/pools/vm-storage/demo-disk'/>
<backingStore/>
<target dev='vdd' bus='virtio'/>
<alias name='virtio-disk3'/>
</disk>
5. Use the attach-device command to add the device to the StoreVirtual VSA:
#virsh attach-device srvr-1231-demo-1 demo-disk.xml --persistent --live
Device attached successfully
Procedure
1. Remove the StoreVirtual VSA for KVM from the management group.
2. Shut down the VM using the following command:
#virsh shutdown <VSA>
IMPORTANT: Be careful when deleting pools. There is no confirmation prompt before deleting the pool. Once you
submit the command, the pool is deleted.
The following error message is displayed. The KVM installer uses the lsb_release command
output to parse information.
Cannot determine the OS
Verify that lsb_release is available on the host machine.
Table Continued
ifconfig vsa-bridge.
Creating a storage pool fails. A storage pool is required to place the StoreVirtual VSA VM
image that is extracted from the installer. To resolve this
issue:
The VSA network cannot be deleted. The VSA network Determine if the network is already undefined.
should be deleted when StoreVirtual VSA installation fails.
Determine if the network name is the same in the JSON file
and in the output of the virsh net-list –all.
The storage pool cannot be deleted. The storage pool should Determine if storage pool is already undefined.
be deleted when the StoreVirtual VSA installation fails.
Determine if the pool name is the same in the JSON file and in
the output of the virsh pool-list –all command.
You cannot find the StoreVirtual VSA for KVM using the CMC, Open the virsh console for the StoreVirtual VSA.
or remember its IP address. Navigate to the Network Settings window to verify the IP
address.
You want to reinstall the StoreVirtual VSA for KVM. Perform the following steps:
The installation fails and reports that virt-inst failed or Review the Red Hat Linux documentation for common
libvirt errors are displayed. libvirt errors and troubleshooting steps.
Procedure
Procedure
a. Clear Auto Discover by Broadcast to prevent the entire subnet of storage systems from appearing in the Navigation
pane.
b. If your storage systems are on another subnet, add individual IP addresses of storage systems that you want to appear
in the Navigation pane.
Procedure
Procedure
Use the Management Groups, Clusters, and Volumes wizard on the Getting Started Launch Pad to create your storage pool.
Prerequisites
• A management group configured with a minimum of one cluster and one volume.
• The remote server iSCSI initiator ID or Fibre Channel WWN.
Procedure
1. Log in to the management group and use the Management Group Tasks menu to create a server.
2. Complete the information for either the iSCSI or the Fibre Channel server connection.
Detailed information about the various requirements for each type of server connection is explained in the Centralized
Management Console Online Help or the HPE StoreVirtual Storage User Guide.
3. Click OK to finish creating the server connection.
You can now assign volumes to the server connection.
Procedure
Failover manager
To install a Failover Manager for the StoreVirtual VSA, see the section about using the Failover Manager in the HPE
StoreVirtual Storage User Guide. The section provides installation instructions for StoreVirtual Failover Manager for Microsoft
Hyper-V, StoreVirtual Failover Manager for VMware vSphere, and StoreVirtual Failover Manager for KVM. There is not a
separate Failover Manager installer for KVM. Use the StoreVirtual VSA for KVM installer instead. Also, when installing the
StoreVirtual Failover Manager for KVM, you must edit the personality description in the JSON file. See the HPE StoreVirtual
Storage User Guide for details.
CAUTION: Resizing existing disks to add capacity requires that the StoreVirtual VSA be put into repair mode first to
prevent corruption. You must contact Hewlett Packard Enterprise Support to perform the repair procedure. Additionally
if all seven data drives are in use, the only way to increase capacity is to put the StoreVirtual VSA into repair mode.
• During the process of adding a disk, the storage system is restarted, the new disk is formatted, and new writes are
resynchronized with the storage systems in the cluster. If the new disk is large, formatting might take a long time to
complete. Resynchronization might impact performance. If there is only a single storage system in the cluster, the volumes
will go offline.
• Be aware that if you are adding disks that are already in a cluster, the process might take more time. Additionally, the CMC
does not prevent multiple storage systems from being taken offline.
• Hewlett Packard Enterprise recommends that you wait for one disk addition to complete before adding another disk to
ensure no loss of quorum.
• Add disks to only one StoreVirtual VSA at a time. Wait for the first StoreVirtual VSA to complete resynchronization and
verify that the cluster is healthy before adding disks to another VSA.
More information
Configuration requirements on page 11
Guidelines for management groups with mixed physical and VSA storage on page 15
IMPORTANT: Hot-addition of disks is not supported in VMware configurations where the storage controller is LSI Logic
SCSI. Hot-add is supported on StoreVirtual VSAs which run LeftHand OS 11.0 and higher with Paravirtual SCSI
(PVSCSI) adapters.
◦ vSphere Server—from SCSI 1:1 through SCSI 1:6. This assumes that the first disk has already been created and
assigned to SCSI 1:0.
◦ Hyper-V—locations 1 through 6 to SCSI Controller 0. This assumes that the first disk has already been created in SCSI
Controller 0, location 0.
1. Using either the vSphere Client or Microsoft Hyper-V Manager, add up to six disks to the StoreVirtual VSA.
2. Assign each disk to the next sequential SCSI address or location.
3. Configure the disks as follows:
More information
Configuration requirements on page 11
Documentation
For detailed instructions about using the CMC and the StoreVirtual VSA, see the following resources. You can find these
documents on the following website:
http://www.hpe.com/support/StoreVirtualManuals
Websites 53
Support and other resources
Accessing Hewlett Packard Enterprise Support
• For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website:
http://www.hpe.com/assistance
• To access documentation and support services, go to the Hewlett Packard Enterprise Support Center website:
http://www.hpe.com/support/hpesc
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
www.hpe.com/support/hpesc
Hewlett Packard Enterprise Support Center: Software downloads
www.hpe.com/support/downloads
Software Depot
www.hpe.com/support/softwaredepot
• To subscribe to eNewsletters and alerts:
www.hpe.com/support/e-updates
• To view and update your entitlements, and to link your contracts and warranties with your profile, go to the Hewlett
Packard Enterprise Support Center More Information on Access to Support Materials page:
www.hpe.com/support/AccessToSupportMaterials
IMPORTANT: Access to some updates might require product entitlement when accessed through the Hewlett Packard
Enterprise Support Center. You must have an HPE Passport set up with relevant entitlements.
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.
Warranty information
To view the warranty for your product or to view the Safety and Compliance Information for Server, Storage, Power,
Networking, and Rack Products reference document, go to the Enterprise Safety and Compliance website:
www.hpe.com/support/Safety-Compliance-EnterpriseProducts
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 (docsfeedback@hpe.com). 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.