HP StorageWorks SAN Virtualization Services Platform 2.1.
Legal and notice information © Copyright 2008-2009 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 2.1.1, which includes: • Virtualization Services Manager software version 1.1.451 supported by LSI HBA driver version 9.1.
• • • • • • • • • deletion of multiple VSS snapshots at one time when using the VSM GUI. Instead, delete VSS snapshots with the Microsoft Volume Shadow Copy Service that created them. TPRLO support reinstated—Fixed an issue where the receipt of a TPRLO frame caused the DPM to reboot or fail. Memory leak on idle VSM servers—Fixed a VSM memory leak issue that only occurred on idle VSM servers with a minimal setup.
Host operating systems and multipath drivers See http://www.hp.com/storage/spock for a listing of supported operating systems and required multipath drivers. Site registration is required. 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.
• Maximum HBAs per server: 8 (Windows/DSM limit) SVSP front-end capabilities and limitations • Front-end presented capacity of the SVSP system: 1 PB (Maximum of back-end. See the following back-end section for additional limitations.
• 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.
• Do not mix virtual disks with both “Continue-on-fail” and “Always sync” synchronous mirror groups in the same cluster. Operational best practices • Should you want to delete, remove, or undo an operation to an SVSP entity, it is best if you reverse the processes that were used to get you to that operational stage. Additional details are in the HP StorageWorks SAN Virtualization Services Platform administrator guide.
• Before starting a migration task, make sure the task does not have any PiTs (such as user PiTs or mirror PiTs). If PiTs exist, they must be deleted before the task starts, otherwise a future snapshot created on these PiTs (or a rollback to them) after migration will not be consistent. • Before installing or uninstalling VSM, you must make sure that all iSCSI connections are disconnected. You must log out of all existing iSCSI connections.
PA-RISC machines for HP-UX cannot boot from an external disk PA-RISC machines running HP-UX were tested for the ability of HP-UX to be installed directly to a disk presented by a storage array. The machines could not consistently reboot from an external disk, therefore this is not supported at this time.
disk as a back-end logical unit in step 3. The reason is that the disk may contain some SVSP signatures left over from step 1, which may be recognized in step 3. ForceActive external utility issues The following two issues have been identified after installation of the ForceActive external utility: • The AutoRecover key is deleted from the Windows registry. After installation of the VSM software, the AutoRecover key must be re-created manually.
Message when failing over a VSM server after refreshing access paths When failing over a VSM server after refreshing the access paths, the VSM displays a warning message that the back-end LUs are not accessible in the passive VSM server. This may be a false warning, so attempt to fail over despite the message. VSS with synchronous mirror LUNs At this time, the use of Microsoft Volume Shadow Copy Service (VSS) on a LUN that is part of a synchronous mirror within the same domain is not supported.
Windows fault when array unresponsive There is a Windows limitation that when an array becomes unresponsive, it returns a SCSI BUSY or QUEUE status. This causes an endless loop in the Windows StorPort.sys driver because it tries to resend the command. This may lead to a Windows fault condition. VSM must be enabled for "Reboot on fatal error" To allow a second VSM server to take over in case the primary VSM server encounters a fatal error, VSM must be set to "Reboot on fatal error.
b. 3. 4. Click Device Manager. In the right pane, right-click Disk Drives, and select Scan for hardware changes. Ensure the LUNs are configured in the correct operation mode (Controller A failover/failback or Controller B failover/failback) and present the LUNs again. Perform a rescan as described in step 2.
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.
DPM issues TPRLO issue TPRLO does not properly propagate PRLO to shared initiators. Unable to FTP during upgrade If you are unable to connect to a DPM using FTP during an upgrade for the DPM, contact HP services for assistance.
Period of high back-end load after a DPM reboot when synchronous mirror virtual disks are used In a configuration with synchronous mirror virtual disks, there may be a period of higher than normal load on the back-end storage arrays after a DPM reboot. This will vary depending on the capacity of the synchronous mirror virtual disks and with the load and write patterns on those virtual disks before the DPM reboot.
DPM ports connected to a 4 Gb Fibre Channel switch may sometimes auto-negotiate to 2 Gb speed In some cases, the DPM ports may negotiate to a slower speed than their capability. In these cases, verify the SFPs in the DPM and switch are supported and that there is not an unusually high number of errors reported for that link in the port statistics. If there are errors, replace the SFPs and cable. The port can also be manually set to 4 Gb speed on the DPM.
VSM creates HBAs and host entries for a Brocade switch Due to the fabric name server logging into the DPM as an initiator, the switch can sometimes show up in the VSM as an HBA. The DPM should filter out switch ports so they are not presented to the VSM. This has no practical effect, but may be confusing. HP is working to resolve this issue.
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.
