HP MPIO Installation And Reference Manual

Download

installation and reference guide HP MPIO Full Featured DSM for

EVA4x00/6x00/8x00 family of Disk Array s 3.00.00

Part number: AA-RW7SJ-TE

irst edition: February 2008

Legal and notice information

Conﬁdential 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. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as c onstituting an additional warranty. H P shall not be liable for technical or editorial errors or omissions contained herein.

Microsoft, Windows, Windows Server 2003, and Windows Server 2008 are U.S. registered trademarks of Microsoft Corporation.

Contents

Aboutthisguide .......................... 7

Intendedaudience...................................... 7

Relateddocumentation.................................... 7

Documentconventionsandsymbols .............................. 8

HPtechnicalsupport..................................... 9

HP-authorizedreseller .................................... 9

Helpfulwebsites ...................................... 9

1 Installing the HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family

ofDiskArrays ........................... 11

Preparingforinstallation ................................... 11

InstallingHPMPIOEVADSM ................................ 12

InstallingHPMPIOEVADSMonstand-alonesystems.................... 12

Installing HP MPIO EVA DSM on cluster conﬁgurations ................... 13

UpgradingHPMPIOEVADSM ............................... 13

UpgradingHPMPIOEVADSMonstand-alonesystems ................... 13

Upgrading HP MPIO EVA DSM on cluster conﬁgurations................... 13

Migrating from Windows Server 2003 to Windows Server 2008 with H P M PIO EVA DSM . . . . . . 14

RemovingHPMPIOEVADSM................................ 14

Usingsilentinstallation................................... 15

InstallingHPMPIOEVADSM .............................. 16

UpgradingHPMPIOEVADSM ............................. 17

RemovingHPMPIOEVADSM.............................. 17

Creating response ﬁlesforsilentmodeoperations ..................... 17

SettingupbootfromSAN.................................. 18

2SupportforloadbalancinginFailoverClusterServerenvironmentfor

Windows Server 2008 . ...................... 19

Recoveringinaccessiblediskdevices ............................. 19

3 Support for load balancing in Microsoft Cluster Server environment for

Windows Server 2003 . ...................... 21

EnablingsupportforloadbalancinginMSCSenvironments ................... 21

DisablingsupportforloadbalancinginMSCSenvironments................... 22

Recoveringinaccessiblediskdevices ............................. 23

4AdaptiveLoadbalance ..................... 25

5 Managing storage arrays using the HP MPIO EVA DSM with the CLI utility 27

hpdsmdevices ...................................... 27

hpdsmdevicesall ..................................... 28

hpdsmpathsdevice .................................... 28

hpdsmsetdevicepolicy .................................. 29

hpdsmsetdevicealb.................................... 30

hpdsmsetdevicepath ................................... 30

hpdsmcleanupdevice ................................... 30

hpdsmnotify ....................................... 31

HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays 3.00.00

hpdsmhelp........................................ 32

ASoftwarecomponents . ..................... 33

Drivers.......................................... 33

Usermodecomponents................................... 33

HPMPIODSMmanagerGUI .............................. 33

HPMPIOEVADSMcommandlineinterface(CLI)...................... 33

HPMPIOEVADSMperformancemonitoringprovider.................... 34

HPMPIOEVADSMpersistentreservationsclearutility.................... 34

hpprutildevices .................................. 34

hpprutilcleardevice ................................ 34

hpprutilhelp ................................... 35

BMultipathingdrivereventlogmessages............... 37

MPIO.SYSeventlogmessages................................ 37

HPMPIOEVADSMeventlogmessages............................ 39

C Managing MPIO devices using Microsoft-provided interfaces on Windows

Server2008............................ 41

MultipathI/Ofeature ................................... 41

Managingmultipathsupport ................................ 41

MPIO-edDevices ................................... 41

DiscoverMulti-paths .................................. 42

DSMInstall...................................... 43

Managingmultipathdiskdevices .............................. 44

DTroubleshooting . . ....................... 49

Glossary.............................. 51

Index .............................. 53

Figures

MPIOPropertiespagewithMPIO-edDevicestabenabled .............. 42

MPIOPropertiespagewithDiscoverMulti-Pathstabenabled ............. 43

MPIOPropertiespagewithDSMInstalltabenabled................. 44

Multi-Path D

Multi-PathDiskDevicePropertiespage....................... 46

Multi-PathDiskDevicePropertiespage....................... 47

MPIOPathDetailspage............................. 48

iskDevicePropertiespage....................... 45

HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays 3.00.00

Tables

1 2 3

Documentconventions............................... 8

Pre-installationchecklist ............................. 12

Notiﬁcationstrings ............................... 31

MPIO.SYSeventlogmessages .......................... 37

HPMPIOEVADSMeventlogmessages ...................... 39

HPDSMequivalentloadbalancepolicies ..................... 46

About this guid e

