PowerPath for Windows Version 5.5

EMC CorporationCorporate Headquarters:

EMC® PowerPath® and PowerPath/VEfor Microsoft Windows

Version 5.5

Installation and Administration GuideP/N 300-010-646

REV A03

Hopkinton, MA 01748-9103

1-508-435-1000www.EMC.com

2

Copyright © 1997 - 2011 EMC Corporation. All rights reserved.

Published March, 2011

EMC believes the information in this publication is accurate as of its publication date. The information issubject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THISPUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY ORFITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicablesoftware license.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

All other trademarks used herein are the property of their respective owners.

EMC PowerPath and PowerPath/VE for Windows Version 5.5 Installation and Administration Guide

Contents

Preface ............................................................................................................................. 9

Chapter 1 Installing PowerPathBefore you install .............................................................................. 16

EMC Symmetrix storage systems.............................................16EMC VNX OE and CLARiiON storage systems ....................16Obtaining up-to-date information............................................17Choose a convenient time..........................................................17License keys................................................................................ 17Preparing the host and storage system ...................................18Booting from a storage array device ........................................19Preparing a cluster environment..............................................20Installing PowerPath before configuring the network..........20Installing in virtual environments............................................20Coexistence with third-party path management software...22

Before you upgrade or apply a service pack................................. 23Requirements and limitations...................................................24Upgrading PowerPath custom file conversion ......................25

Installation procedures..................................................................... 26Interactive GUI installation (default method) ........................26CLI installation........................................................................... 29

After you install or upgrade............................................................ 33First time installations................................................................33Verify the configuration.............................................................33Configure the PowerPath Management Pack for MOM.......33

Adding features to an existing installation ................................... 35Add features through the GUI..................................................35Add features through the CLI...................................................36

PowerPath installation troubleshooting........................................ 37

EMC PowerPath and PowerPath/VE for Windows Version 5.5 Installation and Administration Guide 3

Contents

Upgrading Windows operating systems ...................................... 39Upgrading to Windows Server 2008 and Windows Server2008 R2 ......................................................................................... 39Installing Windows operating system service packs ............ 40

Unsupported installation changes ................................................. 41No host reboot after installation changes ............................... 41Downgrading PowerPath.......................................................... 41

Chapter 2 Configuring PowerPathIntroduction....................................................................................... 44Adding new paths to a PowerPath logical device ....................... 45Adding new logical devices to the PowerPath configuration.... 46Removing some paths to PowerPath logical devices .................. 48Removing PowerPath logical devices............................................ 49Configuring the Microsoft iSCSI Initiator for PowerPath .......... 52

Chapter 3 Removing PowerPathBefore you remove PowerPath ....................................................... 54

Removing PowerPath software or components .................... 54Uninstalling PowerPath with Windows OS tools........................ 55

Complete PowerPath removal.................................................. 55Feature-specific removal ........................................................... 56

Uninstalling with the PowerPath command line......................... 58PowerPath uninstallation troubleshooting ................................... 61Disconnecting redundant paths to the storage system ............... 62

Chapter 4 Managing PowerPathOverview............................................................................................ 64PowerPath monitor .......................................................................... 64

Launching MMC with the PowerPath snap-in ...................... 65PowerPath registration tools........................................................... 67

PowerPath Licensing Tool ........................................................ 67emcpreg command..................................................................... 67

PowerPath Administrator ............................................................... 68PowerPath Administrator panes.............................................. 68PowerPath Administrator device properties dialog box...... 69Icons: standard, unlicensed, and unknown conditions ........ 71Icons: known failure conditions ............................................... 72Undefined SP conditions........................................................... 73

Local or remote administration ...................................................... 75Setting a local host option ......................................................... 76

EMC PowerPath and PowerPath/VE for Windows Version 5.5 Installation and Administration Guide4

Contents

Setting a remote host option......................................................77Saving and loading Administrator settings .................................. 79

Saving a configuration .............................................................. 79Loading a configuration............................................................ 79

Saving MMC console settings ......................................................... 80PowerPath and Systems Management Server (SMS)................... 81Windows Server 2008 Support........................................................ 82Audit and error log messages ......................................................... 83

Chapter 5 PowerPath in an MSCS ClusterInstalling PowerPath and MSCS..................................................... 86Integrating PowerPath into an existing MSCS cluster................. 87

Moving all resources to node A................................................88Installing PowerPath on node B ...............................................88Configuring additional paths between the storage systemand node B ...................................................................................88Moving all resources to node B.................................................89Installing PowerPath on node A...............................................89Configuring additional paths between the storage systemand node A...................................................................................89Returning node A resources to node A ...................................89Checking for host ID uniqueness..............................................90

Chapter 6 PowerPath in a Veritas Cluster ServerInstalling PowerPath and VCS........................................................ 92Installing PowerPath in an existing VCS environment ............... 93

Appendix A WHQL CertificationWHQL-certified driver..................................................................... 96

Appendix B Files Changed by PowerPathFiles created by PowerPath installation......................................... 98

Index .............................................................................................................................. 105

5EMC PowerPath and PowerPath/VE for Windows Version 5.5 Installation and Administration Guide

Contents


Title Page

Tables

1 Supported upgrade paths ..............................................................................242 CLI parameters and properties .....................................................................303 Troubleshooting scenarios .............................................................................374 CLI parameters and properties .....................................................................595 Troubleshooting scenarios .............................................................................616 PowerPath monitor taskbar icons .................................................................657 Icons on the PowerPath Administrator ........................................................718 Icons of known PowerPath failure conditions ............................................729 Icons of undefined SP PowerPath failure conditions .................................74


Tables


Preface

As part of an effort to improve and enhance the performance and capabilitiesof its product lines, EMC periodically releases revisions of its hardware andsoftware. Therefore, some functions described in this document may not besupported by all versions of the software or hardware currently in use. Forthe most up-to-date information on product features, refer to your productrelease notes.

If a product does not function properly or does not function as described inthis document, please contact your EMC representative.

Audience This manual is part of the PowerPath documentation set. It isintended for use by storage administrators and other informationsystem professionals responsible for installing, using, andmaintaining PowerPath software.

Readers of this manual are expected to be familiar with the hostoperating system, storage system management, and the applicationsused with PowerPath software.

Relateddocumentation

Here is the complete set of PowerPath documentation. All manualsare available on the EMC Powerlink website:

◆ EMC PowerPath Family Product Guide

◆ EMC PowerPath Family CLI and System Messages Reference Guide

◆ EMC PowerPath and PowerPath/VE Family for Microsoft WindowsRelease Notes

◆ EMC PowerPath Family for Windows Release Notes

◆ EMC PowerPath Encryption with RSA User Guide

◆ EMC PowerPath Migration Enabler User Guide


10

Preface

◆ EMC PowerPath Management Pack for Microsoft Operations ManagerUser Guide

If your environment includes EMC Symmetrix storage systems, referalso to the EMC host connectivity guides, which are available on theEMC Powerlink website http://Powerlink.EMC.com.

If your environment includes EMC VNX OE and CLARiiON storagesystems, refer also to the following manuals:

◆ EMC host connectivity guides

◆ VNX OE Storage-System Support website(www.EMC.com/vnxsupport)

◆ CLARiiON Storage-System Support website(www.EMC.com/clariionsupport)

Revision History The following table presents the revision history of this document.

Conventions used inthis document

EMC uses the following conventions for special notices.

Note: A note presents information that is important, but not hazard-related.

CAUTION!A caution contains information essential to avoid data loss ordamage to the system or equipment.

Revision Date Description

A01 September 3, 2010 First release of the EMC PowerPath for WindowsVersion 5.5 Installation and Administration Guide

A02 September 15, 2010 Added uninstallation message in a Windows 2008 R2boot-from-SAN configuration. Added PowerPathConfiguration Checker (PPCC) references. UpdatedPowerlink references.

A03 March 22, 2011 Added VNX OE storage system references andupdated licensing information. Added runemcphostid check to check for conflicts in clusterenvironments.


http://powerlink.emc.com

Preface

Typographical conventionsEMC uses the following type style conventions in this document:

Where to get help EMC support, product, and licensing information can be obtained asfollows.

Normal Used in running (nonprocedural) text for:• Names of interface elements (such as names of windows,

dialog boxes, buttons, fields, and menus)• Names of resources, attributes, pools, Boolean expressions,

buttons, DQL statements, keywords, clauses, environmentvariables, filenames, functions, utilities

• URLs, pathnames, filenames, directory names, computernames, links, groups, service keys, file systems, notifications

Bold: Used in running (nonprocedural) text for:• Names of commands, daemons, options, programs,

processes, services, applications, utilities, kernels,notifications, system call, man pages

Used in procedures for:• Names of interface elements (such as names of windows,

dialog boxes, buttons, fields, and menus)• What user specifically selects, clicks, presses, or types

Italic: Used in all text (including procedures) for:• Full titles of publications referenced in text• Emphasis (for example a new term)• Variables

Courier: Used for:• System output, such as an error message or script• URLs, complete paths, filenames, prompts, and syntax when

shown outside of running text

Courier bold: Used for:• Specific user input (such as commands)

Courier italic: Used in procedures for:• Variables on command line• User input variables

< > Angle brackets enclose parameter or variable values supplied bythe user

[ ] Square brackets enclose optional values

| Vertical bar indicates alternate selections - the bar means “or”

{ } Braces indicate content that you must specify (that is, x or y or z)

... Ellipses indicate nonessential information omitted from theexample


12

Preface

Product information — For documentation, release notes, softwareupdates, or for information about EMC products, licensing, andservice, go to the EMC Powerlink website (registration required) at:

http://Powerlink.EMC.com

Technical support — For technical support, go to EMC CustomerService on Powerlink. To open a service request through Powerlink,you must have a valid support agreement. Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account.


Preface

Your comments Your suggestions will help us continue to improve the accuracy,organization, and overall quality of the user publications. Please sendyour opinion of this guide to:

[email protected]

If you have issues, comments, or questions about specific informationor procedures, please include the title and, if available, the partnumber, the revision (for example, A01), the page numbers, and anyother details that will help us locate the subject you are addressing.


14

Preface


1Invisible Body Tag

This chapter includes the following sections:

◆ Before you install................................................................................ 16◆ Before you upgrade or apply a service pack.................................. 23◆ Installation procedures...................................................................... 26◆ After you install or upgrade............................................................. 33◆ Adding features to an existing installation .................................... 35◆ PowerPath installation troubleshooting ......................................... 37◆ Upgrading Windows operating systems........................................ 39◆ Unsupported installation changes................................................... 41

Installing PowerPath

Installing PowerPath 15

16


Before you installThe sequence of steps to configure a storage system and install EMC®

PowerPath® or PowerPath/VE for Windows Hyper-V on a hostdepends on the storage system you use.

Note: Throughout this document, all references to PowerPath refer toPowerPath and PowerPath/VE for Windows Hyper-V, unless otherwisenoted. PowerPath/VE for Windows Hyper-V provides the samemultipathing functionality as PowerPath for Windows in nonvirtualenvironments, and it supports Migration Enabler and PowerPath Encryptionwith RSA.

EMC Symmetrix storage systemsInstall PowerPath after you set up the EMC Symmetrix® storagesystem and verify that it is working properly.

EMC VNX OE and CLARiiON storage systemsPowerPath installation is an integral part of an EMC VNX™Operating Environment (OE) and CLARiiON® setup andconfiguration procedure.

For information on when to install PowerPath on a host attached to aVNX OE or CLARiiON storage system, refer to the:

◆ VNX OE Storage-System Support website(www.emc.com/vnxsupport)

◆ CLARiiON Storage-System Support website(www.emc.com/clariionsupport). From the home page, selectyour storage system type, then use the Attach server link (CX4systems) or the Install link (all other systems) to generatestep-by-step instructions.

CLARiiON AX-series installation, planning, and troubleshootingdocuments are located on the AX-series support website. Forinformation on accessing the site, refer to the support documentationthat shipped with your storage system. Refer to these documents forprescribed installation information only when AX-series storagesystems are used.



Obtaining up-to-date informationCheck the Powerlink website for current information:

❑ PowerPath documentation — EMC updates PowerPathdocumentation when it releases new features with a service packor when documentation errors are reported. To obtain updatedPowerPath documentation on Powerlink, select Support >Technical Documentation.

❑ Service packs and upgrades — You can download PowerPathservice pack software from Powerlink. Determine which servicepacks (if any) to install after PowerPath, and whether thoseservice packs have any additional installation prerequisites. Toobtain service packs on Powerlink, select Support > Downloads.

Choose a convenient timeInstalling PowerPath requires that you reboot the host. Plan to installor upgrade PowerPath when a reboot will cause minimal disruptionto your site.

License keys The PowerPath for Windows license registration key is on the LicenseKey Card that you received from EMC. The PowerPath/VE forWindows Hyper-V license key is activated through the PowerlinkLicensing portal. When you purchase PowerPath/VE for WindowsHyper-V, the registered user on the software order receives an emailor letter that provides instructions for activating the license at thePowerlink Licensing portal.

Note: The PowerPath/VE for Windows Hyper-V key is required to licensePowerPath in Windows Hyper-V environments.

