installation and reference guide HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays 3.00.
Legal and notice information © Copyright 2006--2008 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 . . . . . . . . . . . . . . . . . . . . . . . . . . Intended audience . . . . . . . Related documentation . . . . . Document conventions and symbols HP technical support . . . . . . HP-authorized reseller . . . . . Helpful web sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
hpdsm help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A Software components . . . . . . . . . . . . . . . . . . . . . . Drivers . . . . . . . . . . . . . . . . . . . . . . User mode components . . . . . . . . . . . . . . . HP MPIO DSM manager GUI . . . . . . . . . . HP MPIO EVA DSM command line interface (CLI) . . HP MPIO EVA DSM performance monitoring provider HP MPIO EVA DSM persistent reservations clear utility hpprutil devices . . . . . . . . . . . . . .
Figures 1 MPIO Properties page with MPIO-ed Devices tab enabled . . . . . . . . . . . . . . 42 . . . . . . . . . . . . . 43 3 MPIO Properties page with DSM Install tab enabled . . . . . . . . . . . . . . . . . 44 4 Multi-Path Disk Device Properties page . . . . . . . . . . . . . . . . . . . . . . . 45 5 Multi-Path Disk Device Properties page . . . . . . . . . . . . . . . . . . . . . . . 46 6 Multi-Path Disk Device Properties page . . . . . . . . . . . . . . . . . . . . . . .
Tables 1 Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Pre-installation checklist 6 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 3 Notification strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 4 MPIO.SYS event log messages . . . . . . . . . . . . . . . . . . . . . . . . . . 37 5 HP MPIO EVA DSM event log messages . . . . . . . . . . . . . . . . . . . . . . 39 6 HP DSM equivalent load balance policies 46 . . . . .
About this guide This guide provides information about HP MPIO Full Featured Device Specific Module (DSM) for EVA4x00/6x00/8x00 family of Disk Arrays (called the “HP MPIO EVA DSM” throughout this guide), including: • Installing, upgrading, and removing HP MPIO EVA DSM • Support for load balancing in Microsoft Cluster Server (MSCS)/Failover Cluster environments • Managing HP MPIO EVA DSM Intended audience This document is intended for users of HP MPIO EVA DSM and users who are experienced with the following
Document conventions and symbols Table 1 Document conventions Convention Element Medium blue text: Related documentation Cross-reference links and e-mail addresses Medium blue, underlined text (http://www.hp.
HP technical support Telephone numbers for worldwide technical support are listed on the HP support web site: http://www.hp.com/support/ Collect the following information before calling: • • • • • • Technical support registration number (if applicable) Product serial numbers Product model names and numbers Applicable error messages Operating system type and revision level Detailed, specific questions For continuous quality improvement, calls may be recorded or monitored.
About this guide
1 Installing the HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays HP MPIO Full Featured Device Specific Module (DSM) for EVA Disk Arrays (HP MPIO EVA DSM) provides multipathing support for HP StorageWorks EVA disk arrays on Windows platforms using the Microsoft Multipath Input-Output (MPIO) framework.
Table 2 Pre-installation checklist Task Check the contents of the HP MPIO EVA DSM kit and the Fibre Channel hardware to make sure nothing is missing. If you are missing any component, contact your account representative, or call the HP Customer Service hotline at (800) 354-9000.
Installing HP MPIO EVA DSM on cluster configurations To install HP MPIO EVA DSM on each member of a cluster configuration, complete the steps below: NOTE: In a cluster configuration, HP MPIO EVA DSM must be installed on one node at a time for all nodes of the cluster. 1. Complete the pre-installation checklist (Table 2) and the pre-installation procedure. 2. Using Cluster Administrator: a. Move all cluster resources owned by the current node to another node in the cluster. b. Pause the current cluster node.
NOTE: In a cluster configuration, HP MPIO EVA 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. 2. Using 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 groups containing resources managed by the current node. 3.
CAUTION: Removing multipathing software from a multipath hardware configuration can cause data loss or corruption. You must disconnect the server from the multipath storage or eliminate all but one path to that storage from the server prior to removing the HP MPIO EVA DSM. To remove HP MPIO EVA DSM, complete the steps below: 1. Back up all user data on multipath storage. 2. If possible, disconnect the storage from the server.
:\MPInstall\setup.exe /s /f1"C:\setup.iss" /f2"C:\MPSInstallLog.txt" The refers to the drive which contains the installation media. The setup.iss is the response file from which information is taken for silent installation. The MPSInstallLog.txt file records information about the silent installation. The ResponseResult section of the MPSInstallLog.txt log file displays the result code, indicating whether or not the silent installation succeeded.
• To install into the user specified directory for both 32 and 64 bit systems, in lines 27 and 32 of the setup.iss file, replace szDir = with szDir = . 4. Choose one of the following options: • To install the Microsoft MPIO Framework component along with the DSM component, use the renamed default setup.iss file. • To install only the DSM component (when the Microsoft MPIO Framework already exists on your system), edit the renamed default setup.iss file as follows: a.
1. At the command prompt, type the following command: setup.exe /r, where /r option enables the record mode. 2. This will result in the GUI installation to run in the record mode. Select the responses in each screen and run through the installation. NOTE: When selecting the response on each screen, do not click the BACK button, and modify the selection. The response file will have to be generated again in such a case. 3. The response file is created at the following location: %WINDDIR%\setup.
2 Support for load balancing in Failover Cluster Server environment for Windows Server 2008 The load balancing for the cluster devices is enabled by default and cannot be turned OFF. • Recovering inaccessible disk devices 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 Failover Cluster Server environment for Windows Server 2008
3 Support for load balancing in Microsoft Cluster Server environment for Windows Server 2003 This section describes the following: • Enabling support for load balancing in MSCS environments • Disabling support for load balancing in MSCS environments • Recovering inaccessible disk devices By default, HP MPIO EVA DSM supports the No Load Balancing policy in Microsoft Cluster Server (MSCS) environments. This is because MSCS uses SCSI-2 reservations to synchronize access to the cluster-managed devices.
1. If MSCS is installed on your system, move all cluster resources owned by the current node to another node in the cluster. If this is not applicable, proceed to step 2. 2. Navigate to the HP MPIO EVA DSM installation directory on the current node using Windows Explorer. 3. Double-click the registry file (depending upon the operating system you are using): • For Windows Server 2003 (32-bit): \x86\hpeaadsm_pr_on.reg • For Windows Server 2003 (IA64): \IA64\hpeaadsm_pr_on.
NOTE: The refers to the folder which you have selected during the HP MPIO EVA DSM installation. The default installation directory is %ProgramFiles%\Hewlett-Packard\HP MPIO DSM\EVA DSM. 4. Follow the on-screen instructions. 5. Reboot the system for the new registry parameter to take effect.
Support for load balancing in Microsoft Cluster Server environment for Windows Server 2003
4 Adaptive Load balance The HP MPIO EVA DSM implements array specific load balancing algorithms that utilizes certain features supported by the disk arrays, to deliver better performance for host I/O requests. The Adaptive Load Balance (ALB) setting is supported on a per logical unit basis and works in conjunction with the load balancing policies supported by the DSM, which includes Round Robin, Shortest Queue Requests, Shortest Queue Bytes, and Shortest Queue Service Time.
Adaptive Load balance
5 Managing storage arrays using the HP MPIO EVA DSM with the CLI utility The command line interface utility (CLI) of HP MPIO EVA DSM enables you to monitor and manage multipathing devices.
hpdsm devices all Syntax: hpdsm devices all The hpdsm devices all command displays information of the device, followed by their path information as shown in the following example. If there are no devices, 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 Device# Device Name Serial No. Active Paths Policy Disk# P.B.T.
hpdsm paths device=1 Path# Controller Port# State HBA Slot# RTP P.B.T.L 1 P8398DXAAQQ013-4 Active 4 00020008 2.0.2.1 2 P8398DXAAQQ013-3 Active 4 00020007 2.0.5.1 3 P8398DXAAQQ010-1 Active 4 00010001 2.0.6.1 4 P8398DXAAQQ010-1 Active 4 00010001 3.0.0.1 5 P8398DXAAQQ013-3 Active 4 00020007 3.0.1.1 6 P8398DXAAQQ013-4 Active 4 00020008 3.0.2.1 7 P8398DXAAQQ010-1 Active 3 00010001 4.0.0.1 8 P8398DXAAQQ013-4 Active 3 00020008 4.0.1.
hpdsm set device alb Syntax: hpdsm set device=x alb=y/n Syntax: hpdsm set device=all alb=y/n The hpdsm set device alb command changes the Adaptive Load Balance setting for the device x or for all the devices, depending on the input parameter specified. Example: hpdsm set device=1 alb=y Device Name : HP HSV210 Device Serial No. : 600508B400101F6A000070001D950000 Change Adaptive Load Balance setting (y/n)? ALB settings changed. y Verify by using "hpdsm devices" command.
hpdsm cleanup device=1 Device Name : HP HSV210 Device Serial No. : 600508B400101F6A000070001D950000 Cleanup the failed path information for this LUN (y/n)? Cleanup Succeeded. y Verify by issuing "hpdsm devices" command. Example: hpdsm cleanup device=all Successful for all the devices. Verify by issuing "hpdsm devices" command. hpdsm notify Syntax: hpdsm notify event=notification_event_number time=number_of_minutes The hpdsm notify command defines user notification of events.
Example: HPDSM NOTIFY EVENT=7 TIME=5 Received HPDSM_PATH_FAILOVER : 600508B400101F6A000070001D950000;(4.0.0.1);from hpeaadsm Received HPDSM_PATH_FAILOVER : 600508B400101F6A000070001D9B0000;(4.0.0.2);from hpeaadsm Received HPDSM_PATH_FAILOVER : 600508B400101F6A000070001DA10000;(4.0.0.3);from hpeaadsm Received HPDSM_PATH_FAILOVER : 600508B400101F6A000070001E160000;(4.0.0.4);from hpeaadsm Received HPDSM_PATH_FAILOVER : 600508B400101F6A000070001E1C0000;(4.0.0.
A Software components This appendix describes the following components of HP MPIO EVA DSM: • Drivers • User mode components Drivers The HP MPIO EVA 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 • HPEAADSM.SYS is the HP DSM driver for EVA disk arrays.
HP MPIO EVA DSM performance monitoring provider The HP MPIO EVA DSM performance monitoring provider (HpPerfProv.DLL) helps you monitor the Input/Output (I/O) performance of a device path using the system monitor. To start the performance monitoring, complete the steps below: 1. Select Start > Programs > Hewlett-Packard > EVA DSM > Path Performance. Alternatively, you can select Start > Run and execute the command perfmon /wmi. 2.
Syntax: hpprutil clear device=m n The hpprutil clear device command clears the reservation present on device x, or clears the reservation present on devices starting from m to n (both inclusive), depending on the input parameter specified. Example: hpprutil clear device=1 The requested operation is in progress. Please wait. HPPRUTIL will attempt to clear the reservation on device 1. Are you sure you want to continue (y/n)? y Attempting to clear the reservation on device 1... reservation on device.
Software components
B Multipathing driver event log messages This appendix lists the event log messages for HP MPIO EVA DSM drivers and provides a description of each message. The error log messages are written in the SYSTEM log file. This appendix provides information about the following event log messages: • MPIO.SYS event log messages • HP MPIO EVA DSM event log messages MPIO.
Event ID Message Description Contents of the data dump 20 A Path Verification request to a device on pseudo-LUN that is controlled by DSM_name has 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 Message Description Contents of the data dump 37 DSM_name is attempting an operation on pseudo-LUN. The Type is noted in the dump data. DSM_name has called DSMNotification on a pseudo-LUN. The type of notification called by DSM 38 A device under pseudo-LUN, being controlled by DSM_name was removed, but the DSM failed the operation. An MPIO call to DSM’s RemoveDevice operation failed.
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.
C Managing MPIO devices using Microsoft-provided interfaces on Windows Server 2008 This appendix describes how to manage MPIO devices using the Microsoft-provided interfaces on Windows Server 2008. Beginning with Microsoft Windows Server 2008, Multipath I/O (earlier called MPIO framework) is provided as an operating system feature. Along with the feature, a few interfaces are provided to enable you to manage the MPIO framework and devices.
Figure 1 MPIO Properties page with MPIO-ed Devices tab enabled To manually add support for new devices, complete the following steps: 1. Click Add in the MPIO Properties page. The Add MPIO Support page displays. 2. Enter the Vendor ID and Product ID for the new devices. All devices with Device Hardware IDs are handled by a DSM (either a vendor-supplied DSM or MS DSM). To manually disable support for a device, select a Device Hardware ID and click Remove.
Figure 2 MPIO Properties page with Discover Multi-Paths tab enabled To enable multipath support for the listed devices, select a Device Hardware ID, and click Add. All devices with this hardware ID are handled by a DSM (either a vendor-supplied DSM or MS DSM). DSM Install In the MPIO Properties page, click the DSM Install tab. This tab enables you to install a vendor-supplied DSM. While installing a DSM, you must specify the driver path, the INF file name, and the DSM Hardware ID.
Figure 3 MPIO Properties page with DSM Install tab enabled NOTE: If the vendor-supplied DSM and MS DSM exist on the same system, the vendor-supplied DSM is always given priority. Managing multipath disk devices Microsoft provides a generic user interface to manage the disk devices that are controlled by MPIO. This interface, which can be accessed through the Multi-Path Disk Device Properties page, under the MPIO tab, enables you to perform basic disk and path management.
Figure 4 Multi-Path Disk Device Properties page 3. Select the MPIO tab. The Properties page displays all information about the selected device (such as Load Balance Policy, DSM Name, number of paths, and path-related information). You can modify the Load Balance Policy of the device by selecting the appropriate policy from the drop-down menu. Figure 5 displays the load balancing policies for HP DSM. HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays 3.00.
Figure 5 Multi-Path Disk Device Properties page NOTE: • HP DSM does not support all the load balance policies listed in the drop-down menu. • The names of the load balance policies as listed in the drop-down menu may differ from that used by the HP DSM CLI and HP MPIO DSM Manager. Table 6 lists the HP DSM equivalent load balance policies.
Figure 6 Multi-Path Disk Device Properties page 5. Modify the MPIO Timer Counters associated with DSM, if required, and click OK. NOTE: Modifying the timer counters for the DSM may result in unexpected system behavior. HP recommends that you do not modify these counters before consulting the HP Service personnel. 6. To change the path state, select the path and click Edit. The MPIO Path Details page for the path displays. Figure 7 shows the MPIO Path Details page. 7.
Figure 7 MPIO Path Details page 48 Managing MPIO devices using Microsoft-provided interfaces on Windows Server 2008
D 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.
Troubleshooting
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 EVA 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. state An attribute that describes the current operational condition of an object. The possible states include: • Good: The multipathing device can be accessed on at least one path.
Index B M C R D S boot from SAN setting up, 18 MPDEV.SYS, 33 MPIO.
