HP StorageWorks SAN Virtualization Services Platform 3.0.4 Release Notes (5697-0763, November 2010)

VSM issues
Thin virtual disks must have read/write permission and cluster flag
Do not create thin virtual disks with:
• Only read-only permissions (in other words, without any read-write permissions)
• Read-write permissions to both VSMs without the cluster flag.
If either operation is performed, the operation is blocked, but the virtual disk is created in a Delete
state. The thin virtual disk is deleted only upon restart or failover of the active VSM.
VSM GUI indicates passive VSM not ready for failover
The VSM GUI may erroneously indicate that the passive VSM server is not ready for a VSM failover
operation (for example, the passive VSM does not detect all the paths seen by the active VSM). This
is usually incorrect, and performing a VSM failover completes successfully.
Disabled Delete menu when virtual disk is member of synchronous mirror group
The Delete menu of a virtual disk that is a member of a synchronous mirror may become disabled
(grayed out). If this virtual disk was previously added to a synchronous mirror group that no longer
exists, then do one of the following:
• Fail over the active VSM to the passive VSM.
• Start and stop the active VSM using the SVSP Monitor.
SVSP web server hang makes GUIs inaccessible
In rare instances, a login to the VSM GUI can fail and display the message Login failed. Check
status of the SVSPs and check that Web Server is started. Checking the web
server status with the SVSP Monitor shows an active status. A workaround is to reboot the active VSM
server.
WSRM configuration step needed on VSM v2 server
When using the Windows System Resource Manager (WSRM) with SMI-S on an HP StorageWorks
Virtualization Services Manager (VSM) v2 server, the allocationpol.xml file must be edited to
change CPUAllocation from 25 to 12. This change does not apply to the VSM v1 server, which
was an HP ProLiant DL360 G5.
Imported LUNs must be aligned to a 1 MB capacity
There may be various issues when working with imported LUNs that are not aligned to a 1 MB
capacity. Operations are limited on unaligned volumes, so HP recommends that after importing the
LUN, migrate the imported virtual disk to a storage pool made of aligned LUNs.
Verify free space before concatenating thin virtual disk on thick virtual disk
Before expanding a regular (thick) virtual disk by concatenating a thin virtual disk on top of the thick
virtual disk, verify that the storage pool has at least 10 percent free space. If there is not enough free
space, the VSM will crash.
14