3PAR Multipath I/O 1.0.

23 for Microsoft Windows Users Guide for (IA64, x64, x86)

3PAR Inc. 4209 Technology Drive Fremont, CA 94538 USA

320-200215 Rev A March 2010

3PAR Confidential

Revision Notice
This is the first release of this manual. A complete revision history is provided at the end of this document.

Changes
The material in this document is for information only and is subject to change without notice. While reasonable efforts have been made in the preparation of this document to assure its accuracy, 3PAR Inc. assumes no liability resulting from errors or omissions in this document or from the use of the information contained herein. 3PARdata reserves the right to make changes in the product design without reservation and without notification to its users.

Updates to the Documentation at 3PAR Central

Any updates to this document, or to other 3PAR technical documents, can be found by logging on to 3PAR Centrals Document Control System from 3PARs Support page at http://www.3par.com/support/index.html

3PAR Technical Support and Services

Contact your local service provider for technical support and services.

Sales and Ordering Information

For sales and ordering information, contact: 3PAR Inc. 4209 Technology Drive Fremont, CA 94538 USA Telephone: 510-413-5999 Fax: 510-413-5699 Email: [email protected]

Reader Comments and Suggestions

Please email your comments and suggestions about this document to [email protected].

Copyrights
2007-2010 3PAR Inc. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior written consent of 3PAR Inc., 4209 Technology Drive, Fremont, CA 94538. By way of exception to the foregoing, the user may print one copy of electronic material for personal use only.

Trademarks
3PAR, InServ, InForm, InSpire and Serving Information are registered trademarks of 3PAR Inc. Microsoft, Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation. UNIX is a registered trademark of The Open Group. All other trademarks and registered trademarks are owned by their respective owners.

Federal Communications Commission Radio Frequency Interference Statement