License ordering and activationEffective February 15, 2011, instead of the physical Right To Use(RTU), the default delivery method for PowerPath licenses iselectronic. An electronic License Authorization Code (LAC) is sentby email in order to redeem the license key on the PowerlinkLicensing portal. This does not affect upgrades because PowerPathretains existing license information.

Physical RTU cards are still available as an option. EMC GlobalSupport, at 1-800-svc4emc or 1-800-782-4362, can provide more

Before you install 17

18


information. The EMC PowerPath Family Electronic License OrderingProcess Technical Notes, available on Powerlink, provides moreinformation about the PowerPath license electronic ordering process.

Take note of the following regarding licenses:

◆ In nonvirtual environments, installing PowerPath on a hostconnected exclusively to a CLARiiON AX-series array does notrequire a license. PowerPath provides full support, with orwithout a PowerPath license, when the host is connectedexclusively to a CLARiiON AX-series array.

◆ If you are upgrading from an earlier version of PowerPath, youdo not need to reregister. PowerPath will use your old key.

◆ Separate license keys are required to enable PowerPath MigrationEnabler or PowerPath Encryption with RSA®. If you are usingPowerPath Encryption with HBA-assist, use the same PowerPathEncryption license key as for PowerPath software-basedencryption. A separate key is required to license PowerPath/VEfor Windows Hyper-V.

◆ Type the registration number exactly as it appears on the card orletter. To reduce common typographical errors, the License Keyfield accepts either uppercase or lowercase letters, and certainnumbers and letters are interchangeable. Specifically, an entry ofthe alphabetic letters O, I, S, and B is equivalent to an entry of thenumbers, 0, 1, 5, and 8.

If you have additional questions about entering licenses, consult theonline help file by pressing F1 from the EMC Licensing Tool. Youmust have Internet Explorer 5.0 or later to view these files. If you donot have this browser installed, you may still view the help file,EmcLicTool.chm, directly from the \help folder on the PowerPathinstallation CD.

Preparing the host and storage systemPrepare the host and storage system:

❑ Go to Powerlink and verify your environment meets therequirements found in the EMC PowerPath for Windows ReleaseNotes and the E-Lab™ Interoperability Navigator by running thePowerPath Configuration Checker (PPCC). For PPCC installationinformation, the EMC PowerPath Configuration Checker User Guide,available on Powerlink, provides additional information.



❑ The EMC PowerPath and PowerPath/VE Family for Windows ReleaseNotes includes the qualified Microsoft MPIO framework versions.

• If the required MPIO framework is not installed on the host,the PowerPath installer prompts you to install it.

• If an unsupported version of the MPIO framework is installedon the host, the PowerPath installer prompts you to upgradeto the supported version. If you do not upgrade, thePowerPath installation aborts.

• If a version of MPIO framework later than the supportedversion is installed, PowerPath provides the option to abortthe installation.

Note: MPIO technologies and functionality are unique to eachoperating system. Refer to the documentation provided by youroperating system manufacturer for specific information.

❑ Configure HBA drivers. Be sure to follow the HBA driverconfiguration guidelines outlined in the E-Lab InteroperabilityNavigator and the HBA vendor documentation. The use ofimproper settings can cause erratic failover behavior, such asgreatly increased I/O delays.

❑ For hosts connected to storage arrays through a Fibre Channelswitch (that is, a fabric), configure the HBAs by using persistentbinding for SCSI target IDs.

❑ For first-time installations, remove any version of EMCNavisphere® Application Transparent Failover (ATF) installed onthe host.

CAUTION!The procedure for migrating from ATF or CLARiiON DriverExtension (CDE) to PowerPath is not straightforward. Use EMCProfessional Services to perform the migration. If you performthe migration yourself, you risk the loss of data.

Booting from a storage array deviceThe following documents provide instructions for configuring astorage array device as the boot device:


20


◆ EMC Fibre Channel with Emulex Host Bus Adapters in the WindowsEnvironment, available on the Emulex website.

◆ EMC Fibre Channel and iSCSI with QLogic Host Bus Adapters in theWindows Environment, available on the QLogic website.

Preparing a cluster environmentChapter 5, "PowerPath in an MSCS Cluster," provides information oninstalling PowerPath in a new or existing cluster.

Installing PowerPath before configuring the network

PowerPath uses the network MAC address to establish a uniqueidentifier for cluster reservations. If PowerPath is installed before anynetwork connections are configured then PowerPath is unable toestablish the unique host identifier.

To install PowerPath before configuring the network:

Note: EMC recommends installing PowerPath after configuring the network.

1. Install PowerPath as described in "Installation procedures" onpage 26.

2. Configure the network.

3. Run the emcphostid utility located in the<installdir>\EMC\PowerPath directory.

The EMC PowerPath Family CLI and System Messages ReferenceGuide provides more information on the emcphostid utility.

4. Restart the host.

Installing in virtual environmentsThe procedure to install PowerPath in virtual environments is thesame as the procedure to install in physical environments. You canfollow the GUI or the CLI installation procedure described in thisdocument.

EMC supports iSCSI connections directly attached to EMC storageusing the Microsoft Initiator in a child partition. In this configurationPowerPath is supported in a child partition to manage multiple iSCSI



paths. However, pass-through disks are not supported when runningEMC PowerPath. For more information on the supported virtualenvironments, refer to the EMC PowerPath and PowerPath/VE Familyfor Windows Release Notes and the E-Lab Interoperability Navigator.


22


Coexistence with third-party path management softwarePowerPath can coexist with MPIO-based third-party pathmanagement software such as:

◆ Hitachi Dynamic Link Manager (HDLM)

◆ IBM Subsystem Device Driver (SDD)

◆ HP StorageWorks Secure Path

◆ HP StorageWorks AutoPath XP Virtual Array

◆ Microsoft MPIO (native multipathing)

PowerPath cannot co-manage devices with third-party pathmanagement software.

When PowerPath coexists with other multipathing software, theHBA cannot be shared between the two.



Before you upgrade or apply a service packBefore upgrading PowerPath or installing a service pack:

1. Go to Powerlink and do the following:

a. Check for the most current information. EMC updates releasenotes periodically and posts them on Powerlink.

b. Download the latest version of EMC Reports, available onPowerlink, and then run the PowerPath ConfigurationChecker (PPCC).

c. Download the PowerPath software on Powerlink at Support >Downloads and save it to your local directory.

2. Save the current PowerPath configuration.

• Run the powermt save command to ensure that you havesaved the latest PowerPath configuration information.

or

• In PowerPath Administrator, right-click the root node andselect All Tasks > Save Config as. Then specify a file nameand click Save.

3. Stop powermt display if it is running.

4. Uninstall any PowerPath hot fixes on the host. Use Add/RemovePrograms or Programs and Features to verify if hot fixes areinstalled.

5. If upgrading, review the information in "Requirements andlimitations" on page 24.

6. Install PowerPath, as described in "Installation procedures" onpage 26.

7. If installing a service pack, verify the configuration is correct andthen save it. This ensures the configuration file is updated to thecurrent format.

Note: PowerPath stores configuration information in a file that may beloaded at boot time. When using the PowerPath Administrator, theconfiguration file can be saved only under the default filename. After aservice pack is applied, the format of the configuration file may changeso it is no longer backward compatible.

Before you upgrade or apply a service pack 23

24


Requirements and limitationsBefore upgrading, ensure your environment meets theserequirements and note any limitations that apply:

◆ Do not remove redundant cable connections from the array.

◆ You can upgrade directly to PowerPath 5.5 from the versionsshown in the following table, meaning you do not need touninstall the earlier version before installing version 5.5.

If you have a version not listed in Table 1, uninstall that version ofPowerPath (for example, PowerPath 2.1.3), reboot, and thenperform a fresh installation of PowerPath 5.5.

◆ Windows Server Core 2008—If PowerPath is installed throughthe GUI on the core version, the license key dialog box will notappear. Use the emcpreg utility to add the license key beforerebooting. "PowerPath registration tools" on page 67 containsmore information.

◆ Upgrading from 4.5.x to 5.5— If you are upgrading fromPowerPath 4.5.x to 5.5, use either the interactive GUI or theinteractive CLI method.

Table 1 Supported upgrade paths

Windows versionYou can upgrade directlyfrom these versions

PowerPathiSCSI version

Windows Server 2003, x86-based version(minimum of SP1)

4.5.x, 4.6.x, 5.0.x, 5.1.x,5.2.x, and 5.3.x

1.1a

Windows Server 2003, Itanium-basedversion (minimum of SP1)

4.5.x, 4.6.x, 5.0.x, 5.1.x,5.2.x, and 5.3.x

Not supported

Windows Server 2003, x64-based version 4.5.x, 4.6.x, 5.0.x, 5.1.x,5.2.x, and 5.3.x

Not supported

Windows Server 2008 5.1 SP2, 5.2.x, and 5.3.x Not supported

Windows Server 2008 Server Core 5.1 SP2, 5.2.x, and 5.3.x Not supported

Windows Server 2008 R2 5.3.x Not supported

a. If you have a valid PowerPath iSCSI 1.1 license key installed, it will beconverted to a PowerPath base license, which provides the sameprotection as a PowerPath iSCSI license key.



◆ Upgrading PowerPath in a boot from SAN environment—Youcan upgrade PowerPath in a boot from SAN environment usingthe same procedure you would use in other environments.

Upgrading PowerPath custom file conversionWhen the powermt.custom file is stored in a location other than thedefault location, the custom file will not be converted whenupgrading PowerPath. This may cause error messages to appear afterupgrading to PowerPath and running powermt load. If you upgradePowerPath without converting the powermt.custom file, you mustrecreate the settings in PowerPath 5.5.

In order for the upgrade to convert the powermt.custom file, performthe following before beginning the upgrade:

1. Copy the powermt.custom file to the default<PowerPath_Installation_Directory>\PowerCommon directory.

2. During the upgrade, when prompted, select to keep the existingcustom file.

After the upgrade and reboot, the settings saved in thepowermt.custom file will be automatically loaded.

Before you upgrade or apply a service pack 25

26


Installation proceduresYou can install PowerPath with the default GUI method or throughthe CLI. Refer to one of the following procedures to installPowerPath.

Note: You must have administrative rights to install PowerPath.

◆ "Interactive GUI installation (default method)" on page 26

◆ "CLI installation" on page 29

PowerPath creates the PowerPath_V55 installation log and theppinstall_info post-installation log by default that can be used forproblem analysis after an installation.

Interactive GUI installation (default method)To install PowerPath with the default interactive prompts:

1. If the PowerPath executable file is saved on your local system, goto Step 2. To install from the software CD:

a. Load the CD. If autoplay is enabled, your browser launchesthe Getting Started page. If autoplay is not enabled, go toStep 2.

b. Click the appropriate link for your operating system and thenselect Run this program from its current location.

c. Click OK.

2. Double-click the PowerPath executable file, or, click Start andselect Run.

In the Run window, browse to or enter the name of thePowerPath installation program:

<drive>:\<PowerPath_pkg_name>

3. Click OK.

4. On the Open File - Security Warning dialog box, click Run.

5. On the Choose Setup Language screen, select the language forthis installation from the list and click OK.



Localized versions of the PowerPath installer are available inBrazilian Portuguese, Latin American Spanish, French, German,Italian, Japanese, Korean, and simplified Chinese.

6. Click Install to install Visual C++ 8.0 run-time components.

Visual C++ 8.0 is a prerequisite to PowerPath installation.

7. In the setup wizard welcome window, click Next.

8. On the CLARiiON AX-series screen, select Yes if the host isconnected exclusively CLARiiON AX series arrays. Otherwise,click No. Click Next.

9. Type your name and organization on the Customer Informationscreen and click Next.

10. Click Next to install PowerPath in the default directory(recommended).

CAUTION!Do not specify the Windows System directory for your system(indicated by the %SYSTEMROOT% environment variable).PowerPath will not function correctly if it is installed in thisdirectory.

11. On the Setup Type dialog box, select the appropriate install typeas follows:

• Typical Install—Installs PowerPath multipathing forSymmetrix, VNX OE, and CLARiiON arrays; if you areupgrading, features present in your current configuration areselected and installed by default.

• Custom Install—Allows you to select features for installation.Features include Migration Enabler, Encryption with RSA,and support for Celerra, Invista (including VPLEX) andthird-party arrays.

– Click the arrow and select one of the following from thedrop-down menu:- This feature will be installed on local hard drive

- This feature, and all subfeatures, will be installed on thelocal hard drive

– Click Space to view the required and available spaceneeded to install selected features.

Installation procedures 27

28


• Complete Install—Installs all PowerPath features andcomponents, including Migration Enabler, Encryption withRSA, and components to support EMC and third-party arrays.

12. Click Next once you have selected the install type and features.

13. In the Ready to Install the Program dialog box, click Install.

a. If PowerPath detects that files that need to be updated arecurrently in use, select one of the following options:

– Automatically close and attempt to restart applications.– Do not close applications (A reboot will be required.)If PowerPath does not detect files currently in use, proceed toStep c.

b. Click OK.

c. On the Windows Security dialog box, click Install to install thedevice software.

Optionally, select Always trust software from <device vendor>.

d. If there is no license in the registry, the EMC Licensing Toolappears.

When prompted by the EMC Licensing Tool, type your24-digit registration number in the License Key field, and thenclick Add.

Note:—When upgrading PowerPath, the existing license key is saved and

