HP StorageWorks SAN Virtualization Services Platform 3.0.
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.2, which includes: • Virtualization Services Manager software version 1.2.551 supported by LSI HBA driver version 9.1.
Fixes The following issue was fixed in HP StorageWorks SAN Virtualization Services Platform from version 3.0.1 to version 3.0.2: • Resolved a timeout issue when trying to access an object without permission (for example, Add permission to a VDisk) and the user was logged off the HP Command View SVSP GUI. The fix was in the WebServer (flag changes). Prerequisites A dual-fabric SAN as defined by the HP SAN Design Reference Guide (http://www.hp.
Table 1 SVSP 3.0.2 supported operating systems OS Version Supported Not supported Comments AIX 5.2 5.3 6.1 HP-UX 11.23 Support for existing customers only, as Secure Path is not available for this version any longer. 11.31 Linux RHEL 4.7 RHEL 4.8 RHEL 5.1 RHEL 5 U2 RHEL 5 U3 RHEL 5 U4 RHEL 6.0 SLES 9 SLES 10 SP2 SLES 10 SP3 SLES 11 Mac OS X NetWare 6.5 OpenVMS SAN Virtualization Services Platform 3.0.
OS Version Supported Not supported Comments 8.3 Solaris 9 1 10 1 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.3 kernel) Xen (RHEL) 5.2 5.3 1 Clusters are not supported at the time of release. See http://www.hp.com/storage/spock for updates to operating systems and features supported. To obtain the HP MPIO Full Feature DSM and DSM Manager: 1. Go to http://www.hp.com and click Support & Drivers. 2.
• Cluster Extensions (CLX) • Disaster Tolerant Cluster Services (DTCS) • MetroCluster To obtain the IBM AIX MPIO ODM for SVSP: 1. Go to http://www.hp.com/go/svsp and click Support & Documents. 2. Click Download drivers and software. 3. In the Search field at the top of the page, enter AIX ODM and click the search arrows. 4. The search results should list the IBM AIX MPIO ODM for SVSP high in the rankings. Click on the link in the search rankings to take you to the web page.
• Synchronous mirrors supports up to 0.5 ms one-way separation (Fibre Channel transport only).
Configuration best practices The following are a list of directives that must be followed for the HP SAN Virtualization Services Platform. • SVSP 3.0.x can be installed only on a 64–bit Windows 2008 Server Standard Edition with SP2. It cannot be installed on a Windows 2008 Server with R2. • Native QLogic HBAs drivers must be installed before VSM can be properly installed on a server.
• Once a synchronous mirror is created, you cannot change the LU number of a synchronous mirror group. • You cannot add synchronous mirroring to a member of an asynchronous mirror group due to the existence of the asynchronous PiTs. However, you can first create a synchronous mirror and then add the asynchronous mirror group to it. • It is recommended that the quorum disk always be in automatic failover (Continue on fail) mode.
• Before installing or uninstalling VSM, you must make sure that all iSCSI connections are disconnected and the VSM is disconnected from the SAN. You must log out of all existing iSCSI connections. • After a disruption (perturbation) of VSM connections, wait at least two minutes to let the VSM rediscover all paths. • When booting from the SAN, make sure the host only sees that LUN through one path when there is no multipathing software on the host.
Operating system issues The Windows Server 2008 UAC prevents applications requiring admin privileges from working Due to security concerns within organizations, users may be prevented from logging into the VSM server with administrative privileges. The User Account Control (UAC) in Windows Server 2008 prevents applications like the VSM Monitor from running unless an administrator authorizes administrative privileges.
• When a file system from the HyperV manager is on the SCSI controllers, they show up as Msft on the SLES10 SP2 guest host. • Virtual Connect (VC) is supported on Windows. • Pass-through or imported virtual disks are not supported in HyperV. • Windows only recognizes 254 LUNs with the HP DSM driver though the Windows operating system supports 255 LUNs (maximum).
Manual failover of loaded system with VSM GUI causes a non-expected system state A manual VSM failover from the VSM GUI with 512 asynchronous mirror data movers causes a non-expected system state (NESS). The scenario is as follows: 1. VSM1 is active. 2. A failover is initiated from VSM1 to VSM2. 3. VSM2 becomes active, but experiences a NESS after a period of time and reboots. 4. VSM1 becomes active again and VSM2 becomes passive after it boots up. 5.
Front-end hosts not able to work with objects When a back-end array or LUN in the DPM back-end disappears or is masked out for a long time and then returns, the front-end hosts are not able to work with the objects (virtual disks, snapshots, and so on) that use the disappearing device (array or LUN). The workaround is that you need to execute an HBA disable/enable cycle or reboot the front-end host when the device returns.
5. Select the user account to which you are logged in (usually the manage account). 6. Change the base preference to base 2 or base 10, as desired. 7. Click the Modify User button, and click OK on the Success pop-up screen. From the CLI: 1. Log in using telnet or ssh. 2. Enter the set cli-parameters base command, where is 2 or 10. Error with Continuous Access license capacity when replicated differently The SVSP 3.0.
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 with VSM server in unknown state If the ForceActive utility is running and the VSM server enters an unknown state, stop the VSM GUI, stop the ForceActive utility, restart the VSM, and then run the utility again. 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).
2. Log in to the Windows 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. New LUNs will appear under Disk Drives. 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.
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 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.
of the synchronous mirror group are failed over to the other DPM before disconnecting an active DPM from the SAN. DPM issues Both DPMs crash when creating a sync mirror group on an inaccessible virtual disk Both DPMs crash if a synchronous mirror virtual disk is created on a back-end LUN that is not accessible to either DPM (but was accessible to the VSM). This is an incorrect configuration (zoning or LUN presentation error) but the DPMs should not crash due to this misconfiguration.
5. To redistribute the virtual disk between the two DPMs in the group, do the following: a. Go to the DPM groups display and select this DPM group. b. Select the Virtual Disks tab in the lower pane. c. Right-click on every virtual disk that needs to be moved back to the new DPM. d. Select Manage > Manage Data Path Module/SVSP > Change Primary/Secondary Data Path Module/SVSP. e. After changing the primary DPM for all required virtual disks, go to the upper pane and right-click on the DPM group. f.
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.
Initial GUI port statistics values are zero for an extended time It can take up to 30 seconds for the port statistics values in the DPM GUI to be retrieved. This may give the indication that nothing is happening. Wait for the collection of the statistics. Running show debug dump command does not work as expected The default show debug dump command attempts to output several binary files to the console. This results in unreadable output.
HP Command View SVSP issues Domains are not listed in Process Manager After installing Command View SVSP, there is an option to open the Process Manager so that an SVSP domain can be selected for management. There is an intermittent issue where sometimes no SVSP domain is listed. A workaround is to close the Process Manager GUI and reopen it. VSM webserver does not support https Command View SVSP does not work when the VSM webserver is configured to use https.
VSM CLI issues Some VSM CLI commands cause the CLI application to stop The ExpandPartition, ExpandPartitionEX, and GetBackEndLUPartitionNumbers commands have been found to stop CLI processing. Do not use these command with a Windows 2008 R2 server. No error message with PurgeVirtualDisks command When purging presented virtual disks with the PurgeVirtualDisks command, no error messages are displayed, even though this operation is not permitted and is not performed on virtual disks with host presentations.
Incorrect error message when creating 65th PiT on a virtual disk When creating the 65th PiT on a virtual disk using the VSM CLI, you receive an error message indicating A SCSI error in I/O to the switch. The correct error message should be the Virtual disk has too many PiTs. HP is working to resolve this issue. The ListSnapshots command fails to return data with too many PiTs The ListSnapshots command with a –PiT argument does not return data with 2048 PiTs.
The CreateSnapcloneGroupEx command fails with HP-UX if the group is still building The CreateSnapcloneGroupEx command should run the first time. However, with HP-UX, if the command is run again while the snapclone operation is still building the copy, the command fails. You should increase the timeout argument to as long as you believe the building operation should last. HP is working to resolve this issue.