This guide provides information about HP MPIO Full Featured D evice SpeciﬁcModule(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:

• Micr osoft Windows Server 2003 (x86, IA64 and x64)

• Micr osoft Windows Server 2008 – Server Core (x86, IA64 and x64)

• Microsoft W

• EVA4000/4100/4400, EVA6000/6100, and EVA8000/8100 disk arrays

• Microsoft Cluster Server (MSCS)/Failover Cluster environments

Related documentation

In addition to this guide, see HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays release notes.

Additional documentation, including whitepapers and best-practices documents, is available at

ttp://www.hp.com

indows 2008 Ser ver core (x86 and x64)

HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays 3.00.00

Document conven

Table 1 Document conventions

tions and symbols

Convention

Medium blue text: Related

documentation

Medium blue, underlined text

ttp://www.hp.com)

Bold font

Italic font

Monospace font

Monospace, italic font

Monospace, bold font

Element

Cross-reference links and e-mail addresses

Web site addresses

• Key names

• Text typed into a GUI element, such as into a box

• GUI elements that are clicked or selected, such as menu and list

items, buttons, and check boxes

Text emphasis

• File and d

• System ou

• Code

• Text typ

• Code variables

• Command-line variables

Emphasis of ﬁle and directory names, system output, code, and text typed at the command line

irectory names

tput

ed at the command line

WARNING!

Indicates that failure to follow directions could result in bodily harm or death.

CAUTION:

Indicates that failure to follow directions could result in damage to equipment or data.

IMPORTANT:

Provides clarifying information or speciﬁc instructions.

NOTE:

Provides additional information.

About this guide

HP technical sup

port

Telephone numb

ttp://www.hp.com/support/

Collect the fol

• Technical support registration number (if applicable)

• Product serial numbers

• Product model

• Applicable error messages

• Operating system type and revision level

• Detailed, sp

For continuous quality improvement, calls may be recorded or monitored.

HP recommends that customers sign up online using the Subscriber’s choice web site:

ttp://www.hp.com/go/e-updates

• Subscribing

newer versi other product resources.

• After signing up, you can quickly locate your products by selecting Bus iness support and then

Storage un

ers for worldwide technical support are listed on the HP support web site:

lowing information before c alling:

names and numbers

eciﬁcquestions

to this ser vice provides you with e-mail updates on the latest product enha ncem ents,

ons of drivers, and ﬁrmware documentation updates as well as instant access to

der Product Category.

HP-authorized reseller

For the name of your nearest HP-authorized reseller:

• In the United States, call 1-800-282-6672.

• Elsewhere, visit the HP web site: h

telephone numbers.

Helpful w

For other

•h

ttp://www.hp.com

•http://www.hp.com/go/storage

•http://

•http://www.docs.hp.com

ttp://www.hp.com.ThenclickContact HP to ﬁnd locations and

eb sites

product information, see the following HP web sites:

www.hp.com/support/

HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays 3.00.00

About this guide

1 Installin g the HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Array s

HP MPIO Full Featured Device Speciﬁc 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. This chapter describes the following:

• Preparing for installation

• Installing HP MPIO EVA DSM

• Upgrading HP MPIO EVA DSM

• Migrating from Windows Server 2003 to Windows Server 2008 with HP MPIO EVA DSM

•RemovingHPMPIOEVADSM

• Using silent installation

• Setting up bo ot from SAN

Preparing for installation

Before installing HP MPIO EVA DSM, verify that your system components support the HP MPIO EVA DSM and determine whether you need to upgrade hardware or software before installation.

To prepare your system for the installation of HP MPIO EVA DSM:

1. Complet

2. Install all hardware components, as described in the hardware installation and conﬁguration

documentation.

3. Install

4. Back up all user data.

5. Log in with administrator privileges.

6. Ensure that no other installation program is in progress (for example, the Found New Hardware

wizard

7. If your system is running Microsoft Terminal Server, change the Terminal Server from Execution

mode to Installation mode.

Table

e the pre-installation checklist (Table 2).

any required operating system service packs.

2 lists the information you need before installing the HP MPIO EVA DSM.

HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays 3.00.00

Table 2 Pre-installation check list

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.

Obtain and review the most current versions of the following documents:

• HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of D isk Arrays release notes

• Installation and conﬁguration information for your system, available at the following web site: ttp://www.hp.com/country/us/eng/prodserv/storage.html

• Supported SAN topologies for HP MPIO EVA DSM, as deﬁned and described in the

HP StorageWorks SAN design reference guide available at the following web site:

http://h18006.www1.hp.com/products/storageworks/san/documentation.html

CAUTION:

Installing HP MPIO EVA DSM when the Terminal Server is in execution mode may have adverse effects on other software products. For detailed information, see the Microsoft web site:

ttp://support.microsoft.com/default.aspx?scid=kb;en-us;186612

Installing HP MPIO EVA DSM

You can install HP MPIO EVA DSM on a stand-alone system or a cluster conﬁguration. The installation procedure depends on the current conﬁguration of your system.

This section describes how to install HP MPIO EVA DSM on the following conﬁgurations:

• Installing HP MPIO EVA DSM on stand-alone systems

• Installing HP MPIO EVA DSM on cluster conﬁgurations

Installing HP MPIO EVA DSM on stand-alone systems

You ca n install this software prior to attaching the hardware. To install the HP MPIO EVA DSM on a stand-alone system, complete the steps below:

1. Complete the pre-installation checklist (Table 2) and the pre-installation procedure.

2. Ensure that only a single path is connected to the storage devices.

3. Conﬁgure the storage sets.

4. Run Launch.exe from the installation location.

5. In the launch window, click Install HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family

of Disk Arrays.

6. Follow the on-screen instructions to complete the installation.

7. Restart the server.

8. Add the redundant paths to the storage devices.

NOTE:

For Windows Server core 2008 – Server Core (x86 and x64), you can run Launch.exe from the installation location, using the command prompt.

Installing the HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays

Installing HP M

PIO EVA DSM on cluster conﬁgurations

To install HP MP

NOTE:

In a cluster conﬁguration, 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. c. Disable failback for all groups containing resources managed by the current node.

3. Install HP MPIO EVA DSM on the current node by following step 2–9 from the procedure

Installing HP MPIO EVA DSM on stand-alone systems.

4. Using Cluster Administrator, resume the current cluster node.

NOTE:

Repeat steps 2–4 for all nodes in the cluster.

5. Using Cluster Administrator: a. Restore failback for all groups containing resources as needed. b. Redistribute cluster resources as desired.

IO EVA DSM on each member of a cluster conﬁguration, complete the steps below:

Upgrading HP MPIO EVA DSM

You can upgrade HP MPIO EVA DSM from an existing version to the current version on a stand-alone system or cluster conﬁguration.

This section describes how to upgrade HP MPIO EVA DSM on the following conﬁgurations:

• Upgra ding HP MPIO EVA DSM on stand-alone systems

• Upgradin

Upgrading HP MPIO EVA DSM on stand-alone systems

To upgrade HP MPIO EVA DSM from a previous version on stand-alone systems, complete the steps below:

1. Complete the pre-installation checklist (Table 2) and the pre-installation procedure.

2. Run Launch.exe from the installation location.

3. In the launch window, click Install HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family

of Disk Arrays.

4. Select the upgrade option.

5. Follow the on-screen instructions to complete the upgrade.

6. Restart the server.

Upgrading HP MPIO EVA DSM on cluster conﬁgurations

To upgrade HP MPIO EVA DSM from a previous version on each member of a cluster conﬁguration, complete the steps below:

gHPMPIOEVADSMonclusterconﬁgurations

HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays 3.00.00

NOTE:

In a cluster conﬁguration, 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.

3. Upgrade HP MPIO EVA DSM on the current node by following steps 2–6 from the procedure

Upgrading HP MPIO EVA DSM on stand-alone systems.

4. Using Cluster Administrator, resume the current cluster node.

NOTE:

Repeat steps 2–4 for all nodes in the cluster.

5. Using Cluster Administrator: a. Restore failback for all groups containing resources as needed. b. Redistribu

te cluster resources as desired.

Migrating from Windows Server 2003 to Windows Server 2008 with HP MPIO EVA DSM

To migrate from Windows Server 2003 to Windows Server 2008 with HP MPIO EVA DSM, complete the steps below:

1. Back up all user data.

2. Install or Upgrade to HP MPIO EVA DSM 3.00.00, see Chapter 1

3. Upgrade to Windows Server 2008.

4. Double-click the batch ﬁle (depending on your operating system):

• For Windows Server 2008 x86:

<Target_Dir>\x86\Win2k8Upgrade.bat

•ForWindowsServer2008IA64:

<Target_Dir>\ia64\Win2k8Upgrade.bat

• For Windows Server 2008 x64:

<Target_Dir>\amd64\Win2k8Upgrade.bat

NOTE:

To upgrade cluster conﬁguration in Windows Server 2003 to Windows Server 2008, see

ttp://support.microsoft.com/kb/935197

Removing HP MPIO EV A DSM

To remove the HP MPIO EVA DSM, you must reconﬁgure the SAN and reboot your server.

Installing the HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays

CAUTION:

Removing multipathing software from a multipath hardware conﬁguration 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. 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/one-storage array, HP recommends removing redundant cable connections.

• If the storage continues to be accessed by other servers still in multipath mode and by this server in single-path mode and it is on an EVA system, use switch zoning to establish the single connection (path) from the server.

NOTE:

Make sure you perform step 1 and step 2 before proceeding further.

3. Select Start > Settings > Control Panel > Add or Remove Programs.

4. Select HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays from the Remove

Program dropdown list.

5. Click Remove and follow the on-screen instructions.

The syste result f

m displays a cautionary statement advising of the potential data loss or corruption that may

rom removing this software.

6. Close th

NOTE:

The LUNs

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 all installed components, to remove HP MPIO EVA DSM.

e Add/Remove Programs window.

maybeinaccessibleatthistime.

Using silent installation

Silent installation can be run from the installation location on your computer or from a network drive. It installs the HP MPIO EVA DSM with little intervention. Si lent installation is useful if you are installing the software on a large number of servers that require software installation.

This section describes the following:

•Insta

• Upgrading HP MPIO EVA DSM

•RemovingHPMPIOEVADSM

•Crea

Syntax:

lling HP MPIO EVA DSM

ting response ﬁles for silent mode operations

HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays 3.00.00

<install drive>:\MPInstall\setup.exe /s /f1"C:\setup.iss" /f2"C:\MPSInstallLog.txt"

The <install drive> refers to the drive which contains the installation media.

The setup.iss is the response ﬁle from which i nformation is taken for silent installation.

The MPSInstallLog.txt ﬁle records information about the silent installation.

The ResponseResult section of the MPSInstallLog.txt log ﬁle displays the result code, indicating whether or not the silent installation succeeded. An integer value is assigned to the ResultCode keyname in the ResponseResult section.

Following are the list of common return values along with their descriptions in the ResultCode key:

Result Code

0Success

–1

–3

–4

–5

–6

–7

–8

–51

–52

Description

General error

Required data not found in the setup.iss ﬁle

Not enough memory available

File does not exist

Cannot write to the response ﬁle

Unable to writ

Invalid path to the InstallShield Silent response (.iss) ﬁle

Cannot create the speciﬁed folder

Cannot access

etothelogﬁle

the speciﬁed ﬁle 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 ﬁle and write the MPSInstallLog.txt (provided there is write permission

in the directory). For 32 bit systems:

<Default_Target_Dir> = C:\Program Files\Hewlett-Packard\HP MPIO DSM\EVA DSM

For 64 bit systems:

<Default_Target_Dir> = C:\Program Files (x86)\Hewlett-Packard\HP MPIO DSM\EVA DSM

<User_Targe

the director

t_Dir> = is a directory on the system on which the new installation is to be done or

yofanexistinginstallation.

You must enclose the paths to the response ﬁle and the log ﬁle, which records the information about the silent i

nstallation, in quotes ("").

Installing HP MPIO EVA DSM

To perform a silent installation of HP MPIO EVA DSM, complete the steps below:

1. Make a copy of the new.iss ﬁle in the installation kit.

2. Rename this copy of the ﬁle as setup.iss

3. Choose one of the following options:

• To install into the default directory for 64 bit systems, in lines 27 and 32 of the setup.iss

ﬁle, replace C:\Program Files\Hewlett-Packard\HP MPIO DSM\EVA DSM with C:\Program Files (x86)\Hewlett-Packard\HP MPIO DSM\EVA DSM.

Installing the HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays

• To install into the user speciﬁed directory for both 32 and 64 bit systems, in lines 27 and 32 of the setup.iss ﬁle, replace szDir = <Default_Target_Dir> with szDir = <User_Target_Dir>.

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 ﬁle.

• To install only the DSM component (when the Microsoft MPIO Framework already exists on your system), edit the renamed default setup.iss ﬁle as follows:

a. In line 34, replace Component-count=2 with Component-count=1. b. Remove line 35. c. In line 36, replace Component-1=DSM with Component-0=DSM.

5. If you want to avoid the automatic reboot feature, edit the setup.iss ﬁle 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 steps below:

1. Make a copy of the update.iss ﬁle in the installation kit.

2. Rename this copy of the ﬁle as setup.iss

3. Choose on

• To upgrade the Microsoft MPIO Framework c omponent along with the DSM component,

use the renamed default setup.iss ﬁle.

• To upgrade only the DSM component (when the Microsoft MPIO Framework already exists

on your system), edit the renamed default setup.iss ﬁle as follows:

a. In line b. Remove line 24. c. In line 25, replace Component-1=DSM with Component-0=DSM.

4. If you w a. In line 39, replace Result=6 with Result=1. b. In line 40, replace BootOption=3 with BootOption=0.

e of the following options:

23, replace Component-count=2 with Component-count=1.

ant to avoid the automatic reboot feature, edit the setup.iss ﬁle as follows:

Removing HP MPIO EV A DSM

To remove HP MPIO EVA DSM, complete the steps below:

1. Make a copy of the uninstall.iss ﬁle in the installation kit.

2. Rename this copy of the ﬁle as setup.iss

3. If you want to avoid the automatic reboot feature, edit the renamed setup.iss ﬁle as follows: a. In line 28, replace Result=6 with Result=1. b. In line 29, replace BootOption=3 with BootOption=0.

Creating response ﬁles for silent mode operations

The package contains the following response ﬁles (.iss ﬁles): new.iss, uninstall.iss and update.iss that are used for silent mode installation, uninstallation and update respectively. In addition

these, you can create your own customized response ﬁles for operations (such as modify/repair) with

to different combinations of the components selected/unselected.

Customized response ﬁles can be created by running the setup.exe in the record mode on one of the systems. This response ﬁle can then be used for doing the same silent mode operation across

ltiple systems.

To create response ﬁle, complete the following steps:

HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays 3.00.00

1. At the command prompt, type the following command: <CMD> setup.exe /r,where/r

option enables the record mode.

2. This will result in the GUI installation to run in the record mod e. 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 ﬁle will have to be generated again in such a case.

3. The response ﬁle is created at the following location: %WINDDIR%\setup.iss,where,

%WINDIR% is the Windows installation directory.

4. Use this setup.iss ﬁle to perform the same silent mode operation on multiple systems across

thesameplatform.

Setting up boot from SAN

HP MPIO EVA DSM can be set up to boot externally from a SAN that uses H P StorageWorks HBAs and RAID arrays. Booting externally 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 speciﬁc setup procedures based on the speciﬁcsoftwaresolutions,HBA ﬁrmware, and boot BIOS versions. See the following documents for detailed information about booting from a SAN:

• HP StorageWorks Booting 32-bit Windows systems and Windows Server x64 Edition

systems from a Storage Area Network application notes, available at this web site:

ttp://h18006.www1.hp.com/products/storageworks/san/documentation.html

• HP StorageWorks Booting I tanium 64-bit Windows Systems from a Storage Area Network

application notes, available at this web site: h

storageworks/san/documentation.html

ttp://h18006.www1.hp.com/products/

Installing the HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays

2 Support for l oad balancing in Failover C lus ter Server environme n t 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 i

If there is a s connected to it. This is because the strong reservation type (persistent reservations) supports load balancing in clusters.

You can use th to remove the

DSM persistent reservations clear utility.

naccessible disk devices

tray reservation on a disk device, the device becomes inaccessible to the host systems

e persistent reservations clear utility that comes with the HP MPIO EVA DSM package

stray reservations. For more information on how to use this utility, see HP MPIO EVA

HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays 3.00.00

Support for load balancing in Failover Cluster Server environment for Windows Server 2008

3 Support for load balancing in Microsoft C luster 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, H P 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. However, HP MPIO EVA DSM provides a feature to support load balancing for all HP disk arrays that support the SCSI-3 persistent reservations management method by mapping the MSCS-issued SCSI-2 reservations to SCSI-3 persistent reservations.

HP MPIO EVA DSM supports load balancing in MSCS environments only under the following conditions:

• All nodes in the cluster must have the same version of the HP MPIO EVA DSM installed.

• Support for load balancing in MSCS environments must be enabled on all cluster nod es in the

HP MPIO EVA DSM.

• The disk array containing the cluster resources must support the SCSI-3 persistent reservations.

NOTE:

Contact HP technical support for details on disk arrays and the ﬁrmware revisions that support persistent reservations.

Enabling support for load balancing in MSCS environments

You can enable load-balancing support in MSCS environments while installing the HP MPIO EVA DSM or anytime after the installation.

CAUTION:

You must enable the load-balancing feature on all nodes in the cluster. If the setting is not consistent across all cluster nodes, the cluster node failover functionality can be impaired.

To enable load balancing at the time of installing HP MPIO EVA DSM, select Enable Load Balancing in Cluster in the Conﬁguration Settings window.

To enable load balancing after you have installed HP MPIO EVA DSM, complete the following steps:

NOTE:

You must repeat the following procedure on all nodes in the cluster, one at a time.

HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays 3.00.00

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 <installdir> on the current node

using Windows Explorer.

3. Double-click the registry ﬁle (depending upon the operating system you are using):

•ForWindowsServer2003(32-bit):

<installdir>\x86\hpeaadsm_pr_on.reg

• For Windows Server 2003 (IA64):

<installdir>\IA64\hpeaadsm_pr_on.reg

• For Windows Server 2003 x64 Edition:

<installdir>\AMD64\hpeaadsm_pr_on.reg

NOTE:

The <installdir> referstothefolderwhichyouhaveselectedduring theHPMPIOEVADSMinstallation. Thedefaultinstallationdirectoryis %ProgramFiles%\Hewlett-Packard\HP MPIO DSM\EVA DSM.InWindows Server 2008 Cluster, the load balancing for the cluster devices is turned on by default.

4. Follow the on-screen instructions.

5. Reboot the system for the new registry parameter to take effect.

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 device(s) using the HPDSM CLI or HP MPIO DSM manager.

Disabling support for load balancing in MSCS environments

To disable the load balancing support in MSCS environments in HP MPIO EVA DSM, complete the following steps:

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 <installdir> on the current node,

using Windows Explorer.

3. Double-click the registry ﬁle (depending upon the operating system you are using):

•ForWindowsServer2003(32-bit):

<installdir>\x86\hpeaadsm_pr_off.reg

• For Windows Server 2003 (IA64):

<installdir>\IA64\hpeaadsm_pr_off.reg

• For Windows Server 2003 x64 Edition:

<installdir>\AMD64\hpeaadsm_pr_off.reg

Support for load balancing in Microsoft Cluster Server environment for Windows Server 2003

NOTE:

The <installdir> referstothefolderwhichyouhaveselectedduring the HP MPIO EVA DSM installation. The default installation directory is

%ProgramFiles

4. Follow the on-screen instructions.

5. Reboot the system for the new registry parameter to take effect.

IMPORTANT:

During the process of enabling or disabling of load balance in an MSCS environment (for a cluster with more than two nodes), you may have a set of nodes using SCSI-3 persistent reservations along with another set of nodes using SCSI-2 reservations. In such cases (as part of step 1 in the above sections), HP recommends that you move the cluster resources to the set of nodes that has the majority reservation.

%\Hewlett-Packard\HP MPIO DSM\EVA DSM.

Recovering inaccessible disk devices

If there is a stray reservation on a disk d evice, the device becomes inaccessible to the host systems connected to it. This is because the strong reservation type (persistent reservations) supports load balancing i

You can use the persistent reservations clear utility that comes with the HP MPIO EVA DSM package to remove the stray reservations. For more information on how to use this utilit y, see HP MPIO EVA

DSM persistent reservations clear utility.

nclusters.

HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays 3.00.00

Support for load balancing in Microsoft Cluster Server environment for Windows Server 2003

4 Adaptive Load balance

The HP MPIO EVA DSM implements array speciﬁc 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, Shor test Queue Requests, Shortest Queue Bytes, and Shortest Queue Service Time.

By default, ALB is disabled for the newly discovered LUN. If the newly discovered LUN is part of any Logical Unit Group, the ALB setting of the existing group prevails.

NOTE:

• AlldevicesthatarepartoftheLogicalUnitGroup,hasthesameALBsetting.

• The ALB sett ing 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/disable) the ALB setting for a given LUN either through the HP MPIO DSM Manager or the HP DSM CLI. See Managing storage arrays with HP MPIO E VA DSM CLI utility for more information.

HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays 3.00.00

Adaptive Load balance

5 Managing storage arrays using theHPMPIOEVADSMwiththeCLI utility

The command line interface utility (CLI) of HP MPIO EVA DSM enables you to monitor and manage multipathing devices. This chapter describes the following CLI commands:

• hpdsm devices

• hpdsm devices all

• hpdsm paths device

• hpdsm set device policy

• hpdsm set device alb

• hpdsm set device path

• hpdsm cleanup device

• hpdsm notify

• hpdsm help

hpdsm devi

Syntax: hpdsm devices

The hpdsm devices command displays information about the HP MPIO devices as shown in the followin found.

NOTE:

See hpdsm set device policy for a deﬁnitionofthepolicies. TheP.B.T.L.columnshowsthedeviceport, bus, targ

Example:

hpdsm devices

Device#

1HP

2 HP HSV210 600508B400101F6A000070001D9B0000 9

3 HP HSV210 600508B400101F6A000070001DA10000 9

4HP

5HP

6 HP HSV210 600508B400101F6A000070001E220000 9

7HP

8 HP HSV210 600508B400101F6A000070001E2E0000 9

ces

g example. If there are no devices present, the following message is displayed: No devices

et, and LUN.

Device Name

HSV210 600508B400101F6A000070001D950000 9

HSV210 600508B400101F6A000070001E160000 9

HSV210 600508B400101F6A000070001E1C0000 9

HSV210 600508B400101F6A000070001E280000 9

Serial No.

Active Paths

Policy

SQST

SQR

NLB

SQST

Disk#

Disk 10 4.0.1.1

Disk 11 4.0.1.2

Disk 12 4.0.1.3

Disk 13 3.0.2.4

Disk 14 2.0.2.5

Disk 15 2.0.2.6

Disk 16 3.0.2.7

Disk 17 3.0.2.8

P.B.T.L ALB

HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays 3.00.00

hpdsm devices a

Syntax: hpdsm devices all

The hpdsm devices all command displays information of the device, followed by their path information as displayed: No devices found.

NOTE:

See hpdsm set device policy for a deﬁnition of the policies. The P.B.T.L. column shows the device port, bus, target, a

Example:

hpdsm devices all

Device#

Device Name Serial No.

HP HSV210 6005008B400101F6000170000 2

shown in the following example. If there are no devices, the following message is

nd LUN.

Active Paths

Policy

SQST

Disk#

Disk1 4.0.2.3

P.B.T.L ALB

Path# Controller Port#

2 P898DXAAQQO101U-2 Active 6 00010002 4.0.2.3

Device#

2 HP HSV210 6005008B400101F600018000 2

Path# Controller Port#

2 P898DXAAQQO101U-2 Active 6 00010002 4.0.2.4

P898DXAAQQO101U-2 Active

Device Name Serial No.

P898DXAAQQO101U-2 Active

State

HBA Slot#

RTP P.B.T.L

00010002 3.0.2.3

Active Paths

RTP P.B.T.L

00010002 3.0.2.4

Policy

SQST

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.

Disk#

Disk2 3.0.2.4

P.B.T.L ALB

NOTE:

• The P.B.T.L. column shows the device port, bus, target, and LUN.

• TheRTPcolumnshowsthetargetportinformationasdeﬁned by SCSI-3 speciﬁcation.

• The Controller Port# column shows the controller serial number followed by target port number.

Managing storage arrays using the HP MPIO EVA DSM with the CLI utility

hpdsm paths device=1

Path# Controller Port

2 P8398DXAAQQ013-3 Active

3 P8398DXAAQQ010-1 Active

6 P8398DXAAQQ01

8 P8398DXAAQQ013-4 Active 3 00020008 4.0.1.1

9 P8398DXAAQQ013-3 Active 3 00020007 4.0.2.1

P8398DXAAQQ013-4 Active

P8398DXAAQQ010-1 Active

P8398DXAAQQ013-3 Active

P8398DXAAQQ010-1 Active 3 00010001 4.0.0.1

3-4

hpdsm set device policy

State

Active

HBA Slot#

RTP P.B.T.L

00020008 2.0.2.1

00020007 2.0.5.1

00010001 2.0.6.1

00010001 3.0.0.1

00020007 3.0.1.1

00020008 3.0.2.1

Syntax: hpdsm

set device=x policy=policy

Syntax: hpdsm set device=all policy=policy

The hpdsm set device policy command sets the load-balancing policy for device x to one of the following:

• No_Load_Bala

nce (NLB) - All I/O requests a re routed through a chosen active path.

• Round_Robin (RR) - All I/O requests are distributed across all active paths to the device in a

round robin manner.

• Shortest_Qu

eue_Requests (SQR) - Each I/O request is routed to the active path with the least

number of outstanding requests.

• Shortest_Queue_Bytes (SQB) - Each I/O request is routed to the active path with the least number

of outstand

ing data bytes.

• Shortest_Queue_ServiceTime (SQST) - Each I/O request is routed to the active path where the

total outstanding time for pending I/O requests is the least.

The example below dem onstrates the i nformation displayed by the hpdsm set device policy command.

NOTE:

You cannot cha nge 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.

HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays 3.00.00

hpdsm set devic

Syntax: hpdsm set device=x alb=y/n

Syntax: hpdsm set device=all alb=y/n

The hpdsm set de or for all the de

Example:

hpdsm set device=1 alb=y

Device Name : HP HSV210

Device Serial No. : 600508B400101F6A000070001D950000

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.

ealb

vice alb command changes the Adaptive Load Balance setting for the device x

vices, depending on the input parameter speciﬁed.

hpdsm set device path

Syntax: hpdsm set device=x path=y

The hpdsm set device path command changes the preferred path for device x,asshowninthe example below.

NOTE:

Use the hpdsm paths device command to view the available paths for the device.

hpdsm set device=1 path=1

Device Name : HP HSV210

Device Serial No. : 600508B400101F6A000070001D950000

Controller Port No.

Change Load Balance policy (y/n)? y

Preferred Path changed. Verify by issuing "hpdsm paths device=<number>" 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 speciﬁed device x, as shown in the example below.

: P8398DXAAQQ013

Example:

Managing storage arrays using the HP MPIO EVA DSM with the CLI utility

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 d

Successful for all the devices. Verify by issuing "hpdsm devices" command.

hpdsm notif y

evice=all

Syntax: hpdsm

The hpdsm not

notify event=notification_event_number time=number_of_minutes

ify command deﬁnes user notiﬁcation of events. The time attribute deﬁnes the number

of minutes that will elapse from the time the event occurs until the user is notiﬁed. The maximum value that can be entered is 35000 minutes.

NOTE:

Syntax: hpds

m notify event=notification_event_number

The above command will make the notiﬁcation to wait indeﬁnitely until the user terminates the wait (eg: with Ctr

l-C).

Table 3 deﬁnes the selections for the notiﬁcation command string.

Table 3 Notiﬁcation string s

Notiﬁcation string

HPDSM_NEW_DEVICE

HPDSM_ADDITIONAL_PATH

Notiﬁcation_ event_

number

Notiﬁes the user when DSM:

Detects a new device.

Detects a redundant path to an existing device.

Determines that a device conﬁguration

HPDSM_MAX_PATH_REACHED

contains the maximum number of supported paths.

HPDSM_LAST_PATH_FAILURE

HPDSM_PATH_FAILOVER

HPDSM_MAX_LUNS_REACHED

HPDSM_ALL_NOTIFICATIONS

The above notiﬁcations are sent by the HP MPIO EVA DSM and MPIO framework to the CLI. The CLI displays the event in the command window as shown in the following example.

HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays 3.00.00

Detects that the last path to the device is removed.

Detects an existing path to a device

has failed and a n alternate path is being used.

Determines that the conﬁguration

contains the maximum number of supported LUNs.

Detects any event related to MPIO framework and DSM occurs.

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.5);from hpeaadsm Received HPDSM_PATH_FAILOVER : 600508B400101F6A000070001E220000;(4.0.0.6);from hpeaadsm Received HPDSM_PATH_FAILOVER : 600508B400101F6A000070001E280000;(4.0.0.7);from hpeaadsm Received HPDSM_PATH_FAILOVER : 600508B400101F6A000070001E2E0000;(4.0.0.8);from hpeaadsm Received HPDSM_DEVICE_REMOVAL : 600508B400101F6A000070001D950000;(2.0.6.1);from hpeaadsm Received HPDSM_DEVICE_REMOVAL : 600508B400101F6A000070001D9B0000;(2.0.6.2);from hpeaadsm Received HPDSM_DEVICE_REMOVAL : 600508B400101F6A000070001DA10000;(2.0.6.3);from hpeaadsm Received HPDSM_DEVICE_REMOVAL : 600508B400101F6A000070001E160000;(2.0.6.4);from hpeaadsm Received HPDSM_DEVICE_REMOVAL : 600508B400101F6A000070001E1C0000;(2.0.6.5);from hpeaadsm Received HPDSM_DEVICE_REMOVAL : 600508B400101F6A000070001E220000;(2.0.6.6);from hpeaadsm Received HPDSM_DEVICE_REMOVAL : 600508B400101F6A000070001E280000;(2.0.6.7);from hpeaadsm Received HPDSM_DEVICE_REMOVAL : 600508B400101F6A000070001E2E0000;(2.0.6.8);from hpeaadsm Received HPDSM_NEW_DEVICE : 600508B400101F6A000070001D950000;(3.0.0.1);from hpeaadsm Received HPDSM_NEW_DEVICE : 600508B400101F6A000070001D9B0000;(3.0.0.2);from hpeaadsm Received HPDSM_NEW_DEVICE : 600508B400101F6A000070001DA10000;(3.0.0.3);from hpeaadsm Received HPDSM_NEW_DEVICE : 600508B400101F6A000070001E160000;(3.0.0.4);from hpeaadsm Received HPDSM_NEW_DEVICE : 600508B400101F6A000070001E1C0000;(3.0.0.5);from hpeaadsm Received HPDSM_NEW_DEVICE : 600508B400101F6A000070001E220000;(3.0.0.6);from hpeaadsm Received HPDSM_NEW_DEVICE : 600508B400101F6A000070001E280000;(3.0.0.7);from hpeaadsm Received HPDSM_NEW_DEVICE : 600508B400101F6A000070001E2E0000;(3.0.0.8);from hpeaadsm Received HPDSM_ADDITIONAL_PATH : 600508B400101F6A000070001D950000;(3.0.1.1);from hpeaadsm Received HPDSM_ADDITIONAL_PATH : 600508B400101F6A000070001D9B0000;(3.0.1.2);from hpeaadsm Received HPDSM_ADDITIONAL_PATH : 600508B400101F6A000070001DA10000;(3.0.1.3);from hpeaadsm Received HPDSM_ADDITIONAL_PATH : 600508B400101F6A000070001E160000;(3.0.1.4);from hpeaadsm Received HPDSM_ADDITIONAL_PATH : 600508B400101F6A000070001E1C0000;(3.0.1.5);from hpeaadsm Received HPDSM_ADDITIONAL_PATH : 600508B400101F6A000070001E220000;(3.0.1.6);from hpeaadsm Received HPDSM_ADDITIONAL_PATH : 600508B400101F6A000070001E280000;(3.0.1.7);from hpeaadsm Received HPDSM_ADDITIONAL_PATH : 600508B400101F6A000070001E2E0000;(3.0.1.8);from hpeaadsm Received Moved to STATE_NORMAL from MPIO Disk(17) Received HPDSM_ADDITIONAL_PATH : 600508B400101F6A000070001D950000;(2.0.6.1);from hpeaadsm Received Moved to STATE_NORMAL from MPIO Disk(18) Received HPDSM_ADDITIONAL_PATH : 600508B400101F6A000070001D9B0000;(2.0.6.2);from hpeaadsm Received Moved to STATE_NORMAL from MPIO Disk(19) Received HPDSM_ADDITIONAL_PATH : 600508B400101F6A000070001DA10000;(2.0.6.3);from hpeaadsm Received HPDSM_ADDITIONAL_PATH : 600508B400101F6A000070001E160000;(2.0.6.4);from hpeaadsm

