HP StorageWorks SAN Virtualization Services Platform 2.1.1 release notes (5697-0066, July 2009)

NOTE:
All the above communications are confined to the SVSP domains. External communications (for
example, the GUI and other SOAP clients connected to the web server) are done according to the
site configuration (either through IPv4 or IPv6 addresses).
• If an IPv6 address is added or deleted while VSM is running, the VSM Monitor cannot detect this
change without restarting the VSM application.
• Downloading the VSM GUI client for IPv6 (for example, when IPv6 is configured as the desired
communication protocol between the web server and the client) must be done using the Microsoft
Internet Explorer 7 or Mozilla Firefox (version 3.0.3 and higher) browser. There is a known limit-
ation with Microsoft Internet Explorer 6, and it cannot be used.
• To log into the VSM GUI using IPv6 format, you need to enclose the address within right and left
brackets. For example: [fd00::21d:9ff:fe6b:1da9].
PiT deletions after reaching threshold Guard level
There are three configurable capacity threshold limits: Warning, Guard, and Emergency. When the
Guard level is reached, more than one of the older PiTs may be deleted. See the HP StorageWorks
SAN Virtualization Services Platform Manager user guide for details.
Incorrect number of paths displayed for clustered virtual disks
After adding presentations to a clustered virtual disk to more than one host, occasionally some of the
hosts do not display the correct number of paths. In these cases, perform the following:
1. Set the presentation to one UDH only.
2. Rescan for new devices.
3. Count the number of paths.
4. Set presentations to the second UDH.
5. Rescan for new devices.
6. Count the number of paths.
7. Remove the presentation.
8. Rescan for new devices on each UDH.
9. Set presentation to both UDHs at once.
Read-only permissions are not supported in the VSM GUI
Do not assign read-only permissions to a virtual disk using the VSM GUI, even if this is allowed in the
GUI.
Potential for I/O loss with synchronous mirrors due to active DPM failure
I/O loss could occur with synchronous mirroring using “Sync Always” groups (not with “Continue on
Fail” groups) when an active DPM is completely disconnected from the domain. Ensure that members
of the synchronous mirror group are failed over to the other DPM before disconnecting an active DPM
from the SAN.
HP StorageWorks SAN Virtualization Services Platform 2.1.1 release notes 15