12.8 HPE StoreVirtual Storage VSA Installation and Configuration Guide-A00090616en - Us

HPE StoreVirtual Storage VSA Installation and
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.
Part Number: TA768-96337

Published: October 2019
Edition: 13
© Copyright 2010, 2019 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 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.
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
Java® and Oracle® are registered trademarks of Oracle and/or its affiliates.
UNIX® is a registered trademark of The Open Group.
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
TA768-96334 May 2017 11 • Updated StoreVirtual VSA for vSphere functionality

• Improved configuration information
• Added configuration checklists
TA688-63137 March 2016 10 • Updated for Hewlett Packard Enterprise branding

• Revised CPU information
• Updated StoreVirtual VSA for KVM chapter, including
supported Linux versions, configuration requirements,
installation instructions, and troubleshooting
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
Installation Planning Checklists........................................................................................... 6

Checklist: Planning the virtual network.........................................................................................................................................................................6
Checklist: Planning the virtual storage pool............................................................................................................................................................... 7
Checklist: Planning the vSphere configuration for StoreVirtual VSA for vSphere...............................................................................7
Checklist: Planning the Hyper-V configuration for StoreVirtual VSA for Hyper-V.............................................................................8
Checklist: Planning the KVM configuration for the StoreVirtual VSA for KVM.....................................................................................8
Planning for the StoreVirtual VSA.................................................................................... 10

Configuration requirements..............................................................................................................................................................................................11
Best practices for configuring the StoreVirtual VSA..........................................................................................................................................13
Unsupported configurations for the StoreVirtual VSA..................................................................................................................................... 13
Hardware and network design for the StoreVirtual VSA.................................................................................................................................14
Guidelines for management groups with mixed physical and VSA storage.........................................................................................15
Sample configurations..........................................................................................................................................................................................................15
Technical videos.......................................................................................................................................................................................................................16
Installing the StoreVirtual VSA for vSphere....................................................................17

Supported versions of VMware.......................................................................................................................................................................................17
Configuration requirements for the StoreVirtual VSA for vSphere...........................................................................................................17
Best practices for StoreVirtual VSA for vSphere..................................................................................................................................................18
Unsupported configurations for StoreVirtual VSA for vSphere.................................................................................................................. 18
Installing the StoreVirtual VSA for vSphere............................................................................................................................................................ 18
Updating virtual hardware version for vSphere ................................................................................................................................. 19
Installation wizard parameters for the StoreVirtual VSA for vSphere....................................................................................21
iSCSI rescan...............................................................................................................................................................................................................24
HPE iSCSI Rescan software............................................................................................................................................................ 24
Installing the iSCSI Rescan software......................................................................................................................................... 24
Installing the iSCSI Rescan software with the VMware Update Manager...........................................................25
Uninstalling the iSCSI Rescan software...................................................................................................................................25
Uninstalling the iSCSI Rescan software with the VMware Update Manager.....................................................26
Installing the StoreVirtual VSA OVF version...........................................................................................................................................................26
Configuring a data disk...................................................................................................................................................................................... 26
Powering on the StoreVirtual VSA and setting the IP address and host name................................................................27
Troubleshooting the StoreVirtual VSA for vSphere........................................................................................................................................... 28
iSCSI rescan script fails to establish all sessions................................................................................................................................. 30
Installing the StoreVirtual VSA for Hyper-V................................................................... 31

Supported versions of Microsoft Windows Server...............................................................................................................................................31
Configuration requirements for the StoreVirtual VSA for Hyper-V.......................................................................................................... 31
Best practices for StoreVirtual VSA for Hyper-V................................................................................................................................................. 31
Unsupported configurations for StoreVirtual VSA for Hyper-V..................................................................................................................31
Installing the StoreVirtual VSA for Hyper-V........................................................................................................................................................... 32
Installation wizard parameters for the StoreVirtual VSA for Hyper-V...................................................................................32
Configuring Microsoft Hyper-V for Windows Server 2016...........................................................................................................34
Configuring Microsoft Hyper-V for Windows Server 2019...........................................................................................................35
Troubleshooting the StoreVirtual VSA for Hyper-V.......................................................................................................................................... 36
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
Getting started with StoreVirtual Storage.......................................................................47

CMC Installation....................................................................................................................................................................................................................... 47
Installing and opening the CMC in Microsoft Windows...................................................................................................................47
Installing and opening the CMC in Linux.................................................................................................................................................47
Getting started with CMC...................................................................................................................................................................................................47
Finding StoreVirtual VSAs with the CMC................................................................................................................................................ 48
Completing the StoreVirtual VSA hardware configuration...........................................................................................................49
Creating a StoreVirtual cluster.......................................................................................................................................................................49
Creating a server connection to the StoreVirtual VSA storage .................................................................................................50
Reviewing the Best Practice Summary......................................................................................................................................................50
Failover manager.....................................................................................................................................................................................................................50
StoreVirtual VSA and added storage capacity...................................................................................................................................................... 50
Creating additional disks...................................................................................................................................................................................51
Creating a disk for added capacity..............................................................................................................................................................52
Adding disks to RAID...........................................................................................................................................................................................52
Documentation ........................................................................................................................................................................................................................ 52
Websites................................................................................................................................. 53
Support and other resources.............................................................................................. 54

Accessing Hewlett Packard Enterprise Support................................................................................................................................................... 54
Accessing updates..................................................................................................................................................................................................................54
Customer self repair...............................................................................................................................................................................................................55
Remote support........................................................................................................................................................................................................................55
Warranty information............................................................................................................................................................................................................55
Regulatory information........................................................................................................................................................................................................56
Documentation feedback....................................................................................................................................................................................................56
5
Installation Planning Checklists
Verify the prerequisites for the virtual network, the virtual storage pool, and the StoreVirtual VSAs before you begin
installation.
Checklist: Planning the virtual network

Design and configure the virtual switches and network adapters. Use a virtual network environment with 1 GbE connectivity or
higher.
Procedure
Name of the storage network:
Name of the management network (optional):
Host names for the StoreVirtual VSAs:
◦ Host name #1:
◦ Host name #2:
◦ Host name #3:
IP addresses for the StoreVirtual VSAs:
◦ IP address #1:
◦ IP address #2:
◦ IP address #3:
Subnet mask:
Default gateway:
Mail server:
Time server:
DNS servers:
◦ DNS server #1:
◦ DNS server #2:
Virtual IP address of StoreVirtual cluster for iSCSI:

VIP IP:
6 Installation Planning Checklists

More information
Configuration requirements on page 11
Checklist: Planning the virtual storage pool

Procedure
Set the server time correctly to ensure that StoreVirtual VSA licenses remain valid.
Allocate enough drive space:
◦ Up to 32 GB for the StoreVirtual VSA

◦ Up to 50 TB of virtualized storage
Configure a redundant RAID configuration:
◦ Dedicated RAID set for the StoreVirtual VSA

◦ Disks configured to be persistent
◦ (Optional) Configuration plan for tiered storage for Adaptive Optimization
Reserve CPUs for the StoreVirtual VSA capacity.
Install license keys for the desired capacity and duration.
Reserve memory based on the total disk capacity.
Checklist: Planning the vSphere configuration for StoreVirtual VSA for

