HP StorageWorks SAN Virtualization Services Platform 3.0.1 Release Notes (5697 - 0405, May 2010)

If the LUN is already imported and mounted to the VSM: Use the MountVol D:\ /P command
(where D is the drive letter assigned to the mounted, imported LUN) for every LUN receiving an
Import-in-Place. This unmount the LUN and prevents Windows Server 2008 from remounting it
after a reboot. Be sure you do not unmount the setup virtual disk.
• For a Windows HyperV environment, the only supported guest operating systems are the Windows
operating systems—Windows Server 2003 SP2, Windows Server 2008 SP1/SP2, and Windows
Server 2008 R2. HP DSM is not expected to support any non-Windows guest operating system
in a HyperV environment.
• When a file system from the HyperV manager is on the SCSI controllers, they show up as Msft on
the SLES10 SP2 guest host.
• Virtual Connect (VC) is supported on Windows.
• Pass-through or imported virtual disks are not supported in HyperV.
• Windows only recognizes 254 LUNs with the HP DSM driver though the Windows operating
system supports 255 LUNs (maximum).
• Automatic failback of Microsoft Cluster Service resource groups does not occur when both the
HBA cables of one node are pulled out and reinserted.
OpenVMS support without async mirrors
OpenVMS 8.3 is supported with the exception of asynchronous mirrors.
SMI-S provider can delete some setup virtual disks
SVSP normally uses three setup virtual disks that are a part of a synchronous mirror group. It is possible
while using the SMI-S provider to delete two of these setup virtual disks, but not the third. This can
cause system availability issues, so ensure that care is taken to not delete any setup virtual disks.
Setting the cluster bit for Serviceguard in Linux or HP-UX
If virtual disks are presented through Data Path Modules with Linux or HP-UX, do not set the cluster
bit, as this will force the DPMs to abort pending writes after a period of time.
Capacity limits with thin provisioned volumes
When you run out of free space in a storage pool, a write to a thin provisioned virtual disk will create
an error to the I/O, but information about that error may not convey the idea that thin volume space
has run out because the SCSI standards have not taken this into account yet. You should receive a
message or alert from the VSM indicating that space for a thin volume has run out, because the VSM
understands thin volumes. This can be prevented by properly setting and actively monitoring your
pool protection thresholds, adding capacity, or adding thin provisioning licenses.
VSM issues
Threshold limit message only sent once
When a threshold limit is reached, a single event log message is generated, instead of a message
being sent every five minutes.
12