installation and reference guide HP MPIO Full Featured DSM for EVA3000/ 5000 VCS 4.xxx Disk Arrays 3.02.
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 ...............................................................................................
5 Managing storage arrays using the HP MPIO EVA DSM with the CLI utility ................................................................................................. 31 hpdsm hpdsm hpdsm hpdsm hpdsm hpdsm hpdsm hpdsm hpdsm hpdsm devices ......................................................................................................................... devices all ..................................................................................................................... paths device ....
Figures 1 MPIO Properties page with MPIO-ed Devices tab enabled ............................................ 52 2 MPIO Properties page with Discover Multi-Paths tab enabled ........................................ 53 3 MPIO Properties page with DSM Install tab enabled .................................................... 54 4 Multi-Path Disk Device Properties page ...................................................................... 55 5 Multi-Path Disk Device Properties page ...............................
Tables 1 Document conventions ............................................................................................... 7 2 Snapshot of pre-installation checklist .......................................................................... 12 3 Load balancing policies ........................................................................................... 27 4 Notification strings ..................................................................................................
About this guide This guide provides information about HP MPIO Full Featured Device Specific Module (DSM) for EVA3000/5000 VCS 4.
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-authorized reseller Your nearest HP-authorized reseller: • In the United States, call 1-800-282-6672.
About this guide
1 Installing the HP MPIO Full Featured DSM for EVA3000/5000 VCS 4.xxx 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 2 lists the information you need before installing the HP MPIO EVA DSM. Table 2 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. Obtain and review the most current versions of the following documents: • HP MPIO Full Featured DSM for EVA3000/5000 VCS 4.
Installing HP MPIO EVA DSM on a clustered system To install HP MPIO EVA DSM on a clustered system, complete the following steps: NOTE: On a clustered system, you must install HP MPIO EVA DSM on one node at a time. Repeat this on all the nodes in a cluster. 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.
5. Follow the on-screen instructions to complete the upgrade. 6. Restart the system. Upgrading HP MPIO EVA DSM on a clustered system To upgrade HP MPIO EVA DSM from a previous version to the current version on a clustered system, complete the following steps: NOTE: On a clustered system, HP MPIO EVA DSM must be upgraded on one node at a time for all nodes in the cluster. 1. 2. 3. 4. Complete the pre-installation checklist (Table 2) and the pre-installation procedure, see Preparing for installation.
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, go to the installation location from the command prompt and run Launch.exe. Select Remove > Remove allinstalled components, to remove HP MPIO EVA DSM. Using silent installation You can execute the silent installation from the installation location on your computer or from a network drive. It installs the HP MPIO EVA DSM with little intervention.
–6 Cannot write to the response file –7 Unable to write to the log file –8 Invalid path to the InstallShield Silent response (.iss) file –51 Cannot create the specified folder –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).
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: • To upgrade the Microsoft MPIO Framework component along with the DSM component, use the renamed default setup.iss file.
NOTE: When selecting the response on each screen, do not click BACK and modify the selection. In such a case, the response file needs to be generated again. Use this setup.iss file to perform the same silent mode operation on multiple systems across the same platform. 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.
Installing the HP MPIO Full Featured DSM for EVA3000/5000 VCS 4.
2 Support for load balancing in Failover Cluster Server environment for Windows Server 2008 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
3 Support for load balancing in Microsoft Cluster Server environments 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, in HP MPIO EVA 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. 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.
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\hpegldsm_pr_off.reg • For Windows Server 2003 (IA64): \IA64\hpegldsm_pr_off.reg • For Windows Server 2003 x64 Edition: \AMD64\hpegldsm_pr_off.
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: • 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".
NOTE: • All devices that are part of the Logical Unit Group, has the same ALB setting. • The ALB setting is not applicable for devices that have the No Load Balancing policy enabled. • The ALB setting for a given LUN is persistent across host system reboots. You can modify (enable or disable) the ALB setting for a given LUN either through the HP MPIO DSM Manager or HP DSM CLI. For more information, see Chapter 5. HP MPIO Full Featured DSM for EVA3000/5000 VCS 4.xxx Disk Arrays 3.02.
Load balancing
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.
2 COMPAQ HSV111_(C) COMPAQ 600508B4000149B50002800000230000 8 SQST— Subset Disk 2 5.0.4.2 N 3 COMPAQ HSV111_(C) COMPAQ 600508B4000149B50002800000290000 8 NLB Disk 3 5.0.0.3 N 4 COMPAQ HSV111_(C) COMPAQ 600508B4000149B500028000002F0000 8 NLB Disk 4 5.0.3.4 Y 5 COMPAQ HSV111_(C) COMPAQ 600508B4000149B50002800000350000 8 SQB Disk 5 5.0.3.5 N 6 COMPAQ HSV111_(C) COMPAQ 600508B4000149B500028000003B0000 8 SQB Disk 6 3.0.3.
Controller Port# Path# State HBA Slot# RTP P.B.T.L 1 P4889B59IM500PActive 1 7 00010002 3.0.2.3 2 P4889B59IM5024Available 1 6 00010002 4.0.2.3 * Device#:2 Device Name:COMPAQ HSV111_(C)COMPAQ Serial No:6005008B400101F600018000 Active Paths: 2 Policy:SQST-Subset Disk 2 P.B.T.L:3.0.2.4 ALB:N Path# Controller Port# State 1 P4889B59IM500P-1 Active 2 P4889B59IM5024-1 Available HBA Slot# RTP P.B.T.L 7 00010002 3.0.2.4 6 00010002 4.0.2.
3 P4889B59IM5024-1 Active 4 00020003 5.0.3.1 4 P4889B59IM5024-2 Active 4 00020004 5.0.4.1 5 P4889B59IM5024-2 Available 4 00020004 3.0.1.1 6 P4889B59IM501F-2 Available 4 00010002 3.0.3.1 7 P4889B59IM5024-1 Available 4 00020003 3.0.4.1 8 P4889B59IM501F-1 Available 4 00010001 3.0.6.
Syntax: hpdsm set device=x subset=add/remove path=y,z Syntax: hpdsm set device=all subset=add/remove path=all Syntax: hpdsm set device=all subset=add/remove path=y,z The hpdsm set device=x subset=add/remove path=y,z command enables or disables subset setting for device x and adds or removes y,z to or from the subset, as shown in the following example: Example: hpdsm set device=1 subset=add path=all Device Name:COMPAQ HSV111_(C)COMPAQ Device Serial No.
Device Serial No.:600508B4000149B500028000001D0000 Change Adaptive Load Balance setting (y/n)? y ALB settings changed. Verify by using "hpdsm devices" command. Example: hpdsm set device=all alb=y Successful for all the devices. Verify by using "hpdsm devices" command. 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 example.
hpdsm cleanup device=1 Device Name:COMPAQ HSV111_(C)COMPAQ Device Serial No.:600508B4000149B500028000001D0000 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 NOTIFY EVENT=7 TIME=5 (TIME:7/4/2008,15:20:08:13) nl Received HPDSM_PATH_FAILOVER:600508B4000149B500028000004D0000;from hpegldsm (TIME:7/4/2008,15:20:08:42) nl Received HPDSM_PATH_FAILOVER:600508B4000149B50002800000470000;from hpegldsm (TIME:7/4/2008,15:20:08:65) nl Received HPDSM_PATH_FAILOVER:600508B4000149B50002800000410000;from hpegldsm (TIME:7/4/2008,15:20:08:88) nl Received HPDSM_PATH_FAILOVER:600508B4000149B500028000003B0000;from hpegldsm (TIME:7/4/2008,15:20:08:103) nl Received HPDSM_ADDI
Managing storage arrays using the HP MPIO EVA DSM with the CLI utility
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 • HPEGLDSM.SYS is the HP DSM driver for EVA disk arrays.
NOTE: To manage HP MPIO EVA DSM 3.02.00 and later, use HP MPIO DSM Manager 3.00.00 or later. Table 5 HP MPIO DSM manager GUI files File Description SecurePathMgr.dll This is the Microsoft Management Console snap-in DLL used to manage the HP DSMs. VolInfoDLL.dll Gathers information about the drive letter, mount points, and volume labels from the system. SpWmiInfo.dll Handles the communication with the HP DSMs using WMI interfaces. SpNotifier.dll Used by the SpMonitor.
CAUTION: Using this utility incorrectly may result in loss of data and/or incorrect operation of MSCS/Failover Cluster. HP shall not be liable for problems resulting from the incorrect use of this utility or for solving them. The persistent reservations clear utility is located on the HP MPIO EVA DSM installation media, and gets copied to the HP MPIO EVA DSM installation directory during the installation.
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... Successfully cleared the reservation on device. hpprutil clear device=1 2 The requested operation is in progress. Please wait. HPPRUTIL will attempt to clear the reservation on device 1 to 2. Are you sure you want to continue (y/n)? y Attempting to clear the reservation on device 1...
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.SYS event log messages Table 6 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 310 Message Description 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. X represents the serial number of the disk. A reboot of the system is recommended to overcome this inconsistent state. HP MPIO Full Featured DSM for EVA3000/5000 VCS 4.xxx Disk Arrays 3.02.
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 EVA3000/5000 VCS 4.xxx Disk Arrays 3.02.
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 8 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 58 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.
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.
• Available — Path is currently available, but not used for device access. The path is only in this state when no load balancing policy has been selected for the LUN. • Standby — Intermediate state of the path before it is initialized (made ready for device access), normally will not be seen. • 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.
Index P B boot from SAN, 19 C commands for managing storage arrays, 31 components, software, 41 conventions, text symbols, 7 D performance monitoring provider, 42 persistent reservation clear utility, 42 pre-installation, 11 R recovering inaccessible disk devices, 21, 25 related documentation, 7 removing HP MPIO EVA DSM, 15 disk devices, inaccessible, recovering, 21, 25 documentation HP website, 7 drivers Multipathing bus, 41 replacement class, 41 S E T silent installation, 16 software components,