hpdsm help

Syntax: hpdsm help

The hpdsm help comm and displays help information for the CLI.

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 MP

• MPIO.SYS is the multipathing bus driver.

• MPDEV.SYS is the replacement class driver. It communicates with MPIO.SYS.

• MPSPFLTR.SY

• HP DSM driver

• HPEAADSM.SYS is the HP DSM d river for EVA disk arrays. It interacts with MPIO.SYS to

provide dev

HP recommends that you do not remove, delete, or disable these drivers while multipath hardware is attached to your system.

IO Framework Drivers

S is a port driver ﬁlter (HBA upper ﬁlter).

ice-speciﬁcfunctions.

User mode components

The user mode components includes:

•HPMPIODSMmanagerGUI

• HP MPIO EVA DSM command line interface

• HP M PIO EVA DSM performance monitoring provider

• HP MPIO EVA DSM persistent reservations clear utility

HP MPIO DSM manager GUI

The HP MP receive separate installation package.

NOTE:

To manage HP MPIO EVA DSM 3.00.00 and later, use HP MPIO DSM Manager 3.00.00 or later.

HP MPIO EVA DSM command line interface (CLI)

The HP MPIO EVA DSM command line interface (HPDSM.EXE) enables you to monitor and manage HP DSMs in an MPIO environment.

