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

Accessing VSM may require Java Web Services cleanup

It may be necessary that Java Web Services be run (using Start > Run > Javaws) in order to access

VSM through Internet Explorer or Mozilla. Delete all entries in the windows. (This is required when a

remote client cannot be opened.) Some of the files may be locked by another user or application (like

Remote Desktop), or you need to delete these sessions before running Java Web Services.

IPv6 support limitations

The following are limitations with IPv6 support:

• Communications between VSM servers and the web server (running on the VSM server) and the

CORBA layer is still based on IPv4 addresses. In addition, the SaSnap utility needs an IPv4 address

to fetch the data from a remote VSM server. Consequently, each VSM server must have at least

one IPv4 address, but may have IPv6 addresses as well.

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.

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.