vSphere
Procedure
A qualified server for VMware.
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.
Microsoft NET 3.5 on the installer client.
vCenter servers properly licensed before connecting to them using the StoreVirtual VSA for vSphere installer.
The iSCSI storage adapter added on each host.
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
Installation Planning Checklists 7

Checklist: Planning the Hyper-V configuration for StoreVirtual VSA for
Hyper-V
Procedure
A qualified server for Microsoft Hyper-V.
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.)
Disks must be configured as fixed, not dynamic.
Microsoft .NET 3.5 on the installer client.
Dedicated NTFS partition for the StoreVirtual VSA.
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
Name for the virtual machine in the KVM server.
Up to seven data disks.
Disk size from 5 GB minimum to 50 TB maximum.
8 Installation Planning Checklists

Reserved IP addresses recommended, with subnet mask and gateway.
Dedicated, bridged, or bonded bridged network environment.
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
Installation Planning Checklists 9

Planning for the StoreVirtual VSA
StoreVirtual VSA software is a Virtual Storage Appliance that provides complete array functionality of StoreVirtual Storage for
VMware vSphere, Microsoft Hyper-V, and KVM environments without external array hardware. The StoreVirtual VSA uses
scale-out, distributed clustering to provide a pool of storage with enterprise storage features and simple management. Multiple
StoreVirtual VSAs running on multiple servers create a scalable pool of storage that offers high data availability.
Beginning with Version 11.0, StoreVirtual VSAs are Adaptive Optimization-capable and can use multiple tiers of storage.
Adaptive Optimization stores data which is accessed most frequently on the fastest performing media in a storage system—
typically solid-state drives. Adaptive Optimization in HPE StoreVirtual automatically adapts to changing workloads and moves
data accordingly and transparently. After Adaptive Optimization is enabled, the LeftHand OS stores the most accessed data to
faster/higher tiers in the Adaptive Optimization-capable storage tier.
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:
• Design and configuration of the virtual switches and network adapters

• Host names and IP addresses for StoreVirtual VSAs
• Virtual network configuration, including the virtual IP address (VIP) of the StoreVirtual cluster for iSCSI access
Designing your virtual storage pool

The design of your virtual storage pool affects both its performance and its reliability for production use. Use the concepts and
practices in this manual when installing and managing your virtual storage pool to ensure optimal performance and reliability.
10 Planning for the StoreVirtual VSA

Configuration requirements
The following configuration requirements are prerequisites for Hewlett Packard Enterprise to support your virtual storage pool
for production use.
• Available drive space of up to 32 GB for StoreVirtual VSA plus up to 50 TB of virtualized storage.

• A redundant RAID configuration. Hewlett Packard Enterprise recommends installing the ESX, Hyper-V, or KVM hypervisor
on top of a redundant RAID configuration. Do not use RAID 0.
• A sufficient number of CPUs reserved for the StoreVirtual VSA capacity. The table, Number of CPUs recommended by
StoreVirtual VSA capacity, lists CPU guidelines based on disk type and capacity. The exact number may vary depending
on the hardware in your environment. Ensure that you have additional memory and additional processors allocated for any
other hosted VMs on the same system.
Table 1: Number of CPUs recommended by StoreVirtual VSA capacity
Disk type Capacity CPUs to reserve
SFF SSD All 4 or 5
SFF SAS Up to 10 TB 2
SFF or LFF MDL-SAS Up to 10 TB 2
SFF or LFF MDL-SAS Up to 50 TB 3
• 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.
Table 2: Memory requirements for StoreVirtual VSA disks
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
Planning for the StoreVirtual VSA 11

Total virtualized capacity Total memory requirement in GB Total Adaptive Optimization and
Space Reclamation memory
requirements in GB
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.
Table 3: StoreVirtual VSA license capacity
Maximum capacity Duration Maximum cluster size Adaptive Optimization
1 TB 3 years 3 No
To extend the promotionally

licensed 1 TB StoreVirtual VSA,
you must upgrade the capacity as
well as extend the duration.
4 TB ◦ 3 years 3 No
◦ 5 years
10 TB ◦ 3 years Unlimited Yes

◦ 5 years
◦ No term
50 TB ◦ 3 years Unlimited Yes

◦ 5 years
◦ No term
• Virtual network environment with 1 GbE connectivity or higher, including the following:
◦ A host name for the StoreVirtual VSA.

◦ A network configuration plan, including reserved IP addresses, subnet mask, and gateway for the StoreVirtual VSA. If
you use DHCP, be sure to reserve statically assigned IP addresses for all storage systems on the DHCP server.
Reserved IP addresses are required.
• Dedicated RAID set for StoreVirtual VSA.

• If using tiered storage for Adaptive Optimization, plan the configuration of the datastore and physical disks in preparation
for installing and configuring the tiered storage on the StoreVirtual VSA.
In the StoreVirtual VSA, Tier 0 designates the fastest storage media. Tier 1 designates the next tier down in speed.
• High availability configuration requirements. The minimum configuration for high availability with automatic failover
consists of two or more StoreVirtual VSAs on separate physical servers with Network RAID-10 and a Failover Manager or
Quorum Witness.
A manual failover configuration can be achieved with two or more StoreVirtual VSAs on separate physical servers and
clustered with a Virtual Manager.
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
Best practices for configuring the StoreVirtual VSA

For detailed information about designing and configuring the StoreVirtual VSA solution, see the StoreVirtual VSA design and
configuration white paper.
Other configuration recommendations are useful to improve the reliability and performance of your virtual storage pool.
Consider implementing as many of these best practices as possible in your virtual storage pool environment.
• 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
Unsupported configurations for the StoreVirtual VSA

• The StoreVirtual VSA does not support bonding virtual network interfaces. Instead, Hewlett Packard Enterprise
recommends bonding network adapters on the host servers.

NOTE: The StoreVirtual VSA for vSphere is configured with two network interfaces. The StoreVirtual VSA for KVM can
have one or two interfaces, chosen during installation. The StoreVirtual VSA for Hyper-V is configured with one network
interface.
• 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
Hardware and network design for the StoreVirtual VSA

The hardware platform and network design used for a virtual storage pool affect the capacity, performance, and reliability of
that virtual storage pool. Some hardware platform requirements are described in Configuration requirements. Other
considerations for planning a StoreVirtual VSA implementation include the following:
• Virtual switch or network

• Controllers and hard disk drives
• Network adapters
Virtual switch or network

The virtual switch or network should be dedicated to the StoreVirtual VSA and iSCSI initiators that are accessing the
StoreVirtual cluster.
The virtual switch or virtual network that is used for StoreVirtual VSA should be at least a redundant Gigabit network, if
possible. Performance and reliability can be improved even further by using more than two ethernet adapters in the iSCSI and
StoreVirtual VSA virtual networks or by using 10 GbE network adapters.
See the StoreVirtual compatibility matrix for supported network adapters:
https://h20272.www2.hpe.com/spock/
Controllers and drives
The internal disk controller and disk drives of a platform affect the capacity and I/O performance of the StoreVirtual VSA.
Ideally, StoreVirtual VSAs should use storage that is hosted by many drives. If you are designing a new server that will host
StoreVirtual VSAs, you should incorporate the following recommendations.
• 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