IO DSM m anager GUI monitors and manages the HP DSMs. It also enables administrator to

email notiﬁcations on path/device failure events. The HP MPIO DSM Manager is provided as a

NOTE:

To manage the HP MPIO EVA DSM 3.00.00 and later, use HP MPIO DSM M anager 3.00.00 or later.

HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays 3.00.00

HP MPIO EVA DSM p

erformance monitoring provider

The HP MPIO EVA D Input/Output

(I/O) performance of a device path using the system monitor.

To start the pe

1. Select Start >

SM performance monitoring provider (HpPerfProv.DLL) helps you m onitor the

rformance monitoring, complete the steps below:

Programs > Hewlett-Packard > EVA DSM > Path Performance.

Alternatively, you can select Start > Run and execute the command perfmon /wmi.

2. Select HP DSM High Performance Provider performance object and add the appropriate counters.

HP MPIO EVA DSM persistent reservations clear utility

The HP M PIO EVA DSM persistent reservations clear utility enables you to view and clear reservations on the disk(s) that are left behind due to incorrect installation or removal of the HP MPIO EVA DSM or an unsuccessful cluster node failover.

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 M PIO EVA DSM installation directory during the installation. You can run this utility either on a system that has HP MPIO EVA DSM installed or on a system where H P MPIO EVA DSM is not installed.

