Hp Technical Support - HP StoreVirtual 4000 Release Note

VSA
On a Windows 2008 Server, if proxy is configured, the VSA installer cannot connect to the ESX
Server
If proxy settings are configured on the Windows 2008 Server and you are using the VSA installer
on that server, the installer will not be able to connect to the ESX Server. First disable any proxy
settings and then run the VSA installer.
User cannot create a VSA disk size greater than the size of the physical drive (C:\)
When installing the HP LeftHand VSA for Microsoft Hyper-V, the size of the virtual hard drive is
currently limited to the reported drive size and does not take into account any additional mount
points that are within that drive.
To resolve this issue, do one of the following:
◦
Create a virtual hard drive size that is less than the physical drive size and then increase the
size of the virtual hard drive size after installation, using the Hyper-V Edit Disk Size option.
◦
Add a disk after creating the VSA for Hyper-V.
The VSA for Hyper-V cannot see multiple physical disks from a host when using a Dell Server
The HP LeftHand Storage VSA Installation and Configuration Guide user guide incorrectly states
the following is an unsupported configuration.
◦
In a VSA for Hyper-V configuration, only one physical disk can be viewed when the VSA is
connected to a Dell 2950 storage system.
The correct unsupported configuration should be the following:
◦
In a VSA for Hyper-V configuration, only disk 1 can be used if you are using physical disk
pass-thru on any Dell server. However, multiple VHDs can be used.
VSA for Hyper-V reboot fails if the physical disk of the VSA for Hyper-V is an iSCSI mounted
volume
Do not use an iSCSI volume on a SAN as the physical disk for a VSA.
When using a VSA for vSphere on a server with SSD drives, random reads drop noticeably from
version 9.0 to version 9.5
A version 9.5 VSA for vSphere using SSD drives as storage can become CPU-bound when
performing I/O, particularly when performing 8k random reads. This scenario can generate
alerts, and reduce overall performance. To reduce the likelihood of high CPU utilization, add a
second vCPU in VMware vCenter or vSphere.
Windows 2012 Hyper-V systems report LIS tools are out of date
For HP StoreVirtual VSAs and Failover Managers running on the Windows Server 2012 Hypervisor,
the Networking Tab of the Windows Hyper-V Manager will show that the network status is
Degraded (Integration services upgrade required) and the IP address of the VSA
or Failover Manager will not be displayed. This is a limitation of the Linux Integration Services
(LIS) component version 3.4 released by Microsoft. The HP StoreVirtual Configuration Interface
can be used to obtain valid networking information and status until Microsoft releases a version
of LIS that supports network monitoring.

HP Technical Support

For worldwide technical support information, see the HP support website:
http://www.hp.com/support
22 HP Technical Support