StoreVirtual VSAs and other virtual machines should have at least four ethernet (minimum 1 GbE) network adapters so that
two adapters can be dedicated to the StoreVirtual VSA and iSCSI traffic.
Guidelines for management groups with mixed physical and VSA

storage
StoreVirtual VSAs and physical storage systems can be mixed in management groups. When mixing virtual and physical
storage systems, and mixing differently configured StoreVirtual VSAs, consider the following requirements and guidelines.
• Running managers on physical platforms

When possible, locate all managers in a management group on physical platforms instead of StoreVirtual VSAs, and ideally
on the fastest platforms in the management group. While StoreVirtual VSAs can run managers, physical platforms provide
better performance and a lower likelihood that they will be rebooted for administration reasons.
• Installing StoreVirtual VSAs that are running managers on separate physical platforms
If StoreVirtual VSAs are running managers, ensure that those StoreVirtual VSAs reside on separate physical platforms.
Otherwise, rebooting a single physical platform could cause a loss of quorum in the management group.
• Managing the performance impact of mixing platforms in clusters
Mixing StoreVirtual VSAs built from different hardware in the same cluster also yields unpredictable performance.
Typically, the overall performance of the cluster is close to the aggregate average of the storage systems in the cluster.
Additionally, you may perceive performance degradation if a faster StoreVirtual VSA fails, thus causing volumes to fail over
to a slower StoreVirtual VSA. Such performance degradation is normal in a mixed cluster.
• Managing the storage capacity of mixing platforms in clusters
While clusters can contain storage systems with different capacities, all storage systems in a cluster operate at a capacity
equal to that of the smallest-capacity storage system. The additional capacity on the StoreVirtual VSA operates according
to the same rules for physical storage systems in a cluster. The StoreVirtual VSA will operate at a capacity equal to that of
the smallest capacity StoreVirtual VSA in the cluster.
See “Clusters and storage systems” in the HPE StoreVirtual Storage User Guide for more information.
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.
• Two StoreVirtual VSAs in a single management group

• A single cluster
• Two managers
• A Failover Manager added to the management group
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

Figure 2: Two-storage system configuration
Three-storage system-plus configuration

All configurations greater than two storage systems can be redundant, and do not require a Virtual Manager or Failover
Manager. A configuration greater than two storage systems contains the following elements.
• Three or more storage systems in a management group

• Multiple clusters with as many StoreVirtual VSAs as desired in each cluster
• Running three or five managers, as appropriate
Figure 3: Three-storage system-plus configuration
Technical videos
Videos that illustrate installing the StoreVirtual VSA are available at the following website:
https://www.youtube.com/playlist?list=PLZ_dk9GbLIdsaoT3WzfRMkxCd1kcYgiDh

Installing the StoreVirtual VSA for vSphere
The StoreVirtual VSA for vSphere is pre-formatted for use with VMware vSphere. If you are using an evaluation copy, and want
to continue using the fully-featured StoreVirtual VSA after the trial period has ended, you must purchase a license key. After
you apply the license key, your configuration can be used as is in a production environment, or reconfigured if necessary.
Supported versions of VMware

See the HPE StoreVirtual 4000 and HPE StoreVirtual VSA Compatibility Matrix on https://h20272.www2.hpe.com/SPOCK/
Pages/spock2Html.aspx?htmlFile=hw_lefthand.html&lang=en&cc=in&hpappid=117135_SPOCK_PRO_HPE
Configuration requirements for the StoreVirtual VSA for vSphere

• A qualified server for VMware. For a list of qualified servers, see the VMware compatibility guide, at: http://
www.vmware.com/resources/compatibility/search.php
• Virtual disks with up to 64 TB 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.
• StoreVirtual VSA for vSphere virtual disks must be configured as independent and persistent to prevent VM snapshots
from affecting them.
• The VMFS datastores for the StoreVirtual VSA must not be shared with any other VMs.
• Microsoft NET 3.5 on the installer client.
• vCenter servers properly licensed before connecting to them using the StoreVirtual VSA for vSphere installer.
• The iSCSI storage adapter added on each host.
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.
Table 4: Minimum and maximum heap sizes
Version/build Minimum heap value Maximum heap value Maximum open VMDK
storage per host
ESXi 5.1 Build 1065491 and 256 MB 640 MB 60 TB

later
ESXi 5.5 16 MB 256 MB 128 TB
ESXi 6.0 16 MB 256 MB 128 TB
Table Continued
Installing the StoreVirtual VSA for vSphere 17

Version/build Minimum heap value Maximum heap value Maximum open VMDK
storage per host
ESXi 6.5 16 MB 256 MB 128 TB
ESXi 6.7 16 MB 256 MB 128 TB
Best practices for StoreVirtual VSA for vSphere

• Configure the StoreVirtual VSA for vSphere to start automatically and first, and before any other virtual machines, when
the vSphere Server on which it resides is started. This configuration ensures that the StoreVirtual VSA for vSphere is
brought back online as soon as possible to rejoin its cluster automatically.
• Locate the StoreVirtual VSA for vSphere on the same virtual switch as the VMkernel network used for iSCSI traffic. Using
the same virtual switch allows for a portion of iSCSI I/O to be served directly from the StoreVirtual VSA for vSphere to the
iSCSI initiator without using a physical network.
However, if the StoreVirtual VSA and the Windows initiator VM (that is deployed on the data store and created from
StoreVirtual volumes) are on the same ESX server and the StoreVirtual VSA is the gateway for StoreVirtual volumes, use
separate virtual switches (one for the StoreVirtual VSA for vSphere and one for iSCSI traffic) to improve performance.
• Locate the StoreVirtual VSA for vSphere on a virtual switch that is separate from the VMkernel network used for vMotion.
This configuration prevents vMotion traffic and StoreVirtual VSA for vSphere I/O traffic from interfering with each other
and affecting performance.
• Hewlett Packard Enterprise recommends installing vSphere Server on top of a redundant RAID configuration with a RAID
controller that has battery-backed cache enabled. Do not use RAID 0.
Unsupported configurations for StoreVirtual VSA for vSphere

• Use of VMware snapshots, VMotion, High-Availability, Fault Tolerance, or Distributed Resource Scheduler (DRS) on the
StoreVirtual VSA for vSphere itself.
• Use of any vSphere Server configuration that VMware does not support.
• Extending the data virtual disks, vSphere Server SCSI 1:x, of the StoreVirtual VSA for vSphere while in a cluster. Create
additional disks and hot-add them instead.
• Co-location of a StoreVirtual VSA for vSphere and other virtual machines on the same physical platform without
reservations for the StoreVirtual VSA for vSphere CPUs and memory in vSphere.
• Co-location of a StoreVirtual VSA for vSphere and other virtual machines on the same VMFS datastore.
• Running StoreVirtual VSA for vSphere’s on top of existing StoreVirtual Storage is not recommended.
More information
StoreVirtual VSA and added storage capacity on page 50
Installing the StoreVirtual VSA for vSphere

The installer for the StoreVirtual VSA for vSphere includes a wizard that guides you through the following tasks:
18 Installing the StoreVirtual VSA for vSphere

