HP MPIO Full Featured DSM for P6x00 family of Disk Arrays 4.04.00 Installation and Reference Guide Abstract This document provides information about managing, installing, upgrading, and removing HP MPIO Full Featured Device Specific Module (DSM) for P6x00 family of Disk Arrays (called the HP MPIO EVA DSM throughout this document). This document also includes information on support for load balancing in Microsoft Cluster Server (MSCS)/Failover Cluster environments.
© Copyright 2014 Hewlett-Packard Development Company, L.P. Acknowledgments 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 1 Installing the HP MPIO Full Featured DSM for P6x00 family of Disk Arrays.........5 Preparing for installation............................................................................................................5 Installing HP MPIO EVA DSM.....................................................................................................6 Installing HP MPIO EVA DSM on a stand-alone system..............................................................
hpprutil clear device......................................................................................................25 hpprutil help.................................................................................................................25 B Multipathing driver event log messages.......................................................26 MPIO.SYS event log messages..................................................................................................
1 Installing the HP MPIO Full Featured DSM for P6x00 family of Disk Arrays HP MPIO EVA DSM provides multipathing support for HP StorageWorks disk arrays on Windows platforms using the Microsoft Multipath Input-Output (MPIO) framework.
Table 1 Snapshot of pre-installation checklist Task Check the contents of the HP MPIO EVA DSM kit and the Fibre Channel hardware to ensure nothing is missing. If you are missing any component, contact your account representative, or call the HP Customer Service hotline at (800) 354-9000.
3. 4. Install HP MPIO EVA DSM on the current node by following the steps 2–7 from the procedure provided for “Installing HP MPIO EVA DSM on a stand-alone system”. Using Cluster Administrator, resume the current cluster node. NOTE: 5. Repeat steps 2–4 for all the nodes in a cluster. Using Cluster Administrator: a. Restore failback for all the groups containing resources as needed. b. Redistribute cluster resources as desired.
Removing HP MPIO EVA DSM To remove HP MPIO EVA DSM, you must re-configure the SAN and reboot your system. 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 following steps: 1. Back up all user data on multipath storage. 2.
Following is the list of common return values along with their descriptions in the ResultCode key. Result Code Description 0 Success –1 General error –3 Required data not found in the setup.iss file –4 Not enough memory available –5 File does not exist –6 Cannot write to the response file –7 Unable to write to the log file –8 Invalid path to the InstallShield Silent response (.
4. If you want to avoid the automatic reboot feature, edit the setup.iss file as follows: a. In line 50, replace Result=6 with Result=1. b. In line 51, replace BootOption=3 with BootOption=0. Upgrading HP MPIO EVA DSM To upgrade from a previous version of HP MPIO EVA DSM to the current version, complete the following steps: 1. Make a copy of the setup.iss file in the installation location with the name setup.iss. 2. Choose one of the following options: a.
Setting up boot from SAN You can set up HP MPIO EVA 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.
2 Support for load balancing in Failover Cluster Server environment for Windows Server 2012 Load balancing for the cluster devices is enabled by default and cannot be turned OFF. This section describes the following: • “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.
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.
NOTE: • All devices that are part of the logical unit group, have the same subset setting. • The subset setting is not applicable for devices that have the No Load Balancing policy enabled. • The subset setting for a given LUN is persistent across Load Balance policies and host system reboots. • The paths that are part of the subset are reported as "Active" and other paths are reported as "Available".
4 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.
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.
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. • The HBA Slot # is displayed as "0" for iSCSI devices. hpdsm paths device=1 Path# Controller State State HBA Slot# RTP P.B.T.L 1 P8398DXAAQQ013-4 Active 4 00020008 3.0.2.3 2 P898DXAAQQO101U-2 Active 4 00020007 2.0.5.
Example: hpdsm set device=1 subset=add path=all Device Name:HP HSV210 Device Serial No.:600508B400101F6A000070001D950000 Change Subset setting (y/n)? y Subset setting changed. Verify by using "hpdsm devices" command. Example: hpdsm set device=all subset=remove path=1 Successful for all the devices. Verify by using "hpdsm devices" command.
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. Verify by issuing "hpdsm devices" command. Example: hpdsm cleanup device=all Successful for all the devices.
HPDSM NOTIFY EVENT=7 TIME=5 TIME:7/4/2008,15:20:08:13) Received HPDSM_PATH_FAILOVER:600508B400101F6A000070001D950000;from hpeaadsm (TIME:7/4/2008,15:20:08:42) Received HPDSM_PATH_FAILOVER:600508B400101F6A000070001D9B0000;from hpeaadsm (TIME:7/4/2008,15:20:08:65) Received HPDSM_PATH_FAILOVER:600508B400101F6A000070001DA10000;from hpeaadsm (TIME:7/4/2008,15:20:08:88) Received HPDSM_PATH_FAILOVER:600508B400101F6A000070001E160000;from hpeaadsm (TIME:7/4/2008,15:20:08:114) Received HPDSM_DEVICE_REMOVAL:600508B400
Commands to manage the HP EVA DSM parameters Following are some of the commands to manage the HP EVA DSM parameters: • HPDSM SetDefaultLBPolicy device • HPDSM SetDefaultALBSetting device • HPDSM SetDefaultDsmLoadOrder device • HPDSM SetDefaultUsePR device • HPDSM GetDefaultLBPolicy device • HPDSM GetDefaultALBSetting device • HPDSM GetDefaultDsmLoadOrder device • HPDSM GetDefaultUsePR device • HPDSM ReStoreFactoryDefaults device NOTE: HPDSM SetDefaultUsePR device and HPDSM GetDefaultUsePR
5 Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.com/support Before contacting HP, collect the following information: • Product model names and numbers • Technical support registration number (if applicable) • Product serial numbers • Error messages • Operating system type and revision level • Detailed questions For continuous quality improvement, calls may be recorded or monitored.
Product Feedback To make comments and suggestions about HP MPIO Full Featured DSM for P6x00 family of Disk Arrays 4.04.00, send an email to multipathfeedack@hp.com. Document conventions and symbols Table 4 Document conventions Column Head Column Head Blue text:“Table 4” Cross-reference links and e-mail addresses Blue, underlined text:http://www.hp.com Website addresses Bold text • Keys that are pressed. • Text typed into a GUI element, such as a box.
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.
Drivers 23 run this utility either on a system that has HP MPIO EVA DSM installed or on a system where HP MPIO EVA DSM is not installed. To run this utility on a system where the HP MPIO EVA DSM is installed, complete the following steps: 1. Open the command prompt with administrative privileges and change the path to C:\Program Files (x86)\Hewlett-Packard\HP MPIO DSM\P6000 DSM\amd64. 2. Enter the command hpprutil /?at the command prompt to display the instructions for using this utility.
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 describes the following event log messages: • “MPIO.SYS event log messages” • “HP MPIO EVA DSM event log messages” MPIO.
Table 5 MPIO.SYS event log messages (continued) Event ID Message Description Contents of the data dump 22 A fail-over on pseudo-LUN was A failover attempt on a attempted, however the attempt pseudo-LUN has failed. This failed. The devices will be removed. indicates that the DSM did not return a valid path after the call to InvalidatePath. 23 All paths have failed. Pseudo-LUN will be removed.
Table 5 MPIO.SYS event log messages (continued) 28 Event ID Message Description 40 Device instance DSM_name of pseudo-LUN was rejected because the maximum transfer length of the underlying adapter is too low. The device will be accepted after a reboot. This message can occur in a N/A heterogeneous HBA environment if one HBA’s maximum transfer length is smaller than any other HBA’s maximum transfer length.
Table 5 MPIO.SYS event log messages (continued) Event ID Message Description Contents of the data dump 45 DSM_name attempted an operation This is a periodic version of Event The Type is noted in the dump data. on pseudo-LUN. This has occurred ID = 37. If a particular DSM ‘n’ times in the past ‘m’ seconds. notification type occurs too frequently, you may see this event being logged periodically for all instances of that DSM notification.
Table 6 HP MPIO EVA DSM event log messages (continued) Event ID 30 Message Description 114 The multipath capable disk X has been This event is logged when the last path to a multipath capable disk with serial number X (for which the dis connected from the system. generation of removal event notifications have been disabled) is disconnected from the system. 301 The DSM failed to initialize during startup. 302 An unrecoverable path failure occurred All paths to an existing multipath disk have failed.
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.
1. 2. Go to Device Manager>Disk drives. Right-click and select Scan for hardware changes. Problem: The vendor specific load balance policy (Shortest Queue Service Time) may not be displayed in the MPIO property sheet. Solution: Use HP DSM CLI or HP MPIO DSM Manager to set the vendor specific load balance policy.
Glossary This glossary defines terms used in this guide or related to this product and 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.
state target topology 34 Glossary 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. • Degraded — One or more paths are failed to the storage unit. The definition of target depends on the environment: • For parallel SCSI configurations, the target is the actual target number assigned to a device.
Index I T Installing the HP MPIO, 5 Installing HP MPIO EVA DSM, 6 Installing HP MPIO EVA DSM on a clustered system, 6 Installing HP MPIO EVA DSM on a stand-alone system, 6 Preparing for installation, 5 Removing HP MPIO EVA DSM, 8 Setting up boot from SAN, 11 Upgrading HP MPIO EVA DSM, 7 Upgrading HP MPIO EVA DSM on a clustered system, 7 Upgrading HP MPIO EVA DSM on a stand-alone system, 7 Using silent installation, 8 Creating response files for silent mode operations, 10 Installing HP MPIO EVA DSM, 9 Remo