To run this utility on a system where the HP MPIO EVA DSM is installed, complete the steps below:

1. Select Start > Programs > Hewlett-Packard > EVA DSM > HPDSM PR Utility.

2. Enter the command hpprutil /? at the command prompt to display the instructions for using

this utility.

This chapter describes the following hpprutil commands:

•hpprutildevices

• hpprutil clear device

• hpprutil help

hpprutil devices

Syntax: hpprutil devices

The hpprutil devices command displays details of reservations on the devices as shown in the following example. If there are no devices present, the following message is displayed: No Devices Found.

Example:

hpprutil devices

Device#

2 COMPAQ HSV210 3.0.2.2

hpprutil clear device

Syntax: hpprutil clear device=x

Device Name

COMPAQ HSV210 3.0.2.1

SCSI Address

Reservation

NT Disk#

Disk1

Disk2

Software components

Syntax: hpprutil clear device=m n

The hpprutil clear device command clears the reservation p resent on device x,orclearsthe reservation present on devices starting from m to n (both inclusive), depending on the input parameter speciﬁed.

Example:

hpprutil clear

The requested operation is in progress. Please wait.

HPPRUTIL will attempt to clear the reservation on device 1.

Are you sure you

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... Successfully cleared the reservation on device.

Attempting to clear the reservation on device 2... Successfully cleared the reservation on device.