• Configuring the virtual machine on the network
• Configuring virtual or physical hard drives
• Powering on the StoreVirtual VSA
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
2. Double-click the downloaded executable to start the installation.

3. In the command-line window that opens, enter 1 to run the installer CLI, or enter 2 to run the installer GUI. Both versions
require the same information and perform the same installation.
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
Updating virtual hardware version for vSphere

The VM compatibility setting is used to select the ESXi host versions, when a VM is created or an existing VM is upgraded. The
compatibility setting determines the virtual hardware available to the VM, which corresponds to the physical hardware
available on the host.
Procedure to upgrade the hardware version of the following VMs created on ESXi host:

• HPE StoreVirtual VSA
• Failover Manager (FOM)
Table 5: Compatibility Matrix
ESX/ESXi version Version 11 Version 10 Version 9 Version 8 Version 7
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 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
To upgrade the VM's hardware version from version 7 to version 11.
1. Log in to ESXi host (version 6.0 / 6.5 / 6.7).

2. Shut down the running VM (VSA / FOM).
3. Click VM and select option Upgrade VM Compatibility.
4. Choose option ESXi 6.0 virtual machine from the drop-down, to configure VM compatibility.

5. Verify the hardware version (figure shows version 11).
NOTE: VMware ESXi 5.5 should not be updated to VM version 7 as it disables Edit settings option for the VSA/FOM.
Installation wizard parameters for the StoreVirtual VSA for vSphere
Parameter Definition
Host Setup vCenter Server that will host the StoreVirtual VSA. Enter
either the IP address or host name of the server.
Select Host List of vSphere hosts managed by the vCenter Server or

single vSphere Server, and health status and configuration
details for the host. Select the host on which to deploy the
StoreVirtual VSA. If deploying more than one StoreVirtual
VSA, you can choose to do so at the end of the wizard.
Table Continued

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 to configure the StoreVirtual VSA as Adaptive
Optimization-capable, and use multiple tiers of storage.
Datastore List of datastores available on the host. Select the desired

datastore on which to store the virtual appliance files.
Network Network settings include the following information:
• 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.
• The NIC designated as the preferred interface for

LeftHand OS, which is used for cluster communication
and iSCSI host traffic. Select eth0 or eth1.
Table Continued

Virtual Machine Information for creating the virtual machine, including the
following:
• Name for the virtual machine as you want it to appear in

the VM inventory on the host or vCenter
• Type of drive mapping to the StoreVirtual VSA virtualized
storage — Virtual Machine Disk Format (VMDK) or Raw
Device Mapping (RDM)
VMDK or Raw Disk Virtual or raw drive requirements
• Maximum of 7 drives
• Minimum size: 5 GB
• Maximum size: 64 TB in vSphere 5.5, 6.0, 6.5 and 6.7.
Depending on which type of mapping was selected in the

previous step, the wizard opens one of the following windows:
Virtual hard drives window

Select up to 7 virtual hard drives and designate the size.
If configuring tiered storage, assign a tier to each drive.
Tier 0 is the fastest tier.
Raw Disk window

Select up to 7 raw disks that you have prepared, and
which are available. These drives must have no partitions
or volumes on them, or the installer will not list them.
If configuring tiered storage, assign a tier to each drive.
Tier 0 is the fastest tier.
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.

More information
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.
HPE iSCSI Rescan software

The HPE iSCSI Rescan software automates volume discovery at boot time. The software is a VMware Installable Bundle (VIB)
available from the HPE vibsdepot.
The HPE iSCSI Rescan software has three main components:
• The ignite script in /etc/init.d/hp-iscsi-rescan.init
• The rescan program which is a python script in /opt/hp-storevirtual/hp-iscsi-rescan.py
• The boot time log file in /var/log/hp-iscsi-rescan.log
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.
Installing the iSCSI Rescan software
Prerequisites
Download the HPE iSCSI Rescan software for your ESXi version from http://vibsdepot.hpe.com/hpe/HPE-StoreVirtual/.
Procedure
1. Extract the zip file hpe-iscsi-rescan_X.X.0-12.0.0.1-offline_bundle.zip to retrieve the hpe-

iscsi-rescan-X.X.0-12.0.0.1.vib file.
2. Enable SSH on the vSphere hosts.

3. Copy the VIB file to the ESXi host:
SCP hpe-iscsi-rescan-X.X.0-1.00.vib to /tmp on the vSphere hosts.
4. Log in to the vShpere hosts using SSH.

5. Install hp-iscsi-rescan.init:
~ # esxcli software vib install -v /tmp/ hpe-iscsi-rescan-X.X.0-1.00.vib
The following messages indicate a successful installation:
Message: Operation finished successfully.
Reboot required: false
VIBs Installed: Hewlett-Packard_bootbank_ hp-iscsi-rescan-X.X.0-1.00
VIBs Removed:
VIBs Skipped:
6. Validate that the VIB is correctly installed:

esxcli software vib list | grep hp-iscsi-rescan
If the installed VIB is not listed, then installation may have failed. For installation information, check /var/log/
vmkernel.log.
7. Verify that the log file /var/log/hp-iscsi-rescan.log exists.

This log tracks the iSCSI rescan script operation.
8. Log off the SSH session.
9. (Optional) Disable SSH.
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/.
Uninstalling the iSCSI Rescan software
Prerequisites
The iSCSI rescan must not be running.
Procedure
1. Enable SSH on the vSphere hosts.

2. Log in to the vShpere hosts using SSH.
3. Uninstall hp-iscsi-rescan:
~ # esxcli software vib remove -n hp-iscsi-rescan
The following messages indicate a successful uninstall:
Message: Operation finished successfully.
Reboot required: false
VIBs Installed

VIBs Removed: Hewlett-Packard_bootbank_ hp-iscsi-rescan-X.X.0-1.00
VIBs Skipped:
4. Log off the SSH session.

5. (Optional) Disable SSH.
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/.
Installing the StoreVirtual VSA OVF version

Import the StoreVirtual VSA for vSphere OVF version as a virtual appliance through the Virtual Infrastructure Client.
Procedure
1. Download the .ovf zip file from the website:

2. Unzip the files.
3. Reserve the memory for the StoreVirtual VSA.
More information
Configuring a data disk

Procedure
1. In the vSphere Client, navigate to the Inventory Panel.

2. Click Add at the bottom of the Hardware tab.
3. Select Hard Disk as the type of device to add and click Next.
4. Select Create a new virtual disk and click Next.
5. In the Disk Capacity section, designate a capacity that is suitable for the amount of storage available on your vSphere
Server.
6. In the Location section, select Store with Virtual Machine, and click Next.
7. For the first disk, select the Virtual Device Node to be SCSI 1:0 from the list. For additional disks, assign SCSI 1:1 through
1:6, in sequential order.
CAUTION: Selecting anything other than SCSI 1:0 for the first disk causes RAID to be unconfigurable later.

8. Select Mode > Independent > Persistent and click Next.
9. Review the device configuration and click Finish.
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.
8. Press Tab to select OK and press Enter.

9. Press Enter again to confirm the action.
10. After the settings are configured, press Enter to confirm the IP address change.
11. On the Available Network Devices window, press Tab to select Back and press Enter.
12. On the Configuration Interface, press Tab to select Log Out and press Enter.
13. In the vSphere Client Information Panel, select the Summary tab.
14. In the General section on the Summary tab, verify that the IP address and host name are correct, and that VMware Tools
are running.
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.

