HP StorageWorks SAN Virtualization Services Platform 2.1 release notes (5697-8060, March 2009)

New back-end LUNs require rescan
To discover new back-end LUNs, perform a rescan from Computer Management on the VSM server.
Do not use the Rescan devices option from the Windows Management GUI. Use this general procedure
when assigning a new EVA LUN:
1. Present a new LUN (or group of new LUNs) to the VSM using HP Command View.
2. Log in to the VSM server, right-click on the My Computer icon, and select Manage.
3. Click Device Manager. In the right pane, right-click Disk Drives, and select Scan for hardware
changes.
4. After the screen stops refreshing, open the VSM GUI and navigate to Entities > Back End LUs >
Rescan Devices. The added LUs appear in the GUI under the list of back-end LUs.
LUNs must have a preferred path/controller
VSM does not support EVA LUNs that are configured in No Preference mode. They must be preferred
to Path A or B. If No Preference LUNs are presented to the VSM server, they will not display in the
GUI, and are therefore not manageable by the VSM. To resolve this issue:
1. Using HP Command View EVA, unpresent the No Preference LUNs.
2. Perform a rescan of the hardware with the VSM GUI.
a. Log in to the VSM server, right-click on the My Computer icon, and select Manage.
b. Click Device Manager. In the right pane, right-click Disk Drives, and select Scan for hardware
changes.
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
HP StorageWorks SAN Virtualization Services Platform 2.1 release notes 11