no input is required.—To enable Migration Enabler, PowerPath Encryption with RSA, or

additional array support, enter the license key or keys.

e. Click OK.

14. In the InstallShield Wizard Completed dialog box, click Finish.

15. In the setup wizard, click Yes to reboot now or No to reboot later.

16. If you performed a Custom Install or a Complete Install, and youare not planning to use the PowerPath Migration Enabler orPowerPath Encryption with RSA features, EMC recommends thatyou disable these services and change the Startup type todisabled.



Note: When Encryption services are enabled, Migration services areautomatically enabled.

17. When the host restarts, follow the instructions in "After youinstall or upgrade" on page 33.

CLI installation To install PowerPath using the more advanced command lineinterface, follow these steps.

1. Use this command syntax to install PowerPath:

<drive>:\<PowerPath_pkg_name> <install_parameters> <logfile> <Property>=<Value>"

• For a silent installation, which does not require user input, usethis syntax:

Note: Silent installation errors are logged in <logfile>, the locationspecified in the installation command. No error message appears inthe PowerPath Administrator GUI.

<drive>:\<PowerPath_pkg_name> /s /v"/q /L*v <logfile> <Property>=<Value>"

• For an interactive installation, which requires user input, usethis syntax:

<drive>:\<PowerPath_pkg_name> /v"/L*v <logfile> <Property>=<Value>"

Where:

– <drive> is the drive letter, for example, C.– <PowerPath_pkg_name> is the PowerPath package name.

For example, EMCPP.x86_32.5.5.0.GA.exe orEMCPP.x86_x64.5.5.0.GA.exe

– <install_parameters> is one or more parameters described inTable 2 on page 30.

– <logfile> creates the log file where the log message will besent, for example, C:\logs\PPsetup.log.

– Ensure the specified directory exists within the specifiedpath.

– <Property>=<Value> is one or more optional propertiesdescribed under the /v parameter in Table 2 on page 30.


30


Example: Silent installation

To install PowerPath using the silent installation method and toalso set the PowerPath license, disable reboot, and installMigration Enabler, enter:

Note: Silent installations include the /s and /q parameters.

C:\EMCPP.x86_32.5.5.0.GA.exe /s /v"/q /L*v C:\logs\PPsetup.logLICENSENUM=0000-0000-0000-0000-0000-0000 NO_REBOOT=1 ADDLOCAL=ME"

Example: Interactive installation

To install PowerPath using the interactive CLI method and to setthe PowerPath license, copy, and install PowerPath files toC:\Test folder, disable reboot, and install components to supportIBM ESS and Hitachi arrays, enter:

C:\EMCPP.x86_32.5.5.0.GA.exe /v"/L*v C:\Install_IBM_HDS.logLICENSENUM=0000-0000-0000-0000-0000-0000 INSTALLDIR=C:\TestNO_REBOOT=1 ADDLOCAL=IBM,HDS"

2. After installing PowerPath, restart the host and then follow theinstructions in "After you install or upgrade" on page 33.

If you performed a complete install, and you are not planning touse the PowerPath Migration Enabler or PowerPath Encryptionwith RSA features, EMC recommends that you disable theseservices and change the Startup type to disabled.

Note: When Encryption services are enabled, Migration services areautomatically enabled.

CLI parameters Table 2 describes command line parameters and options.

Table 2 CLI parameters and properties (1 of 3)

Parameters Description

/s Suppresses installation shield dialog boxes.



/v Directs InstallShield to pass the specified string (enclosed in quotes) to the Microsoft Installer (MSI).Example:/v"<Property>=<Value>"

Where:<Property> and <Value> descriptions follow.

Property Value description

LICENSENUM=<number>

Where <number> must be a valid license or no license will be saved.

INSTALLDIR=<path>

Where <path>= Location to copy and install PowerPath files.Examples:INSTALLDIR=C:\Test

INSTALLDIR=C:\Program Files\EMC

NO_REBOOT=1 The value 1 specifies that the host will not reboot after PowerPath is installed.

Note: EMC recommends NO_REBOOT=1 so that you can manually restart at aconvenient time.

UPGRADE_MPIO=1

The value 1 specifies to upgrade the existing MPIO framework. Include this propertyif an MPIO version earlier than the one supported is installed. PowerPath installationaborts if the host has a version of the MPIO framework earlier than the supportedversion. Refer to the release notes for supported versions.

ADDLOCAL=<feature>

Where <feature> can be any combination of the following items.

Note:—Use commas to separate multiple entries.—PowerPath multipathing for Symmetrix, VNX OE, and CLARiiON arrays is

installed by default.

• ALL= Complete installation• ME = Migration Enabler• RSA = Encryption with RSA• IBM = IBM TotalStorage ESS arrays• CELERRA = Celerra arrays• HDS = Hitachi arrays• HPXP = HP XP arrays• INVISTA = Invista and VPLEX devices (INVISTA will be selected by default)Example:ADDLOCAL=ME,RSA




32


FORCE_DRIVER_UPDATE=1

The value 1 will continue to install PowerPath and ignore the device manager checkfor any pending device installation or uninstallation activities.

/q Indicates a quiet installation (no user interaction).

/L*v<logfile>

Directs the Microsoft Installer to write verbose output to the file specified with this option. The target directoryfor the log file must exist before starting a silent installation by using the logging option (as required by theWindows installer engine).





After you install or upgradeThis section describes post-installation tasks.

First time installationsIf you installed PowerPath for the first time on a host:

1. Power on the host.

PowerPath is now fully configured, with multiple paths to logicaldevices.

2. If the environment is Fibre Channel, ensure zones are configuredappropriately. The VNX OE and CLARiiON storage-systemsupport websites and the host connectivity guides provideadditional information.

3. If you have not already done so, check Powerlink for any servicepacks and install any required service packs.

Verify the configurationTo verify the configuration:

1. Power on the host.

PowerPath is fully configured with multiple paths to logicaldevices and (if appropriate) correct zones when you boot.

2. Verify the correctness of your configuration by running thefollowing at the command prompt:

powermt displaypowermt display dev=allpowermt display ports

Note: If PowerPath sees no devices, but the devices are seen by the operatingsystem, verify that the devices are configured for PowerPath support.

Configure the PowerPath Management Pack for MOMYou can configure the PowerPath management daemon to remotelymonitor specific PowerPath events. This feature is available in aseparate software package available on Powerlink. The management

After you install or upgrade 33

34


daemon integrates with Microsoft Operations Manager and allowsyou to retrieve license and version information from remotePowerPath hosts. It also can generate alerts when paths or volumesremain dead for a configurable time frame. The EMC PowerPathManagement Pack for Microsoft Operations Manager User Guide providesmore information on configuring and using the managementdaemon.



Adding features to an existing installationIf PowerPath is installed on your host and you want to installadditional features, such as Migration Enabler, Encryption with RSA,or components to support third-party arrays, follow one of theseprocedures:

◆ "Add features through the GUI" on page 35

◆ "Add features through the CLI" on page 36

Add features through the GUITo add features to an existing installation using the GUI:

1. Open the Control Panel and double-click Add/Remove Programs(Windows Server 2003) or Programs and Features panel(Windows Server 2008).

2. Select the installed version of PowerPath, and click Change.

3. In the Setup wizard welcome window, click Next.

4. On the Program Maintenance dialog box, select Modify and clickNext.

5. On the Custom Setup dialog box, select the feature you want toinstall from the drop-down menu.

Note:—A selected feature displays a hard drive icon next to it. A red X

indicates the feature is not selected.—The icon next to each feature name indicates the feature’s install state.

Click Help in the Custom Setup dialog box for more informationabout the icons.

6. Select This feature will be installed on local hard drive, andclick Next.

7. In the Ready to Modify the program dialog box, click Install.


9. In the setup wizard, click Yes to reboot now or No to reboot later.

Adding features to an existing installation 35

36


Note: If you are installing Migration Enabler or Encryption with RSAthen a reboot is not required. However, installing Migration Enabler orEncryption with RSA with any other feature requires a reboot.

10. In the Shut Down Windows dialog box, select Restart from thelist and click OK.

Add features through the CLITo add features to an existing installation using the CLI method, usethis command syntax:

<drive>:\<PowerPath_pkg_name> /s /v"/q /L*v <logfile>LICENSENUM=<license_key> NO_REBOOT=1 ADDLOCAL=<feature>"

For example, to install PowerPath Migration Enabler and Invista typethe following on single line:

C:\EMCPP.x86_32.5.5.0.GA.exe /s /v"/q /L*v C:\logs\PPsetup.logLICENSENUM=0000-0000-0000-0000-0000-0000 NO_REBOOT=1ADDLOCAL=ME,INVISTA"

When the NO_REBOOT=1 parameter is used, reboot manually afterinstallation.

Note: If you are installing Migration Enabler or Encryption with RSA then areboot is not required. However, installing Migration Enabler or Encryptionwith RSA with any other feature requires a reboot.

Table 2 on page 30 describes of the parameters and options.



PowerPath installation troubleshootingTable 3 on page 37 lists PowerPath installation troubleshootingscenarios.

Table 3 Troubleshooting scenarios (1 of 2)

Problem Error message Suggested action

PowerPath drivers may be present on ahost where a PowerPath package hasbeen uninstalled.

Incompatible files from aprevious PowerPath versionexist on the host. PowerPathrecommends runningPPRemoveAll with a rebootand then proceed with thePowerPath installationprocess. Run PPRemoveAllnow?

Perform the following:1. Choose Yes to run PPRemoveAlla.

Otherwise, choose No and runPPREMOVE=ALLa manually.

2. Reboot the host.3. Install PowerPath.

Upgrade of PowerPath may fail becausePowerPath drivers are missing on thehost.

PowerPath detected a problemthat is blocking theupgrade. Contact EMCCustomer Support forassistance.

Perform the following:1. Run PPREMOVE=ALL to remove

PowerPath.2. Reboot the host.3. Install PowerPath.

If the installation is still blocked, contactEMC Customer Support.

Upgrade of a PowerPath driver may fail. The PowerPath upgrade couldnot complete. PowerPathrecommends runningPPRemoveAll with a rebootand then proceed with thePowerPath installationprocess. Run PPRemoveAllnow?

Perform the following:1. Choose Yes to run PPRemoveAlla.

Otherwise, choose No and runPPREMOVE=ALLa manually.

2. Reboot the host.3. Install PowerPath.

Installation of a PowerPath driver may fail. PowerPath encountered aproblem installing driversand will roll back theinstallation changes.Contact EMC Customer Supportfor assistance.

Contact EMC Customer Support.

PowerPath installation troubleshooting 37

38


One of more PowerPath drivers mayrequire a host reboot.

One or more PowerPathdrivers require a hostreboot. Reboot the host andthen proceed with thePowerPath installationprocess.

Reboot the host and then installPowerPath.

One or more PowerPathdrivers require a hostreboot. Reboot the host, andretry the repair.

Reboot the host and then try driver repairagain.

Repair of a PowerPath driver fails. The PowerPath repairoperation could notcomplete. Contact EMCCustomer Support forassistance.

Contact EMC Customer Support.

a. The PPRemoveAll utility removes all PowerPath multipathing entries from the host. Use this option only when youencounter a problem with an existing installation or attempt at removal.

Table 3 Troubleshooting scenarios (2 of 2)




Upgrading Windows operating systemsYou can upgrade your Windows operating system to a major release(from Windows Server 2003 to Windows Server 2008 or WindowsServer 2008 R2) or to an operating system service pack.

Note: The EMC E-Lab Interoperability Navigator and the EMCPowerPath and PowerPath/VE for Windows Release Notes provideinformation on the required service packs on different operatingsystems, supported versions of PowerPath, and any other systeminformation that may apply to the operating system you plan toinstall.

Upgrading to Windows Server 2008 and Windows Server 2008 R2When upgrading the operating system in one of the followingscenarios:

◆ From Windows Server 2003 (with PowerPath installed) toWindows Server 2008 or Windows Server 2008 R2

◆ From Windows Server 2008 (with PowerPath installed) toWindows Server 2008 R2

the Windows operating system migration agent does not re-installmost PowerPath drivers during the upgrade. After the upgrade, allPowerPath functionalities are disabled. When upgrading in aboot-from-SAN environment, the operating system upgrade may failand the system may not reboot. This issue is also documented inEMC Knowledgebase Solution emc221704.

Procedure To upgrade the Windows operating system:

1. Remove PowerPath.

2. Upgrade the Windows operating system.

3. Install PowerPath.

The EMC PowerPath and PowerPath/VE Family for Windows ReleaseNotes provides additional information.

Upgrading Windows operating systems 39

40


Installing Windows operating system service packsYou do not need to uninstall PowerPath before installing anoperating system service pack such as when installing Windows 2008SP1 on a Windows 2008 host.



Unsupported installation changesThis section describes unsupported installation changes.

No host reboot after installation changesUninstalling an earlier version of PowerPath without rebooting, andthen installing a newer version may cause a system crash. To avoidthis issue, reboot after installing, uninstalling, or upgradingPowerPath.

Note: When the system is not rebooted after installing, uninstalling, orupgrading PowerPath, the operating system confuses the uninstallation ofold drivers with the installation of new drivers, causing the system panic.

Downgrading PowerPathDo not attempt to install an older version of PowerPath on hostscurrently running a more recent version of PowerPath.

To downgrade PowerPath:

