HP MPIO Full Featured DSM for XP family of Disk Arrays 4.00.
Legal and notice information © Copyright 2005, 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 ...............................................................................................
Use case scenarios ............................................................................................................. 30 5 Managing storage arrays using the HP MPIO XP DSM with the CLI utility ................................................................................................. 31 hpdsm hpdsm hpdsm hpdsm hpdsm hpdsm hpdsm hpdsm hpdsm devices ......................................................................................................................... devices all .........
Figures 1 MPIO Properties page with MPIO-ed Devices tab enabled ............................................ 50 2 MPIO Properties page with Discover Multi-Paths tab enabled ........................................ 51 3 MPIO Properties page with DSM Install tab enabled .................................................... 52 4 Multi-Path Disk Device Properties page ...................................................................... 53 5 Multi-Path Disk Device Properties page ...............................
Tables 1 Document conventions ............................................................................................... 7 2 Snapshot of pre-installation checklist .......................................................................... 12 3 Load balancing policies ........................................................................................... 29 4 Notification strings .................................................................................................. 37 5 MPIO.
About this guide This guide provides information about HP MPIO Full Featured Device Specific Module (DSM) for XP family of Disk Arrays (called the “HP MPIO XP DSM” throughout this guide), which includes: • Installing, upgrading, and removing HP MPIO XP DSM • Support for load balancing in Microsoft Cluster Server (MSCS)/Failover Cluster environments • Managing HP MPIO XP DSM Intended audience This document is intended for customers who use the HP MPIO XP DSM software and users with knowledge of: • • • • • •
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
http://www.hp.com/go/e-updates • Subscribing to this service provides you with e-mail updates on the latest product enhancements, newer versions of drivers, and firmware documentation updates as well as instant access to other product resources. • After signing up, you can quickly locate your products by selecting Business support and then Storage under Product Category. HP websites For additional information, see the following HP websites: • • • • http://www.hp.com http://www.hp.
About this guide
1 Installing the HP MPIO Full Featured DSM for XP family of Disk Arrays HP MPIO XP 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 XP DSM. Table 2 Snapshot of pre-installation checklist Task Check the contents of the HP MPIO XP 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.
NOTE: For Microsoft Windows Server 2008 – Server Core (x86 and x64) and Microsoft Windows Server 2008 R2 – Server Core (IA64 and x64), you can run Launch.exe from the installation location, using the command prompt. Installing HP MPIO XP DSM on a clustered system To install HP MPIO XP DSM on a clustered system, complete the following steps: NOTE: On a clustered system, you must install HP MPIO XP DSM on one node at a time. Repeat this on all the nodes in a cluster. 1. 2. 3. 4.
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 XP family of Disk Arrays. 4. Select the upgrade option. 5. Follow the on-screen instructions to complete the upgrade. 6. Reboot the system.
NOTE: To recover from an unsuccessful migration, restore your system from the full backup you made before starting the migration. Migrating from Secure Path to HP MPIO XP DSM on a stand-alone system To migrate from Secure Path to HP MPIO XP DSM on a stand-alone system, complete the following steps: 1. 2. Complete the pre-installation checklist (Table 2) and procedure, see Preparing for installation. Choose one of the following options: • If your system has only XP storage arrays, remove Secure Path.
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. Using Cluster Administrator, resume the current cluster node. NOTE: Repeat steps 2–3 for all nodes in the cluster. 4. 5.
Migrating HP MPIO XP DSM from Windows Server 2003 to Windows Server 2008 To migrate HP MPIO XP 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 XP DSM 4.00.00. For more information, see Chapter 1. 3. Upgrade to Windows Server 2008. 4. Double-click the batch file (depending on your operating system): • For Windows Server 2008 x86: \x86\Win2k8Upgrade.
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 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 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 default directory for 64 bit systems, in lines 27 and 32 of the setup.iss file, replace C:\Program Files\Hewlett-Packard\HP MPIO DSM\XP DSM with C:\Program Files (x86)\Hewlett-Packard\HP MPIO DSM\XP DSM. • 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.
Creating response files for silent mode operations The installation kit contains the following response files (.iss files): new.iss, uninstall.iss and update.iss that are used to install, remove, and upgrade the software. In addition to these, you can create your own customized response files for operations such as modify or repair, by selecting or unselecting the different combination of the components. Customized response files can be created by running the setup.
Installing the HP MPIO Full Featured DSM for XP family of Disk Arrays
2 Support for load balancing in Failover Cluster Server environment for Windows Server 2008 and Windows Server 2008 R2 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.
Support for load balancing in Failover Cluster Server environment for Windows Server 2008 and Windows Server 2008 R2
3 Support for load balancing in Microsoft Cluster Server environments for Windows Server 2003 This section describes the following: • Enabling or disabling support for load balancing in MSCS environments • Recovering inaccessible disk devices By default, in HP MPIO XP DSM, load balancing is enabled in Microsoft Cluster Server (MSCS) environments. The MSCS uses SCSI-2 reservations to synchronize access to the cluster-managed devices.
NOTE: You must repeat the following procedure on all nodes in the cluster, one at a time. 1. 2. 3. 4. 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. Navigate to the HP MPIO XP DSM installation directory on the current node. Double-click the registry file (depending on your operating system).
NOTE: Once all the nodes in the cluster have the support for load balancing in MSCS enabled, you can change the load-balancing policy for the cluster devices using the HP DSM CLI or HP MPIO DSM manager. 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 Microsoft Cluster Server environments for Windows Server 2003
4 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: • 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". You can modify (enable or disable and add or remove paths) the subset setting for a given LUN through the HP DSM CLI.
5 Managing storage arrays using the HP MPIO XP DSM with the CLI utility The command line interface utility (CLI) of HP MPIO XP 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.
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.
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.
NOTE: • device=all changes the SUBSET STATE for all the devices • path=all enables or disables subset settings and adds or removes all the available paths to or from the subset • Paths in the failed state cannot be added or removed to or from the subset • hpdsm set device=x subset=remove path=all will cleanup the failed paths and disables the subset hpdsm set device path Syntax: hpdsm set device=x path=y The hpdsm set device path command changes the preferred path for device x, as shown in the following ex
Device Serial No.:50 142460C01 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. 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.
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 help Syntax: hpdsm help The hpdsm help command displays help information for the CLI.
A Software components This appendix describes the following components of HP MPIO XP DSM: • Drivers • User mode components Drivers The HP MPIO XP 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 • HPXPDSM.SYS is the HP DSM driver for XP disk arrays. It interacts with MPIO.
HP MPIO XP DSM command line interface (CLI) The HP MPIO XP DSM command line interface (HPDSM.EXE) enables you to monitor and manage HP DSMs in an MPIO environment. HP MPIO XP DSM performance monitoring provider The HP MPIO XP 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 OPEN-V 4.0.3.0 PR Disk6 2 HP OPEN-V 4.0.3.1 PR Disk7 hpprutil clear device Syntax: hpprutil clear device=x 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.
Software components
B Multipathing driver event log messages This appendix lists the event log messages for HP MPIO XP 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 XP 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 18 A Single Path Fail-Over is being attempted on pseudo-LUN. A pseudo-LUN has just one path, and DSM has requested a failover. The Path ID of the failing device 19 An operation failed on devicedue to lack of memory. Resource allocation failed during an attempted failover, and failover is not currently active. The Path ID of the failing device 20 A Path Verification request to a device on pseudoLUN that is controlled by DSM_namehas failed.
Event ID Message Description DSM_name failed to return a Path to pseudo-LUN. One of the following events occurred during failover: MPIO’s call to the DSMs InvalidatePath failed; DSM did not return a new path; DSM did not return a path when MPIO called the LBGetPath routine. N/A 33 DSM_name returned a bogus path todevice. MPIO is unable to find an operational device-path pair representation (device info) for the path that the DSM wants to use for the I/O to the device.
HP MPIO XP DSM event log messages Table 6 lists the HP MPIO XP DSM event log messages and provides a description of each message. Table 6 HP MPIO XP DSM event log messages Event ID Message Description 101 Discovered a new multipath capable disk with serial number X; first path SCSI address Y. A new multipath disk has been discovered. X represents the serial number of the new disk. Y is the SCSI address of the first path to this disk.
Event ID Message Description 303 Too many paths for disk with serial number X. Path (SCSI address Y) not added. A new path in excess of the supported number of paths for an existing multipath disk has been discovered. X represents the serial number of the disk. Y is the SCSI address of the newly found path. 304 An unrecoverable path failure occurred on SCSI address Y. Disk X is still accessible over redundant path(s). A redundant path to an existing multipath disk has failed.
Multipathing driver event log messages
C Managing MPIO devices using Microsoft-provided interfaces on Windows Server 2008 and Windows Server 2008 R2 This appendix describes how to manage MPIO devices using the Microsoft-provided interfaces on Windows Server 2008 and Windows Server 2008 R2. 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 XP family of Disk Arrays 4.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 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 .
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. nl 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.
Glossary This glossary defines the terms used in this guide or related to this product. It is not a comprehensive glossary of computer terms. controller A hardware device that facilitates communication between a host and one or more LUNs organized as an array. DSM Device Specific Module fabric A network that contains high-speed fiber connections resulting from the interconnection of switches and devices. A fabric is an active and intelligent non-shared interconnect scheme for nodes.
• Failed — Path is currently unusable for the I/O stream. 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.
Index MPIO.