Troubleshooting the StoreVirtual VSA for vSphere
Cause
Table 6: Troubleshooting the StoreVirtual VSA for vSphere
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

Issue Description
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
Information about this error is in VMware KB articles KB

1019598 and KB 2033073.
To resolve this issue, redeploy the StoreVirtual VSA.
In Windows
The Installation wizard freezes. Reset the Hardware Acceleration in Windows:
1. Open the Windows Display Settings > Advanced

settings > Troubleshoot tab.
2. Move the Hardware Acceleration slider to one notch
above None.
3. Click OK twice to exit the Properties dialog.
4. Restart the Installation wizard.
In Linux
Table Continued

Issue Description
The installer does not start automatically. Run

CMC_Installer.bin
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.
iSCSI rescan script fails to establish all sessions

Symptom
The iSCSI rescan script runs for the full duration. You may see messages similar to the following:
2013-11-25 16:38:19,138: INFO: Waiting for iSCSI sessions to re-establish to

these targets: iqn.2003-10.com.lefthandnetworks:HPcs300-mg-01:241:prodvmsa,
iqn.2003-10.com.lefthandnetworks:HPcs300-mg-01:253:prodvms-vola
2013-11-25 16:38:43,533: INFO: Storage adapter rescan complete
2013-11-25 16:38:43,533: ERROR: Failed to establish all iSCSI sessions
2013-11-25 16:38:43,533: ERROR: Exiting because the rescan duration expired.
User intervention may be required.
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.

Installing the StoreVirtual VSA for Hyper-V
The StoreVirtual VSA for Hyper-V is pre-formatted for use with Microsoft® Windows® Server. Install the StoreVirtual VSA for
Hyper-V on a Windows server configured with redundant RAID. If you are using an evaluation copy and want to continue using
the fully-featured StoreVirtual VSA for Hyper-V after the trial period has ended, you must purchase a license key. After you
apply the license key, your configuration can be used as is in a production environment, or reconfigured if necessary.
Supported versions of Microsoft Windows Server

StoreVirtual VSA for Hyper-V is supported on 64-bit systems only.
Pages/spock2Html.aspx?htmlFile=hw_lefthand.html&lang=en&cc=in&hpappid=117135_SPOCK_PRO_HPE
Configuration requirements for the StoreVirtual VSA for Hyper-V

• A qualified server for Microsoft Hyper-V. To verify that the server is listed and qualified for Hyper-V Server, go to
http://windowsservercatalog.com/results.aspx?&bCatID=1283&cpID=0&avc=11&ava=0&OR=1&PGS=25.Then search
for “Hyper-V” as an additional qualification. See the supported Windows versions.
• Virtual disks with 5 GB - 50 TB of space per disk on internal disk storage, or direct attached storage that is not accessible
from more than one physical server. (The LeftHand OS software consumes a small amount of the available space.).
• StoreVirtual VSA for Hyper-V virtual disks must be fixed, not dynamic.
• Microsoft .NET 3.5 on the installer client
• The NTFS partition for the StoreVirtual VSA must not be shared with any other VMs.
• Define the 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.
Best practices for StoreVirtual VSA for Hyper-V

• Configure the StoreVirtual VSA for Hyper-V to start automatically and first, and before any other virtual machines. The
default installation configuration for the StoreVirtual VSA for Hyper-V is set to automatically start if it was running when
the server shut down.
• For the StoreVirtual VSA for Hyper-V, dedicate a virtual network for iSCSI traffic.
• Hewlett Packard Enterprise recommends installing Hyper-V Server on top of a redundant RAID configuration with a RAID
Unsupported configurations for StoreVirtual VSA for Hyper-V

• Use of Microsoft Live Migration, Quick Migration, or snapshots on the StoreVirtual VSA itself.
• Use of any Hyper-V Server configuration that Microsoft does not support.
• Extending the data virtual disk(s), the first SCSI Controller in Hyper-V, of the StoreVirtual VSA while in a cluster. Create
additional disks and hot-add them instead.
Installing the StoreVirtual VSA for Hyper-V 31

• Co-location of a StoreVirtual VSA and other virtual machines on the same NTFS partition.
• Running StoreVirtual VSA for Hyper-Vs on top of existing StoreVirtual Storage is not recommended.
Installing the StoreVirtual VSA for Hyper-V

The installer for the StoreVirtual VSA for Hyper-V includes a wizard that guides you through configuring the virtual machine
on the network, configuring virtual or physical hard drives, and powering on the StoreVirtual VSA for Hyper-V.
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
Installation wizard parameters for the StoreVirtual VSA for Hyper-V
Installer Step Definition
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
32 Installing the StoreVirtual VSA for Hyper-V

Network Includes the following network information:
• Host name for the StoreVirtual VSA for Hyper-V.

• IP address.
Reserved IP address is recommended. DHCP is available. 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 virtual machines. Select the appropriate network from the
list.
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:
• Name for the virtual machine in Hyper-V

• Type of hard drives, virtual, or physical
• Check box to power on the StoreVirtual VSA for Hyper-V after it is installed
Hard drives, either Virtual or physical drive requirements

virtual or physical
• Maximum of 7 drives
• Minimum size: 5 GB
• Maximum size: 2,040 GB or 64 TB in Windows Server 2016
One of two windows opens, depending on which type of drives were selected in the Virtual machine
window.
Virtual hard drives window

Select up to 7 virtual hard drives and designate the size.
If configuring tiered storage, assign a tier to each drive. Tier 0 is the fastest tier.
Physical Drives window

Select up to 7 physical drives that you have prepared, and which are offline. These drives must have
no partitions or volumes on them, or the installer will not list them. To reuse HVSA disks for
expanding storage on a new HVSA, partitions must first be manually deleted.
If configuring tiered storage, assign a tier to each drive. Tier 0 is the fastest tier.
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.
Configuring Microsoft Hyper-V for Windows Server 2016

Procedure
1. Ensure that all Windows Server 2016 updates are installed.

2. Disable TCP Chimney Offloading using Windows PowerShell:
netsh int tcp set global chimney=disabled
3. Disable TCP receive window auto-tuning using Windows PowerShell:

netsh int tcp set global autotuninglevel=disabled

4. Set the Domain Profile as off.
netsh advfirewall set DomainProfile state off
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.
d. Create DWORD 32 bit TcpNumConnections with value 16777214.
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.
7. Create NIC teaming.

Use two 10 GB NICs for VSA iSCSI traffic and configure Team (for example, team NetworkInterface1 and
NetworkInterface2 to VSA_TEAM).
Configuring Microsoft Hyper-V for Windows Server 2019

Procedure
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.

Troubleshooting the StoreVirtual VSA for Hyper-V
Cause
Table 7: Troubleshooting the StoreVirtual VSA for Hyper-V
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:
1. Close your CMC session.

2. In the Hyper-V Manager, power off the StoreVirtual VSA
for Hyper-V.
3. Right-click and select Delete from Disk.
4. Optional: Delete the .vhd files to recover the disk space.
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)
and the IP address of the StoreVirtual VSA or Failover

