HP StorageWorks SAN Virtualization Services Platform 2.02 release notes (5697-8024, February 2009)

Operating system issues
PA-RISC machines for HP-UX cannot boot from an external disk
PA-RISC machines running HP-UX were tested for the ability of HP-UX to be installed directly to a disk
presented by a storage array. The machines could not consistently reboot from an external disk,
therefore this is not supported at this time.
Setting the cluster bit for Serviceguard in Linux or HP-UX
When creating virtual disks that are to be used by Linux or HP-UX, the cluster bit check box must be
set in the Create Virtual Disk wizard—Enter Virtual Disk parameters screen. See Figure 22 in the HP
StorageWorks SAN Virtualization Services Platform Manager user guide on page 99 for an example
of the set check box.
Capacity limits with thinly provisioned volumes
When you run out of free space in a storage pool, a write to a thinly provisioned virtual disk may
appear successful, but the data is missing. You should receive a message from any operating system
that thin volume expansions has exceeded the threshold limit. This can be prevented by properly
setting and actively monitoring your pool protection thresholds, adding capacity, or adding thin
provisioning licenses.
VSM issues
Out of memory error when importing a LUN
When importing a LUN using the VSM GUI, you may experience an error 33; out of memory. This
issue was noticed when the installation of Windows did not come from the CDs supplied with the
SVSP product. If you receive this error, HP recommends that you allow Microsoft Windows to determine
the virtual memory size using memory management, and rebooting the VSM server.
Setting the host personality to ALUA changes host OS type to “unknown”
After changing the host type, the personality is set to “unknown.” The personality must be manually
changed to the correct setting.
Changing virtual disk or group DPM selection from two to one DPM is not allowed
VSM does not allow changing the virtual disk or virtual disk group DPM’s selection from two to one
DPM. Reducing the DPM selection to a single DPM most be done by removing permissions and
reassigning the permissions through a single DPM.
Computer name of single VSM server in SAN must not be changed
When a single VSM server is connected to the SAN, its computer name must not be changed. Changing
the VSM server computer name is allowed if two VSM servers are connected to the SAN. However,
changing the names must be done to a specific procedure, and to one VSM server at a time.
HP StorageWorks SAN Virtualization Services Platform 2.02 release notes 9