installation and reference guide HP MPIO Full Featured DSM for SAN Virtualization Services Platform 3.01.
Legal and notice information © Copyright 2006, 2009 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 ...............................................................................................
A Software components ....................................................................... 33 Drivers .................................................................................................................................... User mode components ............................................................................................................. HP MPIO DSM manager GUI ..............................................................................................
Figures 1 MPIO Properties page with MPIO-ed Devices tab enabled ............................................ 44 2 MPIO Properties page with Discover Multi-Paths tab enabled ........................................ 45 3 MPIO Properties page with DSM Install tab enabled .................................................... 46 4 Multi-Path Disk Device Properties page ...................................................................... 47 5 Multi-Path Disk Device Properties page ...............................
Tables 1 Document conventions ............................................................................................... 7 2 Snapshot of pre-installation checklist .......................................................................... 12 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 users with knowl
Convention Element • Key that are pressed Bold text Italic text • Text typed into a GUI element, such as a box • GUI elements that are clicked or selected, such as menu and list items, buttons, tabs, and check boxes Text emphasis • 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
HP websites For additional information, see the following HP websites: • • • • http://www.hp.com http://www.hp.com/go/storage http://www.hp.com/support/manuals http://www.hp.com/support/downloads HP MPIO Full Featured DSM for SAN Virtualization Services Platform 3.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.
Table 2 lists the information you need before installing the HP MPIO SVSP DSM. Table 2 Snapshot of pre-installation checklist Task Check the contents of the HP MPIO SVSP 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.
Installing HP MPIO SVSP DSM on a clustered system To install HP MPIO SVSP DSM on a clustered system, complete the following steps: NOTE: On a clustered system, you must install HP MPIO SVSP DSM on one node at a time. Repeat this on all the nodes in a cluster. Ensure that the system sees the paths from both the SVSP Data Path Modules. 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.
Upgrading HP MPIO SVSP DSM on a stand-alone system To upgrade HP MPIO SVSP DSM from a previous version on a stand-alone system, complete the following steps: 1. Complete the pre-installation checklist (Table 2) and the pre-installation procedure, see Preparing for installation. 2. Run Launch.exe from the installation location. 3. In the launch window, click Install HP MPIO Full Featured DSM for SAN Virtualization Services Platform. 4. Select the upgrade option. 5.
NOTE: After the upgrade, reboot the host and present back all the SVSP devices. Migrating HP MPIO SVSP DSM from Windows Server 2003 to Windows Server 2008 To migrate HP MPIO SVSP DSM from Windows Server 2003 to Windows Server 2008, complete the following steps: 1. Back up all user data. 2. Install or upgrade to HP MPIO SVSP DSM 3.01.00. For more information, see Chapter 1. 3. Upgrade to Windows Server 2008. 4.
2. If possible, disconnect the storage from the server. If it is necessary to maintain single-path connections from the server to the storage (as in the case of servers that boot from a SAN device), use the following guidelines: • If it is a one-host or one-storage array, HP recommends removing redundant cable connections. • If the storage continues to be accessed by multiple paths, use switch zoning to establish single path connection. NOTE: Ensure you perform steps 1 and 2 before proceeding further. 3.
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 resultant code, indicating whether or not the silent installation succeeded. An integer value is assigned to the ResultCode keyname in the ResponseResult section.
• 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 = . 3. 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: 4.
you can create your own customized response files for operations such as modify or repair, by selecting or deselecting the different combination of the components. Customized response files can be created by running the setup.exe in the record mode on one of the systems. This response file can then be used to perform the same silent mode operation across multiple systems. To create the response file, complete the following steps: 1. 2. At the command prompt, type the following command: setup.
Installing the HP MPIO Full Featured DSM for SAN Virtualization Services Platform
2 Support for load balancing in Microsoft Windows Server 2008 Failover Cluster/Microsoft Windows 2003 Cluster Server In Windows Server 2008 Failover Cluster, loading balancing is supported and enabled by default and cannot be turned off. In Windows Server 2003 Cluster Server, only NLB is supported.
Support for load balancing in Microsoft Windows Server 2008 Failover Cluster/Microsoft Windows 2003 Cluster Server
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 string Notification_ event_ number 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 NOTIFY EVENT=7 TIME=5 (TIME:9/22/2008,21:3:46:793); nl Received HPDSM_LB_POLICY_CHANGED : 600A0B80001111550000043AE3D6D548;from (TIME:9/22/2008,21:4:4:683); hpevsdsm nl Received HPDSM_PREF_PATH_CHANGED : 600A0B80001111550000F0C9E3D6D548;from (TIME:9/22/2008,21:4:28:980); hpevsdsm nl Received HPDSM_LB_POLICY_CHANGED : 600A0B80001111550000043AE3D6D548;from (TIME:9/22/2008,21:5:9:152); hpevsdsm nl Received HPDSM_PATH_FAILOVER : 600A0B80001111550000043AE3D6D548;(2.0.0.
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_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 111 The removal event notifications for multipath capable disk X have been disabled 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 disabled upon request in the DSM. 112 The removal event notifications for multipath capable disk X have been enabled upon request.
Event ID Message Description 308 An unrecoverable failure has occurred on multipath capable disk X. The data on this disk may be inaccessible. This event is logged when the DSM detects an unrecoverable failure of a multipath capable disk. Although the disk may be visible to the system, the data on the disk may not be accessible. Please check the status of the multipath capable disk at the array end. X represents the serial number of the disk.
Multipathing driver event log messages
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.
MPIO-ed Devices When initiated, the MPIO Properties page defaults to the MPIO-ed Devices tab. This tab displays the Device Hardware IDs of the devices that support multipathing and are currently managed by MPIO. Figure 1 shows the MPIO Properties page with the MPIO-ed Devices tab enabled. Figure 1 MPIO Properties page with MPIO-ed Devices tab enabled To manually add support for new devices, complete the following steps: 1. 2. Click Add in the MPIO Properties page. The Add MPIO Support page displays.
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 dropdown menu. Figure 5 displays the load balancing policies for HP DSM. HP MPIO Full Featured DSM for SAN Virtualization Services Platform 3.01.
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 7 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. 7. 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.
Figure 7 MPIO Path Details page 50 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.
• 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. 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.
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 R 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 drivers Multipathing bus, 33 replacement class, 33 recovering inaccessible disk devices, 21 related documentation, 7 removing HP MPIO SVSP DSM, 15 S silent installation, 16 software components, 33 Subscriber's Choice, HP, 8 symbols in text, 7 T technical support service locator website, 9 text symbols, 7 U
