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

3. Ensure the LUNs are configured in the correct operation mode (Controller A failover/failback or
Controller B failover/failback) and present the LUNs again.
4. Perform a rescan as described in step 2.
Import some HP and IBM back-end LUs only to designated pools
HP HSG-80 and IBM FAStT 200/500 LUNs should be imported-in-place only to pools designated for
LUN import, as no new volumes may be created from these pools. Data must be migrated to another
pool that is not designated for LUN import.
NOTE:
These LUN import pools only need to have 1 GB of capacity and may be reused after detaching the
previously imported LUN. See the “Working with back-end LUs” chapter in the HP StorageWorks
SAN Virtualization Services Platform Manager user guide for more details.
Asynchronous mirrors and jobs do not fail when the source site is unavailable
Asynchronous mirror groups and jobs on the destination system do not fail when the source system
is down. It is expected VSM behavior that a job stays in a Normal state when the source site is down.
Accessing VSM may require Java Web Services
It may be necessary that Java Web Services be run (using Start > Run) 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.
Suspend active snapclone or migration tasks before deleting
If you have a virtual disk doing snapclone or migration tasks, and delete that task in the middle of
the data moving process (without suspending it first), the task becomes stuck and never completes the
deletion. When this issue occurs, you should perform the VSM failover procedure (through Tools >
Maintenance, and perform Failover VSM) in order to be able to complete the deletion process.
IPv6 support limitations
The following are limitations with IPv6 support:
• iSNS support is currently blocked.
• 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).
HP StorageWorks SAN Virtualization Services Platform 2.02 release notes 11