HP StorageWorks SAN Virtualization Services Platform 3.
Legal and notice information © Copyright 2008-2010 Hewlett-Packard Development Company, L.P.
Description HP StorageWorks SAN Virtualization Services Platform (SVSP) is a hardware and software solution that enhances the storage capabilities of approved storage arrays. Using Virtualization Service Manager (VSM) software, redundant VSM servers and Data Path Modules (DPMs) map application server I/O to locations on storage systems. Versions HP SAN Virtualization Services Platform 3.0, which includes: • Virtualization Services Manager software version 1.2.530 supported by LSI HBA driver version 9.1.7.
Fixes The following issues were fixed in HP StorageWorks SAN Virtualization Services Platform from version 2.1.1 to version 3.0: • PiT expansions to a thin volume could fail as a result of fragmentation. • Multiple areas were improved that resulted in both VSMs receiving FEE1DEAD and memory dumps for unknown reasons. • The export query label appeared as an empty or blank string on the query menu. • A rolling DPM SAC reboot would occur when a synchronous mirror with a PiT was greater than 4 TB.
Installation instructions For a new or upgrade installation of Virtualization Services Manager or Data Path Module software, contact HP Support. After installing the VSM GUI, change the registry as described below and reboot the VSM server. At the location HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ CrashControl\CrashDumpEnabled, set the registry key to 0x1 (instead of 0x2). Host operating systems and multipath drivers Table 1 lists the SVSP 3.0 supported and non-supported operating systems.
OS Version SLES 9 SLES 10 SP2 SLES 10 SP3 SLES 11 Mac OS X NetWare 6.5 OpenVMS 8.3 Solaris 9 10 VMware ESX 3.5 ESX 4.0 Windows 2003, R2, SP2 2008 SP1, SP2 2008 R2 HyperV HyperV v2 Xen (Citrix) 5 5.5 (RHEL 5.
OS Version Supported Not supported Comments 5.2 5.3 To obtain the HP MPIO Full Feature DSM and DSM Manager: 1. Go to http://www.hp.com and click Support & Drivers. 2. In the Step 1 area, select the Download drivers and software (and firmware) option. The Step 2 field becomes available. 3. In the “For product” field of the Step 2 area, enter DSM and click Go. A screen listing other multi-path software for Windows is displayed. 4. Click Windows MPIO DSM for SAN Virtualization Services Platform.
• Maximum number of servers (with 2 HBA ports/server) per DPM pair: 512 (2048 with 4 DPM pairs) • Maximum number of tasks per domain (total snapclones, async mirrors, and internal migrations): 512 • Maximum HBAs per server: 8 (Windows/DSM limit) • DPM maximum number synchronous mirror groups: 128 per DPM group (512 with 4 DPM groups) • Defined maximum distances: • Asynchronous mirrors are supported up to 150 ms one-way separation (iSCSI only), and minimum bandwidth set to 3 Mbps.
• • • • • • • Maximum host ports per back-end LU: 8 Maximum number of back-end LUs: 1024 Maximum number of back-end paths (PSCs): 4096 Largest back-end LUN: 2047 GB Smallest back-end LUN: array dependent Maximum number of back-end LUNs per back-side initiator/target pair: 254 (LUNs 1–254) 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. • SVSP 3.
• Do not overload the array that contains the setup virtual disks. An overloaded array is one where the average write response time for the VSM setup virtual disk exceeds 20 msec. • The default threshold for capacity alerts is 10%. When setting capacity alerts, you should set the alerts slightly higher (for example, add 5%) to ensure that the storage administrator is notified in time. • Once a synchronous mirror is created, you cannot change the LU number of a synchronous mirror group.
• Do not change any back-end logical unit characteristic (for example, number, name, size [by expanding or contracting], and so on) once it has been virtualized (for example, entered into a VSM storage pool) or is being managed by the VSM. The LUN identification has been written on the LU by VSM. • Before starting a migration task, make sure the task does not have any PiTs (such as user PiTs or mirror PiTs).
Upgrade order When upgrading from SVSP 2.x, the VSM servers must be upgraded first, and then the Data Path Modules may be upgraded. Each is done one-at-a-time, making the upgrade process a rolling upgrade. Operating system issues Miscellaneous Windows issues The following are currently issues with Microsoft Windows: • A LUN after an Import-in-Place operation can be accessed (read/write) as normal disk from the VSM server.
Setting the cluster bit for Serviceguard in Linux or HP-UX If virtual disks are presented through Data Path Modules with Linux or HP-UX, do not set the cluster bit, as this will force the DPMs to abort pending writes after a period of time.
Cannot have same first 29 characters in sync mirror task names You cannot have two synchronous mirror tasks with the first 29 characters of their names being identical. When this occurs, an Object already exists message appears, and the operation (adding the second task) fails. Cannot expand VDG without same DPM as the members You are unable to expand a virtual disk group (VDG) if the added virtual disks do not have the same active Data Path Module and the virtual disk group members.
Error with Continuous Access license capacity when replicated differently The SVSP 3.0 Continuous Access license correctly charges the size of the source on both sites as long as it is the same type of replication (for example, remote copy (snapclone) or async mirror).
Deletion of last DPM in a DPM group Do not delete the last DPM in a DPM group (even though it is enabled for recovery purposes). To recover from this situation, the following procedures should be followed: • For non-synchronous mirror objects: Use Remove Host Permissions and then reassign the permissions to hosts that are visible to the presented DPMs. • For synchronous mirror objects: 1. Delete the host/UDH from the setup. 2. Verify that the host is visible through the presented DPMs. 3.
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.
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.
DPM issues Replacing a DPM in a DPM group when upgrading from SVSP 2.x to SVSP 3.0 When upgrading from SVSP 2.x to SVSP 3.0, an issue occurs when replacing a DPM in a DPM group that was created in SVSP 2.x. This may also occur when trying to add a new DPM to the old DPM group. The newly added DPM will not join the old DPM group. To recover from this issue, perform the following steps: 1. Manually delete the old (partial) DPM group. 2.
Change active switch command does not work with Sun Solaris hosts The change active switch command is an operation that you can initiate on the VSM to force a virtual disk to become active on the other DPM. This is typically used in maintenance operations to proactively failover virtual disks to one of the DPMs so that the other DPM can be serviced.
DPM NTP configuration does not work with Windows The DPM only supports NTP servers that support network time protocol query (ntpq) and the full RFC-1305 specification. In particular, Windows only implements ‘Simple NTP’ and is not supported by the DPM as an NTP server.
• Persistent reservations and SCSI-2 reserve-release do not work correctly in some cases: • Persistent reserve completes successfully on passive SCSI-2 on a reserved virtual disk. • Persistent reserver completes successfully on the active DPM. The virtual disk is SCSI-2 reserverd.
Incorrect error message when ExpandVirtualDisk command is missing argument When the ExpandVirtualDisk command is missing the MBfromPool argument, the error message incorrectly states that the StoragePool name is missing. The error message should indicate that Not all sizes specified for all StoragePools. HP is working to resolve this issue.
Incorrect error message when ManageSnapcloneGroup command is missing the Opcode argument in HP-UX If the Opcode argument is missing from the ManageSnapcloneGroup command in HP-UX, you will receive an incorrect error message stating that both parameters are missing, instead of only the Opcode missing. HP is working to resolve this issue. The CreateSnapcloneGroupEx command fails with HP-UX if the group is still building The CreateSnapcloneGroupEx command should run the first time.
