HP StorageWorks SAN Virtualization Services Platform 3.0 release notes (5697-0404, April 2010)

• 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 reserver completes successfully on the active DPM. The virtual disk is SCSI-2 reserverd.
• 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.
VSM CLI issues
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
immediately marked by the VSM as failed. A message in the VSM will state Snapclone Tasks
XXX has changed status to FAILED, reason: Host doesn't exist. The snapclone
group needs to be deleted and created again with a valid host name.
Error received with GetDpmInfo command when using –VDGroup argument
An error is received when using the GetDpmInfo command with the -VDGroup argument. Do not
use the -VDGroup argument. The -VirtualDisk argument works correctly with this command.
Incorrect error message displayed with CreateSnapshotWithLun command
When running the CreateSnapshotWithLun command on a LUN that was already used, the
message Selected LUN is in the range that belongs to the host in another
domain is displayed instead of the message The Specified LUN is already used by this
host. HP is working to resolve this issue.
22