HP MPIO Full Featured DSM for SAN Virtualization Services Platform 4.01.
Legal and notice information © Copyright 2006, 2010 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents About this guide ................................................................................... 7 Intended audience ...................................................................................................................... Related documentation ................................................................................................................ Document conventions and symbols ...............................................................................................
Commands to manage the HP EVA DSM parameters .............................................................. 31 A — Software components ................................................................... 33 Drivers .................................................................................................................................... User mode components ............................................................................................................. HP MPIO DSM manager GUI .........
Tables 1 Document conventions ............................................................................................... 7 2 Snapshot of pre-installation checklist .......................................................................... 11 3 Load balancing policies ........................................................................................... 23 4 Notification strings .................................................................................................. 31 5 MPIO.
About this guide This guide provides information about HP MPIO Full Featured Device Specific Module (DSM) for SAN Virtualization Services Platform (called the “HP MPIO SVSP DSM” throughout this guide), which includes: • Installing, upgrading, and removing HP MPIO SVSP DSM • Support for load balancing in Microsoft Cluster Server (MSCS)/Failover Cluster environments • Managing HP MPIO SVSP DSM Intended audience This document is intended for customers who use the HP MPIO SVSP DSM software and has the knowledg
Convention Element • File and directory names Monospace text • System output • Code • Commands, their arguments, and argument values Monospace, italic text Monospace, bold text • Code variables • Command variables Emphasized monospace text CAUTION: Indicates that failure to follow directions could result in damage to equipment or data. NOTE: Provides additional information. HP technical support For worldwide technical support information, see the HP support website: http://www.hp.
To make comments and suggestions about product documentation, please send a message to: storagedocsFeedback@hp.com. All submissions become the property of HP. Product feedback To make comments and suggestions about HP MPIO Full Featured DSM for SAN Virtualization Services Platform 4.01.00, please send a message to: multipathfeedback@hp.com. HP MPIO Full Featured DSM for SAN Virtualization Services Platform 4.01.
About this guide
1 Installing the HP MPIO Full Featured DSM for SAN Virtualization Services Platform HP MPIO SVSP DSM provides multipathing support for HP StorageWorks disk arrays on Windows platforms using the Microsoft Multipath Input-Output (MPIO) framework. Preparing for installation Before installing HP MPIO SVSP DSM, verify that your system components support the software and determine whether you need to upgrade the system's hardware or software before installation.
Task Obtain and review the most current versions of the following documents: • HP MPIO Full Featured DSM for SAN Virtualization Services Platform release notes • Installation and configuration information for your system, available at the following website: http://www.hp.com/country/us/eng/prodserv/storage.html • Supported SAN topologies for HP MPIO SVSP DSM, as defined and described in the HP StorageWorks SAN design reference guide available at the following website: http://h18006.www1.hp.
1. 2. 3. 4. Complete the pre-installation checklist (Table 2) and the pre-installation procedure, see Preparing for installation. Using the Cluster Administrator: a. Move all cluster resources owned by the current node to another node in the cluster. b. Pause the current cluster node. c. Disable failback for all the groups containing resources managed by the current node.
NOTE: After the upgrade, reboot the host and present back all the SVSP devices. Upgrading HP MPIO SVSP DSM on a clustered system To upgrade HP MPIO SVSP DSM from a previous version to the current version on a clustered system, complete the following steps: NOTE: On a clustered system, HP MPIO SVSP DSM must be upgraded on one node at a time for all nodes in the cluster. 1. Complete the pre-installation checklist (Table 2) and the pre-installation procedure, see Preparing for installation. 2.
3. Upgrade to Windows Server 2008. 4. Double-click the batch file (depending on your operating system): • For Windows Server 2008 x86: \x86\Win2k8Upgrade.bat • For Windows Server 2008 IA64: \ia64\Win2k8Upgrade.bat • For Windows Server 2008 x64: \amd64\Win2k8Upgrade.bat NOTE: For more information on upgrading the operating system of a clustered system from Windows Server 2003 to Windows Server 2008, see http://support.microsoft.com/kb/935197.
6. Close the Add/Remove Programs window. NOTE: The LUNs may be inaccessible at this time. 7. Reboot the system. NOTE: For Windows Server 2008 Server Core and Microsoft Windows Server 2008 R2 Server Core, go to the installation location from the command prompt and run Launch.exe. Select Remove > Remove all installed components, to remove HP MPIO SVSP DSM. Using silent installation You can execute the silent installation from the installation location on your computer or from a network drive.
Result Code Description –52 Cannot access the specified file or folder NOTE: The C: in /f1C: and /f2C: refers to a local drive on the system or a network drive which is used to obtain the response file and write the MPSInstallLog.txt (provided the directory has the write permission enabled).
1. Make a copy of the update.iss file in the installation location with the name setup.iss. 2. Choose one of the following options: • To upgrade the Microsoft MPIO Framework component along with the DSM component, use the renamed default setup.iss file. • To upgrade only the DSM component (when the Microsoft MPIO Framework already exists on your system), edit the renamed default setup.iss file as follows: 3. a. In line 23, replace Component-count=2 with Component-count=1. b. c. Remove line 24.
Setting up boot from SAN You can set up HP MPIO SVSP DSM to boot externally from a SAN that uses HP StorageWorks HBAs and RAID arrays. Booting the system from an external device offers the following advantages: • Optional elimination of server-based internal boot devices • Decreased downtime in the event of a server failure Booting from a SAN requires specific setup procedures based on the specific software solutions, HBA firmware, and boot BIOS versions.
Installing the HP MPIO Full Featured DSM for SAN Virtualization Services Platform
2 Support for load balancing in Cluster environment In Windows Server 2008 and Windows Server 2008 R2 Failover Cluster, load balancing is enabled by default and cannot be disabled. In Windows Server 2003 Cluster Server, only NLB is supported. Recovering inaccessible disk devices If there is a stray reservation on a disk device, the device becomes inaccessible to the host systems connected to it. This is because the strong reservation type (persistent reservations) supports load balancing in clusters.
Support for load balancing in Cluster environment
3 Load balancing Load Balancing is used to distribute I/O request across multiple paths to a logic unit for optimal usage of paths and improve I/O performance. Depending on the load balancing policy set for a logic unit, an appropriate path is selected based on the statistics over that path. The DSM currently supports the following five load balance policies.
Load balancing
4 Managing storage devices using the HP MPIO SVSP DSM with the CLI utility The command line interface utility (CLI) of HP MPIO SVSP DSM enables you to monitor and manage multipathing devices.
hpdsm devices all Syntax: hpdsm devices all The hpdsm devices all command displays the information of the device, followed by their path information as shown in the following example. If there are no devices present, the following message is displayed: No devices found. NOTE: See hpdsm set device policy for a definition of the policies. The P.B.T.L. column shows the device port, bus, target, and LUN. Example: hpdsm devices all Total No.
P.B.T.L:7.0.1.2 Path# ALB:N/A Controller Port# State 1 00000724C00373-1 Active 2 00000724C00373-5 3 HBA Slot# RTP P.B.T.L 2 00020011 3.0.0.2 Active 2 00020015 3.0.1.2 00000724C00519-3 Standby 2 00010003 3.0.2.2 4 00000724C00519-7 Standby 2 00010007 3.0.3.2 5 00000724C00373-1 Active 1 00020011 7.0.0.2 6 00000724C00373-5 Active 1 00020015 7.0.1.2 7 00000724C00519-3 Standby 1 00010003 7.0.2.2 8 00000724C00519-7 Standby 1 00010007 7.0.3.
hpdsm paths device Syntax: hpdsm paths device=x The hpdsm paths device command displays information about the paths available for device x, as shown in the following example. NOTE: • The P.B.T.L. column shows the device port, bus, target, and LUN. • The RTP column shows the target port information as defined by SCSI-3 specification. • The Controller Port# column shows the controller serial number followed by target port number.
NOTE: You cannot change the load balance policy for the devices using SCSI-2 reservations in an MSCS environment. Example: hpdsm set device=1 policy=rr Device Name: HP HSV210 Device Serial No.:600508B400101F6A000070001D950000 Change Load Balance policy (y/n)? y Load Balance policy changed. Verify by issuing “hpdsm devices” command. Example: hpdsm set device=all policy=rr Successful for all the devices. Verify by issuing "hpdsm devices" command.
hpdsm cleanup device Syntax: hpdsm cleanup device=x Syntax: hpdsm cleanup device=all The hpdsm cleanup device command allows you to clean up the failed path information for a specified device x or for all the devices, depending on the input parameters specified, as shown in the following example. Example: hpdsm cleanup device=1 Device Name:HP HSV210 Device Serial No.:600508B400101F6A000070001D950000 Cleanup the failed path information for this LUN (y/n)? y Cleanup Succeeded.
Table 4 defines the selections for the notification command string. Table 4 Notification strings Notification_ event_ number Notification string Notifies the user when DSM: HPDSM_NEW_DEVICE 1 Detects a new device. HPDSM_ADDITIONAL_PATH 2 Detects a redundant path to an existing device. HPDSM_MAX_PATH_REACHED 3 Determines that a device configuration contains the maximum number of supported paths. HPDSM_LAST_PATH_FAILURE 4 Detects that the last path to the device is removed.
• HPDSM SetDefaultLBPolicy device • HPDSM SetDefaultDsmLoadOrder device • HPDSM GetDefaultLBPolicy device • HPDSM GetDefaultDsmLoadOrder device • HPDSM ReStoreFactoryDefaults device For more information on using these commands run the hpdsm help command. For information on managing MPIO devices using Microsoft-provided interfaces on Windows Server 2008 and Windows Server 2008 R2, see the following MPIO document published by Microsoft: http://download.microsoft.
A — Software components This appendix describes the following components of HP MPIO SVSP DSM: • Drivers • User mode components Drivers The HP MPIO SVSP DSM components include the following multipath drivers: • Microsoft MPIO Framework Drivers • MPIO.SYS is the multipathing bus driver. • MPDEV.SYS is the replacement class driver. It communicates with MPIO.SYS. • MPSPFLTR.SYS is a port driver filter (HBA upper filter). • HP DSM driver • HPEVSDSM.
HP MPIO SVSP DSM command line interface (CLI) The HP MPIO SVSP DSM command line interface (HPDSM.EXE) enables you to monitor and manage HP DSMs in an MPIO environment. HP MPIO SVSP DSM performance monitoring provider The HP MPIO SVSP DSM performance monitoring provider (HpPerfProv.DLL) allows you to monitor the Input-Output (I/O) performance of a device path using the system monitor. To start the performance monitoring, complete the following steps: 1.
Example: hpprutil devices Device# Device Name SCSI Address Reservation NT Disk# 1 HP HSVX700 6.0.1.1 PR Disk1 2 HP HSVX700 6.0.0.2 PR Disk2 3 HP HSVX700 2.0.0.3 PR Disk3 4 HP HSVX700 6.0.0.4 PR Disk4 5 LOGICAL VOLUME 8.0.4.
The hpprutil help command displays help information for hpprutil.
B — Multipathing driver event log messages This appendix lists the event log messages for HP MPIO SVSP DSM drivers and provides a description of each message. The error log messages are written in the SYSTEM log file. This appendix describes the following event log messages: • MPIO.SYS event log messages • HP MPIO SVSP DSM event log messages MPIO.SYS event log messages Table 5 lists MPIO driver event log messages, an explanation of each message, and a description of the data that accompanies the message.
Event ID Message Description 20 A Path Verification request to a device on pseudo-LUN that is controlled by DSM_namehas failed. This may indicate a path failure. A call to a DSM's PathVerify routine to a pseudo-LUN has failed. This event occurs during final initialization after PathVerify has checked whether the device can be reached through a newly found path. N/A 21 The internal state of device_object is inconsistent. This indicates potential failures in this support.
Event ID 38 Message Description Contents of the data dump A device under pseudoLUN, being controlled by DSM_name was removed, but the DSM failed the operation. An MPIO call to DSM’s RemoveDevice operation failed. DSM ID of the failed attempt HP MPIO SVSP DSM event log messages Table 6 lists the HP MPIO SVSP DSM event log messages and provides a description of each message.
Event ID Message Description 112 The removal event notifications for multipath capable disk X have been enabled upon request. This event is logged when generation of removal event notifications (Event IDs 304, 302 and 108) for the multipath capable disk with serial number X has been enabled upon request in the DSM. 113 The multipath capable disk X has been disconnected from the system.
Event ID Message Description 309 The DSM cannot manage multipath capable disk X (SCSI address Y) due to an internal error. The DSM cannot manage multipath capable disk X (SCSI address Y) due to an internal error. 310 The DSM detected an inconsistency in the path (SCSI address Y) to the multipath capable disk X. This path has been marked as failed. This event is logged when DSM detects that the path with SCSI address Y is inconsistent and is moved to failed state.
— Multipathing driver event log messages
C — Troubleshooting This appendix discusses some of the common problems that you may encounter while using the HP MPIO DSM. It also describes how to troubleshoot these problems. Problem: HP MPIO DSM fails to load and displays a yellow-bang in the Device Manager screen. Solution: To troubleshoot this problem, complete one of the following: • Verify if the Multi-path I/O feature is enabled. If not, enable the Multi-path I/O feature.
Solution: Run the following commands from the command prompt pointed to the folder "C:\Program Files\Common Files\Hewlett-Packard\HP MPIO DSM\COMMON FILES\mof" and register the following mof files: • mofcomp hpwmi.mof • mofcomp HPDSMHighPerfProvider.mof • mofcomp -N:root\wmi LBPolicy.mof • mofcomp -N:root\wmi mpdisk.mof • mofcomp -N:root\wmi mpio.mof • mofcomp -N:root\wmi pdo.mof Problem: HPDSM CLI or HP MPIO DSM Manager does not display the output.
Glossary This glossary defines the terms used in this guide or related to this product. It is not a comprehensive glossary of computer terms. ALB Adaptive Load Balance (ALB) is a feature provided by the SVSP DSM that utilizes certain features supported by the array, to deliver better performance for host I/O requests. controller A hardware device that facilitates communication between a host and one or more LUNs organized as an array.
port A The relative number of an HBA. A specific port number is determined according to its order of discovery by the Windows operating system. HBA's include SCSI, Fibre Channel, and IDE adapter types. SAN Storage Area Network. A configuration of networked devices for storage. target The definition of target depends on the environment: • For parallel SCSI configurations, the target is the actual target number assigned to a device.
Index B boot from SAN, 19 C commands for managing storage arrays, 25 components, software, 33 conventions, text symbols, 7 D disk devices, inaccessible, recovering, 21 documentation HP website, 7 providing feedback, 8 drivers Multipathing bus, 33 replacement class, 33 E event log messages, 39 I inaccessible disk devices, recovering,, 21 installation, silent, 16 installing HP MPIO SVSP DSM, 12 L log, event, messages, 39 log, MPIO.