1. Uninstall the newer version of PowerPath.

2. Restart the host.

3. Install the earlier version of PowerPath.

Unsupported installation changes 41

42



2

This chapter contains procedures to reconfigure the operating systemand PowerPath when system configuration changes are made:

◆ Introduction ........................................................................................ 44◆ Adding new paths to a PowerPath logical device ........................ 45◆ Adding new logical devices to the PowerPath configuration..... 46◆ Removing some paths to PowerPath logical devices ................... 48◆ Removing PowerPath logical devices ............................................. 49◆ Configuring the Microsoft iSCSI Initiator for PowerPath............ 52

Configuring PowerPath

Configuring PowerPath 43

44


IntroductionYou must reconfigure PowerPath after making configuration changesthat affect host-to-storage-system connectivity or logical deviceidentification.

For example:

◆ Fibre Channel switch zone changes

◆ Adding or removing Fibre Channel switches

◆ Adding or removing HBAs or storage-system ports

◆ Adding or removing logical devices

◆ Redeploying existing logical devices

Note: If you do not reconfigure PowerPath after making configurationchanges, many of these changes are treated as unintentional, and PowerPathtries to prevent them from affecting applications.

Many platform-specific and some PowerPath reconfigurationoperations will fail if the affected logical devices are in use (either justmarked alive or with I/O in progress). This is noted in theappropriate places in the procedures that follow.

After any reconfiguration, you must monitor the outcome ofindividual reconfiguration steps and confirm that the resultingchanges are as expected, before relying on the new configuration.Otherwise, some paths may not be as expected.

Whenever you make any modification to the default settings, such aschanging the default load-balancing policies, then you must run thepowermt save command to ensure that the new settings persistacross reboot.



Adding new paths to a PowerPath logical deviceThis procedure adds new paths to a logical device already configured(with at least one path) in PowerPath.

This procedure can be done without interruption to runningapplications on Microsoft hosts.

CAUTION!All operations must succeed for the reconfiguration to besuccessful. If any step fails, resolve that issue before proceeding.Do not use the new configuration until the entire procedurecompletes successfully.

Path limit Do not configure more than 32 paths per logical device.

Procedure To add paths to a PowerPath logical device:

1. Run powermt display to confirm the current configuration.

2. Run powermt display dev=all to confirm the configuration of thelogical devices to which new paths will be added.

3. Ensure that the number of logical devices, hardware paths, andI/O paths are as expected. The path state should be alive forknown good paths and dead for known bad paths.

If there is a problem, correct it before proceeding.

4. Make physical path additions as required:

a. Map the logical device to additional storage-system ports.

b. Add new HBAs. For details, refer to your vendordocumentation.

c. Attach cables.

d. Rezone Fibre Channel switches.

5. If using SAN Manager, Volume Logix, or Access Logix, make newpaths available to the host using those tools.

6. Scan for hardware changes in the device manager or alternately,reboot. In some cases, the operating system may prompt for areboot after new devices are added.

7. Reconfigure PowerPath.

Adding new paths to a PowerPath logical device 45

46


8. Inspect the new PowerPath configuration:

a. Run powermt display dev=all.

The new paths should be displayed with a state of alive.

b. Run powermt restore to test all paths.

c. Scan operating system error logs to ensure no errors arelogged against the new paths.

9. Correct any issues detected.

10. Run powermt save to save the new configuration.

Adding new logical devices to the PowerPath configurationThis procedure adds new logical devices (with one or more paths) tobe managed by PowerPath and applies to managed storage systemclasses only.

Logical devices can be added without interruption of service, sinceno existing application can be using a logical device that is not yetavailable.

After successful configuration, new pseudo devices can be used.

CAUTION!All operations must succeed for the reconfiguration to besuccessful. If any step fails, resolve that issue before proceeding.Do not use the new configuration until the entire procedurecompletes successfully.

Procedure To add logical devices to the PowerPath configuration:

1. Run powermt display to confirm the current configuration.Ensure that the number of logical devices, hardware paths, andI/O paths are as expected. The path state should be alive forknown good paths and dead for known bad paths.

2. Make logical device and physical path changes as required:

a. Create new logical devices.

b. Map logical devices to one or more storage-system ports.

c. Add new HBAs. For details, your vendor documentation willprovide more details.



d. Attach cables.

e. Rezone Fibre Channel switches.

3. If using SAN Manager, Volume Logix, or Access Logix, make newpaths available to the host using those tools.

4. Scan for hardware changes in the device manager. Alternately,reboot. In some cases, the operating system may prompt for areboot after new devices are added.


6. After adding LUNs to a storage group and scanning the disk viathe device manager/diskpart scan operation or through a reboot,the powermt display dev=all command may return an errorcount of 1 for the new LUNs. Run the powermt restore commandto reset the error count to 0.


a. Run powermt display dev=all.

All paths associated with the new logical devices should bedisplayed with a state of alive.

b. Run powermt restore to test all paths to the new logicaldevice.

c. Scan operating system error logs to ensure no errors arelogged against the new paths and logical device.

8. Correct any issues detected, before saving the PowerPathconfiguration or using the new logical device.

9. Set PowerPath-specific options for the new logical devices, suchas load-balancing and failover policy, path modes, write throttleenablement, and priority.



12. On the host where EMC ControlCenter is installed, run thecommand that refreshes the ControlCenter database of deviceinformation. Refer to the documentation for your version ofControlCenter.

Adding new logical devices to the PowerPath configuration 47

48


Removing some paths to PowerPath logical devicesThis procedure removes some (but not all) paths to logical devicesconfigured in PowerPath.

CAUTION!Do not remove the last live path to a logical device unless you planto remove the logical device entirely, as data access will beinterrupted. If a PowerPath device is open, powermt remove doesnot remove that device or the last path to that device.

Procedure To remove some paths to PowerPath logical devices:

1. Run powermt display dev=all to confirm the configuration of thelogical devices from which paths will be removed.

2. Check the number of existing paths.

The path state should be alive for known good paths and dead forknown bad paths.

3. If there is a problem, correct it before proceeding.

4. Identify the physical paths to be removed or zoned out, andconfirm that there are other paths to the affected logical devices.(Otherwise, applications using those logical devices couldexperience I/O errors when you proceed.)

5. Run powermt display dev=all to identify the PowerPath HBAnumber associated with the paths to be removed. In complextopologies, there can be multiple paths on an HBA.

6. Run powermt set mode=standby to set the mode to standby forall paths to be removed. If an HBA is to be removed, specify theHBA (instead of the device) when running powermt set mode.

7. Physically disconnect the paths or logically disconnect them byremoving them from active zones.

As a result of this, the operating system may log some errormessages. However, PowerPath prevents these errors fromaffecting applications.

8. Scan for hardware changes in the device manager. Alternately,reboot. In some cases, the operating system may prompt for areboot after new devices are added.



9. Run powermt restore, and confirm that the paths listed as deadare the ones you intended to remove.

10. Run powermt remove, specifying both the hba and devarguments.

CAUTION!If you do not specify the hba argument, all paths to thespecified logical device are removed.

11. Remove HBAs as required and reboot if needed.


a. Run powermt display.

The output should show fewer total paths than before. Allpaths should have a state of optimal.

b. Run powermt display dev=all.

All remaining paths associated with the affected logicaldevices should be displayed with a state of alive.

13. Correct any issues detected before saving the PowerPathconfiguration or using the new logical devices.


Removing PowerPath logical devicesThis procedure removes logical devices (with all configured paths tothose logical devices) configured in PowerPath. Logical devices canbe removed without interruption of service only if no applications areusing or configured to use the logical devices you are removing.

The procedure may fail if any application is using a device associatedwith any path to be removed.

Procedure To remove PowerPath logical devices:

1. Inspect the current PowerPath configuration:

a. Run powermt display to confirm the current configuration.Ensure that the total number of logical devices, hardwarepaths, and I/O paths are as expected.

Removing PowerPath logical devices 49

50


Since one or more paths may have failed, not all paths may belisted as optimal.

b. Run powermt display dev=all to confirm the configuration ofthe logical devices that will be removed.

c. Check the number of existing paths.

The path state should be alive for known good paths and deadfor known bad paths.

2. If either of the above displays indicates a problem, correct itbefore proceeding.

3. Identify the logical devices to be removed.

4. Identify the physical paths that also may be removed.

5. Run powermt display dev=all to identify the PowerPath HBAnumber associated with the paths to be removed. In complextopologies, there can be multiple paths on an HBA.

6. Reconfigure all applications that are using the logical devices tobe removed, so they are no longer configured to use them.

7. Unmount file systems.

8. Remove the volume groups using the appropriate volumemanager command.

9. Scan for hardware changes in the device manager. Alternately,reboot.

10. If using SAN Manager, Volume Logix, or Access Logix, removeaccess to the logical devices to be removed, using those tools.

As a result of this step, the operating system may log some errormessages. These are expected and are harmless.

11. Run powermt remove dev=all.

12. Run powermt save.

13. Disconnect physical paths or zone out paths with switched fabriczone changes as required.

14. Run powermt restore, and confirm that the paths listed as deadare associated with the logical devices you intend to remove.

15. Depending on the type of HBA installed, scan for hardwarechanges in the device manager. Alternately, reboot.



In some cases, the operating system may prompt for a reboot afternew devices are added.


a. Run powermt display.

The output should show fewer total paths than before. Allpaths should have a summary state of optimal.

b. Run powermt display dev=all.

All remaining paths associated with the affected logicaldevices should be displayed with a state of alive.

17. Correct any issues detected above, before saving the PowerPathconfiguration or using the new logical devices.


Removing PowerPath logical devices 51

52


Configuring the Microsoft iSCSI Initiator for PowerPathTo configure the Microsoft iSCSI initiator for PowerPath:

Note: Also refer to the recommended array and hardware guidelines.

1. Obtain the Microsoft iSCSI initiator installation kit and launch theinstallation program.

2. Select Microsoft MPIO Multipathing Support for iSCSI andthen click Next.

3. Select Enable multi-path while creating sessions on the targetand then click OK.


3Invisible Body Tag


◆ Before you remove PowerPath ........................................................ 54◆ Uninstalling PowerPath with Windows OS tools ......................... 55◆ Uninstalling with the PowerPath command line .......................... 58◆ PowerPath uninstallation troubleshooting .................................... 61◆ Disconnecting redundant paths to the storage system ................ 62

Removing PowerPath

Removing PowerPath 53

54

Removing PowerPath

Before you remove PowerPathBefore you remove PowerPath from the host:

❑ Check Powerlink for the most current information. EMC updatesrelease notes periodically and posts them on Powerlink.

❑ Stop any application actively sending I/O. In addition, close anyremaining applications and client files to avoid warning messageswhen rebooting after the uninstall.

Note: If you try to uninstall PowerPath when there are active migrations,the message "Migration(s) is (are) pending" appears and theuninstallation process aborts. Contact EMC Customer Support if you seethe message "An internal error has occurred. Migrations may bepending."

Removing PowerPath software or componentsYou can remove PowerPath and all related components, or you canremove specific features, such as Migration Enabler or PowerPathEncryption. You can also remove specific multipathing componentsyou may no longer need, such as components to support third-partyarrays.

You can use the Windows Add/Remove Programs or Programs andFeatures tools to remove PowerPath, or you can use the moreadvanced PowerPath command line interface. Use one of thesemethods to uninstall PowerPath software or features.

◆ "Uninstalling PowerPath with Windows OS tools" on page 55

◆ "Uninstalling with the PowerPath command line" on page 58

Note: Rebooting is recommended when removing PowerPath.


Removing PowerPath

Uninstalling PowerPath with Windows OS toolsThe procedures in this section describe how to uninstall PowerPathsoftware or components using Windows operating system tools.

◆ "Complete PowerPath removal" on page 55 removes PowerPathmultipathing and makes other PowerPath features unavailablefor installation changes through the Windows GUI. Futureinstallation changes can only be made through the PowerPathexecutable file or the PowerPath CLI once you complete thisprocedure.

◆ "Feature-specific removal" on page 56 removes specificPowerPath features, such as Migration Enabler, PowerPathEncryption, or components that provide support for third-partyarrays.

Complete PowerPath removalUse this procedure to completely remove PowerPath.

1. Uninstall any hot fixes installed on the host. Use Add/RemovePrograms or Programs and Features to verify if hot fixes areinstalled.

2. For Windows 2003, follow these steps. For Windows 2008, refer toStep 3.

a. Open the Control Panel and double-click Add/RemovePrograms.

b. On the Add/Remove Programs panel, select the installedversion of PowerPath, and click Remove.

3. For Windows 2008, open the Control Panel and double-clickPrograms and Features.

• If User Account Control (UAC) is turned on, click Yes on theelevation.

• If you belong to the Administrative group, click Allow in theelevation.

• If you are a standard user, give the administrative credentialsto uninstall.

4. When prompted to remove PowerPath, click Yes.

Uninstalling PowerPath with Windows OS tools 55

56

Removing PowerPath

5. When prompted to reboot the host, click No to reboot later.

Note: You can reboot after disconnecting redundant cables.

6. Complete the steps in "Disconnecting redundant paths to thestorage system" on page 62.

Feature-specific removalUse this procedure to remove specific PowerPath features.