device=1

want to continue (y/n)? y

hpprutil help

Syntax: hpprutil help

The hpprutil help command displays help information for hpprutil.

HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays 3.00.00

Software components

BMultipathingdrivereventlog messages

ThisappendixliststheeventlogmessagesforHPMPIOEVADSMdriversandprovidesadescriptionof each message. The error log messages are written in the SYSTEM log ﬁle.

This appendix provides information about the following event log messages:

•MPIO.SYSeventlogmessages

•HPMPIOEVADSMeventlogmessages

MPIO.SYS event log messages

Table 4 lists MPIO d river event log messages, an explanation of each message, and a description of the

data that accompanies the message.

Table 4 MPIO.

SYSeventlogmessages

Event ID Message

Pseudo-LUN created.

Added device to pseudo-

LUN.

There was an error creating a device claimed by the DSM.

A fail-over on pseudo-LUN occurred.

Pseudo-LUN is currently in a degraded state. One or more paths have failed, though the process is now complete.

A Single Path Fail-Over is being attempted on

pseudo-LUN

Description

MPIOcreatedanewpseudo-LUN (a new disk p object).

Anewinsta pseudo-LUN device object is seen through a different path.

MPIO failed to create a new (or update an existing) pseudo-LUN device obj

DSM_name

it.

Apseudo-LUNhandleda failover. This message does not indicate whether the failover was success

At least hasfailed. Thissignalstheend of failover hand ling for the pseudo-LUN and that the device is now o less path.

A pseudo-LUN has just one path, andDSMhasrequestedafailover.

hysical device

nce of an existing

ect, even though

claimed support for

ful.

one path to a pseudo-LUN

perating with at least one

Contents of the data dump

N/A

The current number of paths to the device

N/A

The Path ID of the failed device

N/A

The Path ID of the failing device

An operation failed on

device due to lack of memory.

HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays 3.00.00

Resource allocation failed during an attempted failover, and failover is not currently active.

The Path ID of the

ing device

fail

Event ID Message

Description

Contents of the data dump

A Path Verification request to a device on pseudo-LUN that is controlled by DSM_name has failed. This may indicate a path failure.

The internal state of device_object is inconsistent. This indicates potential failures in this support.

A fail-over on pseudo-LUN was attempted, however the attempt failed. The devices will be removed.

All paths have failed. Pseudo-LUN will be removed.

A PnP Operation rejected, as device is not in a state where the request can be honored.

AcalltoaDSM’sPathVerify routine to a pseudo-LUN has failed. This event occurs during ﬁnal initialization after PathVerify has checked whether the device can be reached through a newly found path.

MPIO is unable to run through its maintained list of pseudo-LUNs.

Afailovera

