HP StorageWorks Enterprise Virtual Array Release Notes (XCS 09534000) (5697-3074, January 2014)

Emulex HBAs require unique zoning
When multiple Emulex HBAs are connected to the same EVA4400, each HBA requires unique
zoning.
QLogic HBA speed setting
In a Linux direct connect environment with QLogic 4 Gb/s HBAs, auto speed negotiation is not
supported. The QLogic HBA speed setting must be set to 4 Gb/s.
EVA6400/8400 host port negotiates to incorrect speed
The EVA6400/8400 might not correctly negotiate to 4 Gb/s when connected to an HP M-Series
4400, 4700, or 6140 switch with ports set to autonegotiate. The workaround is to set the switch
port to 4 Gb/s.
Creating 16 TB or greater virtual disks in Windows 2008
When creating a virtual disk that is 16 TB or greater in Windows 2008, ensure that the Allocation
unit size field is set to something other than Default in the Windows New Simple Volume wizard.
The recommended setting is 16K. If this field is set to Default, you will receive the following error
message:
The format operation did not complete because the cluster count is
higher than expected.
Importing Windows dynamic disk volumes
If you create a snapshot, snapclone, or mirrorclone with a Windows 2003 RAID-spanned dynamic
volume on the source virtual disk, and then try to import the copy to a Windows 2003 x64 (64-bit)
system, it will import with Dynamic Foreign status. The following message displays in the DiskPart
utility:
The disk management services could not complete the operation.
This error occurs because the 64-bit version of DiskPart fails to import dynamic RAID sets on a new
server.
To avoid this issue, use the 32-bit version of DiskPart instead of the 64-bit version. Copy DiskPart
from a 32-bit x86 Windows system, located in C:\WINDOWS\system32. Place the DiskPart utility
in a temporary folder on the 64-bit x64 Windows system.
Losing a path to a dynamic disk
If you are using Windows 2003 with dynamic disks and a path to the EVA virtual disk is temporarily
lost, the Logical Disk Manager (LDM) will erroneously show a failed dynamic volume. For more
information, see the following issue on the Microsoft knowledge base website:
http://support.microsoft.com/kb/816307
To resolve the issue, reboot the Windows 2003 server to restore the dynamic volume.
VMware configuration details for raw device mapping
Raw Device Mapping is not supported with Windows 2003 Virtual Machine Guest Operating
System on versions earlier than ESX 3.5.0.
To avoid issues with RDM LUNs, complete the following changes for the applicable ESX version.
For VMware ESX 3.0.1 or 3.0.2
Using the Virtual Infrastructure Client console, complete the following steps:
1. From the Configuration Tab, select Advanced Settings > Disk.
2. Add HSV3: HSV4 to the following setting: HSV1:HSV2:DGC:MSA_VOLUME:HSV3:HSV4
3. Click OK to apply the changes.
Workarounds 15