Note: You cannot uninstall PowerPath multipathing for EMC arrays usingthis procedure. Only the complete uninstall procedure removes defaultmultipathing components.

1. Open the Control Panel and double-click:

• For Windows Server 2003:

Add/Remove Programs

• For Windows Server 2008:

Programs and Features panel

2. Select the installed version of PowerPath, and clickChange/Remove.

3. In the setup wizard welcome window, click Next.

4. On the Program Maintenance dialog box, select Modify and clickNext.

5. To select a feature to uninstall (Migration Enabler and/orEncryption with RSA), click the drop-down arrow beside thefeature on the Custom Setup dialog box:

Note:—A selected feature displays a hard drive icon next to it. A red X next to

it indicates features that are not selected.—The icon next to the feature name indicates the install state of the

feature. Click Help in the Custom Setup dialog box for moreinformation about the icons.

a. Select This feature will not be available.

b. Click Next.


Removing PowerPath

6. In the Ready to Modify the program dialog box, click Remove.


8. If you removed multipathing support for any storage systems,complete the steps in "Disconnecting redundant paths to thestorage system" on page 62.

Uninstalling PowerPath with Windows OS tools 57

58

Removing PowerPath

Uninstalling with the PowerPath command lineThe command line method allows you to uninstall PowerPathmultipathing and/or other features, such as Migration Enabler orPowerPath Encryption.

Use this procedure to remove PowerPath and/or other features.

1. If you are completely removing PowerPath, uninstall any hotfixes installed on the host. Use Add/Remove Programs orPrograms and Features to verify if hot fixes are installed.

2. Use this command syntax to uninstall PowerPath:

<drive>:\<PowerPath_pkg_name> <install_parameters> <logfile> <Property>=<Value>"

• For a silent removal, which does not require user input, usethis syntax:

Note: Silent uninstallation errors are logged in <logfile>, the locationspecified in the uninstallation command. No error message appearsin the PowerPath Administrator GUI.

<drive>:\<PowerPath_pkg_name> /s /v"/q /L*v <logfile> <Property>=<Value>"

• For an interactive removal, which requires user input, use thissyntax:

<drive>:\<PowerPath_pkg_name> /v"/L*v <logfile> <Property>=<Value>"

Where:

– <drive> is the drive letter, for example, C.– <PowerPath_pkg_name> is the PowerPath package name.

For example, EMCPP.x86_32.5.5.0.GA.exe orEMCPP.x86_x64.5.5.0.GA.exe

– <install_parameters> is one or more parameters described inTable 4 on page 59.

– <logfile> creates the log file where the log message will besent, for example, C:\logs\PPsetup.log.

Note: Make sure the specified directory exists within the specifiedpath.

– <Property>=<Value> is one or more optional propertiesdescribed under the /v parameter in Table 4 on page 59.


Removing PowerPath

Example: Silent removal

The following example of a silent uninstall removes PowerPathand all other installed features, such as Migration Enabler andPowerPath Encryption. It also disables reboot.

C:\EMCPP.x86_32.5.5.0.GA.exe /s /v"/q /L*v C:\logs\PPremove.log NO_REBOOT=1PPREMOVE=CLEAN"

Examples: Interactive removal

The following example of an interactive uninstall disables rebootand removes components to support HP XP and Hitachi arrays.

C:\EMCPP.x86_32.5.5.0.GA.exe /v"/L*v C:\Uninstall_HPXP_HDS.log NO_REBOOT=1PPREMOVE=HPXP,HDS"

The following example of an interactive uninstall removes onlyPowerPath Migration Enabler:

C:\EMCPP.x86_32.5.5.0.GA.exe /v"/L*v C:\logs\PPremove.log NO_REBOOT=1PPREMOVE=ME"

3. After uninstalling, complete the steps in "Disconnectingredundant paths to the storage system" on page 62.

CLI parameters Table 4 describes the CLI parameters and properties.


Parameter Description

/s Suppresses installation shield dialog boxes.

/v Directs InstallShield to pass the specified string (enclosed in quotes) to the Microsoft Installer (MSI).For example, /v" <properties>"

Property Value description

NO_REBOOT=1 The value 1 specifies that the host will not reboot after PowerPath is installed.

Note: EMC recommends NO_REBOOT=1 so that you can manually restart at aconvenient time.

Uninstalling with the PowerPath command line 59

60

Removing PowerPath

PPREMOVE=<feature>

Specifies the features to uninstall. Use commas to separate multiple entries, forexample: PPREMOVE=ME,RSA• CLEAN = Removes PowerPath and all other features, such as Migration

Enabler and PowerPath Encryption. It also removes driver files andcorresponding registry entries.

• ALL = Invokes PPRemoveAll utility, which removes all PowerPath multipathingentries from the host. Use this option only when you encounter a problem withan existing installation or attempt at removal.

• ME = Migration Enabler• RSA = Encryption with RSA• IBM = IBM TotalStorage ESS arrays• CELERRA = Celerra arrays• HDS = Hitachi arrays• HPXP = HP XP arrays• INVISTA = Invista and VPLEX devices

Note: Other PPREMOVE values (such as PP, 1, and 2) are not supported. If anyother values are used, an error message indicates that it is not a supported valueduring a GUI uninstallation. The same message is written to the log file.

FORCE_DRIVER_UPDATE=1

The value 1 will continue to uninstall PowerPath and ignore the device managercheck for any pending device installation or uninstallation activities.

/q Indicates a quiet removal (no user interaction).

/L*v<logfile>

Directs the Microsoft Installer to write verbose output to the file specified with this option. The targetdirectory for the log file must exist before starting a silent removal by using the logging option (as requiredby the Windows installer engine).


Parameter Description


Removing PowerPath

PowerPath uninstallation troubleshootingTable 5 on page 61 lists PowerPath uninstallation troubleshootingscenarios.

Table 5 Troubleshooting scenarios


Uninstalling MPIO and PowerPath in aboot-from-SAN configuration on aWindows 2003 host with no other thirdparty DSM installed requires two reboots.

In a boot-from-SANconfiguration, two hostreboots are required touninstall PowerPath andMPIO. To uninstall PowerPathand MPIO, choose Yes. Touninstall PowerPath andleave MPIO installed, chooseNo. To exit, choose Cancel.

Click Yes to uninstall PowerPath andMPIO.Click No to uninstall only PowerPath.Click Cancel to abort uninstallation.

Uninstalling PowerPath in aboot-from-SAN configuration on aWindows 2008 R2 host.

In a boot-from-SANconfiguration, two hostreboots are required touninstall PowerPath. Touninstall PowerPath, chooseOK. To exit, choose Cancel.

Click OK to uninstall PowerPath.Click Cancel to abort uninstallation.

MPIO is ready to be uninstalled in aboot-from-SAN configuration.

PowerPath has prepared thesystem to uninstall MPIO.MPIO will be removedcompletely once PowerPath isuninstalled. Reboot the hostand then uninstallPowerPath.

Reboot the host and then uninstallPowerPath.After PowerPath is uninstalled, the MPIOframework will also be uninstalled.

The host needs a reboot. PowerPath has detected thata reboot is pending. Rebootthe host and then uninstallPowerPath.

Reboot the host and then uninstallPowerPath.

PowerPath uninstallation troubleshooting 61

62

Removing PowerPath

Disconnecting redundant paths to the storage systemAfter uninstalling PowerPath, disconnect redundant paths to thestorage system.

CAUTION!Data corruption is possible if multiple paths remain on a systemafter PowerPath is removed.

To disconnect redundant paths:

1. From the Start menu, select Shut Down. Before you reboot, shutdown the host and disconnect redundant paths from the host tothe storage system.

2. In the Shut Down Windows dialog box, select Shut Down fromthe list, and click OK.

3. With the host shut down, disconnect redundant cables from theHBAs to the storage system interface ports.

Note: SAN (fabric) configurations may have multiple logicalconfigurations per physical connection. Ensure that no redundant zonedpaths exist.

4. Reboot the host.

PowerPath is completely removed from the host.

5. The setup wizard appears and asks if you want to reboot the host.Click yes to reboot now, or no to reboot later.


4Invisible Body Tag


◆ Overview............................................................................................. 64◆ PowerPath monitor............................................................................ 64◆ PowerPath registration tools ............................................................ 67◆ PowerPath Administrator................................................................. 68◆ Local or remote administration........................................................ 75◆ Saving and loading Administrator settings ................................... 79◆ Saving MMC console settings .......................................................... 80◆ PowerPath and Systems Management Server (SMS) ................... 81◆ Windows Server 2008 Support......................................................... 82◆ Audit and error log messages .......................................................... 83

Managing PowerPath

Managing PowerPath 63

64

Managing PowerPath

OverviewThe PowerPath Administrator graphical user interface for WindowsServer consists of two applications:

◆ PowerPath monitor — Continuously monitors your PowerPathconfiguration and alerts you of status changes. The "PowerPathmonitor" section provides additional information.

◆ PowerPath Administrator — Configures, monitors, and managesPowerPath devices. The "PowerPath Administrator" on page 68provides additional information.

PowerPath monitorPowerPath monitor (on the taskbar of your Windows desktop)continuously monitors the status of your PowerPath configuration.PowerPath monitor can be set to alert you with visual and audiblecues when the status changes.

For example, if a path fails, the icon changes accordingly as seen inTable 6 on page 65. Depending on the Notification settings youchoose on the Options tab of the EMC PowerPath Admin (root node)Properties dialog box (see PowerPath Administrator online help forWindows Server), PowerPath monitor may:

◆ Sound an alarm.

◆ Restore the PowerPath Administrator main window.

◆ Flash the taskbar icon.

◆ Or any combination thereof.


Managing PowerPath

Table 6 shows the taskbar icons and the status each represents.

Note: All non-Optimal monitor icons appear only if you have selected theFlash Taskbar Icon on the Options tab of the EMC PowerPath Admin (rootnode) Properties dialog box. The root node is the top-level view of yourconfiguration and represents the host that is being managed by PowerPath.

Launching MMC with the PowerPath snap-inYou can use PowerPath Monitor to do the following:

◆ Launch Microsoft Management Console (MMC) with thePowerPath snap-in.

◆ Notify you of PowerPath status changes if you are running it on alocal host.

Note: The EMC PowerPath Administrator Monitor monitors the local hostonly. It does not remotely monitor the status of another host. The icon is onlypresent on the Windows taskbar on the host with EMC PowerPathAdministrator installed. If you are running PowerPath for the first time on aremote host, you must start the application according to the instructions at"Local or remote administration" on page 75.

Table 6 PowerPath monitor taskbar icons

Taskbar Icon Status

Optimal — All configured paths are operating properly.

Degraded — Some but not all paths have failed.

All Failed — All configured paths have failed.

Server Not Responding — Cannot communicate with Monitor service.This occurs if the PowerPath Administrator Suite encountered errors duringinitialization.

PowerPath monitor 65

66

Managing PowerPath

To launch the Microsoft Management Console (MMC) with thePowerPath Snap-in, do one of the following:

◆ Double-click the PowerPath Monitor icon on the Windowstaskbar to launch the default MMC console with the PowerPathSnap-in.

or

◆ Right-click the PowerPath Monitor icon to display the followingcontext menu options:

• PowerPath Administrator — Launches PowerPathAdministrator.

• Close Monitor — Closes the EMC PowerPath AdministratorMonitor.


Managing PowerPath

PowerPath registration toolsYou can use the PowerPath Licensing Tool or the emcpreg commandto register PowerPath and related products.

PowerPath Licensing ToolThe Licensing Tool is used to register PowerPath and other products,from the Windows GUI. The Licensing Tool is displayed duringPowerPath installation (except when the host is connected to aCLARiiON AX-series array). To manage licenses, you can launch thetool by selecting Start > Programs > EMC > PowerPath LicensingTool.

This tool allows you to add or remove licenses. For more information,see the online help (press F1) or launch the help file,EMCLicTool.chm, from the PowerPath software CD or the \helpdirectory.

Note: You must have Internet Explorer 5.1 or later to view the online helpfiles. If you do not have this browser installed, you may still view the help filefrom the EMCLicTool.chm file.

emcpreg commandThe emcpreg command facilitates scripting options and is the onlyway to manage licenses with the Windows Server 2008 core version.The emcpreg command is supported with all supported Windowsplatform versions.

To add a license with emcpreg command line, enter:

emcpreg -add <key>

where <key> is the product license key.

The PowerPath CLI and System Messages Reference on Powerlinkprovides additional information.

PowerPath registration tools 67

68

Managing PowerPath

PowerPath AdministratorFor Windows Server, the PowerPath Administrator runs as a snap-inprogram within Microsoft Management Console (MMC). You can useMMC and the PowerPath Snap-in to monitor a local or remote host."Local or remote administration" on page 75 provides additionalinformation.

The PowerPath Administrator is a graphical user interface forconfiguring, monitoring, and managing PowerPath devices. ThePowerPath Administrator continuously monitors a multipathstorage-system environment and automatically updates theconfiguration information that appears.

You can use PowerPath Administrator to set up and change yourdevice configuration and manage physical and logical pathcomponents. The PowerPath Administrator displays a hierarchicalrepresentation of paths, logical devices, and HBAs.

PowerPath Administrator displays the components of a PowerPathsystem as objects. PowerPath Administrator icons represent thePowerPath objects in your configuration. The type of icon reflects thestate or status of the particular object selected. Table 7 on page 71 andTable 8 on page 72 display PowerPath Administrator icons.