ttempt on a pseudo-LUN has failed. This indicates that the DSM did not return a va

lid path after the call

to InvalidatePath.

There are no available paths to thepseudo-LUN.Thedevicehas gone into t

otal failure and will be

removed.

APnPrequ

est for QueryRemove was rejected because the device is in the paging, hiber, or crash dump path

state.

N/A

Requests that were queued to pseudo-LUN have failed during resubmission.

DSM_name failed to return a Path to pseudo-LUN.

DSM_name returned a bogus path to device.

DSM_name supplied an invalid ID for an operation on notification_type.

An unknown DSM supplied an invalid ID for an operation on pseudo-LUN.

An issued request from the pseudo-

LUN’s queue failed. This alwaysoccurswhenthedeviceis in the process of being removed.

One of the following events occurred during failover: MPIO’s call to the DSMs InvalidatePath

;DSMdidnotreturnanew

failed path; DSM did not return a path when MPIO called the LBGetPath

ne.

routi

MPIO is unable to ﬁnd an

tional device-path pair

opera representation (device info) for the path that the DSM wants to use

eI/Otothedevice

for th

MPIO received a DSMNotiﬁcation

,butisunabletomapthe

call DSMID to a device.

DSM called DSMSendRequest to haveMPIOsendarequestonits

lf, but MPIO is unable to ﬁnd

beha the pseudo-LUN requested.

Path ID u

sed for

resubmission

N/A

Path ID

Bogus

ned by DSM; if

retur the Path ID = NULL, the DSM has failed

turn a path.

to re

DSM I

DSM ID

Multipathing driver event log messages

Event ID Message

DSM_name is attempting an

operation on pseudo-LUN. The Type is noted in the dump data.

A device under pseudo-LUN, being controlled by DSM_name was removed, but the DSM failed the operation.

Description

DSM_name has called DSMNotiﬁc ation on a pseudo-LUN.

An MPIO call to DSM’s RemoveDevice operation failed.

Contents of the data dump

Thetypeof notiﬁcation called by DSM

DSM ID of the failed attempt

HP MPIO EVA DS

Table 5 lists

Table 5 HP MPIO EVA DSM event log messages

Event ID Message

101

102

103

107

108

the HP MPIO EVA DSM event log messages and provides a description of each message.

Discovered a new multipath capable disk with serial number X; first path SCSI address Y.

A new path (SCSI address Y) was added to existing multipath capable disk X.

The path (SCSI address Y) to multipath capable disk X has recovered.

The preferred path (SCSI address Y) for multipath capable disk X has been restored.

The DSM has completed remove processing for path (SCSI address Y) to multipath capable disk X.

M event log messages

Descriptio

A new multipath disk has been discovered. X represents the serial number of the new disk. Y is the SCSI address of the ﬁrst path to this disk.

A new path to an existing multipath disk has been discovered. X represents the serial number of the disk. Y is the SCSI address of the new path that was found.

A failed path to an existing multipath disk has recovered. X represents the serial number of the disk. Y is the SCSI address of the path that has been recovered.

A previously selected path has been restored as the preferred path for I/O operation. X represents the serial number of the disk. Y is the SCSI address of the preferred path that has been restored.

The DSM has completed processing the removal notiﬁcation for a path to a given multipath disk. X represents the serial number of the disk. Y is the SCSI address of the path for which the removal notiﬁcation has been processed.

109

11 0

111

The DSM (version X) has been started successfully.

The previously failed multipath capable disk X has recovered.

The removal event notifications for multipath capable disk X have been disabled upon request.

HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays 3.00.00

TheDSMhassuccessfullycompletedtheinitialization during startup. X is the version of the DSM.

This message is logged when the DSM detects that a previously failed (inoperative) multipath capable disk with serial number X has recovered and become operational again.

This event is logged when generation of removal event notiﬁcations (Event IDs 304, 302 and 108) for the multipath capable disk with serial number X has been disabled upon request in the DSM.

Event ID Message

The removal event notifications for

112

multipath capable disk X have been enabled upon request.

Description

This event is logged when generation of removal event notiﬁcations ( Event IDs 304, 302 and 108) for the multipath capable disk with serial number X has been enabled upon request in the DSM.

113

301

302

303

304

305

The multipath capable disk X has been disconnected from the system.

The DSM failed to initialize during startup.

An unrecoverable path failure occurred on SCSI address Y. Disk X failed due to no redundant paths available.

Too many paths for disk with serial number X. Path (SCSI address Y) not added.

An unrecoverable path failure occurred on SCSI address Y. Disk X is still accessible over redundant path(s).

The DSM timed out on the I/O throttle operation for multipath capable disk X.

This event is logged when the last path to a multipath capable disk with serial number X (for which the generation of removal event notiﬁcations have been disabled) is disconnected from the system.

The DSM did not initialize successfully during startup.

All paths to an existing multipath disk have failed. X represents the serial number of the disk. Y is the SCSI address of the last path that failed.

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.

A redundant path to an existing multipath disk has failed. X represents the serial number of the disk. Y is the SCSI address of the path that failed.

The DSM

was unable to successfully throttle I/O activity within the time-out period, for the speciﬁed multipath disk. X represents the serial number of

the dis

307

308

309

An unrecoverable failure has occurred on multipath capable disk X. This disk will henceforth not be accessible.

An unrecoverable failure has occurred on multipath capable disk X. The data on this disk may be inaccessible.

The DSM cannot manage multipath capable disk X (SCSI address Y) due to an internal error.

vent is logged when the DSM detects an

This e

overable failure of a multipath capable disk,

unrec and requests MPIO not to support this disk going forward. Please check the status of the multipath capable disk at the array end. X represents the

al number of the disk.

seri

event is logged when the DSM detects an

This

ecoverable failure of a multipath capable disk.

unr Although the disk may be visible to the system, the data on the disk may not be accessible. Please check

status of the multipath capable disk at the array

the end. X represents the serial number of the disk.

The DSM cannot manage multipath capable disk X (SCSI address Y) due to an internal error.

Multipathing driver event log messages

CManagingMPIOdevicesusing Microsoft-provided interfaces on Window s 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. Microsoft also supplies an inbox Microsoft DSM (MS DSM), which provides multipath support for SCSI-3 compliant disk devices.

This appendix addresses the following topic:

• Multipath I/O feature

• Managing multipath support

• Managing multipath disk devices

Multipath I/O feature

Multipath I/O feature enables the operating system to manage the disk devices that support multipathing. You must enable this feature before managing devices that support multipath. Installing the HP MPIO EVA DSM automatically enables the Multipath I/O feature.

Alternatively, you can enable this feature manually as follows:

1. Go to Serv

displays.

2. Select Multipath I/O. The MPIO framework and MS DSM are installed, and the MPIO applet is

added to

er Manager and select Features > Add Features. TheAddFeaturesWizardpage

the Control Panel.

Managing multipath support

Microsoft provides a Control Panel applet that enables you to manage multipath suppor t for disk devices. This interface allows users to enable or disable multipath support for the selected devices, allows users to install vendor-speciﬁcDSM,orboth.

To use the applet, go to Control Panel and select MPIO. The MPIO Properties page displays.

The MPIO Properties page includes the following tabs:

•MPIO-edDevices

• Discover Multi-paths

•DSMInstall

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 supoprt multipathing and are currently managed by MPIO.

Figure 1 shows the MPIO Properties page with the MPIO-ed Devices tab enabled.

HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays 3.00.00

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 d evices with Device H ardware IDs

are hand

To manually disable support for a device, select a Device H ardware ID and click Remove.

