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

SVSP back-end capabilities and limitations
• Back-end array capacity of the SVSP system: 1 PB using 512 2–TB back-end LUs
• Maximum number of back-end LUs: 512, up to 8 paths per BELU (2048 paths) per DPM group
(4 per DPM)
NOTE:
There is a limit of 254 back-end LUs (just under 1/2 PB using 2 TB per LU) per array, enforced
by the VSM.
• Largest back-end LUN: 2047 GB
• Smallest back-end LUN: array dependent
• Maximum number of stripe set members: 16
Configuration best practices
The following are a list of directives that must be followed for the HP SAN Virtualization Services
Platform.
• Install VSM on a server running Windows Server Standard Edition 2003 R2 with SP2 and Storport
hotfix KB932755.
• Microsoft KB939315 is not approved for use.
• Native QLogic HBAs drivers must be installed before VSM can be properly installed on a server.
• HP recommends that you place the setup virtual disks on three dedicated storage pools (that will
not be used for allocating any other virtual disks).
• Using the VSM client requires a JRE version of 1.5.0.06 up to 1.6.11. The VSM client does not
support JRE 1.6.12.
• The VSM client is approved for use only with Internet Explorer version 6 SP1 and version 7 with
subsequent service packs, or Mozilla Firefox version 2.0 and its service packs.
• Before the initial launching of the VSM client, ensure you know which VSM server is active so you
target the correct (active) VSM server of the system.
• Before connecting an upgraded or replacement VSM server to the SAN, you should install all the
license keys on the server. (Once connected to the SAN, the higher version VSM server—which
would be this one—becomes active, so the server needs to have the required licenses). See the
HP StorageWorks SAN Virtualization Services administrator guide for the upgrade process.
• When installing a new VSM system, you must first connect only one VSM server to the SAN, create
the setup virtual disk, and only then connect the second VSM server to the SAN. If there are two
VSM servers on the same system that see each other on the SAN, but cannot find the setup virtual
disk because it was not yet created, they will repeatedly alternate between active and passive
states.
• The Windows system disk of the VSM server and the VSM setup virtual disk must not be converted
into a dynamic disk.
• You should not upgrade (or accept automatic updates for) operating-system software components
such as iSCSI initiators and QLogic HBA drivers. Only explicit VSM components are approved
for use. Operating system security updates are supported.
• You must not change the computer name of the VSM server if it is the only VSM server that manages
the system, or if it is the only server that is currently connected to the SAN. Changing the computer
6