Manager will not be displayed. This is a limitation of the LIS
component version 3.4 released by Microsoft. The HPE
StoreVirtual management software (CMC, CLI) can be used to
obtain valid networking information and status until
Microsoft releases a version of LIS that supports network
monitoring.

Installing the StoreVirtual VSA for KVM
The StoreVirtual VSA for KVM 2014 is pre-formatted for use with the KVM hypervisor. Install the StoreVirtual VSA for KVM on
a server running Linux with redundant RAID. If you are using an evaluation copy and want to continue using the fully-featured
StoreVirtual VSA for KVM after the trial period has ended, you must purchase a license key. After you apply the license key,
your configuration can be used as is in a production environment, or reconfigured if necessary.
Supported versions of Linux

Pages/spock2Html.aspx?htmlFile=hw_lefthand.html&lang=en&cc=in&hpappid=117135_SPOCK_PRO_HPE.
Configuration requirements for the StoreVirtual VSA for KVM

• 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 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.
• Name for the virtual machine in the KVM server

• Up to 7 data disks
• Size from 5 GB minimum to 50 TB maximum
• Reserved IP addresses recommended, with subnet mask and gateway
• Dedicated, bridged, or bonded bridged network environment
• 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 automatically start 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.
Preparing the storage configuration

Storage pool
Currently, only file-based data disks are supported and must be created as raw .img devices. The supported raw devices are
direct/dev/attach, multipath, and logical volumes (LVM).
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.
Installing the StoreVirtual VSA for KVM 37

As noted, at least one storage pool is required to hold the OS image. Storage pools are equivalent to VMware datastores. You
can create storage pools from raw disks or partitions, or logical volumes. It is recommended that you create separate storage
pools for the OS image and data disks.
Creating a directory pool

A directory pool is the default pool type and the simplest type of pool in KVM. You map a pool name to a directory location on
the file system.
Procedure
1. Create the pool directory:

2. mkdir -p /data/pools/vm-storage
3. Create the pool definition file (named vm-storage-pool.xml):

<pool type='dir'>
<name>vm-storage</name>
<source>
</source>
<target>
<path>/data/pools/vm-storage</path>
<permissions>
<mode>0755</mode>
<owner>-1</owner>
<group>-1</group>
</permissions>
</target>
</pool>
4. Define and enable the pool:

virsh pool-define vm-storage-pool.xml
virsh pool-start vm-storage
virsh pool-autostart vm-storage
5. Verify the status of the pool:

6. virsh pool-list
7. The command output should display the following:

Name State Autostart
---------------------------------------
vm-storage active yes
8. Verify the pool definition:

9. virsh pool-dumpxml vm-storage
10. The command output should display the following:

<pool type='dir'>
<name>vm-storage</name>
<uuid>b08e8311-e178-4220-a3e5-3a5219250fe9</uuid>
<capacity unit='bytes'>850036850688</capacity>
<allocation unit='bytes'>201455038464</allocation>
<available unit='bytes'>648581812224</available>
<source>
</source>
<target>
38 Installing the StoreVirtual VSA for KVM

<path>/data/pools/vm-storage</path>
<permissions>
<mode>0755</mode>
<owner>-1</owner>
<group>-1</group>
</permissions>
</target>
</pool>
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.
LVM logical volumes

LVM logical volumes can be used to provide raw devices to the StoreVirtual VSA, either on their own or in conjunction with
multipathing. While most distributions offer the user the option of enabling LVM at install time, this choice is left up to the
user. While the root LV on the host can be shrunken to provide space, doing this is not recommended as it can cause data loss.
The preferred method is to create a raw image file and mount it as a loopback device on the host. This device can be prepared
as an LV capable disk and used by the StoreVirtual VSA. Be careful prior to enabling or installing LVM if you have existing raw
devices on the system.
Creating a loopback LVM volume
Procedure
1. Create the img file:

qemu-img create -f raw lvm-rawdevice 1T
2. Link the img file to a loop device:

losetup /dev/loop0 /data/pools/1TB-pool/lvm-rawdevice
3. Create a pv using the file:

pvcreate /dev/loop0
4. Create a new vg using the loop0 device as a physical volume:

vgcreate vg-1TB-pool /dev/loop0
5. Create the new volume:

lvcreate -n raw-vol1-lv100g -L 100G vg-1TB-pool
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.

Best practices for StoreVirtual VSA for KVM
• Dedicate a virtual network for iSCSI traffic.
• Hewlett Packard Enterprise recommends installing the KVM hypervisor on a redundant RAID configuration with a RAID
Unsupported configurations for StoreVirtual VSA for KVM

• StoreVirtual VSA for KVM does not support bonding the interfaces on the StoreVirtual VSA itself. Instead, bond the
adapters on the KVM host.
• NAT networking configurations are not supported.
Installing the StoreVirtual VSA for KVM

Procedure
1. Download the StoreVirtual VSA for KVM bundle from the Hewlett Packard Enterprise website:
The file name is HPE_StoreVirtual_VSA_Installer_for_Linux_KVM-<version>.tgz.
2. Extract the bundle in the target location using the following command:
tar –xvf HPE_StoreVirtual_VSA_Installer_for_Linux_KVM-<version >.tgz
3. Create a JSON input file by running the following command:

./StoreVirtual_VSA_Installer_for_KVM_<version > -create-default-json
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.
disks 2 -tiering
• Create additional NICs with the -nics parameter. The following syntax creates a configuration with two NICs.
nics 2
• If you plan to deploy a Failover Manager, use the following syntax:

./StoreVirtual_VSA_for_KVM_Installer-xx.x.xx.xxxx -create-fom
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.

Example input file for the StoreVirtual VSA for KVM installer
{
"HostName": "VSA1",
"OSImageStoragePool": "vm-storage",
"Personality": "VSA",
"SANiQ_Preferred": 0,
"Networks": [
{
"DHCP": 0,
"IPAddress": "10.1.16.146",
"Subnet": "255.255.0.0",
"Gateway": "10.1.0.1",
"NetworkInterface": "kvm-storage-10g"
}
],
"Disks": [
{
"Location": "/dev/sdc",
"Size": "",
"Tier": "Tier 1"
},
{
"Location": "/dev/sdd",
"Size": "",
"Tier": "Tier 0"
}
]
}
Table 8: Values required for the StoreVirtual VSA for KVM JSON file
Installer configuration Definition
HostName Name for the virtual machine.
OSImageStoragePool A valid storage pool where the OS image will be located.
Table Continued

Installer configuration Definition
Personality VSA or FOM (Failover Manager).
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 StoreVirtual Failover Manager for
KVM.
SANiQ_Preferred Defaults to 0 for eth0.
Additional_NICs Set to 1 for a second NIC. Will configure as eth1.
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.
6. Accept the terms of the license agreement.

7. Verify that the virtual machine is running by entering the following command:
virsh list –all
8. Verify the IP address and host name by entering the following command:

virsh console <VSA>
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.
Adding memory and a vCPU

Procedure
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>
Adding disks to the StoreVirtual VSA for KVM

Procedure
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
NOTE: If you are using a raw device, skip this step.
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'/>