PowerPath Administrator panesAs part of MMC, the PowerPath Administrator has two panes:

◆ The scope pane displays PowerPath objects in a hierarchical listthat can be expanded or collapsed.

◆ The result pane provides a view of configuration statistics forPowerPath objects selected in the scope pane.


Managing PowerPath

Figure 1 shows a sample PowerPath Administrator display.

Figure 1 Sample PowerPath Administrator display

PowerPath Administrator device properties dialog boxYou can access most of the PowerPath Administrator functionsthrough the tabs available in the device Properties dialog box.Right-click the PowerPath object and select Properties.

The PowerPath properties are as follows:

◆ PowerPath admin (root node) properties — Use this to:

• Show root node details.

• Set local or remote host options.

• Set error notification options.

• Set Auto-Restore.

• View array management information.

To display this tab:

1. Select the root node in the scope pane.

2. Right-click.

3. Select Properties.

PowerPath Administrator 69

70

Managing PowerPath

Note: The root node is the top-level view of your configuration andrepresents the host that is being managed by PowerPath. The Root NodeProperties dialog box contains a Details, Computer, and Options tab.(The Computer tab is present only when you are connected to a remotehost). The Options tab contains a Notification box, an Auto-Restore box,and an Array Management Information box.

◆ Storage array properties — Use this to show storage arraydetails. To display this tab, select a storage array, right-click, andselect Properties.

◆ Storage array port properties — Use this to show storage arrayport details. To display this tab, select a storage array port,right-click, and select Properties.

◆ Adapter properties — Use this to show adapter details andchange modes on the adapter. To display this tab, select anadapter, right-click, and select Properties.

◆ Disk properties — Use this to show disk details, change modeson the disk, and change load-balancing policies and priorities. Todisplay this tab, select a disk, right-click, and select Properties.

◆ Path properties — Use this to show path details and change themode of a path. To display this tab, select a path, right-click, andselect Properties.

Note: The previous examples illustrate the most common PowerPathAdministrator functions. The PowerPath Administrator online help forWindows Server provides complete information on using all the PowerPathAdministrator functions.

If you do not have the Internet Explorer 5.1 or later installed on your system,you will be unable to launch the PowerPath online help files for WindowsServer from the MMC console. If you want to view the help file withoutinstalling Internet Explorer, you can launch theEmcPowerPathAdminMMC.chm file directly from the \help folder on thePowerPath installation CD.


Managing PowerPath

Icons: standard, unlicensed, and unknown conditionsTable 7 shows icons for standard, unlicensed, unknown, andmismatched states. Standard icons represent a configuration in whichPowerPath is optimal.

Note: The online help provides more information on icons and theirmeaning.

Table 7 Icons on the PowerPath Administrator

Object Standard Icon Unlicensed Icon Unknown Icon Mismatched Icon

Root Node — Graphicalrepresentation of the host andtop level view of yourconfiguration.

N/A

Storage Array — An attachedstorage system that provideslogical devices which aremanaged by PowerPath.

N/A

Storage Array Port —Identifies a port within a specificstorage array that provides I/Opaths to the logical devices.

N/A

Disk — A logical devicemanaged by PowerPath.Logical devices are diskdevices presented by thestorage system.

N/A

Adapter — A device thatprovides an interface betweenthe SCSI or Fibre Channel busand the computer I/O bus. Anadapter can have multiple pathsassociated with it.

N/A

Path — The logical or physicalI/O path from the host to thestorage system, including theHBA, cable, and interface port.


72

Managing PowerPath

Icons: known failure conditionsWhen a path fails, the failure propagates through other PowerPathAdministrator objects. These objects are displayed in a hierarchy inthe scope pane and result pane. These known failure icons representconfigurations that are less than optimal.

Table 8 on page 72 shows known failure icons. Icons for:

◆ Degraded conditions.

◆ Failed conditions.

◆ Unlicensed and degraded conditions.

◆ Unlicensed and failed conditions.

Degraded PowerPath objects are represented by a red slash throughthe standard object icon. (Because a path is either open or closed, thepath icon is never shown as degraded.) Failed PowerPath objects arerepresented by a red X through the standard object icon.

The definition of degraded and failed status depends on the contextshown in Table 8 on page 72. For example, an unlicensed version ofPowerPath with degraded or failed paths displays icons that combineelements of both the unlicensed and degraded icons.

Unless specified otherwise, all icons display in both the summaryand details panes.

Table 8 Icons of known PowerPath failure conditions (1 of 2)

Object Degraded Icon Failed IconUnlicensed and DegradedIcon

Unlicensed and FailedIcon

Root Node EMC PowerPathAdministrator isidentifying a

degradation within themanaged environment.

EMC PowerPathAdministrator is ina failed state.

EMC PowerPath isunlicensed andidentifying a

degradation within themanaged environment.

EMC PowerPathAdministrator isunlicensed and in

a failed state.

StorageArray

One or more(but not all)paths to thestorage arrayhave failed or

are in a degraded state.

All paths to thespecific arrayhave failed. Thisarray is not

available.

EMC PowerPathAdministrator isunlicensed. Oneor more (but not

all) paths to the array havefailed or are in a degradedstate.

EMC PowerPathAdministrator isunlicensed. Allpaths to the

specific array havefailed.This array is notavailable.


Managing PowerPath

Undefined SP conditionsThe following icons represent a rare condition on active/passivearrays, including VNX OE and CLARiiON, that produce a doublelink control card (LCC) failure. If you see these icons, the LCC faultlight on the VNX OE or CLARiiON array should be amber. Refer tothe VNX OE or CLARiiON documentation for troubleshootinginformation, or contact EMC Customer Support for information onreplacing an LCC.

StorageArray Port

One or more (butnot all) paths tothe storage arrayport have failed or

are in a degraded state.

All paths to thespecific array porthave failed. This

array port is not available.

EMC PowerPathAdministrator isunlicensed. Oneor more (but not

all) paths to the array porthave failed or are in adegraded state.

EMC PowerPathAdministrator isunlicensed. All

paths to the specific arrayport have failed. This arrayport is not available.

PowerPathdevice

One or more (butnot all) paths tothe disk device

have failed.

All paths to thespecific diskdevice have

failed. This disk is notavailable.

EMC PowerPathAdministrator isunlicensed. One

or more (but not all) pathsto the disk device havefailed.


paths to the specific diskdevice have failed. Thisdisk is not available.

Adapter One or more (butnot all) adaptershave either failed

or degraded. Displays inthe Adapters folder in thescope pane.

One or more (but not all)paths have failed on thespecific adapter.

All paths on thisadapter havefailed.

EMC PowerPathAdministrator isunlicensed. One

or more (but not all) pathshave failed on the specificadapter.


paths on this adapter havefailed.

Path Not applicable. One or more ofthe hardwarecomponentsthat make up

the path has failed;therefore, the entire pathfailed.

Not applicable. EMC PowerPathAdministrator isunlicensed, and

one or more of thehardware components thatcomprise the path hasfailed; therefore, the entirepath fails.

Table 8 Icons of known PowerPath failure conditions (2 of 2)

Object Degraded Icon Failed IconUnlicensed and DegradedIcon

Unlicensed and FailedIcon


74

Managing PowerPath

Table 9 on page 74 shows icons and descriptions specific toCLARiiON arrays.

Table 9 Icons of undefined SP PowerPath failure conditions

Standard Icon Degraded Icon Failed Icon Unlicensed IconUnlicensed andDegraded Icon

Unlicensed andFailed Icon

TheCLARiiONlink control

cards (LCC) havefailed. The SPowning the disk isunknown and thedisk is unavailable.


cards (LCC) havefailed. The SPowning the disk isunknown and oneor more (but not all)paths to the diskdevice has failed.The disk isunavailable.


cards (LCC) havefailed. The SPowning the disk isunknown and allpaths to the diskdevice has failed.The disk isunavailable.

ThePowerPathAdministra

tor is unlicensedand the CLARiiONlink control cards(LCC) have failed.The SP owning thedisk is unknownand the disk isunavailable.


tor is unlicensedand the CLARiiONlink control cards(LCC) have failed.The SP owning thedisk is unknownand one or more(but not all) pathsto the disk devicehas failed. The diskis unavailable.


tor is unlicensedand the CLARiiONlink control cards(LCC) have failed.The SP owning thedisk is unknownand all paths to thedisk device hasfailed. The disk isunavailable.


Managing PowerPath

Local or remote administrationWith MMC and the PowerPath Snap-in, you can monitor a local hostor a remote host.

◆ Local administration — EMC PowerPath Administrator isinstalled on the local host by default. The installation processprovides a preconfigured .msc file to launch the MicrosoftManagement Console (MMC). Once PowerPath is installed, youcan use PowerPath to monitor the local host immediately.

To launch MMC with the PowerPath Snap-in:

Select Start > Programs > EMC > PowerPath > EMCPowerPathAdmin.

Note: The path starts the PowerPath Snap-in and the MMC console onthe local host with no other action required. However, there may bescenarios in which you need to add the PowerPath Snap-in to a newMMC console. For example, you may want to create another instance ofPowerPath Administrator on the local host or you may have deleted thePowerPath Snap-in and want to add it again. "Setting a local host option"on page 76 provides additional information on how to add thePowerPath Snap-in to the MMC console to monitor a local host.

◆ Remote administration — If you want to monitor a remote hostthat has PowerPath for Windows Server 2003 installed, you maysupply the credentials for remote access to that host. "Setting aremote host option" on page 77 provides additional informationon how to add the PowerPath Snap-in to monitor a remote hostwith PowerPath installed.

Note: When PowerPath 3.0.5 or later is installed for Windows Server2003 on more than one host, you can use the Remote Host Option tomonitor any host from any other host.

Local or remote administration 75

76

Managing PowerPath

Setting a local host optionAdding the PowerPath Snap-in to MMC and monitoring a local hostis a two-part procedure.

Part 1: Opening the MMCTo open the MMC:

1. Click Start

◆ If you are using Windows Server 2003, select Run.

◆ If you are using Windows Server 2008 there are two options:

• Use the Windows Interface:

a. In the Start Search text box from the Start menu, type mmc.

b. Press Enter.

• Use a command line:

a. In the Start Search text box from the Start menu, type cmd.

b. Press Enter.

c. At the command prompt, type mmc.

d. Press Enter.

2. In the Open field, run mmc.

3. Click OK.

An MMC Console appears. The MMC title bar displays Console1.Within this pane is the Console Root. Initially this folder isempty. However, once the snap-in is added, this folder willcontain the EMC PowerPath Administrator (and any other addedsnap-ins) and is displayed as expandable icons under theConsole Root folder.

Part 2: Adding the EMC PowerPath Administrator snap-in1. From the MMC console, select File > Add/Remove Snap-in. The

Add/Remove Snap-in window appears.

2. In the Add/Remove Snap-in window, click Add.

3. From the Add Standalone Snap-in window, select EMCPowerPath Administration and click Add.

4. In the EMC PowerPathAdmin dialog box, select Local Computer.


Managing PowerPath

5. Click Finish.

6. In the Add Standalone Snap-in dialog box, click Add to addanother snap-in or click Close.

7. In the Add/Remove Snap-in dialog, click OK.

EMC PowerPath Administrator is now added to the MMCconsole.

You can now use EMC PowerPath Administrator to configure,manage, and monitor PowerPath devices.

Once you have changed your configuration, save the configuration."Saving a configuration" on page 79 provides additional information.

Setting a remote host optionAdding the PowerPath snap-in to MMC and monitoring a remotehost that has PowerPath 3.0.5 or higher for Windows Server 2003installed is a two-part procedure.

Part 1: Opening the MMCTo open the MMC:

1. Click Start

◆ If you are using Windows Server 2003, select Run.

◆ If you are using Windows Server 2008 there are two options:

• Use the Windows Interface:

a. In the Start Search text box from the Start menu, type mmc.

b. Press Enter.

• Use a command line:

a. In the Start Search text box from the Start menu, type cmd.

b. Press Enter.

c. At the command prompt, type mmc.

d. Press Enter.

Local or remote administration 77

78

Managing PowerPath

2. In the Open field, run mmc.

3. Click OK.

An MMC Console appears. The MMC title bar displays Console1.Within this pane is the Console Root. Initially this folder isempty. However, once the snap-in is added, this folder willcontain the EMC PowerPath Administrator (and other snap-insyou may add) and is displayed as expandable icons under theConsole Root folder.

Part 2: Adding the EMC PowerPath Administrator snap-in1. From the MMC console, select File > Add/Remove Snap-in.

The Add/Remove Snap-in window appears.

2. In the Add/Remove Snap-in window, select Add.

3. From the Add Standalone Snap-in window, select EMCPowerPath Administration and click Add.

4. In the EMC PowerPathAdmin dialog box, select AnotherComputer.

5. Enter the computer name or browse for the remote computer.

6. In the Browse for Computer dialog box, click OK.

7. Enter your User Name, Domain Name, and Password.

8. Click Finish.

Note: The User Name, Domain Name, and Password fields aresubsequently available for editing from the root node Properties page ifyou are using MMC to monitor a remote host. The section "Set RemoteHost Options" in the PowerPath Administrator online help, providesadditional information.