WARNING: Changes or modifications to this unit not expressly approved by the party responsible for compliance could void the users authority to operate the equipment. This device complies with Part 15 of FFC Rules. Operation is subjected to the following two conditions (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense.

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

Table of Contents
1 Introduction
1.1 Overview 1.2 Audience 1.3 Related Documentation 1.4 Organization 1.5 Typographical Conventions 1.6 Advisories 1.2 1.2 1.3 1.4 1.5 1.5

2 Overview and Features

2.1 Overview 2.2 About Microsoft Multipath I/O 2.3 About 3PAR Multipath I/O for Microsoft Windows 2.4 CD Contents 2.5 Features 2.6 System Requirements 2.7 Special Considerations 2.2 2.2 2.2 2.3 2.4 2.6 2.7

Table of Contents

iii

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

3 Installation, Deinstallation and Upgrade

3.1 Overview 3.2 Installing 3PAR MPIO for Microsoft Windows
3.2.1 3.2.2 3.2.3 Before You Begin Software Installation Verifying Installation

3.2 3.2 3.3 3.5 3.6 3.9 3.10 3.11 3.13 3.13 3.17 3.19

3.3 Additional Instructions for Remote Booting 3.4 Upgrading 3.5 Deinstalling 3.6 3PAR MPIO and MSCS Environments
3.6.1 3.6.2 3.6.3 Fresh Installation (MSCS Environments) Deinstalling MPIO Software (MSCS Environments) Online Upgrade of MPIO Software (MSCS Environments)

4 Using the 3PAR MPIO CLI

4.1 Overview of the 3PAR MPIO CLI 4.2 mpiocli Command 4.3 Using the 3PAR MPIO CLI
4.3.1 4.3.2 4.3.3 Getting Setting Information Setting Load Balance Policy Setting Event Log Level

4.1 4.2 4.7 4.7 4.7 4.8

RH

Revision History

iv

Table of Contents

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

1 Introduction
In this chapter
1.2 Audience 1.3 Related Documentation 1.4 Organization 1.5 Typographical Conventions 1.6 Advisories 1.2 1.3 1.4 1.5 1.5

Introduction

1.1

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

1.1 Overview
This guide provides information for installing and using 3PAR Multipath I/O for Microsoft Windows. 3PAR Multipath I/O for Microsoft Windows is used to support Microsoft MPIO technology for hosts connecting to 3PAR InServ Storage Servers.

1.2 Audience
This guide is for Microsoft Windows administrators who are responsible for maintaining the Windows operating environment and who understand the InServ Storage Server and the following operating systems:

for x86 - Windows Server 2003. for x64 - Windows Server 2003, Enterprise Edition for Intel Xeon Processor-64 and AMD Opteron-based systems.

for IA64 - Windows Server 2003, Enterprise Edition for Itanium-based systems.

1.2

Overview

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

1.3 Related Documentation

The following documents also provide information related to InServ Storage Servers and the InForm Operating System: For information about Online upgrade support of 3PAR MPIO, specific Windows OS platforms and 3PAR InForm OS version requirements, and a list of hot fixes from Microsoft S400/S800 Storage Server hardware configurations, component numbering and layout, and system cabling E200 Storage Server hardware configurations, component numbering and layout, and system cabling Identifying storage server components and alerts. CLI commands and their usage. 3PAR InForm Command Line Interface Reference Configuring and managing InServ Storage Servers and using the InForm Management Console (IMC) Configuring and managing InServ Storage Servers and using the InForm Command Line Interface (CLI) Using 3PAR Remote Copy 3PAR Remote Copy Users Guide 3PAR CLI Administrators Guide 3PAR InForm Management Console Online Help 3PAR Messages and Operators Guide 3PAR InServ E200 Storage Server Physical Planning Manual 3PAR InServ S-Class Storage Server Physical Planning Manual Read the 3PAR InForm OS Configuration Matrix, which can be found on the Document Control System (DCS).

Related Documentation

1.3

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

1.4 Organization
This guide is organized as follows:

Chapter 1, Introduction (this chapter), provides an overview of this guide, including information on audience, related documentation, and typographical conventions.

Chapter 2, Overview and Features, gives an overview of Microsoft Multipath I/O (MPIO) and 3PAR Multipath I/O for Microsoft Windows, including features and system requirements.

Chapter 3, Installation, Deinstallation and Upgrade, describes how to install, verify, and deinstall 3PAR Multipath I/O for Microsoft Windows when working with hosts running Windows 2003.

Chapter 4, Using the 3PAR MPIO CLI, provides reference information and describes how to use the 3PAR Multipath I/O for Microsoft Windows CLI.

This guide also contains a revision history describing the major changes for each version.

1.4

Organization

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

1.5 Typographical Conventions

This guide employs the following typographical conventions: Typeface ABCDabcd Meaning Used for dialog elements such as titles, button labels, and other screen elements. ABCDabcd Used for paths, filenames, and screen output. Open the file \gui\windows\setup.exe Example When prompted, click Finish to complete the installation.

1.6 Advisories
To avoid injury to people or damage to data and equipment, be sure to observe the cautions and warnings in this guide. NOTE: Notes are reminders, tips, or suggestions that supplement the procedures included in this guide.

CAUTION: Cautions alert you to actions that can cause damage to equipment, software, or data.

REQUIRED: Requirements signify procedures that must be followed as directed in order to achieve a functional and supported implementation based on testing at 3PAR.

WARNING: Warnings alert you to actions that can cause injury to people or irreversible damage to data or the operating system.

Typographical Conventions

1.5

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

1.6

Advisories

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

2 Overview and Features

In this chapter
2.1 Overview 2.2 About Microsoft Multipath I/O 2.3 About 3PAR Multipath I/O for Microsoft Windows 2.4 CD Contents 2.5 Features 2.6 System Requirements 2.7 Special Considerations 2.2 2.2 2.2 2.3 2.4 2.6 2.7

Overview and Features

2.1

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

2.1 Overview
This chapter provides an overview of Microsoft Multipath I/O (MPIO) and 3PAR Multipath I/O for Microsoft Windows.

2.2 About Microsoft Multipath I/O

In September of 2002, Microsoft introduced MPIO technology to enable increased levels of system availability and performance through load-balancing and inter operability of thirdparty storage products. MPIO is enabled through third-party storage solutions providers such as 3PAR and supported by Windows 2003. The introduction of Microsoft MPIO has delivered a standard and interoperable path for communication between storage products and the Windows 2003 Server. MPIO is a technology that enables the use of more than one physical path to access a storage device. By offering fault tolerance and/or load balancing of I/O traffic, multipathing provides improved system reliability and availability.

2.3 About 3PAR Multipath I/O for Microsoft Windows

3PAR is among the first enterprise storage vendors to endorse Microsoft MPIO by developing products that utilize this new technology. 3PAR MPIO for Microsoft Windows addresses the following requirements:

Dynamic configuration of the multipath bus driver and disks based on installed adapters and devices and dynamic response to events occurring on the system. This dynamic configuration capacity extends to boot and page file devices.

Transparent system architecture that relies on plug-and-play capabilities and maintains compatibility with existing driver stacks.

Support for dynamic load balancing properties. Support for the Microsoft Cluster Service (MSCS) clustered environment.

2.2

Overview

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

2.4 CD Contents
The 3PAR MPIO for Microsoft Windows application is provided on the CD in the following folders:
Table 2-1. 3PAR MPIO for Microsoft Windows Drivers

Folder x64 x86

Contents for x64 based installations for x86 based installations

IA64

for IA64 based installations

Patch

Patch files for internal use only

CD Contents

2.3

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

2.5 Features
3PAR MPIO for Microsoft Windows provides the following system features and enhancements:

Fan Topology - 3PAR MPIO for Microsoft Windows enables support for fan topology through a fabric switch. That is, a single Microsoft Windows host initiator can now see multiple InServ Storage Server host ports when connecting over a SAN environment. See Figure 2-1.

Figure 2-1. Fan Topology

Multiple paths to a 3PAR device - 3PAPR MPIO for Microsoft Windows provides multiple path support from a host to an InServ Storage Server for enhanced system performance and reliability. For specific path support information, see the 3PAR InForm OS Configuration Matrix, which can be found on the Document Control System (DCS).

Multiple virtual volume exports to a host - 3PAR MPIO for Microsoft Windows includes support for up to 255 virtual volumes exported to each host.

Dynamic load balancing policies - 3PAR MPIO for Microsoft Windows provides a dynamic load balancing mechanism to distribute read/write requests across multiple available paths.

2.4

Features

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

Properties include: Fail Over Only, Round Robin, Round Robin with a subset of paths, Least Weighted Path, and Least Queue Depth.

Fail Over Only - This type of load balance policy is also called Active/Passive, though no actual load balancing is performed. Only one single active path can send I/O; all other paths are standby paths. If the active path fails, then one of the standby paths is used. If the formally active path is reconnected, it will become active and the standby path that was active returns to standby.

Round Robin - In this type of load balancing, all paths are active paths and are used for sending I/O in a round robin fashion. This is the default setting. NOTE: Round Robin is the only supported load balancing policy for a quorum disk device within a Microsoft Cluster environment.

Round Robin with a subset of paths - In this type of load balancing, a set of paths are configured as active, and a set of paths are configured as standby. I/O is sent in a round robin fashion over the active paths. If all of the active paths fail, one of the standby path is used. If any of the formerly active paths become available again, the formerly active paths are used and the standby path that was active becomes a standby path again.

Least Queue Depth - With this type of load balancing, the path with the fewest number of requests queued is the one where the I/O is sent. NOTE: All paths associated with the device drive are active.

Least Weighted Path -With this type of load balancing, each path is assigned a weight and I/O is sent on the path with the lowest weight. If the path with the lowest weight fails, the path with the next lowest weight is used. NOTE: The path with the least weight is the only active path to the device drive. More than one path may have the same weight, ranging from 0 to 99, and a default weight of 0. New paths are assigned the default weight.

Automatic error handling and failover recovery - 3PAR MPIO for Microsoft Windows evaluates I/O status to determine whether an I/O request requires retry or failover and communicates this information to the Windows operating system.
Features

2.5

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

If one path reports failure, 3PAR MPIO for Microsoft Windows moves all I/O requests to other available paths. When the failed path becomes available again, the driver automatically redirects I/O requests to the recovered path.

Automatic discovery - 3PAR MPIO for Microsoft Windows can detect and remove a device that is physically exported to or removed from a host. 3PAR MPIO for Microsoft Windows builds or removes the path depending on the devices updating status.

MSCS clustered environment support - 3PAR MPIO for Microsoft Windows can coexist with MSCS cluster environments.

Online upgrade support - The online upgrade of InServ Storage Servers is supported when the host is running 3PAR MPIO for Microsoft Windows.

2.6 System Requirements

3PAR MPIO is supported on x86, x64, and IA64 platforms. For specific Windows OS platforms and 3PAR InForm OS version requirements, and a list of hot fixes from Microsoft, refer to the 3PAR InForm Configuration Matrix.

2.6

System Requirements

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

2.7 Special Considerations

While using 3PAR MPIO for Microsoft Windows, please observe the following considerations:

Due to the power and flexibility of the InServ Storage Server and the InForm OS management software, it is possible to export a large number of VLUNs in a very short period of time. However, the Windows Disk Manager may not be capable of handling such a large number of disks at once. Therefore, it is recommended that you close the Windows Disk Manager application until the Windows Device Manager can see all disk devices. Once all the disks are visible, you can open the Windows Disk Manager to perform disk management operations such as formatting disks and assigning drive letters or mount points.

When using 3PAR MPIO for Microsoft Windows, always use a Windows management console for disk device configuration, including installing and deinstalling 3PAR MPIO for Microsoft Windows.

In order for 3PAR MPIO software to work correctly in a Microsoft Cluster Service environment, all host cluster nodes must have the same version of the 3PAR MPIO software.

For IA64 and x64 only: 3PAR MPIO only supports the Storport driver from QLogic and Emulex HBA vendors. Refer to the 3PAR InForm OS Configuration Matrix for supported HBA driver information.

For x86 only: Microsoft has encountered a problem with deinstalling earlier versions of 3PAR MPIO. This issue has been addressed in 3PAR MPIO for Microsoft Windows, version 1.0.10. However, for all versions prior to version 1.0.10 of the 3PAR MPIO software, you must use the install.exe file included with 3PAR MPIO for Microsoft Windows in order to deinstall the product.

During MPIO installation, the call to UpdateDriverForPlugAndPlayDevices restarts the disk stacks. However, if MPIO is being installed on a system with mirrored disks, the disks appear as failed redundancy. This happens only if disk management applications (that use the dmadmin service) are running at the time of MPIO installation. It is strongly advised that all disk management applications (including but not limited to,

diskmgmt.msc and diskpart.exe) be closed prior to MPIO installation. To prevent the mirrored disks from showing up as failed redundancy please ensure that the dmadmin
service is not running at the time of MPIO installation

Special Considerations

2.7

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

2.8

Special Considerations

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

3 Installation, Deinstallation and Upgrade

In this chapter
3.1 Overview 3.2 Installing 3PAR MPIO for Microsoft Windows 3.3 Additional Instructions for Remote Booting 3.4 Upgrading 3.5 Deinstalling 3.6 3PAR MPIO and MSCS Environments 3.2 3.2 3.9 3.10 3.11 3.13

Installation, Deinstallation and Upgrade

3.1

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

3.1 Overview
This chapter describes how to install and verify installation of 3PAR MPIO for Microsoft Windows. Instructions for deinstalling the software are also provided in this chapter. CAUTION: Attempting to update HBA drivers or firmware concurrently with the upgrade, installation, or deinstallation of 3PAR MPIO software, may lead to unpredictable results. HBA driver or firmware upgrades should be completed either before or after 3PAR MPIO software upgrades. Follow the HBA manufacturer's documentation for driver or firmware upgrades. Refer to the 3PAR Implementation Guides for the Microsoft Windows and HBA combination being upgraded for supported HBA driver versions.

NOTE: Installation and deinstallation of 3PAR MPIO software differs when working with cluster nodes running in a MCSC environment. See 3PAR MPIO and MSCS Environments on page 3.13 for specific instructions.

3.2 Installing 3PAR MPIO for Microsoft Windows

The following section includes preinstallation and installation instructions for 3PAR MPIO for Microsoft Windows.

3.2

Overview

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

3.2.1 Before You Begin

CAUTION:

Before installing 3PAR MPIO for Microsoft Windows on a host, you must remove any Dynamic Multipathing (DMP) drivers provided by other vendors who are not using Microsoft MPIO framework to develop MPIO solution.

Per Microsofts guidance, Microsoft MPIO architecture supports the co-existence of multiple DSMs by design. The 3PAR MPIO solution is MPIO framework compliant and follows the Microsoft recommendation to install the complete Microsoft MPIO driver package as part of the 3PAR MPIO solution deliverable. Other vendors who also deliver the Microsoft MPIO solution should be compliant to the Microsoft MPIO framework and follows the same recommendation from Microsoft. 3PAR is not responsible to support other vendors DSM in the coexistence environment. If the host is currently running Microsoft MPIO software installed by another vendor, installing the 3PAR MPIO package will overwrite the Microsoft MPIO driver package. Therefore it is customers responsibility to ensure the Microsoft MPIO driver versions they install from 3PAR and other vendors are always at the same Microsoft MPIO DDK level.

NOTE: For a list of possible hot fixes for MPIO from Microsoft, see the 3PAR InForm OS Configuration Matrix.

NOTE: 3PAR MPIO for Microsoft Windows includes support for up to 255 virtual volume exports per host.

NOTE: The number of LUNs on the system may affect the installation time for 3PAR MPIO for Microsoft Windows.

Installing 3PAR MPIO for Microsoft Windows

3.3

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

NOTE: It is strongly advised that all disk management applications (including but not limited to, diskmgmt.msc and diskpart.exe) be closed prior to MPIO installation. To prevent the mirrored disks from showing up as failed redundancy please also ensure that the dmadmin service is not running at the time of MPIO installation.

Before installing 3PAR MPIO for Microsoft Windows:

Verify that the host computer is running the appropriate operating system:

(for x86) - Microsoft Windows 2003. (for x64) - Microsoft Windows Server 2003, Enterprise Edition, for Intel Xeon Processor64 and AMD Opteron-based systems.

(for IA64) - Microsoft Windows Server 2003, Enterprise Edition, for Itanium-based systems.

To view your service pack level, right click the My Computer desktop icon and then click Properties . Click the General tab to see information about the operating system and service pack level. For more information, see the 3PAR InForm OS Configuration Matrix which is available on DCS.

Verify that the Windows .NET framework is installed on the host computer. The 3PAR software will not install correctly without the .NET framework present. The .NET framework can be obtained from the following site: http://msdn2.microsoft.com/en-us/netframework/default.aspx

Remove any multipathing drivers provided by other vendors. Refer to the vendor's documentation for removal instructions. After removing any multipathing drivers provided by other vendors, you must also remove and reinstall all HBA drivers provided by that vendor.

For the host machine initially installing 3PAR MPIO software, only a single I/O path connection between the host machine and the InServ Storage Server, is allowed.

(Optional). To expedite installation, remove all VLUNs except VLUN 0. The Windows Computer Management application should remain closed at all times during the 3PAR MPIO installation.

3.4

Installing 3PAR MPIO for Microsoft Windows

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

3.2.2 Software Installation

To install 3PAR MPIO for Microsoft Windows: 1 2 Log on to the host as Administrator. Insert the 3PAR Multipath I/O for Microsoft Windows CD, P/N 780-2000056, into a CD-ROM drive. 3 Open Windows Explorer and double click the icon for the CD-ROM drive that holds the 3PAR software CD and expand the appropriate folder, (IA64, x64 or x86). 4 5 Double-click the MSMPIO.msi icon. Follow the instructions in the 3PAR Multipath I/O for Microsoft Windows installer window (Figure 3-1 on page 3.5).

NOTE: The Disk Cost button analyzes the amount of available storage space and compares it to the amount required for the 3PAR MPIO installation. The default option is to install for Everyone which creates the necessary program folder and desktop icon for everyone who has access to the system. Accept the default settings.

Figure 3-1. Installing 3PAR MPIO for Microsoft Windows

Installing 3PAR MPIO for Microsoft Windows

3.5

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

When finished, close the 3PAR Multipath I/O for Microsoft Windows installer window and then reboot the host computer.

3.2.3 Verifying Installation

To verify installation of 3PAR Multipath I/O (MPIO) for Microsoft Windows: 1 2 3 If necessary, log on to the host as Administrator. On the Windows desktop, right click My Computer and then click Manage . Verify the following components: a b In the left pane tree control, click Device Manager. In the right pane tree, click to expand Disk Drives . Depending on your configuration, you should see at least one 3PARdata VV Multi-Path Disk Device icon and at least one 3PARdata VV SCSI Disk Device icon in the window's right pane. c d In the left pane tree control, click Device Manager. In the right pane tree, click to expand SCSI and RAID Controllers . You should see Multi-Path Support in the windows right pane. e f In the left pane tree control, click Device Manager. In the right pane tree, click to expand System Devices . You should see 3PAR Multi-Path Device Specific Module in the windows right pane. g Click the 3PAR Multi-Path Device Specific Module icon and then click the Driver folder tab. This tab should contain the Microsoft Windows Hardware Compatibility Publisher certification statement

CAUTION: After installing 3PAR MPIO for Microsoft Windows, the TargetDir registry key appears under:

HKEY_LOCAL_MACHINE/Software/3par/MPIO/TargetDir
to record the location of the install package files (Figure 3-2). Do not try to edit the registry key value as this will cause driver removal to fail.

3.6

Installing 3PAR MPIO for Microsoft Windows

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

Figure 3-2. Windows Registry Key

After installing 3PAR MPIO for Microsoft Windows, a detailed driver registry key appears in: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\tpddsm

The registry key parameters are as follows:

DsmPersistentReservationKey : A unique key generated by the 3PAR MPIO installation engine based on the TPDM prefix plus the system IP address. Modification of this key is prohibited. If the system IP address is reassigned after installing 3PAR MPIO software, you must run the install.exe program using the -r option in order to regenerate this key value. This program can be found under the 3PAR MPIO install directory.

DsmUsePersistentReservation: 3PAR MPIO as well as 3PAR InServ Storage Server device supports SCSI-3 Persistent Reservation.

Installing 3PAR MPIO for Microsoft Windows

3.7

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

NOTE: The key value for DsmPersistentReservationKey is used for SCSI reservations within MSCS environments. Therefore, it must be unique for all host cluster nodes. If you create a new system by cloning from another host cluster node within the same MSCS environment, the cloned system may contain the same DsmPersistentReservationKey as the original. You must run

install.exe with the -r option on all cloned systems to generate a unique key
for each. This same effort is required if the system does not contain a static IP address prior to the 3PAR MPIO installation.

DsmMaximumStateTransitionTime : Maximum time period for a Persistent Reservation request, failing with a retry-able unit attention to be retrieved, before failing back to MSCS.

EventLogLevel : Used to display the event log to the System Event Viewer, increase the maximum log size when necessary. Settings are as follows:

0 error events only 1 warning events in addition to error events 2 informational events in addition to warning and error events (default) 3 Includes SCSI-3 reservation activities and informational events, in addition to warning and error events. Microsoft cluster validates each cluster disk every three seconds, therefore there will be many read reservation key events recorded to the System event log. It is recommended to use this event log level for a short period of time with adequate event log space.

SupportedDeviceList : 3PAR-supported device identification. TimeOut : Time-out value for SCSI driver pass-through command (10 is the default). Version: Version number of the currently installed 3PAR MPIO for Microsoft Windows software.

NOTE: Any changes to the above parameters will require a system reboot in order to take effect.

3.8

Installing 3PAR MPIO for Microsoft Windows

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

NOTE: At this point you can install additional paths by physically connecting additional paths from the host to the InServ Storage Server.

3.3 Additional Instructions for Remote Booting

The following special instructions apply to enable remote booting of the Windows 2003 operating system from a 3PAR InServ Storage Server when using 3PAR Multipath I/O (MPIO) for Microsoft Windows. 1 Install the appropriate Windows operating system with a single path connected, referring to the HBA vendor's installation documentation for instructions on installing the remote booting device. 2 Before installing 3PAR MPIO for Microsoft Windows on the host computer, make sure the appropriate Windows operating system is functioning correctly with a single path connected. For complete details, refer to the appropriate 3PAR Implementation Guide for information on the remote booting of Windows hosts from a 3PAR InServ Storage Server.

NOTE: Once 3PAR MPIO for Microsoft Windows is successfully installed and the host computer has been rebooted, additional paths can be connected. However, before deinstalling 3PAR MPIO for Microsoft Windows, you should make sure that you have only a single path connected.

NOTE: Refer to the appropriate 3PAR Implementation Guide for detailed instructions.

Make sure that the BIOS for all HBAs are enabled.

Additional Instructions for Remote Booting

3.9

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

3.4 Upgrading
NOTE: There was an issue in the 3PAR MPIO 1.0.17 x64 window installer (MSMPIO.MSI) program preventing direct upgrade to the later release. A patch is available to fix the local cached copy of MSMPIO.MSI saved in the host environment. The 3PAR MPIO 1.0.23 for x64 platform installer will prevent upgrading from 3PAR MPIO 1.0.17 x64 platform if the following patch instructions have not yet been applied. 1.Create a folder from the host containing MPIO 1.0.17 x64. For example, mkdir c:\mmp NOTE: Microsoft .Net Framework version 2.0 or above is required to run patch for MPIO 1.0.17 x64 2.From the 3PAR MPIO 1.0.23 CD contents, copy all files from subfolder patch\x64 to the folder created in step 1. For example, copy v:\patch\x64\* c:\mmp 3.Open a Windows command prompt and change directory to the new created folder. For example, cd c:\mmp 4.Execute the mmp1017 command. For example, mmp1017 5.Once the command has completed, follow the normal upgrade procedure to upgrade 3PAR MPIO to the later release.

To upgrade 3PAR MPIO for Microsoft Windows, from release 1.0.17 or later, follow the same procedure as for installing. Refer to Installing 3PAR MPIO for Microsoft Windows on page 3.2.

3.10

Upgrading

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

These instructions are only applicable to a standalone system when upgrading from version 1.0.16 and on. For upgrading within a MSCS cluster environment, refer to 3PAR MPIO and MSCS Environments on page 3.13. NOTE: If you have previously installed 3PAR Multipath I/O (MPIO) for Microsoft Windows release 1.0.10 or earlier, you must remove it first and reboot the host server before installing the latest release. (Refer to Installing 3PAR MPIO for Microsoft Windows on page 3.2.

NOTE: It is not necessary to remove a multi-path connection to maintain the single-path connection from the host server to the InServ Storage Server during the upgrade process as long as one I/O path is connected.

3.5 Deinstalling
Deinstall 3PAR MPIO for Microsoft Windows, as follows. Note that you must copy

install.exe from the current version package to the prior installed location for any version
prior to 1.0.10.

WARNING: During deinstallation, the 3PAR MPIO package installer removes the entire MPIO driver stack. To deinstall 3PAR MPIO in the case where 3PAR MPIO and MPIO from another vendor are currently installed, mask the virtual volume from the InServ Storage Server, but keep the installed 3PAR MPIO driver on the host, to avoid removing Microsoft MPIO drivers used by other vendors.

CAUTION: Before deinstalling 3PAR MPIO for Microsoft Windows, make sure you have only a single path connected between the host and the InServ Storage Server and that data transfer from the host to the storage server has been quiesced. This is required to ensure successful deinstallation/installation of 3PAR MPIO software and to prevent accidental data loss that can occur if volumes are exported simultaneously over multiple paths without multipathing software installed on the host.

Deinstalling

3.11

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

NOTE: When deinstalling 3PAR MPIO for Microsoft Window from a boot or pagefile device, Windows will notify you of an error the first time you attempt to remove this software. This is because the driver is currently in use by the operating system. After rebooting the host computer, follow the deinstallation procedure again to complete removal of the entire driver package.

1 2

Log on to the host as Administrator. To deinstall 3PAR MPIO, version 1.0.10 or later, skip to step 3 on page 3.13. a Click Start , point to Run , type regedit, and press ENTER. The Registry Editor window appears. b In the left pane of the Registry Editor, click the MPIO icon nested under My Computer >HKEY_LOCAL_MACHINE >SOFTWARE >3PAR (Figure 3-3).

Figure 3-3. Windows Registry Editor

3.12

Deinstalling

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

In the right pane, find the package location for TargetDir (for example, C:\Program Files\3PAR\MPIO).

Copy the file install.exe from the package subdirectory on the 3PAR Multipath I/O for Microsoft Windows CD, version 1.0.23, to the package location determined above in order to overwrite the existing install.exe in the package subdirectory.

CAUTION: You must copy install.exe from the current version package (1.0.23) to the prior installed location for prior version removal.

Click Start > Settings > Control Panel > Add/Remove Programs . The Add/Remove Programs window appears.

4 5 6 7

Select 3PAR Multipath I/O for Microsoft Windows . Click Remove . Reboot the host computer. If you received an error when you clicked Remove in step 5, repeat step 1 through step 6 to complete the removal of the entire software package.

3.6 3PAR MPIO and MSCS Environments

The process for installing and deinstalling 3PAR MPIO software differs for environments where servers are running in a cluster with MSCS. This section includes specific instructions for working with MSCS clustered environments.

CAUTION: Before installing 3PAR MPIO for Microsoft Windows, make sure you have only a single path connected.

3.6.1 Fresh Installation (MSCS Environments)

Use the following procedure to perform a fresh installation of 3PAR MPIO for Microsoft Windows on cluster nodes in a MSCS environment:

3PAR MPIO and MSCS Environments

3.13

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

CAUTION: For fresh installations of 3PAR MPIO software, you must take the same precautions recommended by Microsoft when establishing a new Microsoft Cluster Services Cluster. Permitting more then one non-clustered host server access to disks may cause data corruption. Follow the fresh install directions precisely.

CAUTION: Installing 3PAR MPIO software onto an MSCS node will cause temporary inaccessibility of the cluster resources from the client. Therefore, downtime is required to complete the following procedure.

Designate one cluster node to use as the first node on which to install the 3PAR MPIO software.

Move all cluster resources to the designated cluster node as follows: a On the cluster nodes Windows desktop, click Start > Programs > Administrative Tools . Click Cluster Administrator > Manage . b In the left pane tree control of the Cluster Administrator window, right-click the cluster group name and then click Move Group (Figure 3-4).

Figure 3-4. Moving a Group in the Cluster Administrator Window

3.14

3PAR MPIO and MSCS Environments

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

If necessary, choose the designated cluster node as the destination for the move group operation.

For each additional resource group, repeat steps b and c. Resources are moved to the designated cluster node.

On all other cluster nodes, set startup type to Manual as follows: a On the cluster nodes Windows desktop, right click My Computer and then click Manage . a b In the left pane tree control, click Services and Applications . In the right pane, double-click Services , right-click Cluster Service and then click Properties. c In the Cluster Service Properties dialog box that appears, set Startup type to Manual (Figure 3-5 on page 3.15).

Figure 3-5. Setting Startup Type to Manual

3PAR MPIO and MSCS Environments

3.15

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

d 4

Click OK .

Shut down all cluster nodes for which you have set Startup type to Manual . Do not shut down the cluster node that you have designated as the first node on which to install 3PAR MPIO software.

On the designated cluster node, perform the following: a b Stop the cluster service by clicking Stop in the Cluster Service Properties dialog box. Telnet to the InServ Storage Server and check the reservations on that host by issuing the showrsv command (see the 3PAR CLI Reference for details). A message stating No reservations found should be returned. c Install the 3PAR MPIO software on the designated cluster node and then reboot the host cluster node. Refer to Installing 3PAR MPIO for Microsoft Windows on page 3.2 for detailed instructions.

6 7

If desired, add additional paths to the designated cluster node. For each of the shut down cluster nodes: a b Start the cluster node. Install 3PAR MPIO software and then reboot the cluster node. Refer to Installing 3PAR MPIO for Microsoft Windows on page 3.2 for detailed instructions.

For each of the cluster nodes that were rebooted at the end of step 7, set Startup type to Automatic and start cluster service as follows: a On the cluster nodes Windows desktop, right click My Computer and then click Manage . b c In the left pane tree control, click Services and Applications . In the right pane, double-click Services , right-click Cluster Service and then click Properties . d In the Cluster Service Properties dialog box that appears, set Startup type to Automatic and then click Start . e Click OK.

Repeat this process for each cluster node until the cluster service is started on all cluster nodes.

3.16

3PAR MPIO and MSCS Environments

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

If necessary, redistribute the groups to reflect the configuration in use prior to installing 3PAR MPIO software.

3.6.2 Deinstalling MPIO Software (MSCS Environments)

Use the following procedure to deinstall 3PAR MPIO for Microsoft Windows on nodes in a MSCS environment:

CAUTION: When deinstalling 3PAR MPIO software, you must take the same precautions recommended by Microsoft when establishing a new Microsoft Cluster Services Cluster. Permitting more then one non-clustered host server access to disks may cause data corruption. Follow the deinstallation directions precisely.

CAUTION: Deinstalling 3PAR MPIO software from an MSCS cluster node will cause temporary inaccessibility of the cluster resources from the client. Therefore, downtime is required to complete the following procedure.

Choose a cluster node to deinstall the 3PAR MPIO software and move all cluster resources off of this node and on to alternate cluster nodes.

On all cluster nodes, (except the cluster node chosen in step 1), set the startup type to Manual as follows: a a b On the Windows desktop, right click My Computer and then click Manage . In the left pane tree control, click Services and Applications . In the right pane, double-click Cluster Service , right-click Service , and then click Properties . c In the Cluster Service Properties dialog box that appears, set Startup type to Manual (Figure 3-6).

3PAR MPIO and MSCS Environments

3.17

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

Figure 3-6. Setting Startup Type to Manual

d 3

Click OK .

On the designated cluster node chosen in step 1, set the startup type to Automatic and stop cluster service. To stop cluster service, in the Cluster Service Properties dialog box, set Startup type to Automatic and then click Stop .

Deinstall existing 3PAR MPIO software from the stopped cluster node. See Deinstalling on page 3.11 for details.

Shut down all other cluster nodes on which 3PAR MPIO software is installed. Do not shut down the cluster node from which you deinstalled 3PAR MPIO software in step 4.

6 7

Reboot the stopped cluster node. After rebooting the stopped node, confirm that cluster services are running and that Startup type is set to Automatic .

Boot one of the cluster nodes that was shut down in step 5 and deinstall 3PAR MPIO software. After deinstalling the software, be sure to reboot the cluster node and then

3.18

3PAR MPIO and MSCS Environments

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

follow the instructions in step 9 to set Startup type to Automatic and start cluster service. 9 On the cluster node from which you deinstalled 3PAR MPIO software in step 4, set Startup type to Automatic and start cluster service as follows: a a b On the Windows desktop, right click My Computer and then click Manage . In the left pane tree control, click Services and Applications . In the right pane, double-click Cluster Service , right-click Service , and then click Properties . c In the Cluster Service Properties dialog box that appears, set Startup type to Automatic and then click Start . d Click OK.

10 Repeat step 8 for each of the remaining cluster nodes until all cluster nodes have 3PAR MPIO software deinstalled and cluster service is restarted on all. 11 If necessary, redistribute the groups to reflect the configuration in use prior to installing 3PAR MPIO software.

3.6.3 Online Upgrade of MPIO Software (MSCS Environments)

Use the following procedures to upgrade 3PAR MPIO software on a cluster node where 3PAR MPIO for MSCS has been previously installed.

CAUTION: As part of the online upgrade of 3PAR MPIO software, you must actually perform the upgrade of the 3PAR MPIO software on the cluster node within the MSCS environment. The active cluster node still provides access to the client during this procedure, but this accessibility will be disrupted for a brief period while cluster resources are moving between cluster nodes.

1 2

Designate an idle cluster node to use in performing the software upgrade. On the cluster node to be upgraded, move all cluster resources out from the current cluster node and shut down cluster service as follows: a On the cluster nodes Windows desktop, click Start , point to Programs and then Administrative Tools . Click Cluster Administrator and then click Manage .

3PAR MPIO and MSCS Environments

3.19

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

In the left pane tree control of the Cluster Administrator window, right-click the cluster group name and then click Move Group (Figure 3-7). The system moves the cluster resources from the active to an idle cluster mode, making the cluster node idle.

Figure 3-7. Moving a Group in the Cluster Administrator Window

On the cluster nodes Windows desktop, right-click My Computer and then click Manage .

d e

In the left pane tree control, click Services and Applications . In the right pane, double-click Services , right-click Cluster Service , and then click Properties .

In the Cluster Service Properties dialog box that appears, set Startup type to Manual and then click Stop (Figure 3-8).

3.20

3PAR MPIO and MSCS Environments

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

Figure 3-8. Setting Startup Type to Manual

g 3

Click OK .

Upgrade existing 3PAR MPIO software from the idle cluster node as described in Upgrading on page 3.10.

4 5

Reboot the idle cluster node if this has not been done in step 3. Start cluster service on the idle cluster node (so that it joins the cluster) and set Startup type to Automatic as follows: a On the idle cluster nodes Windows desktop, right click My Computer and then click Manage . b c In the left pane tree control, click Services and Applications . In the right pane, double-click Services , right-click Cluster Service and then click Properties . d In the Cluster Service Properties dialog box that appears, set Startup type to Automatic and then click Start .

3PAR MPIO and MSCS Environments

3.21

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

e 6

Click OK.

Move all the cluster resources from the active cluster node to the cluster node with the upgraded 3PAR MPIO software. This makes the node with the newer version of 3PAR MPIO software the only active node.

For each additional cluster node, repeat step 1 on page 3.19 through step 5 on page 3.21, skipping step 2 on page 3.19 (moving the cluster resource).

If necessary, reset the active cluster node after all cluster nodes have been upgraded with the new software.

3.22

3PAR MPIO and MSCS Environments

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

4 Using the 3PAR MPIO CLI

In this chapter
4.1 Overview of the 3PAR MPIO CLI 4.2 mpiocli Command 4.3 Using the 3PAR MPIO CLI 4.3.1 Getting Setting Information 4.3.2 Setting Load Balance Policy 4.3.3 Setting Event Log Level 4.1 4.2 4.7 4.7 4.7 4.8

4.1 Overview of the 3PAR MPIO CLI

mpiocli.exe is included in the 3PAR Multipath I/O for Windows package. The path
environment will be set when 3PAR Multipath I/O for Windows is installed.

Using the 3PAR MPIO CLI

4.1

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

4.2 mpiocli Command

COMMAND mpiocli DESCRIPTION

This is the command line utility command for 3PAR Multipath I/O for Microsoft Windows.

SYNTAX mpiocli [options <arg>] OPTIONS -help

Displays online help for 3PAR Multipath I/O for Microsoft Windows.

-f [<filename>]
Specifies the name of the output file. Required with the -info option. If

<filename> is not specified, the default filename mpiocli.log is used. The

filename is located under the windows system directory.

-d <Physical_Disk_Number>
Displays the device information specified in the physical disk number(s), for example

-d 3 or -d 4,11,12. -info [-pd] [-d Physical_Disk_Number(s)][-f <filename>]

Displays 3PAR MPIO settings, system information and device information for all devices, including mounted volumes with drive letters or mount directories.

-setevt <levels>
Sets the Windows system event log level for 3PAR MPIO as follows (rebooting the host server is not required once the level is specified):
0 1 2

- Only display error messages. - Display warning messages plus level 0. - Display information messages plus level 0 and level 1. Display SCSI-3 reservation information plus level 0, level 1, and level 2.

3-

4.2

mpiocli Command

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

-setlb <lbmode> [-p <Path_ID>] [-w <Path_Weight>] [-d <Physical_Disk_Number>]

This option sets the device load balance policy as follows: <lbmode> 1 2 3 Definition Fail Over Only Round Robin Round Robin Subset Required Arguments

-p <Path_ID> - Specifies the active path.

none. All paths are active paths.

-p <Path_ID>...
Specifies the active paths.

4 5

Least Queue Depth Least Weight

none.

-p <Path_ID> -w <Path_Weight>...
Assign a weight to each path. The path with the lowest number will be assigned I/O.

If <-d Physical_Disk_Number> is not specified, the command sets all devices in the system to the same specified load balance policy.

SPECIFIERS
None.

RESTRICTIONS
None.

mpiocli Command

4.3

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

EXAMPLES
Example of mpiocli -info using MPIO 1.0.22:

4.4

mpiocli Command

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

Example of mpiocli -info -pd:

Example of mpiocli -info -pd 3:

mpiocli Command

4.5

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

Example of changing the load balancing policy only disk 3 from 2 (RoundRobin) to 1(FailOverOnly):

NOTES
None.

4.6

mpiocli Command

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

4.3 Using the 3PAR MPIO CLI

This section describes how to use the 3PAR MPIO CLI mpiocli command. For specific details, see: mpiocli Command on page 4.2.

4.3.1 Getting Setting Information

You can query the current 3PAR device for information on each device, including registry settings, adapter information, and device load balance policies as follows. Specifying -f

<filename> collects detailed information for devices such as SCSI logical unit number, bus ID,
port ID, target ID, etc. C:\>mpiocli -info [-pd] [-d <Physical_Disk_Number>] [-f <filename>]

4.3.2 Setting Load Balance Policy

For a description of each policy, see Features on page 2.4.
`

To set the device load balancing to Fail Over Only: C:\>mpiocli -setlb 1 -p <Path_ID> -d <Physical_Disk_Number>

NOTE: If -d <Physical_Disk_Number> is not specified, all devices are set to failover only. The active path is <Path_ID>; all others are passive.

To set the device load balancing to Round Robin: C:\>mpiocli -setlb 2 -d <Physical_Disk_Number>

To set the device load balancing to Round Robin with a subset of paths: C:\>mpiocli -setlb 3 -p <Path_ID>... -d <Physical_Disk_Number>

To set the device load balancing to Least Queue Depth: C:\>mpiocli -setlb 4 -d <Physical_Disk_Number>

Using the 3PAR MPIO CLI

4.7

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

To set the device load balancing to Least Weight: C:\>mpiocli -setlb 5 -p <Path_ID> -w <Path_Weight> -p <Path_ID> -w <Path_Weight>... -d <Physical_Disk_Number>

NOTE: The path with the least weight is the only active path to the device drive. It is recommended to set each path with a different weight, though more than one path may have the same weight. The program randomly choose a healthy path to send I/O if more than one path contains the same least weight. The range of weight that can be assigned is from 0 to 99, with a default weight of 0. New added paths are always assigned to the default weight.

4.3.3 Setting Event Log Level

`

To set event log values for 3PAR MPIO: C:\>mpiocli -setevt <level>

NOTE: MPIOcli sets the 3PAR MPIO Event Log Level through WMI. It is not required to reboot the host server in order to take effect.

4.8

Using the 3PAR MPIO CLI

3PAR Confidential

3PAR MPIO 1.0.23 Users Guide

Revision History
Release level 320-200215 Rev A March 2010 Revision summary First release of this manual to support the release of 3PAR Multipath I/O for Microsoft Windows, version 1.0.23. Previous versions of this document were published under part number 320-200184.

Revision History

RH.1

3PAR MPIO 1.0.23 Users Guide

RH.2
3PAR Confidential