<address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
</disk>
• If you are using a raw device, you will see <disk type='block'> and <source dev=>
<disk type='block' device='disk'>
<source dev='/dev/sdd'/> <backingStore/>
<target dev='vdc' bus='virtio'/>
</disk>
4. Edit the <disk> </disk> section in the newly created demo-disk.xml file as follows:
a. Delete the <address type=> parameter.
b. Change the source 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:
<source file='/data/pools/vm-storage/demo-disk'/>
<backingStore/>
<target dev='vdd' bus='virtio'/>
</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
6. Verify that the disk was added to the StoreVirtual VSA:

#virsh dumpxml srvr-1231-demo-1
You should see a section for the newly added disk:
<source file='/data/pools/vm-storage/demo-disk'/>
<backingStore/>
<target dev='vdd' bus='virtio'/>
</disk>

The disk should be available to the StoreVirtual VSA shortly.
7. To use the new space, add the new disk to all StoreVirtual VSAs in the same cluster.
Uninstalling the StoreVirtual VSA for KVM

Delete the StoreVirtual VSA for KVM by shutting down and removing the guest virtual machine and then removing the image
file.
Procedure
1. Remove the StoreVirtual VSA for KVM from the management group.
2. Shut down the VM using the following command:
#virsh shutdown <VSA>
3. If the VM is not responding or fails to shut down, shut it down manually:

#virsh destroy <VSA>
4. Undefine the VMs configuration:

#virsh undefine <VSA>
5. Remove the OS and disk image file from the VM:
IMPORTANT: Be careful when deleting pools. There is no confirmation prompt before deleting the pool. Once you
submit the command, the pool is deleted.
#virsh vol-delete --pool vm-storage <VSA>.img

#virsh vol-delete --pool vm-storage <VSA>_disk<no>.img
Troubleshooting the StoreVirtual VSA for KVM

Issue Solution
Verify that all KVM-related prerequisites have been installed.
The following error message is displayed.
For more information, see Configuration requirements for
Cannot validate the KVM environment the StoreVirtual VSA for KVM.
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.
Verify that there is enough memory and CPU resources

The following error message is displayed.
available to deploy the StoreVirtual VSA. For more
Cannot find the required memory information, see Configuration requirements.
An error message displays that parsing the default JSON file
The installation script parses the configuration file and
failed, or that user inputs could not be validated.
updates the values. Review the JSON file inputs and verify
that there are no extra spaces for invalid characters.
Table Continued

The following error message is displayed. The StoreVirtual VSA deployment script determines the
netmask and gateway from the network interface. When there
Failure to retrieve netmask from vsa-
is no IP address assigned to the StoreVirtual VSA bridge, this
bridge
error may occur. To resolve this issue, verify that an IP
address has been allocated to the StoreVirtual VSA bridge:
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:
1. Verify that the storage pool directory is available.

2. Verify that there is available space to create a storage
pool.
3. Verify for available space to create storage pool in the
system.
4. Review the libvirt logs for any system-level errors.
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:
1. Remove the StoreVirtual VSA for KVM from the

management group.
2. Close the CMC.
3. Shut down the StoreVirtual VSA using virsh commands.
4. Optional: Delete the .img files to recover the disk space.
5. Rerun the StoreVirtual VSA for KVM installer.
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.

Getting started with StoreVirtual Storage
CMC Installation
Install the CMC on the computer or virtual machine that you use to administer the StoreVirtual Storage. You administer the
entire network of StoreVirtual VSAs from this CMC.
The CMC installation requires 63 MB disk space and 64 MB RAM during runtime.
Installing and opening the CMC in Microsoft Windows

Procedure
1. Download the CMC installer from the following website: http://www.hpe.com/info/StoreVirtualDownloads

2. Start the CMC installer.
3. Follow the steps in the installation wizard.
When the installation completes, Hewlett Packard Enterprise is added as a separate Program Group and a shortcut icon is
added to the Microsoft Windows desktop.
4. To open the CMC, do one of the following:
a. Double-click the icon on your desktop.

b. From the Start menu, select All Programs > HPE > HPE StoreVirtual > HPE StoreVirtual Centralized Management
Console.
Installing and opening the CMC in Linux

Prerequisites
You must be running the X Window System to install the application.
Procedure
1. Click the CMC installer.

2. Follow the steps in the installation wizard.
When the installation completes, Hewlett Packard Enterprise is added as a separate Program Group.
3. To open the CMC, navigate to the directory in which you installed the files.
4. Run the script
./HP StoreVirtual Centralized Management Console
Getting started with CMC

Procedure
1. Find StoreVirtual VSAs with the CMC

2. Complete the StoreVirtual VSA hardware configuration
3. Create a StoreVirtual cluster
Getting started with StoreVirtual Storage 47

4. Create a server connection to the StoreVirtual VSA storage
5. Review the Best Practice Summary
Finding StoreVirtual VSAs with the CMC

The CMC is configured to find all StoreVirtual VSA and physical storage systems on the subnets which the system running the
CMC is connected to. The first time you open the CMC, it automatically finds all the storage systems and they appear in the
Navigation pane.
To control which storage systems appear in the CMC, you can change the configuration.
Procedure
1. Open the CMC.

2. Click Find Systems on the Getting Started Launch Pad.
3. In the Find Systems window, use these features to control the list of storage systems:
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.
Figure 4: Editing Find Systems to control the storage systems displayed
48 Getting started with StoreVirtual Storage

Callout Description
1 1. Clear Auto Discover by Broadcast
2 2. Add IP addresses for specific storage systems
Completing the StoreVirtual VSA hardware configuration

Configure the storage system features, such as RAID, bonding the NICs, and setting up email alert notification.
Procedure
1. Open the CMC.

2. Select the StoreVirtual VSA in the Navigation pane to expand the hardware configuration categories.
Figure 5: Configuring the hardware
1. Configure RAID and the network from these categories
3. Verify that RAID Stripe is configured.

4. Verify that the network settings are correct.
Creating a StoreVirtual cluster

Prerequisites
Complete the hardware configuration.
Procedure
Use the Management Groups, Clusters, and Volumes wizard on the Getting Started Launch Pad to create your storage pool.

The wizard has online help available on each page.
Creating a server connection to the StoreVirtual VSA storage

Operating systems running on servers, clients or hosts, may access storage volumes on StoreVirtual systems using Fibre
Channel or iSCSI connectivity. Creating the server in the CMC creates the secure connection endpoint between each server and
its associated volumes.
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.
Reviewing the Best Practice Summary

Review the Best Practice Summary on the SAN Status Page in the CMC to ensure that you are following best practices for
configuring the StoreVirtual VSA and storage volumes. The Best Practice Summary provides an easy-to-use reference about
best practices that can increase the reliability and performance of your configurations.
Procedure
1. Navigate to the SAN Status Page in the CMC.

2. Log in to the management group to verify the Best Practices for that management group.
3. Move the mouse over a best practice item to see an explanation of the best practice.
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.
StoreVirtual VSA and added storage capacity

Consider the following when adding storage capacity:
• Add up to six disks, for a total of seven disks.

• For a cluster, ensure that all storage systems in the cluster have the same capacity.