9. In the Add Standalone Snap-in window, click Add to addanother snap-in or click Close.

10. In the Add/Remove Snap-in window, click OK. EMC PowerPathAdministrator is now added to the MMC console.


Managing PowerPath

Saving and loading Administrator settingsYou can use EMC PowerPath Administrator to configure, manage,and monitor PowerPath devices. The first time you run EMCPowerPath Administrator, there is a default configuration. If youmake changes, you can save them to a configuration file. The filerecords the serial numbers, mode, policy, and priority for eachconfigured path. You can also load the last known configuration or apreviously saved file.

Note: PowerPath configuration files are distinct from the MicrosoftManagement Console (MMC) configuration files. If you close the MMCwindow, MMC prompts you to save the MMC settings. These settings are notthe same as the EMC PowerPath Administrator settings. Saving the MMCconsole settings does not save your PowerPath configuration changes. Thesechanges will be lost unless you complete the following procedure.

Saving aconfiguration

To save the current PowerPath Administrator settings:

Note: Saving the configuration may override an existing configuration file.Provide a unique file name and use the Save As option to avoid overridingan existing configuration file.

◆ Enter powermt save [file=pathname]

or

◆ In PowerPath Administrator, right-click the root node and selectAll Tasks > Save Config as. Then specify a file name and clickSave.

Loading aconfiguration

You can load the last known reboot state or a previously saved EMCconfiguration file.

To load a configuration:

1. In the scope pane, select the EMC PowerPathAdmin root node.

2. To load a previously saved PowerPath configuration, right-clickthe root node and select All Tasks > Load Config File.

To load the last known reboot state, right-click the root node andselect All Tasks > Load Reboot Config.

Saving and loading Administrator settings 79

80

Managing PowerPath

Saving MMC console settingsThe MMC console enables you to display the PowerPath Snap-in datain many ways. If you change your MMC console configuration (forexample, if you resize columns, change column displays, or changecolumn sort order), you may want to save these new MMC consolesettings.

If you close the MMC console itself, or the PowerPath Snap-in withinthe MMC console, MMC prompts you with the following message:

Save console settings to <filename>.msc?

Click Yes to save the latest console settings. By default, the MMCconsole settings are saved as console1.msc in the folder:

%SystemDrive%\Programs\Administrative Tools

You can save the console settings anytime with the Console, Savemenu option in the MMC console.

To save the file with a different name or to a different location, go toMMC Console > Save As.


Managing PowerPath

PowerPath and Systems Management Server (SMS)PowerPath has been qualified with the Systems Management Server(SMS) software from Microsoft, which allows remote management oflarge groups of Windows-based systems. SMS allows you to remotelymanage patches, distribute software, deploy operating systems, andperform software and hardware inventories.

The high level steps for deploying PowerPath using SMS are:

1. Create a PowerPath package in SMS.

2. Create a program for that PowerPath package.

3. Assign distribution points to that package.

4. Advertise the package to target clients by defining a collection.

See the Microsoft SMS product documentation for detailedinstructions.

PowerPath and Systems Management Server (SMS) 81

82

Managing PowerPath

Windows Server 2008 SupportThe Windows Server 2008 support introduces modifications to thetraybar monitor program and the User Account Control (UAC):

◆ The traybar monitor program now communicates to thePowerPath service where it previously communicated directlywith the kernel driver. This means that if the PowerPath service isdisabled or fails to start, the traybar monitor will not function andan error will be displayed.

◆ For those tasks that require administrator privileges, you receivethe elevated prompt when:

• Opening the GUI from the traybar monitor.

• Launching admin GUI from a program group.

• Starting the license tool.

When the license tool is launched from the Installation program,you do not receive an elevation prompt.

Note: The above information is valid only for built in administrator accountsand any accounts which are part of the administrator group, if UAC is turnedon.


Managing PowerPath

Audit and error log messagesThe EMC PowerPath Family CLI and System Messages Reference onPowerlink describes audit logging, including instructions for settingup logging in your environment. It also lists error messages,descriptions, and suggested corrective action.

Audit and error log messages 83

84

Managing PowerPath


5


◆ Installing PowerPath and MSCS...................................................... 86◆ Integrating PowerPath into an existing MSCS cluster ................. 87

PowerPath in an MSCSCluster

PowerPath in an MSCS Cluster 85

86

PowerPath in an MSCS Cluster

Installing PowerPath and MSCSIf you are installing PowerPath and MSCS for the first time, installPowerPath first, and then install MSCS. Installing PowerPath firstavoids disruption of cluster services at a later time. The MicrosoftMSCS documentation provides complete information on planning,configuring, managing, and troubleshooting MSCS.

After installing PowerPath and MSCS, run the emcphostid checkcommand to check for host conflicts. If the host IDs are not unique,run the emcphostid set command to set a unique host ID.



Integrating PowerPath into an existing MSCS clusterYou can integrate PowerPath into an existing MSCS cluster, withoutshutting down the cluster, if there is close coordination between thenodes and the storage system.

Each node in a cluster can own a distinct set of resources. node A isthe primary node for its resources and the failover node for node Bresources. Conversely, node B is the primary node for its resourcesand the failover node for node A resources.

The Microsoft MSCS documentation provides complete informationon planning, configuring, managing, and troubleshooting MSCS.

Note: If after installing PowerPath on the cluster, you test node failover bydisconnecting all cables for a LUN or otherwise disrupting the path betweenthe active host and the array, Windows logs event messages that indicatehardware or network failure and possible data loss. If working correctly, thecluster will fail over to a node with an active path and you can ignore themessages from the original node as logged in the event log.You should check the application generating I/O to see if there are anyfailures. If there are none, everything is working normally.

The following procedure describes how to install PowerPath on atwo-node cluster. You can also install PowerPath on clusters withmore than two nodes. In these cases, the appropriate action is notedwhere applicable for clusters with more than two nodes.

To add PowerPath to an existing MSCS cluster (with MSCS runningon both nodes), follow these procedures:

◆ "Moving all resources to node A" on page 88

◆ "Installing PowerPath on node B" on page 88

◆ "Configuring additional paths between the storage systemand node B" on page 88

◆ "Moving all resources to node B" on page 89

◆ "Installing PowerPath on node A" on page 89

◆ "Configuring additional paths between the storage systemand node A" on page 89

◆ "Returning node A resources to node A" on page 89

◆ "Checking for host ID uniqueness" on page 90

Integrating PowerPath into an existing MSCS cluster 87

88


Moving all resources to node A1. Start the MSCS Cluster Administrator utility, select:

Start > Programs > Administrative Tools > ClusterAdministrator.

The Cluster Administrator window appears.

2. In the left pane of the window, select all groups owned by node B.

3. To move the resources to node A, select File > Move Group.

Alternatively, select Move Group by right-clicking all groupnames under Groups in the left pane.

4. To pause node B, click node B and select File > Pause Node.

This keeps the node from participating in the cluster duringPowerPath installation.

Installing PowerPath on node B1. Install PowerPath on node B, following the steps in "Installation

procedures" on page 26.

2. Shut down node B.

In a cluster with more than two nodes, install PowerPath on theseother nodes (steps 1 and 2). For example, in a four-node cluster,replace node B with nodes B, C, and D as shown in step 4 in thesection "Moving all resources to node A" on page 88.

Configuring additional paths between the storage system and node B1. If necessary, reconfigure the storage system so its logical devices

appear on multiple ports.

2. If necessary, install additional HBAs on node B.

3. Connect cables for new paths between node B and the storagesystem.

4. Power on node B.

5. To resume node B, click node B and select File > Resume Node.

In a cluster with more than two nodes, configure additional pathsbetween the storage system and these other nodes. For example, in a



four-node cluster, replace node B with nodes B, C, and D in steps 2, 3,4, and 5 above.

Moving all resources to node B1. In the left pane of the Cluster Administrator window, select all

groups.

2. To move the resources to node B, select File > Move Group.

In a cluster with greater than two nodes, move all resources toany of the remaining nodes. For example, in a four-node cluster,replace node B with any combination of nodes B, C, and D towhich you want to move resources. You could also moveresources to nodes B and C or move them to B, C, and D, or anypermutation of nodes B, C, and D taken alone or together.

3. To pause node A, click node A and select File > Pause Node.

Installing PowerPath on node A1. Install PowerPath on node A, following the steps in "Installation

procedures" on page 26.

2. Shut down node A.

Configuring additional paths between the storage system and node A1. If necessary, configure the storage system so its logical devices

appear on multiple ports.

2. If necessary, install additional HBAs on node A.

3. Connect cables for new paths between node A and the storagesystem.

4. Power on node A.

5. To resume node A, click node A and select File > Resume Node.

Returning node A resources to node A1. Use the MSCS Cluster Administrator utility, select all groups

previously owned by node A.

2. To move the resources back to node A, select File > Move Group.

Integrating PowerPath into an existing MSCS cluster 89

90


Checking for host ID uniquenessRun the emcphostid check command to check for host uniqueness. Ifthe host IDs are not unique, run the emcphostid set command to setunique host IDs.


6


◆ Installing PowerPath and VCS......................................................... 92◆ Installing PowerPath in an existing VCS environment ................ 93

PowerPath in a VeritasCluster Server

PowerPath in a Veritas Cluster Server 91

92

PowerPath in a Veritas Cluster Server

Installing PowerPath and VCSIf you are installing PowerPath and VCS for the first time, installPowerPath first, and then install VCS. Installing PowerPath firstavoids disruption to the cluster services at a later time. The VeritasStorage Foundation High Availability (SFHA) documentationprovides complete information on planning, configuring, managing,and troubleshooting VCS.

After installing PowerPath and VCS, run the emcphostid checkcommand to check for host conflicts. If the host IDs are not unique,run the emcphostid set command to set a unique host ID.



Installing PowerPath in an existing VCS environment

CAUTION!Be sure to follow the steps to manage your cluster environment.Failure to do so can result in data corruption and data loss. Refer tothe VCS documentation on how to configure and manage VCS in aclustered environment.

To install PowerPath in an existing VCS:

1. In the Cluster Administrator window, ensure all resources are onthe primary node in the cluster. When the cluster resources are onthe primary node, the ClusterService in the Status View dialogbox appears as online.

Note: The procedure for setting up VCS on Windows Server 2008 maydiffer from Windows Server 2003. The Veritas documentation providesadditional information. The procedure for installing PowerPath on VCSfollows the same steps as mentioned for VCS on Windows Server 2003.

2. From the navigation pane on the left, right-click ClusterServiceand select Disable. This disables the secondary node in the VCSconfiguration.

3. Install PowerPath on the secondary node. Follow the proceduresin “Installation procedures” on page 26.

4. After installation and reboot of the secondary node, right-clickClusterService and select Enable to re-enable the node in theVCS configuration.

5. Right-click ClusterService, select Switch to, and then select thesecondary node to move all cluster resources over to thesecondary node.

6. Run vxdisk list. You will see the devices are in the BasicGroupand RAW group.

The vxdisk list command will display the proper DiskType andDiskGroup information.

Installing PowerPath in an existing VCS environment 93

94


7. Once the resources are available on the secondary node:

a. Run vxassist rescan.

b. Run vxdisk list to verify the disks are now in the proper diskgroup and show MBR.

If there are additional nodes in the cluster configuration, repeatsteps 2 through 7 for each node.

8. Run the emcphostid check command to check for hostuniqueness. If the host IDs are not unique, run the emcphostidset command to set unique host IDs.

DiskType and DiskGroup informationThe vxdisk list command displays DiskType as RAW instead of MBRand all disks appear to be in the default DiskGroup BasicGroup afterthe installation of PowerPath.

C:\Documents and Settings\Administrator>vxdisk listName MediaName Diskgroup DiskStyle Size(MB) FreeSpace(MB) Status EnclosureID P#C#T#L#Harddisk0 BasicGroup MBR 156327 127327 Uninitialized DISKS@lhclu056 P0C0T0L0Harddisk1 Disk1 dg1 RAW 10236 0 Imported DGC0 P2C0T0L0Harddisk2 Disk2 dg1 RAW 10236 0 Imported DGC0 P2C0T1L1Harddisk3 Disk3 dg1 RAW 10236 5118 Imported DGC0 P2C0T0L2Harddisk4 Disk4 dg1 RAW 10236 5118 Imported DGC0 P2C0T1L3

C:\Documents and Settings\Administrator>vxassist rescanSuccessfully rescanned

Note: Notice disk now properly show diskstyle as MBR

C:\Documents and Settings\Administrator>vxdisk listName MediaName Diskgroup DiskStyle Size(MB) FreeSpace(MB) Status EnclosureID P#C#T#L#Harddisk0 BasicGroup MBR 156327 127327 Uninitialized DISKS@lhclu056 P0C0T0L0Harddisk1 Disk1 dg1 MBR 10236 0 Imported DGC0 P2C0T0L0Harddisk2 Disk2 dg1 MBR 10236 0 Imported DGC0 P2C0T1L1Harddisk3 Disk3 dg1 MBR 10236 5118 Imported DGC0 P2C0T0L2Harddisk4 Disk4 dg1 MBR 10236 5118 Imported DGC0 P2C0T1L3

1. Disable the primary node in the VCS configuration and installPowerPath as described in “Installation procedures” on page 26.

2. After installing PowerPath, reboot the primary node.