ledbyaDSM(eitheravendor-suppliedDSMorMSDSM).

Discover Multi-paths

In the MPIO Properties page, click the Discover Multi-Paths tab. This tab displays the Device Hardware IDs of the devices that s upport multipathing, which are currently not managed but supported by MPIO.

Figure 2 shows the MPIO Properties page with the Discover Multi-Paths tab enabled.

Managing MPIO devices using Microsoft-provided interfaces on Windows Server 2008

Figure 2 MPIO Properties page with Discover Multi-Paths tab enabled

To enable

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.WhileinstallingaDSM,youmustspecifythedriverpath,theINFﬁle name, and the DSM Hardware ID. Figure 3 shows the MPIO Properties page with the DSM Install tab enabled.

multipath support for the listed devices, select a Device Hardware ID, and click Add.

HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays 3.00.00

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 gi

ven 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 D evice Properties page, under the MPIO tab, enables you to perform basic d isk and path management. Figure 4 shows the Multi-Path Disk Device Properties page. HP MPIO EVA DSM supports the management infrastructure of the MPIO tab for features that are applicable to the HP DSM.

To manage the Multi-Path Disk D evice through this interface, complete the following steps:

1. Go to Device Manager and select the MPIO managed device identiﬁed by Multi-Path Disk device.

2. Right-click and select Properties. The Multi-Path Disk Device Properties page displays.

Managing MPIO devices using Microsoft-provided interfaces on Windows Server 2008

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.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.

Table 6 HP DSM equivalent loa d balance policies

MPIO Tab

Failover Only No Load Balance (NLB)

Round Robin With Subset Not applicable

Round Robin Round Robin (RR)

Least Queue Depth Shortest Queue Requests (SQR)

Weighted Paths Not applicable

Vendor-Speciﬁc

HP DSM

Shortest Queue Service Time* * This policy cannot be selected for the HP MPIO

FF EVA DSM from the MPIO tab.

4. To view additional information about the DSM, click Details. The DSM Details page displays.

Figure 6 shows the DSM Details page.

Managing MPIO devices using Microsoft-provided interfaces on Windows Server 2008

Figure 6 Multi-Path Disk Device Properties page

5. Modify th

e MPIO Timer Counters associated with DSM, if required, and click OK.

NOTE:

Modifyin recomme

g the timer counters for the DSM may result in unexpected system behavior. HP

nds 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 showstheMPIOPathDetailspage.

7. Modify the details of the path, if required, and click OK.

HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays 3.00.00

Figure 7 MPIO Path Details page

Managing MPIO devices using Microsoft-provided interfaces on Windows Server 2008

D Trou bleshooting

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. To do this, go

to Server Manager and select Features > Add Features > Multipath I/O.

• Verify if the version of MPIO framework installed on the system is compatible with the minimum version

supported by this DSM (applicable for Windows Server 2003 only). To ﬁnd out the version of MPIO framework installed on the system, complete the following steps:

1. Select Computer Management > Device manager > SCSI and RAID controllers.

2. Right-click Mutli-Path Support and select Properties. The Properties page displays.

3. Verify the version of MPIO framework from the Drivers tab. For more information on the

versions of MPIO framework supported by the DSM, see the HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays 3.00.00 release notes.

Problem: HP MPIO DSM fails to manage the disk devices.

Solution: To troubleshoot this problem, complete the following steps:

1. Verify if the device is currently u n der multipath support. To do this, go to Control Panel,andselect

MPIO. Verify the existence of the corresponding device hardware ID in the MPIO-ed devices tab.

2. If the hardware ID is not present, do one of the following:

• Add the corresponding hardware ID. For more information on adding the corresponding hardware IDs, see Managing multipath disk devices

•ReinstalltheHPMPIODSM.

Problem: HP DSM CLI and HP MPIO DSM Mana ger fail to list devices after upgrade from Windows Server 2003 to Windows Server 2008.

Solution: Double-click one of the following batch ﬁles (depending on your operating system):

• For Windows Server 2008 x86:

<Target_Dir>\x86\Win2k8Upgrade.bat

• For Windows Server 2008 IA64:

<Target_Dir>\ia64\Win2k8Upgrade.bat

• For Windows Server 2008 x64:

<Target_Dir>\amd64\Win2k8Upgrade.bat

where <Target_Dir> is the location where the DSM is installed.

HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays 3.00.00

Troubleshooting

Glossary

This glossary deﬁnes the terms used in this g uide 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

controller A hardware device that facilitates communication between a host and one

DSM Device SpeciﬁcModule

fabric A network that contains high-speed ﬁber connections resulting from the

certain features suppor ted by the array, to deliver better per formance for host I/O requests.

or more LUNs organized as an array.

interconnection of switches and devices. A fabric is an active and intelligent non-shared interconnect scheme for nodes.

failover The automatic substitution of a functionally equivalent system

a component that has failed.

HBA Host Bus Adapter. An I/O device that serves as the interface connecting a host

system to the SCSI bus or SAN (Storage Area Network)

host The computer system on which the Multipath software is running.

LUN LogicalUnitNumber. TheactualunitnumberassignedtoadevicebytheRAID

system controller.

mode A user-selectable parameter that speciﬁes path behavior during normal and

failure conditions. Paths c an be set to one of the following modes:

• Preferred — Indicates the path you choose for the desired I/O paths. When

a path is in preferred mode, load balance is not enabled and the Load Balance Type displays as none.

• Alternate — Indicates a path that is used for device access and I/O activities

when the preferred path fails.

MPIO Multipathing Input/Output.

path A virtual communication route that enables data and commands to pass

between a host server and a storage device.

path state An attribute that describes the operational condition of a path. A path can exist

in one of the following states:

• Active — Path is currently used for the I/O stream or is available for load

balancing.

• 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 —Intermediatestateofthepathbeforeitisinitialized(madeready

for device access), normally will not be seen.

• Failed —PathiscurrentlyunusablefortheI/Ostream.

component for

HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays 3.00.00

port A TherelativenumberofanHBA.Aspeciﬁc port number is determined according

to its order of discovery by the Windows operating system. HBA’s include SCSI, Fibre Channel, and ID E adapter types.

SAN Storage Area Network. A conﬁguration 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.

• Degraded: O ne or more paths are failed to the storage unit.

target The deﬁnition of target depends on the environment:

• For parallel SCSI conﬁgurations, the target is the actual target number

assigned to a device.

• For Fibre Channel conﬁgurations, a target number is assigned by a mapping

function at the miniport-driver level and is derived from AL_PA (Arbitrated Loop Physical Addresses) in an FC-AL topology.

• For SAN switched fabric, a target is assigned to a WWPN. This target can

have values between 16 and 125.

• For a fabric topology, target is a mapping function derived from the order

of discovery according to port connections at the SAN (Storage Area Network) switch.

topology An interconnection scheme that allows multiple servers and storage devices

to communicate. Arbitrated loop and switched fabric are examples of Fibre Channel topologies.

Glossary

Index

boot from SAN

setting up,18

conventions

text symbols,8

documentation

HP web site,7

drivers

Multipathing bus,33 replacement class,33

Subscriber’s choice web site,9

installation

silent,15

installing

Multipathing software,12

MPDEV.SYS,33 MPIO.SYS,33

related documentation,7 removing Multipathing software,14

Subscriber’s choice, HP,9 symbols in text,8

text symbols,8

web sites

HP documentation,7 HP Subscriber’s choice,9

HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays 3.00.00

HP MPIO Installation And Reference Manual

Specifications and Main Features

Frequently Asked Questions

User Manual