• Ensure that you have the applicable license to accommodate the capacity increase.
• Add capacity by creating virtual disks, which is the recommended method.
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
Guidelines for management groups with mixed physical and VSA storage on page 15
Creating additional disks

Prerequisites
If you have upgraded to LeftHand OS version 11.0 from version 9.0, it is necessary to change the iSCSI controller to a
paravirtual adapter to allow for disks to be added while the StoreVirtual VSA is powered on. Open the vSphere client on the
vSphere server from which the StoreVirtual VSA is being deployed. Right-click the StoreVirtual VSA and select Edit settings.
Change the adapter type from iSCSI controller to paravirtual adapter.
The additional disks can be added to the StoreVirtual VSA in the CMC, while the StoreVirtual VSA is powered on.
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.
• Minimum disk size - 5 GB

• Maximum disk size - 64TB
• Sequential creation:
◦ 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.

Creating a disk for added capacity
Procedure
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:
a. vSphere Server disks as independent and persistent

b. Hyper-V disks as fixed size
4. Increase memory based on the total capacity of the StoreVirtual VSA.
More information
Adding disks to RAID

Procedure
1. In the CMC, navigate to the StoreVirtual VSA.

2. Select the Storage configuration category and select the Disk Setup tab.
3. Select the disk to add to RAID.
4. Right-click and select Add Disk to RAID.
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
• HPE StoreVirtual Storage Online Help

All user guide content is contained in the HPE StoreVirtual Storage Online Help, available from the menu bar under Help >
Help Topics. Context-sensitive help is available by clicking the question mark on any window ( ).
• HPE StoreVirtual Storage User Guide
The HPE StoreVirtual Storage User Guide provides detailed instructions for using the LeftHand OS software to create,
access, and manage the clustered data storage.
• HPE StoreVirtual Storage Remote Copy User Guide
The HPE StoreVirtual Storage Remote Copy User Guide provides instructions for using the Remote Copy capabilities of the
LeftHand OS software.
• HPE StoreVirtual Storage Multi-Site Configuration Guide
The HPE StoreVirtual Storage Multi-Site Configuration Guide provides instructions for configuring and using the
StoreVirtual Multi-Site SAN.

Websites
General websites
Hewlett Packard Enterprise Information Library
www.hpe.com/info/EIL
Single Point of Connectivity Knowledge (SPOCK) Storage compatibility matrix
www.hpe.com/storage/spock
Storage white papers and analyst reports
www.hpe.com/storage/whitepapers
For additional websites, see Support and other resources.
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.
54 Support and other resources

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:
http://www.hpe.com/support/selfrepair
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
www.hpe.com/services/getconnected
HPE Proactive Care services
www.hpe.com/services/proactivecare
HPE Proactive Care service: Supported products list
www.hpe.com/services/proactivecaresupportedproducts
HPE Proactive Care advanced service: Supported products list
www.hpe.com/services/proactivecareadvancedsupportedproducts
Proactive Care customer information

Proactive Care central
www.hpe.com/services/proactivecarecentral
Proactive Care service activation
www.hpe.com/services/proactivecarecentralgetstarted
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
Additional warranty information

HPE ProLiant and x86 Servers and Options
www.hpe.com/support/ProLiantServers-Warranties
HPE Enterprise Servers
www.hpe.com/support/EnterpriseServers-Warranties
HPE Storage Products
www.hpe.com/support/Storage-Warranties
HPE Networking Products
www.hpe.com/support/Networking-Warranties
Support and other resources 55

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:
www.hpe.com/support/Safety-Compliance-EnterpriseProducts
Additional regulatory information

Hewlett Packard Enterprise is committed to providing our customers with information about the chemical substances in our
products as needed to comply with legal requirements such as REACH (Regulation EC No 1907/2006 of the European
Parliament and the Council). A chemical information report for this product can be found at:
www.hpe.com/info/reach
For Hewlett Packard Enterprise product environmental and safety information and compliance data, including RoHS and
REACH, see:
www.hpe.com/info/ecodata
For Hewlett Packard Enterprise environmental information, including company programs, product recycling, and energy
efficiency, see:
www.hpe.com/info/environment
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.
56 Support and other resources

12.8 HPE StoreVirtual Storage VSA Installation and Configuration Guide-A00090616en - Us

Uploaded by

Copyright:

Available Formats

You might also like

12.8 HPE StoreVirtual Storage VSA Installation and Configuration Guide-A00090616en - Us

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

12.8 HPE StoreVirtual Storage VSA Installation and Configuration Guide-A00090616en - Us

Uploaded by

Copyright:

Available Formats

HPE StoreVirtual Storage VSA Installation and

Part Number: TA768-96337

Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.

UNIX® is a registered trademark of The Open Group.

TA768-96334 May 2017 11 • Updated StoreVirtual VSA for vSphere functionality

TA688-63137 March 2016 10 • Updated for Hewlett Packard Enterprise branding

Installation Planning Checklists........................................................................................... 6

Planning for the StoreVirtual VSA.................................................................................... 10

Installing the StoreVirtual VSA for vSphere....................................................................17

Installing the StoreVirtual VSA for Hyper-V................................................................... 31

Getting started with StoreVirtual Storage.......................................................................47

Support and other resources.............................................................................................. 54

Checklist: Planning the virtual network

Name of the storage network:

Name of the management network (optional):

Host names for the StoreVirtual VSAs:

◦ Host name #1:

◦ Host name #2:

◦ Host name #3:

IP addresses for the StoreVirtual VSAs:

◦ DNS server #1:

◦ DNS server #2:

Virtual IP address of StoreVirtual cluster for iSCSI:

6 Installation Planning Checklists

Checklist: Planning the virtual storage pool

Allocate enough drive space:

◦ Up to 32 GB for the StoreVirtual VSA

Configure a redundant RAID configuration:

◦ Dedicated RAID set for the StoreVirtual VSA

Reserve CPUs for the StoreVirtual VSA capacity.

Install license keys for the desired capacity and duration.

Reserve memory based on the total disk capacity.

Checklist: Planning the vSphere configuration for StoreVirtual VSA for

A qualified server for VMware.

Microsoft NET 3.5 on the installer client.

The iSCSI storage adapter added on each host.

Installation Planning Checklists 7

A qualified server for Microsoft Hyper-V.

Disks must be configured as fixed, not dynamic.

Microsoft .NET 3.5 on the installer client.

Dedicated NTFS partition for the StoreVirtual VSA.

Name for the virtual machine in the KVM server.

Up to seven data disks.

Disk size from 5 GB minimum to 50 TB maximum.

8 Installation Planning Checklists

Dedicated, bridged, or bonded bridged network environment.

Installation Planning Checklists 9

• Design and configuration of the virtual switches and network adapters

Designing your virtual storage pool

10 Planning for the StoreVirtual VSA

• Available drive space of up to 32 GB for StoreVirtual VSA plus up to 50 TB of virtualized storage.

Table 1: Number of CPUs recommended by StoreVirtual VSA capacity

Disk type Capacity CPUs to reserve

SFF SSD All 4 or 5

SFF or LFF MDL-SAS Up to 10 TB 2

SFF or LFF MDL-SAS Up to 50 TB 3

Table 2: Memory requirements for StoreVirtual VSA disks

Planning for the StoreVirtual VSA 11