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

Long boot time with large configurations
In a configuration with large numbers of devices, configured with large number of paths, the host
system takes more time to boot up. This is normal Windows behavior, which takes awhile to detect
devices and load drivers.
Open port 5988 for SMI-S in Windows Firewall
The appendix titled “Using VSM with firewalls” in the HP StorageWorks SAN Virtualization Services
Platform administrator guide states that port 5989 should be opened in the Windows Firewall for
HTTPS access to the SMI-S provider. In addition, port 5988 should be opened for HTTP access to the
SMI-S provider.
Cannot write to file error when using an MSA22xx array
The following scenario has been found to cause the virtual disk or LUN of an MSA to become
non-operational.
1. The virtual disk or LUN from an MSA is added to a VSM storage pool.
2. The virtual disk or LUN is removed from the storage pool.
3. The virtual disk or LUN is again added to a pool, or a pool is created from the LUN, and the
pool creation or expansion fails with a Cannot write to file error.
A workaround is to reboot the VSM servers, one after the other. A best practice for avoiding this issue
is to delete the virtual disk after completing step 2, instead of trying to reuse the virtual disk as a
back-end logical unit in step 3. The reason is that the disk may contain some SVSP signatures left over
from step 1, which may be recognized in step 3.
ForceActive with VSM server in unknown state
If the ForceActive utility is running and the VSM server enters an unknown state, stop the VSM GUI,
stop the ForceActive utility, restart the VSM, and then run the utility again.
Deletion of last DPM in a DPM group
Do not delete the last DPM in a DPM group (even though it is enabled for recovery purposes). To
recover from this situation, the following procedures should be followed:
• For non-synchronous mirror objects: Use Remove Host Permissions and then reassign the permissions
to hosts that are visible to the presented DPMs.
• For synchronous mirror objects:
1. Delete the host/UDH from the setup.
2. Verify that the host is visible through the presented DPMs.
3. Re-create the UDH.
4. Reassign the synchronous mirror group permission to the host through the presented DPMs.
SAN Virtualization Services Platform 3.0.1 Release Notes 15