3. Re-enable the node in the VCS configuration.

4. Move all cluster resources over to the primary node. Once theresources are available, run vxassist rescan.


AInvisible Body Tagt

The appendix includes the following section:

◆ WHQL-certified driver...................................................................... 96

WHQL Certification

WHQL Certification 95

96

WHQL Certification

WHQL-certified driverOn Windows Server, the EMC PowerPath driver is WHQL-certified.To view the PowerPath driver signature:

1. Select Start > Settings > Control Panel.

2. From the Control Panel, open the System applet.

3. Click the Hardware tab.

4. Select Device Manager.

5. Expand the SCSI and RAID controllers node.

6. Right-click EMS device bus.

7. In the EMS device bus dialog box, select Properties.

8. Click the Driver tab.

9. Check the Digital Signer field to see the driver signatureinformation.

When the driver is signed, the field contains information aboutthe organization that assigned the driver.


BInvisible Body Tag

The appendix includes the following section:

◆ Files created by PowerPath installation.......................................... 98

Files Changed byPowerPath

Files Changed by PowerPath 97

98

Files Changed by PowerPath

Files created by PowerPath installationThe following files are added when PowerPath is installed on 32-bitand 64-bit hosts. These file locations can change if you do not installto the default locations during PowerPath installation.

Note: All driver files (.sys, .cat, and .inf) are copied to the internal systemdirectories by the operating system when they are installed.

Program Files\EMC\PowerPath◆ ckmadm.exe◆ cstadmin.exe◆ db_recover.ese◆ db_recover.exe.manifest◆ DIFxAPI.dll◆ EMC_PowerPath_Console.msc◆ EmcAdminProxy.dll◆ EmcAdminSvr.exe◆ emcp_mp_rtl.dll◆ emcp_mpio_win.dll◆ emcp_xcryptd.exe◆ emcphostid.exe◆ EmcpLogMsgs.dll◆ EmcPowerPathAdmin.dll◆ EmcPowPN22.dll◆ emcpreg.exe◆ Install.exe◆ libdb45.dll◆ libdb45.dll.manifest◆ libxml2.dll◆ powermig.exe◆ powermt.exe◆ powervt.exe◆ PowMigSrvc.exe◆ PPInstall*.xml◆ ppinstall_info.log◆ PPXMLHelper.dll◆ PPXMLWrite.exe◆ pthreadVC2.dll◆ RKM_Config.exe◆ RKM_Config_CHS.dll◆ RKM_Config_DEU.dll◆ RKM_Config_ESP.dll◆ RKM_Config_FRA.dll◆ RKM_Config_ITA.dll



◆ RKM_Config_JPN.dll◆ RKM_Config_KOR.dll◆ RKM_Config_PTB.dll◆ rkmc_cache_conv.exe

Program Files\EMC\PowerPath\32-bit (X64 and IA64 hosts only)◆ emcp_mp_rtl.dll◆ EmcPowPN22.dll

Program Files\EMC\PowerCommon◆ EmcLicTool.exe◆ EmcLicTool_CHS.dll◆ EmcLicTool_DEU.dll◆ EmcLicTool_ESP.dll◆ EmcLicTool_FRA.dll◆ EmcLicTool_ITA.dll◆ EmcLicTool_JPN.dll◆ EmcLicTool_KOR.dll◆ EmcLicTool_PTB.dll◆ emcp_lic_rtl.dll◆ emcp_mpapi_rtl.dll◆ EmcPowMon.exe◆ EmcPowRes.dll◆ EmcPowSrv.exe◆ EmcpSvcErr.dll◆ libeay32.dll◆ server.pem◆ ssleay32.dll

32-bit hosts only◆ emcp_lic_rtl.dll

Program Files\EMC\PowerCommon\32-bit (X64 and IA64 hosts only)◆ emcp_lic_rtl.dll

Program Files\EMC\PowerCommon\Drivers◆ EmcpBase.cat◆ Emcpbase.inf◆ EmcpBase.sys◆ EmcpClass.cat◆ EmcpClass.inf◆ EmcpClass.sys◆ EmcpCoinst30.dll◆ emcpdm.cat◆ emcpdm.inf◆ EmcpDm.sys

Files created by PowerPath installation 99

100


◆ emcpgpx.cat◆ emcpgpx.inf◆ EmcpGpx.sys◆ EmcpMd.cat◆ EmcpMd.inf◆ EmcpMd.sys◆ EmcpMpx.cat◆ EmcpMpx.inf◆ EmcpMpx.sys◆ EmcpXcr.cat◆ EmcpXcr.inf◆ EmcpXcr.sys◆ LamClar.cat◆ LamClar.inf◆ LamClar.sys◆ LamEss.cat◆ LamEss.inf◆ LamEss.sys◆ LamGen.cat◆ LamGen.inf◆ LamGen.sys◆ Lamhit.cat◆ Lamhit.inf◆ Lamhit.sys◆ Lamhpxp.cat◆ Lamhpxp.inf◆ Lamhpxp.sys◆ Lamhpsx.cat◆ Lamhpsx.inf◆ Lamhpsx.sys◆ LamInv.cat◆ Laminv.inf◆ Laminv.sys◆ LamSymm.cat◆ LamSymm.inf◆ LamSymm.sys◆ mpdev.inf◆ mpdev.sys◆ mpio.cat◆ mpio.inf◆ mpio.sys◆ mpspfltr.sys◆ RSA_CK.cat◆ RSA_CK.inf◆ RSA_CK.sys



Program Files\EMC\RSA\CST\lib (32-bit and X64 hosts)

Program Files\EMC\PowerPath\32bit\RSA\CST\lib (IA64 hosts)◆ aceclnt.dll◆ ccme_base.dll◆ ccme_ecc.dll◆ ccme_eccaccel.dll◆ ccme_eccnistaccel.dll◆ cryptocme2.dll◆ cryptocme2.sig◆ CSP.dll◆ CSP-AuthenticationService.dll◆ CSP-C.dll◆ CSP-CatalogPosix.dll◆ CSP-CatalogService.dll◆ CSP-CatalogWindows.dll◆ CSP-CertService.dll◆ CSP-Configuration.dll◆ CSP-DestinationAlert.dll◆ CSP-DestinationEventLog.dll◆ CSP-DestinationFile.dll◆ CSP-DestinationODBC.dll◆ CSP-DestinationSyslog.dll◆ CSP-EventSource.dll◆ CSPI.dll◆ CSPJNIWrappers.dll◆ CSP-LayoutFlat.dll◆ CSP-LayoutRaw.dll◆ CSP-LayoutXML.dll◆ CSP-lb.dll◆ CSP-LDAP.dll◆ CSP-LDAPClient.dll◆ CSP-LocalDirectory.dll◆ CSP-LocalizationService.dll◆ CSP-LogService.dll◆ CSP-MessageCatalog.dll◆ CSP-OSLogin.dll◆ CSP-PositionalFormatter.dll◆ CSP-RoleManagement.dll◆ CSP-RT.dll◆ CSP-SecurID.dll◆ CSP-Security.dll◆ CSP-SimpleCrypto.dll◆ CSP-SM.dll◆ CSP-SprintfFormatter.dll◆ CSP-TrustedUser.dll◆ CSP-UserManagement.dll


102


◆ CSP-XML.dll◆ CST-admin.dll◆ expat.dll◆ LBJNIWrappers.dll◆ osysrt.dll◆ osysrtxml.dll◆ RKM_Config.bat◆ sdmsg.dll

Program Files\EMC\RSA\CST\xml◆ Config.xml◆ Config-Template.xml◆ CSP.xml◆ CSP-Admin.xml◆ csp-app.xml◆ CSP-Authn.xml◆ CSP-CatalogPosix.xml◆ CSP-CatalogService.xml◆ CSP-CatalogWindows.xml◆ CSP-CertificateManagement.xml◆ CSP-Config.xml◆ CSP-DestinationAlert.xml◆ CSP-DestinationEventLog.xml◆ CSP-DestinationFile.xml◆ CSP-DestinationODBC.xml◆ CSP-DestinationSyslog.xml◆ CSP-LayoutFlat.xml◆ CSP-LayoutRaw.xml◆ CSP-LayoutXML.xml◆ CSP-LDAP.xml◆ CSP-LocalDirectory.xml◆ CSP-LocalizationService.xml◆ CSP-Logging.xml◆ CSP-OSLogin.xml◆ CSP-PAM.xml◆ CSP-PositionalFormatter.xml◆ CSP-RoleManagement.xml◆ CSP-saml-schema-assertion-1.1.xsd◆ CSP-saml-schema-assertion-2.0.xsd◆ CSP-SecurID.xml◆ CSP-SM.xml◆ CSP-SprintfFormatter.xml◆ CSP-TrustedUser.xml◆ CSP-UserManagement.xml◆ CSP-xenc-schema.xsd◆ xmldsig-core-schema.xsd



Program Files\EMC\RSA\Rkm_client\config◆ rkm_init.conf.tmpl◆ rkm_keyclass.conf.tmpl◆ rkm_registration.conf.tmpl◆ rkm_svc.conf.tmpl

Program Files\EMC\RSA\Rkm_Client\lib (32-bit and X64 hosts)

Program Files\EMC\PowerPath\32bit\RSA\Rkm_Client\lib (IA64 hosts)◆ ccme_base.dll◆ ccme_ecc.dll◆ ccme_eccaccel.dll◆ ccme_eccnistaccel.dll◆ cryptocme2.dll◆ cryptocme2.sig◆ CSP-lb.dll◆ CSP-Security.dll◆ kmclient_shared.dll◆ kmcryptolib.dll◆ kmsvcshlib.dll

Windows\Help ◆ EmcLicTool.chm◆ EmcLicToolCHS.chm◆ EmcLicToolDEU.chm◆ EmcLicToolESP.chm◆ EmcLicToolFRA.chm◆ EmcLicToolITA.chm◆ EmcLicToolJPN.chm◆ EmcLicToolKOR.chm◆ EmcLicToolPTB.chm◆ EmcPowerPathAdminMMC.chm

%USERPROFILE% ◆ PowerPath_V55.log(This log file will be created only with GUI-based installation andno parameter is passed to setup.exe)

Windows ◆ PPInstall_Log.txt


104



Index

Aadding logical devices 46adding paths 45administrator, loading configurations 79audit log 83

Bboot from SAN, upgrading PowerPath 25

Ccertification, WHQL 96CLARiiON storage systems 16complete install 28configuring the network after installing

PowerPath 20console settings, saving 80custom install 27

Ddocumentation, related 9downgrading PowerPath 41

EEMC ControlCenter (ECC) 47EMC Licensing Tool 67emcphostid check command 86, 90, 92, 94emcphostid utility 20emcpreg command 67error messages 83

incompatible files 37PowerPath detected a problem 37

PowerPath installation fails 37PowerPath upgrade could not complete 37

Ffile locations, default 98

Iicons, failure condition 72icons, PowerPath Administrator 71incompatible files error message 37INSTALLDIR installation property 31installing additional features at a later time 35installing PowerPath

CD-ROM, loading from 26complete install 28configuring the network after 20custom install 27first-time installation 19interactive installation 29postinstallation 33silent installation 29third party arrays, installing 27typical install 27VCS environment, into 93virtual environments, into 20

interactive installation 29interactive removal 58

LLCC (link control card) failure icons 73license registration key 17logical devices


106

Index

adding devices 46adding paths 45removing devices 49removing paths 48

MMicrosoft iSCSI initiator 52MMC (Microsoft Management Console) with

PowerPath snap-in 65MSCS (Microsoft Cluster Server)

moving resources 88, 89PowerPath integration 87

NNO_REBOOT property 31, 59

Ooperating system, upgrade 39

Ppatches. See also service packs 17paths, removing 48powermt.custom file conversion 25PowerPath Administrator

device properties 69failure condition icons 72icons 71loading configurations 79local host administration 75local host option 76remote host administration 75remote host option 77result pane 68scope pane 68undefined SP icons 73

PowerPath Configuration Checker (PPCC) 18, 23PowerPath detected a problem error message 37PowerPath encountered a problem error message

37PowerPath upgrade error message 37PPREMOVE uninstallation property 60ppremoveall 37

Rremoving logical devices 49removing paths 48removing PowerPath 54

interactive removal 58silent removal 58

Sservice packs 17, 23setting a local host 76setting a remote host option 77silent installation 29silent removal 58SMS (Systems Management Server) deployment

81Symmetrix storage systems 16

Tthird party array installation 27traybar monitor program modifications 82troubleshooting

powermt.custom file conversion 25typical install 27

UUAC (User Account Control) modifications 82uninstalling PowerPath 54upgrading PowerPath

before you upgrade 23boot from SAN 25operating system upgrade 39requirements 24

VVCS (Veritas Cluster Server), PowerPath

installing into 93virtual environments 20VNX OE storage systems 16vxdisk list command 94

WWHQL certification 96Windows Server 2008 operating system,

upgrading 39


Index

Windows Server 2008 R2 operating system,upgrading 39

Windows Server 2008 support modifications 82

107EMC PowerPath and PowerPath/VE for Windows Version 5.5 Installation and Administration Guide

108

Index


PowerPath for Windows Version 5.5

Documents

run ppremovealla

program dialog

lab interoperability

invisible

traybar monitor

run vxassist

powerpath

emc fibre