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

• The personality or OS type of a user-defined host (UDH) cannot be changed in the VSM while
virtual disks are exposed. All virtual disk permissions must be removed before changing the per-
sonality or OS type of a UDH. Not doing so could lead to unexpected results, a crash, or a reboot
of the DPMs.
• Persistent reservations and SCSI-2 reserve-release do not work correctly in some cases:
• Persistent reserve completes successfully on passive SCSI-2 on a reserved virtual disk.
• Persistent reserve completes successfully on the active DPM. The virtual disk is SCSI-2 reserved.
• When upgrading a Windows DSM-B host to the Full-Feature (FF) DSM, permissions to all virtual
disks presented to that host must be removed prior to uninstalling DSM-B and reapplied after FF-
DSM has been installed and the personality selected for the UDH has been changed to 'HP-EVA
VS-ALUA'. An alterative workaround would be to reboot both DPMs after FF-DSM has been installed
and the personality for the UDH has been changed.
HP Command View SVSP issues
HP Command View SVSP has reached end-of-life
The HP Command View SVSP GUI has been discontinued. HP recommends that you use the HP
Virtualization Services Manager (VSM) GUI with SVSP.
VSM CLI issues
The SelectVSMDomain command fails with certain operating systems
The SelectVSMDomain command fails on Hyper-V virtual machines (Windows and Linux) and on
the VMware ESX platform with Linux virtual machines.
Some VSM CLI commands cause the CLI application to stop
The ExpandPartition, ExpandPartitionEX, and GetBackEndLUPartitionNumbers
commands have been found to stop CLI processing. Do not use these command with a Windows
2008 R2 server.
No error message with PurgeVirtualDisks command
When purging presented virtual disks with the PurgeVirtualDisks command, no error messages
are displayed, even though this operation is not permitted and is not performed on virtual disks with
host presentations. Also, when using this command without a group selected, it results in a misleading
warning.
Exception error using Solaris with no VSM CLI virtual disk
The VSM CLI gives an exception error when using the VSM CLI with Solaris and a VSM CLI virtual
disk is not present. Ensure a VSM CLI virtual disk exists before sending CLI commands.
Host not checked when creating snapclone group
When using the CreateSnapcloneGroup command to create a snapclone group, a valid host is
needed. If a host is invalid or the host name is misspelled, a snapclone group is created, but is
24