EMC PowerPath for Microsoft Windows · EMC PowerPath for Microsoft Windows Version 5.2 ......

EMC CorporationCorporate Headquarters:

EMC® PowerPath®

for Microsoft WindowsVersion 5.2

Installation and Administration GuideP/N 300-006-818

REV A04

Hopkinton, MA 01748-9103

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

2

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

Published November, 2009

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 for Microsoft Windows Version 5.2 Installation and Administration Guide

Contents

Preface ........................................................................................................................... 11

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

EMC Symmetrix storage systems.............................................16EMC CLARiiON storage systems ............................................16First-time PowerPath installations ...........................................16Obtaining up-to-date information............................................17Choose a convenient time..........................................................17Locating the license key.............................................................18Preparing the host and storage system ...................................18Booting from a storage array device ........................................19Preparing a cluster environment..............................................20Preparing the browser................................................................20

Installing PowerPath ........................................................................ 21Default interactive installation .................................................22Installing from the CLI...............................................................25For a new PowerPath installation ............................................29Installing additional features at a later time...........................29

After you install................................................................................. 31Verify and save configuration ..................................................31

Upgrading PowerPath ..................................................................... 32Uninstalling previous PowerPath components .....................32Installing a new version of PowerPath without rebooting...33Before upgrading PowerPath....................................................33Upgrade procedure ....................................................................35Upgrading PowerPath in boot from SAN Setup....................36

Installing a PowerPath service pack .............................................. 37Service packs and configuration files ......................................37

EMC PowerPath for Microsoft Windows Version 5.2 Installation and Administration Guide 3

Contents

Upgrading Windows operating systems ...................................... 40Upgrading to Windows Server 2008 and WindowsServer 2008 R2 ............................................................................. 40

EMC Registration Tools ................................................................... 41EMC Licensing Tool ................................................................... 41emcpreg command..................................................................... 41

Coexistence with third-party path management software......... 43

Chapter 2 Removing PowerPathBefore you remove PowerPath ....................................................... 46

Uninstall problem resolution (Technical Advisoryemc194413) .................................................................................. 46

Removing PowerPath from a Windows host ............................... 47Uninstalling PowerPath by using Add/Removeprograms...................................................................................... 47Uninstalling PowerPath by using the programs andfeatures panel .............................................................................. 48Uninstalling PowerPath from the command line .................. 49Uninstalling additional features at a later time ..................... 52

Chapter 3 PowerPath AdministratorOverview............................................................................................ 56PowerPath monitor .......................................................................... 56

Launching MMC with the PowerPath snap-in ...................... 57PowerPath Administrator ............................................................... 59

PowerPath Administrator panes.............................................. 59PowerPath Administrator device properties dialog box...... 60Icons: standard, unlicensed, and unknown conditions ........ 62Icons: known failure conditions ............................................... 63

Local or remote administration ...................................................... 65Setting a local host option ......................................................... 66Setting a remote host option ..................................................... 67

Saving console settings .................................................................... 69Windows Server 2008 Support ....................................................... 70

Chapter 4 PowerPath in an MSCS ClusterInstalling PowerPath and MSCS .................................................... 72Integrating PowerPath into an existing MSCS cluster ................ 73

Moving all resources to node A................................................ 74Installing PowerPath on node B............................................... 75

EMC PowerPath for Microsoft Windows Version 5.2 Installation and Administration Guide4

Contents

Configuring additional paths between the storage systemand Node B ..................................................................................75Moving all resources to Node B................................................75Installing PowerPath on node A...............................................76Configuring additional paths between the storage systemand node A...................................................................................76Returning node A resources to node A ...................................76

Chapter 5 PowerPath in a Veritas Cluster ServerInstalling PowerPath and VCS........................................................ 78Installing PowerPath in an existing VCS environment ............... 79

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

Appendix B Files Changed by PowerPathPowerPath files .................................................................................. 88

Index ................................................................................................................................ 91

5EMC PowerPath for Microsoft Windows Version 5.2 Installation and Administration Guide

Contents


Title Page

Figures

1 Sample PowerPath Administrator display ................................................. 602 Cluster Administrator .................................................................................... 743 VCS Administrator ......................................................................................... 804 Disabling a secondary node in a VCS ......................................................... 815 Enabling a node in a VCS .............................................................................. 826 Moving cluster resources to secondary node ............................................. 83


Figures


Title Page

Tables

1 SIlent Installation parameters ........................................................................262 Installation properties .....................................................................................273 Interactive installation parameters ...............................................................284 Upgrading from previous PowerPath releases ...........................................325 Removing multiple PowerPath versions .....................................................356 Silent removal parameters .............................................................................507 Removal Properties .........................................................................................508 PowerPath monitor taskbar icons .................................................................579 Icons on the PowerPath Administrator ........................................................6210 Icons of known PowerPath failure conditions ............................................6311 PowerPath files ................................................................................................88


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 Migration Enabler User Guide

◆ EMC PowerPath Migration Enabler Release Notes

◆ EMC PowerPath Product Guide

◆ EMC PowerPath for Microsoft Windows Release Notes

◆ EMC PowerPath Encryption with RSA User Guide

◆ EMC PowerPath Encryption with RSA Release Notes


12

Preface

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 CLARiiON storage systems, referalso to the EMC host connectivity guides and the CLARiiONStorage-System Support website (www.emc.com\clariionsupport).

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.

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

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


http://powerlink.emc.com

Preface

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

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.

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.

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


14

Preface


1Invisible Body Tag

This chapter includes the following sections:

◆ Before you install................................................................................ 16◆ Installing PowerPath ......................................................................... 21◆ After you install.................................................................................. 31◆ Upgrading PowerPath....................................................................... 32◆ Installing a PowerPath service pack................................................ 37◆ EMC Registration Tools .................................................................... 41◆ Upgrading Windows operating systems........................................ 40◆ Coexistence with third-party path management software .......... 43

Installing PowerPath

Installing PowerPath 15

16


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

PowerPath® on a host depends on the storage system you use.

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

EMC CLARiiON storage systemsPowerPath installation is an integral part of an EMC CLARiiON®

setup and configuration procedure.

For information on when to install PowerPath on a host attached to aCLARiiON storage system, refer to the CLARiiON storage-systemsupport website (www.emc.com\clariionsupport). From the homepage, select your storage system type, then use the Attach server link(CX4 systems) 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.

First-time PowerPath installationsRemove any version of EMC Navisphere® Application TransparentFailover (ATF) installed on the 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 perform themigration yourself, you risk the loss of data.



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

❑ PowerPath documentation — EMC updates PowerPathdocumentation, including this installation guide, when it releasesnew features with a service pack or when documentation errorsare reported. To obtain updated PowerPath documentation onPowerlink, select Support > Technical Documentation andAdvisories > Software ~ P-R ~ Documentation > PowerPath.

❑ 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 > SoftwareDownloads and Licensing > Downloads P-R > PowerPath forWindows systems.

❑ EMC Issue Tracker — EMC Issue Tracker is an application onPowerlink that allows you to search for known problems anddefects in EMC software. To access Issue Tracker, on Powerlinkselect Support > Interoperability and Product LifecycleInformation > E-Lab Issue Tracker Information > E-Lab IssueTracker.

You can use the Issue Tracker to find:

• Descriptions of PowerPath bugs existing on any host platformthat is supported by PowerPath.

• Workarounds for existing bugs

EMC updates this database regularly between scheduled releasesand service pack releases.

Choose a convenient timeInstalling PowerPath requires you to reboot the host. Plan to install orupgrade PowerPath when a reboot will cause minimal disruption toyour site.

Before you install 17

18


Locating the license keyThe PowerPath license registration key is on the License Key Cardthat you received from EMC. Take note of the following regardinglicenses:

◆ Installing PowerPath on a host connected to a CLARiiONAX-series array does not require a license. PowerPath providesfull support, with or without a PowerPath license, when the hostis connected 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 additional featuressuch as PowerPath Migration Enabler and PowerPath Encryptionwith RSA®.

◆ Type the registration number exactly as written on the card. Toreduce common typographical errors, the License Key fieldaccepts 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, consultthe online help file by pressing F1 from the EMC Licensing Tool.You must have Internet Explorer 5.0 or later to view these files. Ifyou do not have this browser installed, you may still view thehelp file, EmcLicTool.chm, directly from the \help folder on thePowerPath installation CD.

Preparing the host and storage systemTo prepare the host and storage system:

❑ Verify that your environment meets the requirements found inthe following:

• EMC PowerPath for Windows Release Notes, which describesminimum hardware and software requirements for the hostand supported storage systems.

• Refer to the EMC E-Lab™ Interoperability Navigator,available on the Powerlink website and productdocumentation for topologies that PowerPath supports.



❑ Verify that Microsoft MPIO framework 1.21 is installed.

• If the MPIO framework is not installed on the host, thePowerPath installer installs MPIO framework 1.21.

• If a version of the MPIO framework earlier than 1.21 isinstalled on the host, the PowerPath installer prompts you toupgrade to version 1.21. If you do not upgrade, the PowerPathinstallation aborts.

• If a version of MPIO framework later than 1.21 is installed,PowerPath provides the option to abort the installation. Verifythe MPIO compatibility by using the EMC PowerPath forWindows Release Notes or refer to the E-Lab Navigator databasefor additional information before proceeding.

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

❑ Configure HBA drivers. Be sure to follow the HBA driverconfiguration guidelines outlined by EMC. Refer to the E-LabInteroperability Navigator, available on the Powerlink websiteand HBA vendor documentation. The use of improper settingscan cause erratic failover behavior, such as greatly increased I/Odelays.

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

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

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

Install PowerPath after configuring the storage array boot device.There should be just a single path from the host to the storage arraydevice when you install PowerPath. Connect the additional pathsafter installing PowerPath and rebooting the host.

Before you install 19

20


Preparing a cluster environmentChapter 4, ”PowerPath in an MSCS Cluster,” provides informationon installing PowerPath in a new or existing cluster.

Preparing the browser❑ Verify that you have Internet Explorer 5.0 browser or higher

installed on your system.

❑ Check the EMC License Tools online help for assistance onregistering PowerPath. If you do not already have a license in theregistry, the EMC Licensing Tool displays during the installationas described in “Installing PowerPath software” on page 22.Access online help for this application from the Help button or F1key. If you do not have the correct browser installed, you can runthis help file directly from the installation CD. The “EMCRegistration Tools” on page 41 provides additional informationon this topic.



Installing PowerPathPowerPath 5.2 installation allows feature-level installation ofPowerPath, which means that the required features can be selected orcleared for installation.

PowerPath installation is grouped by three different features:

◆ EMC PowerPath

◆ PowerPath Migration Enabler

◆ PowerPath Encryption with RSA

The EMC PowerPath feature is selected by default during theinstallation. If you choose EMC PowerPath as the main feature, itcannot be cleared. The Migration Enabler and Encryption with RSAfeatures require you to select them expressly for installation.

PowerPath can be installed by using one of the following:

◆ Default interactive dialog boxes.

◆ Advanced command line options.

Windows Server Core 2008Windows Server Core 2008 supports PowerPath installation throughthe CLI or GUI.

To install PowerPath through the CLI on Windows Server Core 2008,specify the license key within the command line. When PowerPath isinstalled through the GUI, the license key dialog box does not appear.After GUI installation, use the CLI emcpreg utility to add thePowerPath license key and then reboot.

Note: CLI installation is the preferred method in Windows Server Core 2008,because the GUI does not prompt for the license key.

Any other PowerPath license key management with the server corecan be done through the emcpreg utility, which is described in“emcpreg command” on page 41.


22


Default interactive installationUse this procedure to install PowerPath with the default interactiveprompts.

Note: For a new PowerPath installation, do not connect multiple paths fromthe HBAs to the storage system interface ports or switches until you haveinstalled PowerPath and shut down the host. Follow the procedures in “For anew PowerPath installation” on page 29.

Loading the CD-ROM To load the CD, insert the PowerPath installation CD.

◆ If autoplay is enabled, your browser launches and displays theGetting Started page.

• You can install the software from the Installation section byclicking the appropriate link for your operating system. Toproceed with the installation:

a. Choose Run this program from its current location (or asimilar message depending on your browser).

b. Click OK.

c. Proceed to step 4 of the “Installing PowerPath software” onpage 22 section.

◆ If autoplay is not enabled, proceed to “Installing PowerPathsoftware” on page 22.

Downloading fromPowerlink

To download from Powerlink:

1. From the Support menu, select Software Downloads andLicensing > Downloads P-R > PowerPath for WindowsSystems.

2. Choose your appropriate Windows platform.

3. Save to your local directory.

Installing PowerPathsoftware

To install PowerPath software:

Note: You must have administrative rights to install PowerPath.

1. From the Start menu, select Run.



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

<drive>:\<windows_version>\<PowerPath_package_name>

3. Click OK.

4. On the Choose Setup Language screen, select the language forthis installation from the list and click OK. Localized versions ofthe PowerPath installer are available in Brazilian Portuguese,Latin American Spanish, French, German, Italian, Japanese,Korean, and simplified Chinese.

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

6. On the CLARiiON AX-series screen, do one of the following:

• If this host connects exclusively to CLARiiON AX-seriesarrays, select Yes and click Next.

• If this host does not connect exclusively to CLARiiONAX-series arrays, select No and click Next.

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

8. Click Next to install PowerPath in the default directory, andproceed to step 9.

Note: EMC recommends that you install PowerPath in the defaultdirectory. No action is required to install in the default directory.

To install PowerPath in a directory other than the default:

a. Select the Destination Folder.

b. Click Change.

c. Click OK after selecting the destination folder.

d. Click Next.

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.


24


9. On the Setup Type dialog box, select Typical Install, CustomInstall, or Complete Install as follows:

• To install PowerPath with the default features selected, selectTypical Install and click Next.

Note: If you are upgrading from PowerPath 5.0 or later, the MigrationEnabler feature will also be selected by default.

• To install additional features, select Custom Install andMigration Enabler and/or Encryption with RSA.

a. Select This feature will be installed on local hard drive.

b. Click Next.

Note: Choosing This feature, and all subfeatures, will be installedon the local hard drive, will have the same results.

• To install PowerPath with all features, select Complete Installand click Next.

Note: If you are upgrading from PowerPath 5.0 or later, with anexisting Migration Enabler license key, Migration Enabler is selectedby default.

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

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

Note: The EMC Licensing Tool does not display when PowerPath isbeing installed on a host connected to a CLARiiON AX-series array. Insuch cases, proceed to step 13.

11. When prompted by the EMC Licensing Tool:

a. Type your 24-digit registration number in the License Keyfield.

b. Click Add.

c. Click OK.

If you are upgrading from a previous version, PowerPath savesthe existing license key, and no input is required. “Locating thelicense key” on page 18 provides additional information.



Note: If you want to enable Migration Enabler and/or PowerPathEncryption with RSA, enter the additional license key or keys at thistime.

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

13. The setup wizard appears and asks if you want to reboot the host,click No.

Note: Yes will automatically restart the host.

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

After the host restarts, follow the instructions in “After you install”on page 31 to connect additional paths from the host to the array.

Installing from the CLIPowerPath supports two types of CLI installations:

◆ Silent installations — Unattended PowerPath installation thatuses command-line parameters which do not require any userinput.

◆ Interactive installations — Attended PowerPath installation thatrequires user input.

Note: For a new PowerPath installation, do not connect multiple paths fromthe HBAs to the storage system interface ports or switches until you haveinstalled PowerPath and shut down the host. Follow the procedures in “For anew PowerPath installation” on page 29.

Silent installation To perform a silent PowerPath installation, type the appropriatecommand in a single line:

<drive>:\<windows_version>\<PowerPath_package_name> /s /v"/q /L*v<logfile> <Property=PropertyValue> <Property=PropertyValue>"

where:

• <drive> is the drive letter, for example, C.• <windows_version> is W2003, or W2008• <PowerPath_package_name> is the PowerPath package name.

For example, EMCPP.W2008_x64.5.2.0.GA.exe


26


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

Note: Ensure the specified directory exists within the specified path.

• <Property=PropertyValue> is one or more optionalproperties.

Note: PowerPath installation aborts if you attempt to install it on a host thathas a version of MPIO framework earlier than 1.21. To install PowerPath on ahost with a version of MPIO framework earlier than 1.21, specify theUPGRADE_MPIO=1 property described in Table 2 on page 27.

Table 1 describes the variables used in the syntax.

Table 1 SIlent Installation parameters

Variable Function

/s Suppresses installation shield dialog boxes.

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

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

/L*v<logfile>

Directs the Microsoft Installer to write verbose output to the file specified with thisoption. The target directory for the log file must exist before starting a silentinstallation by using the logging option (as required by the Windows installerengine).



Table 2 describes the optional properties.

Note: After PowerPath is installed, restart the host and follow theinstructions in “After you install” on page 31 to connect additional pathsfrom the host to the array.

Example of silent installationThe following is a valid command line for silent installation andperforms the following functions:

◆ Logs silent installation.◆ Sets the PowerPath License.◆ Disables reboot at completion.◆ Enables Migration Enabler feature for installation.

Table 2 Installation properties

Properties Description

LICENSENUM=<license_key> Value must be a valid license or no license will be saved.

INSTALL_DRIVE=<drive> Drive on which PowerPath will be installed. By default, PowerPath isinstalled on the C: drive.• The installation uses only first character entered and must be a valid

drive letter or the default drive will be used.• The INSTALL_DRIVE value will be ignored if the same version of

PowerPath is already installed on the host.

NO_REBOOT=1 Host will not reboot after PowerPath is installed.

Note: EMC recommends NO_REBOOT=1 so that you can manuallyrestart at a convenient time.

UPGRADE_MPIO=1 Used to upgrade the existing framework version on the host if a lowerversion of MPIO framework is installed on the host a.

ADDLOCAL=<feature> Specifies the features to install. Use commas to separate multiple entries,for example: ADDLOCAL=ME,RSA• ME = Migration Enabler• RSA = Encryption with RSA (not available with Windows 2008)

Note: EMC PowerPath is installed by default.

a. The UPGRADE_MPIO=1 switch is required for all PowerPath 4.6 and later upgrades, if there is an existing MPIODSM framework earlier than 1.21 installed on the host.


28


C:\W2008\EMCPP.W2008_x64.5.2.0.GA.exe /s /v"/q /L*vC:\logs\PPsetup.log LICENSENUM=0000-0000-0000-0000-0000-0000NO_REBOOT=1 ADDLOCAL=ME"

Interactive installation To perform an interactive installation of PowerPath by using the CLI,type the appropriate command in a single line:

<drive>:\<windows_version>\<PowerPath_package_name> /v"/L*v <logfile><Property=PropertyValue> <Property=PropertyValue>"

“Silent installation” on page 25 contains a description of thearguments.


Table 2 on page 27 contains a description of the optional properties.

Note: After PowerPath is installed, shut down the host and follow theinstructions in “After you install” on page 31 to connect additional paths.

Example of interactive installationThe following is a valid command line for interactive installationsand performs the following functions:

◆ Logs interactive installation.◆ Sets the PowerPath License.◆ Sets the PowerPath install drive.◆ Disables reboot at completion.

C:\W2008\EMCPP.W2008_x64.5.2.0.GA.exe /v"/L*v C:\logs\PPsetup.logLICENSENUM=0000-0000-0000-0000-0000-0000 INSTALL_DRIVE=Z NO_REBOOT=1"

Table 3 Interactive installation parameters

Variable Function

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

/L*v<logfile>

Directs the Microsoft Installer to write verbose output to the filespecified with this option. The target directory for the log file must existbefore starting an interactive installation that uses the logging option(as required by the Windows installer engine).



For a new PowerPath installationFor a new PowerPath installation, do not connect multiple paths fromthe HBAs to the storage system interface ports or switches until youhave installed PowerPath and shut down the host.

Do the following:

1. Confirm that there is a single path from the host to each device onthe array.

2. Install PowerPath.

For more information on PowerPath installation, see “InstallingPowerPath” on page 21.

3. Shut down the host.

4. Connect additional cables from the host to the array.

5. Restart the host.

Installing additional features at a later timeIf multipathing is already installed on your host and you want toinstall additional features at a later time, such as Migration Enablerand/or Encryption with RSA, you can install these features by usingthe GUI or CLI.

Installing additionalfeatures using the GUI

To install additional features at a later time using the GUI:

1. Open the Control Panel and double-click:

• For Windows Server 2003:

Add/Remove Programs


Programs and Features panel

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


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


30


5. To select a specific feature (Migration Enabler and/or Encryptionwith RSA), click the drop-down arrow beside the listed feature onthe 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 be installed on local hard drive.

b. Click Next.

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


8. The setup wizard appears and asks if you want to reboot the host.Click No.



Installing additionalfeatures using the CLI

To install additional features at a later time by using the CLI, type theappropriate command in a single line:

Note: Additional features can be installed by both the Silent or InteractiveCLI types of installation.

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

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

See “Silent installation” on page 25 for a description of thearguments.



After you installThis section describes tasks you need to complete after you installPowerPath on a Windows host:

1. With the host shut down, connect the remaining cables from theHBAs to the storage system interface ports, hubs, or switches, orzone multiple paths. For cabling instructions, refer to the productguide for your storage system and, depending on your type ofstorage system, the host connectivity guides or the CLARiiONstorage-system support website(www.emc.com\clariionsupport).

2. Power on the host.

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

3. If the environment is Fibre Channel, ensure zones are configuredappropriately. The CLARiiON storage-system support websiteand the host connectivity guides provide additional information.

4. If you have not already done so, check Powerlink for any servicepacks to PowerPath 5.2, and install any required service packs.

Verify and save configurationTo verify and save 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

3. Save the configuration to the file powermt.custom by runningpowermt save.

After you install 31

32


Note: If PowerPath sees no devices, but the devices are seen by the operatingsystem, verify that the devices are configured for PowerPath support, assuggested in “Before you install” on page 16.

Upgrading PowerPathYou can only upgrade to PowerPath 5.2 from one of the previousPowerPath releases shown in Table 4.

Uninstalling previous PowerPath componentsIf you are upgrading to PowerPath 5.2 from a previous version ofPowerPath, follow these guidelines:

◆ If you are currently running an earlier version of PowerPath notlisted in Table 4, uninstall that version of PowerPath (for example,PowerPath 2.1.3) and perform a fresh installation of PowerPath5.2.

◆ If you are currently running any of the PowerPath versions listedin Table 4, you can upgrade the host directly to PowerPath 5.2without uninstalling the listed version. Do not uninstall anyexisting version of PowerPath on the host before upgrading toPowerPath 5.2.

◆ If a hot fix from an earlier version is installed on the host, then besure to uninstall the hot fix of that earlier version of PowerPathbefore installing PowerPath 5.2.

Table 4 Upgrading from previous PowerPath releases

Windows version PowerPath version PowerPath iSCSI version

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

4.1.x, 4.3.x, 4.4.x, 4.5.x,4.6.x, 5.0.x, and 5.1.x

1.1

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

4.1.x, 4.3.x, 4.4.x, 4.5.x,4.6.x, 5.0.x, and 5.1.x

Not supported

Windows Server 2003,x64-based version

4.4.1, 4.5.x, 4.6.x, 5.0.x,and 5.1.x

Not supported

Windows Server 2008 5.1 SP2 Not supported



Installing a new version of PowerPath without rebootingIf an early version of PowerPath is uninstalled, then a later version ofPowerPath is installed without rebooting, the system panics.

To prevent this issue, reboot after installing, uninstalling, orupgrading PowerPath.

Note: When the system is not rebooted after installing, uninstalling, orupgrading PowerPath, the operating system mixes the uninstallation of theold drivers with the installation of the new drivers which causes the systempanic.

Before upgrading PowerPathNote the following items before upgrading to PowerPath 5.2:

◆ Before upgrading to PowerPath 5.2 for Windows:


– For Windows Server 2003:Add/Remove Programs

– For Windows Server 2008:Programs and Features panel

2. Verify only one version of PowerPath appears in the list ofinstalled programs.

If only one PowerPath version appears, proceed with thestandard upgrade procedure, as described in “Upgradeprocedure” on page 35.

If multiple versions of PowerPath appear, refer to “Multipleversions of PowerPath” on page 34.

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

◆ PowerPath 5.2 requires Microsoft MPIO framework 1.21 or later.

• If the MPIO framework is not installed on the host, thePowerPath installer installs MPIO framework 1.21.

Upgrading PowerPath 33

34


• If a version of the MPIO framework earlier than 1.21 isinstalled on the host, the PowerPath installer prompts you toupgrade to version 1.21. If you do not upgrade, the PowerPathinstallation aborts.

• Verify the MPIO compatibility with the EMC PowerPath forWindows Release Notes or refer to the E-Lab Navigator databasefor additional information before proceeding.

• If a version of MPIO framework later than 1.21 is installed,then PowerPath provides the option to abort the installation.Verify the MPIO compatibility with the EMC PowerPath forWindows Release Notes or refer to the E-Lab Navigator databasefor additional information before proceeding.

◆ Run the powermt save command to ensure that you have savedthe latest PowerPath configuration information.

◆ Stop powermt display if it is running. The EMC PowerPath FamilyCLI and System Messages Reference Guide provides additionalinformation on powermt display.

◆ Upgrading to PowerPath 5.2 preserves license, registration, andconfiguration information. You do not need to reenter the licenseon a host that has a valid PowerPath license. If you have a validPowerPath iSCSI 1.1 license key installed, then it will beconverted to a PowerPath base license. A PowerPath base licenseprovides the same protection as a PowerPath iSCSI license key.

Note: If you are adding a license for another PowerPath feature, such asPowerPath Migration Enabler or PowerPath Encryption with RSA, usethe EMC Licensing Tool or the emcpreg utility to add the additionallicense.

◆ If a hot fix from an earlier version is installed on the host, then besure to uninstall the hot fix of that earlier version of PowerPathbefore installing PowerPath 5.2.

◆ Do not remove the redundant cable connections to the array.

Multiple versions of PowerPathIf you previously upgraded from PowerPath 4.x.x to PowerPath 4.x.x(for example, from 4.3.1 to 4.5.1), multiple versions of PowerPath mayappear in the Add/Remove Programs window (Windows Server2003) or the Programs and Features panel (Windows Server 2008).

Upgrading from PowerPath 4.x to PowerPath 5.2 does not createmultiple versions in Add/Remove Programs. However, if multiple



versions existed on the host when you upgraded to 5.2, the upgradeprocess does not remove the older versions.

Table 5 on page 35 describes the possible scenarios and how to correctthem.

CAUTION!Do not attempt to uninstall the earlier PowerPath versions usingAdd/Remove Programs. Doing so causes a host crash.

Upgrade procedureYou can upgrade PowerPath by using the default interactive dialogsor by using more advanced command line options.

Note: You must have administrative rights to upgrade PowerPath.

Default interactive installationFollow the procedure in “Default interactive installation” on page 22to upgrade to PowerPath by using the default interactive dialogprompts. Note the following differences:

Table 5 Removing multiple PowerPath versions

Problem Corrective action

Two versions of PowerPath appear in Add/Remove Programs (for example, 4.3.1 and4.5.1), and you have not yet upgraded to PowerPath 5.2.

1. Contact Customer Support to get thePowerPath Removeall utility, whichremoves all PowerPath versions onthe host.

2. After removing all PowerPath versionsby using PowerPath Removeall, do afresh install of PowerPath 5.2 asdescribed in “Installing PowerPath” onpage 21.

Three versions of PowerPath appear in Add/Remove Programs (including PowerPath5.2).

Note: PowerPath 5.2 functionality works as expected in spite of the multiple versionentries. However, correct this issue to avoid the host crash scenario described later inthis table.

A host crash occurred while attempting to uninstall earlier versions of PowerPath byusing Add/Remove Programs.

Note: When the host restarts, do not attempt to uninstall PowerPath by usingAdd/Remove Programs.

Upgrading PowerPath 35

36


◆ If the upgrade procedure detects the powermt.custom file on thehost, it prompts you to save or delete this file. If your hardwareconfiguration has not changed, keep the existing file. If yourhardware configuration has changed, delete the existingpowermt.custom file.

◆ If you have a valid PowerPath iSCSI 1.1 license key installed, thenit will be converted to a PowerPath base license. A PowerPathbase license provides the same protection as a PowerPath iSCSIlicense key.

◆ Reboot the host when prompted by the PowerPath installer.

From the command lineFollow the procedure in “Installing from the CLI” on page 25 toupgrade from the command line. You do not need to include theLICENSENUM property if the host already has a valid PowerPathlicense.

Upgrading PowerPath in boot from SAN SetupPowerPath supports an upgrade from previous PowerPathsupported versions installed on a server booting from SAN. Thisupgrade can be done either by interactive installation or from theCLI.

◆ Table 4 on page 32 identifies the supported upgrade versions.

◆ “Uninstalling previous PowerPath components” on page 32 and“Before upgrading PowerPath” on page 33 contain additionalinformation on removing or upgrading PowerPath.



Installing a PowerPath service packBefore you install a service pack, PowerPath 5.2 for Windows Server2003 or Windows Server 2008 must be installed on the host.

Service packs and configuration filesPowerPath 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. Aftera service pack is applied, the format of the configuration file maychange so it is no longer backward compatible.

To avoid losing configuration information, follow the steps in theappropriate section below.

Note: If a hot fix from an earlier version is installed on a host, then be sure touninstall the hot fix of that earlier version of PowerPath before installing theservice pack. The PowerPath base product does not need to be uninstalled,just the hot fix. Reboot the host after removing the hot fix and prior toinstalling PowerPath. A reboot is also required after installing the PowerPathservice pack is applied or installed.

Saving and loading configurations from the command line interface (powermt)To save and load configurations with the powermt utility:

1. Before installing a service pack, back up your old configurationfile. Use the backup to restore your configuration if you uninstallthe service pack later.

powermt save [file=pathname]

2. After installing a service pack and verifying the configuration iscorrect, save your configuration. This ensures the configurationfile is updated to the current format.

powermt display [paths|ports]

Note: The EMC PowerPath Family CLI and System Messages ReferenceGuide provides additional information on the powermt utility.

Installing a PowerPath service pack 37

38


Saving and restoring configurations from the PowerPath AdministratorTo save and load configurations from PowerPath Administrator:

1. Before installing a service pack, back up your configuration file.Use the backup to restore your configuration if you uninstall theservice pack later. “Saving configurations” on page 38, and“Loading configurations” on page 39 provide additionalinformation.

2. After installing a service pack and verifying the configuration iscorrect, save your configuration. This ensures the configurationfile is updated to the current format. “Saving configurations” onpage 38 provides additional information.

Saving configurationsFrom PowerPath Administrator, you can save your configuration anytime. If you do not save your changes, they will be lost on reboot. Youcan save EMC PowerPath Administrator settings to a configurationfile. The file records the serial numbers, mode, policy, and priority foreach configured path.

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.

Use the following procedure to save a PowerPath configuration:

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

2. To save the configuration with the default filename, right-clickthe root node and select All Tasks > Save Config for Reboot.

To save the configuration with a different name, select SaveConfig as. In the Save As dialog box:

a. Navigate to your directory.

b. Type a filename.

c. Click Save.



Note: In the EMC PowerPath Administrator, you can save yourconfiguration at any time. However, the active PowerPath configurationon your desktop does not reflect the saved configuration until you runthe Save Config for Reboot or the Save Config as command. Saving aconfiguration overwrites any previous configuration data.

Loading configurationsYou can load the last known reboot state or alternatively, a previouslysaved EMC PowerPath Administrator configuration 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.

Note: The first time you run EMC PowerPath Administrator, there is adefault configuration. If you make changes to this configuration usingthe EMC PowerPath Administrator that you want to keep, save theconfiguration.

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

Installing a PowerPath service pack 39

40


Upgrading Windows operating systemsYou can upgrade your Windows operating system from WindowsServer 2003 to Windows Server 2008 or Windows Server 2008 R2.

Note: EMC PowerPath for Windows Release Notes provides informationon the required service packs on different operating systems,supported versions of PowerPath, and any other system informationthat may apply to the operating system you plan to install.

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 5.2 installed) toWindows Server 2008 or Windows Server 2008 R2 (Release 2)

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

the operating system upgrade will fail. This issue is also documentedin EMC Knowledgebase Solution emc221704.

Procedure To upgrade to Windows Server 2008 and Windows Server 2008 R2:

1. Remove PowerPath.

2. Upgrade the Windows operating system.

3. Install PowerPath 5.2.



EMC Registration ToolsThere are two ways to register PowerPath and other EMC products:

◆ EMC Licensing Tool

◆ emcpreg command

EMC Licensing ToolThe EMC Licensing Tool is used to register PowerPath and otherEMC products, from the Windows GUI. The EMC Licensing Tool isdisplayed during PowerPath installation (except when the host isconnected to a CLARiiON AX-series array). To manage licenses, youmay launch the tool at any time by selecting Start > Programs > EMC> PowerPath Licensing Tool.

Use the EMC Licensing Tool to add or remove licenses. For moreinformation, see the online help for the EMC Licensing Tool (press F1)or launch the help file, EMCLicTool.chm, available in the PowerPathCD under the \help directory.

Note: You must have Internet Explorer 5.1 or later to view the online helpfiles from the EMC Licensing Tool by pressing F1. If you do not have thisbrowser installed, you may still view the help file directly fromEMCLicTool.chm, that resides on the PowerPath CD under the \helpdirectory.

emcpreg commandStarting with the 5.2 release, emcpreg was added as a command lineutility for license key management. This utility facilitates scriptoptions and supports license management for the core version ofWindows Server 2008. This utility is available in all Windowsplatforms that are supported by 5.2.

To add a license with emcpreg command line, enter:

emcpreg -add <key>

where <key> is the product license key.

EMC Registration Tools 41

42


Note: If PowerPath is installed through the GUI on the core version, thelicense key dialog box will not appear. Before rebooting, use the emcpregutility to add the PowerPath license key.

The EMC PowerPath Family CLI and System Messages Reference Guide,available on the EMC Powerlink website, contains more informationon the emcpreg command line utility.



Coexistence with third-party path management softwarePowerPath 5.2 can coexist with third-party path managementsoftware such as:

◆ Hitachi Dynamic Link Manager (HDLM)

◆ IBM Subsystem Device Driver (SDD)

◆ HP StorageWorks Secure Path

◆ HP StorageWorks AutoPath XP Virtual Array

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

Coexistence with third-party path management software 43

44



2Invisible Body Tag


◆ Before you remove PowerPath ........................................................ 46◆ Removing PowerPath from a Windows host ................................ 47

Removing PowerPath

Removing PowerPath 45

46

Removing PowerPath

Before you remove PowerPathBefore you remove PowerPath from the host:

❑ Check Powerlink or contact EMC Customer Support for the mostcurrent information. EMC updates release notes periodically andposts 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: You will be unable to uninstall PowerPath if you are runningPowerPath Migration Enabler. The message: "Migration(s) is (are) pending.Cannot uninstall" appears and the uninstalling of PowerPath abruptly stops.Contact EMC Customer Support if a message "An internal error has occurred.Migrations may be pending" appears.

Uninstall problem resolution (Technical Advisory emc194413)The PowerPath 5.2 (build 146) software update fixes theuninstallation problem found in PowerPath 5.2 (build 144) andPowerPath 5.1 SP2.

The EMC PowerPath for Windows Release Notes and Technical Advisoryemc194413 describe the appropriate corrective action.


Removing PowerPath

Removing PowerPath from a Windows hostPowerPath 5.2 allows feature-level removal of PowerPath, whichmeans that the features can be selected or cleared for removal.

CAUTION!Data corruption is possible if multiple paths remain on a systemafter PowerPath has been removed. Make sure that you remove anyredundant paths during the uninstall process by following theinstructions in this section.

You can remove PowerPath:

◆ Using the Add/Remove Programs wizard in Windows 2003

◆ Using the Programs and Features panel in Windows 2008

◆ Using the command line interface

Note:—Rebooting is recommended when removing PowerPath.—If a hot fix from an earlier version is installed on a host, be sure to uninstall

the hot fix of that earlier version of PowerPath before uninstalling theprimary package.

Uninstalling PowerPath by using Add/Remove programsTo uninstall PowerPath using Add/Remove Programs in WindowsServer 2003:

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

2. On the Add/Remove Programs panel, select the installed versionof PowerPath, and click Remove.

3. When prompted to remove PowerPath, click Yes.

4. When prompted to restart the host, click No.

Removing PowerPath from a Windows host 47

48

Removing PowerPath

Disconnect redundant paths to the storage systemTo disconnect redundant paths to the storage system:

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.

Uninstalling PowerPath by using the programs and features panelTo uninstall PowerPath using the Programs and Features panel inWindows Server 2008:

1. Open the Control Panel and double-click Programs andFeatures.

2. On the Programs and Features panel, select the installed versionof PowerPath and click uninstall.

3. When prompted to remove PowerPath, click Yes.

• 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 restart the host, click No.


Removing PowerPath

Uninstalling PowerPath from the command linePowerPath supports two types of CLI removals:

◆ Silent removal — Unattended PowerPath removal that usescommand-line parameters which do not require any user input.

◆ Interactive removal — Attended PowerPath removal thatrequires user input.

Note: Disconnect redundant cables from the HBAs to the storage systeminterface ports after PowerPath has been removed and before the host isrebooted. SAN (fabric) configurations may have multiple logicalconfigurations per physical connection. Ensure that no redundant zonedpaths exist.

Silent removal To perform a silent PowerPath removal, type the appropriatecommand in a single line:

<drive>:\<windows_version>\<PowerPath_package_name> /s /v"/q /L*v<logfile> <Property=PropertyValue> <Property=PropertyValue>"

where:

• <drive> is the drive letter, for example, C.• <windows_version> is W2003, or W2008• <PowerPath_package_name> is the PowerPath package name.

For example, EMCPP.W2008_x64.5.2.0.GA.exe• <logfile> creates the log file where the log message will be

sent. For example, C:\logs\PPremove.log.

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

• <Property=PropertyValue> is one or more optionalproperties as described in Table 7 on page 50.


50

Removing PowerPath


Table 7 describes the optional properties.

a. When removing both the Migration Enabler and Encryption with RSA features, use commas toseparate these entries, for example: PPREMOVE=ME,RSA

Note: Other PPREMOVE values (such as PP, 1, and 2) are not supported inPowerPath 5.2. If any other values are used, an error message indicates that itis not a supported value during a GUI uninstallation. The same message iswritten to the log file.

Table 6 Silent removal parameters

Variable Function

/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>"

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

/L*v<logfile>

Directs the Microsoft Installer to write verbose output to the filespecified with this option. The target directory for the log file must existbefore starting a silent removal by using the logging option (asrequired by the Windows installer engine).

Table 7 Removal Properties

Property Description

NO_REBOOT=1 Host does not reboot after PowerPath is removed.

Note: EMC recommends NO_REBOOT=1 so that you canmanually restart at a convenient time.

PPREMOVE=ME The Migration Enabler feature is removed.a

PPREMOVE=RSA The Encryption with RSA feature is removed.a

PPREMOVE=CLEAN PowerPath, including driver files and corresponding registryentries, is removed.

Note: CLEAN option removes all the features including PowerPathMigration Enabler and PowerPath Encryption with RSA.


Removing PowerPath

Example of Silent RemovalThere are valid command lines for silent removals and the followingfunctions:

◆ Logs silent removal.◆ Disables reboot at completion.

C:\W2008\EMCPP.W2008_x64.5.2.0.GA.exe /s /v"/q /L*vC:\logs\PPremove.log NO_REBOOT=1 PPREMOVE=CLEAN"

Interactive removal To perform an interactive PowerPath removal, type the appropriatecommand in a single line:

<drive>:\<windows_version>\<PowerPath_package_name> /v"/L*v <logfile><Property=PropertyValue> <Property=PropertyValue>"

“Silent removal” on page 49 contains a description of the arguments.

Example of interactive removalThere are valid command lines for interactive removals and thefollowing functions:

◆ Logs interactive removal.◆ Disables reboot at completion.

C:\W2008\EMCPP.W2008_x64.5.2.0.GA.exe /v"/L*v C:\logs\PPremove.logNO_REBOOT=1 PPREMOVE=CLEAN"


52

Removing PowerPath

Uninstalling additional features at a later timeIf multipathing is already installed on your host and you want touninstall additional features, such as Migration Enabler and/orEncryption with RSA, at a later time you can uninstall these featuresby using the GUI or CLI.

Note: Multipathing feature (base feature) cannot be uninstalled by using thecustom setup option.

Uninstalling additionalfeatures using the GUI

To uninstall additional features at a later time using the GUI:



Add/Remove Programs


Programs and Features panel

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


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

5. To select a specific feature for uninstallation (Migration Enablerand/or Encryption with RSA), click the drop-down arrow besidethe listed feature 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.

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



Removing PowerPath

8. The setup wizard appears and asks if you want to reboot the host.Click No.



Uninstalling additionalfeatures using the CLI

To uninstall additional features at a later time by using the CLI, typethe appropriate command in a single line:

Note: Additional features can be installed by both the Silent or InteractiveCLI types of installation.

<drive>:\<windows_version>\<PowerPath_package_name> /v"/L*v <logfile>NO_REBOOT=1 PPREMOVE=<feature>"

C:\W2008\EMCPP.W2008_x64.5.2.0.GA.exe /v"/L*v C:\logs\PPremove.logNO_REBOOT=1 PPREMOVE=CLEAN"

“Silent removal” on page 49 contains a description of the arguments.


54

Removing PowerPath


3Invisible Body Tag


◆ Overview............................................................................................. 56◆ PowerPath monitor............................................................................ 56◆ PowerPath Administrator................................................................. 59◆ Local or remote administration........................................................ 65◆ Saving console settings...................................................................... 69◆ Windows Server 2008 Support......................................................... 70

PowerPathAdministrator

PowerPath Administrator 55

56

PowerPath Administrator

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

◆ PowerPath monitor — Continuously monitors your PowerPathconfiguration and can alert you of status changes. The“PowerPath monitor” section provides additional information.

◆ PowerPath Administrator — Configures, monitors, and managesPowerPath devices. The “PowerPath Administrator” on page 59provides 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 8 on page 57. 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.

EMC PowerPath for Microsoft Windows Version 5.2 Installation and Administrative Guide


Table 8 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 65.

Table 8 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 57

58


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.



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 65 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 9 on page 62 andTable 10 on page 63 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.


60


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.



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


62


Icons: standard, unlicensed, and unknown conditionsTable 9 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 9 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.



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 10 on page 63 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 10 on page 63. 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 10 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.


64


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 10 Icons of known PowerPath failure conditions (2 of 2)

Object Degraded Icon Failed IconUnlicensed and DegradedIcon

Unlicensed and FailedIcon



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 hostoption” on page 66 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 3.0.5 or higher for Windows Server 2003installed, you may supply the credentials for remote access to thathost. “Setting a remote host option” on page 67 providesadditional information on how to add the PowerPath Snap-in tomonitor a remote host with PowerPath 3.0.5 or higher 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 65

66


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, do one of the following:

• For 32 bit versions of the operating system run mmc.

• For 64 bit versions of the operating system run mmc/32.

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.

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, you can save thisconfiguration. “Saving and restoring configurations from thePowerPath Administrator” on page 38 provides additionalinformation.

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 67

68


2. In the Open field, do one of the following:

• For 32 bit versions of the operating system run mmc.

• For 64 bit versions of the operating system run mmc/32.

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.

You can now use EMC PowerPath Administrator to configure,manage, and monitor PowerPath devices. Once you have changedyour configuration, you can save this configuration. “Saving and



restoring configurations from the PowerPath Administrator” onpage 38 provides additional information.

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

Saving console settings 69

70


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.


4


◆ Installing PowerPath and MSCS...................................................... 72◆ Integrating PowerPath into an existing MSCS cluster ................. 73

PowerPath in an MSCSCluster

PowerPath in an MSCS Cluster 71

72

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.



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 withgreater than two nodes. In these cases, the appropriate action is notedwhere applicable for clusters with greater 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 74

◆ “Installing PowerPath on node B” on page 75

◆ “Configuring additional paths between the storage systemand Node B” on page 75

◆ “Moving all resources to Node B” on page 75

◆ “Installing PowerPath on node A” on page 76

◆ “Configuring additional paths between the storage systemand node A” on page 76

◆ “Returning node A resources to node A” on page 76

Integrating PowerPath into an existing MSCS cluster 73

74


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

Start > Programs > Administrative Tools > ClusterAdministrator.

The Cluster Administrator window appears.

Figure 2 Cluster Administrator

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 “Installing

PowerPath” on page 21.

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

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

Integrating PowerPath into an existing MSCS cluster 75

76


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

PowerPath” on page 21.

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.


5


◆ Installing PowerPath and VCS......................................................... 78◆ Installing PowerPath in an existing VCS environment ................ 79

PowerPath in a VeritasCluster Server

PowerPath in a Veritas Cluster Server 77

78

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.



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

Installing PowerPath in an existing VCS environment 79

80


Figure 3 VCS Administrator

2. From the navigation pane on the left, right-click ClusterServiceand select Disable as shown in Figure 4 on page 81. This disablesthe secondary node in the VCS configuration.



Figure 4 Disabling a secondary node in a VCS

3. Install PowerPath on the secondary node. Follow the proceduresin “Installing PowerPath” on page 21.

4. After installation and reboot of the secondary node, right-clickClusterService > Enable to reenable the node in the VCSconfiguration as seen in Figure 5 on page 82.


82


Figure 5 Enabling a node in a VCS

5. Move all cluster resources over to the secondary node as seen inFigure 6 on page 83. Right-click Cluster Service, and then selectthe secondary node.



Figure 6 Moving cluster resources to secondary 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.

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

DiskType and DiskGroup information

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


84


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

8. Disable the primary node in the VCS configuration and installPowerPath as described in “Installing PowerPath” on page 21.

9. After installing PowerPath, reboot the primary node.

10. Reenable the node in the VCS configuration.

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

WHQL Certification

WHQL Certification 85

86

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:

◆ PowerPath files................................................................................... 88

Files Changed byPowerPath

Files Changed by PowerPath 87

88

Files Changed by PowerPath

PowerPath filesThe PowerPath installer installs the PowerPath files in the locationsindicated in the Table 11.

Table 11 PowerPath files (1 of 3)

File Install location for 32 bit Install location for 64 bit

aceclnt.dll [ProgramFilesFolder]\EMC\RSA\CST\lib [ProgramFiles (X86)]\EMC\RSA\CST\lib

ccme_base.dll [ProgramFilesFolder]\EMC\RSA\Rkm_Client\lib [ProgramFiles (X86)]\EMC\RSA\Rkm_Client\lib

ccme_ecc.dll [ProgramFilesFolder]\EMC\RSA\CST\lib [ProgramFiles (X86)]\EMC\RSA\CST\lib

ccme_eccaccel.dll [ProgramFilesFolder]\EMC\RSA\CST\lib [ProgramFiles (X86)]\EMC\RSA\CST\lib

ccme.dll [ProgramFilesFolder]\EMC\RSA\Rkm_Client\lib [ProgramFiles (X86)]\EMC\RSA\Rkm_Client\lib

ckmadm.exe [ProgramFilesFolder]\EMC\PowerPath [ProgramFiles (X86)]\EMC\PowerPath

Config.xml [ProgramFilesFolder]\EMC\RSA\CST\config,[ProgramFilesFolder]\EMC\RSA\CST\xml

[ProgramFiles (X86)]\EMC\RSA\CST\config,[ProgramFiles (X86)]\EMC\RSA\CST\xml

cryptocme2.dll [ProgramFilesFolder]\EMC\RSA\Rkm_Client\lib [ProgramFiles (X86)]\EMC\RSA\Rkm_Client\lib

cryptocme2.sig [ProgramFilesFolder]\EMC\RSA\Rkm_Client\lib [ProgramFiles (X86)]\EMC\RSA\Rkm_Client\lib

CSP_Admin.xml [ProgramFilesFolder]\EMC\RSA\CST\config,[ProgramFilesFolder]\EMC\RSA\CST\xml


csp_app.xml [ProgramFilesFolder]\EMC\RSA\CST\config,[ProgramFilesFolder]\EMC\RSA\CST\xml


CSP_AuthenticationService.dll

[ProgramFilesFolder]\EMC\RSA\CST\lib [ProgramFiles (X86)]\EMC\RSA\CST\lib

CSP_Authn.xml [ProgramFilesFolder]\EMC\RSA\CST\config,[ProgramFilesFolder]\EMC\RSA\CST\xml


CSP_C.dll [ProgramFilesFolder]\EMC\RSA\CST\lib [ProgramFiles (X86)]\EMC\RSA\CST\lib

CSP_Config.xml [ProgramFilesFolder]\EMC\RSA\CST\config,[ProgramFilesFolder]\EMC\RSA\CST\xml


CSP_Configuration.dll [ProgramFilesFolder]\EMC\RSA\CST\lib [ProgramFiles (X86)]\EMC\RSA\CST\lib

CSP_lb.dll [ProgramFilesFolder]\EMC\RSA\CST\lib [ProgramFiles (X86)]\EMC\RSA\CST\lib

CSP_LDAP.dll [ProgramFilesFolder]\EMC\RSA\CST\lib [ProgramFiles (X86)]\EMC\RSA\CST\lib



CSP_LDAP.xml [ProgramFilesFolder]\EMC\RSA\CST\config,[ProgramFilesFolder]\EMC\RSA\CST\xml


CSP_LocalDirectory.dll [ProgramFilesFolder]\EMC\RSA\CST\lib [ProgramFiles (X86)]\EMC\RSA\CST\lib

CSP_LocalDirectory.xml [ProgramFilesFolder]\EMC\RSA\CST\config,[ProgramFilesFolder]\EMC\RSA\CST\xml


CSP_Logging.xml [ProgramFilesFolder]\EMC\RSA\CST\config,[ProgramFilesFolder]\EMC\RSA\CST\xml


CSP_LogService.dll [ProgramFilesFolder]\EMC\RSA\CST\lib [ProgramFiles (X86)]\EMC\RSA\CST\lib

CSP_OSLogin.dll [ProgramFilesFolder]\EMC\RSA\CST\lib [ProgramFiles (X86)]\EMC\RSA\CST\lib

CSP_OSLogin.xml [ProgramFilesFolder]\EMC\RSA\CST\config,[ProgramFilesFolder]\EMC\RSA\CST\xml


CSP_RoleManagement.dll


CSP_RoleManagement.xml

[ProgramFilesFolder]\EMC\RSA\CST\config,[ProgramFilesFolder]\EMC\RSA\CST\xml


CSP_RT.dll [ProgramFilesFolder]\EMC\RSA\CST\lib [ProgramFiles (X86)]\EMC\RSA\CST\lib

CSP_SecurID.dll [ProgramFilesFolder]\EMC\RSA\CST\lib [ProgramFiles (X86)]\EMC\RSA\CST\lib

CSP_SecurID.xml [ProgramFilesFolder]\EMC\RSA\CST\config,[ProgramFilesFolder]\EMC\RSA\CST\xml


CSP_SimpleCrypto.dll [ProgramFilesFolder]\EMC\RSA\CST\lib [ProgramFiles (X86)]\EMC\RSA\CST\lib

CSP_Taxonomy.dll [ProgramFilesFolder]\EMC\RSA\CST\lib [ProgramFiles (X86)]\EMC\RSA\CST\lib

CSP_TrustedUser.dll [ProgramFilesFolder]\EMC\RSA\CST\lib [ProgramFiles (X86)]\EMC\RSA\CST\lib

CSP_TrustedUser.xml [ProgramFilesFolder]\EMC\RSA\CST\config,[ProgramFilesFolder]\EMC\RSA\CST\xml


CSP_UserManagement.dll


CSP_UserManagement.xml

[ProgramFilesFolder]\EMC\RSA\CST\config,[ProgramFilesFolder]\EMC\RSA\CST\xml


CSP.dll [ProgramFilesFolder]\EMC\RSA\CST\lib [ProgramFiles (X86)]\EMC\RSA\CST\lib



PowerPath files 89

90


Note: Some driver files are copied to the internal system directories by theoperating system when they are installed.

CSP.xml [ProgramFilesFolder]\EMC\RSA\CST\config,[ProgramFilesFolder]\EMC\RSA\CST\xml


CST_admin.dll [ProgramFilesFolder]\EMC\RSA\CST\lib [ProgramFiles (X86)]\EMC\RSA\CST\lib

cstadmin.exe [ProgramFilesFolder]\EMC\PowerPath [ProgramFiles (X86)]\EMC\PowerPath

emcp_xcryptd.exe [ProgramFilesFolder]\EMC\PowerPath [ProgramFiles (X86)]\EMC\PowerPath

emcpreg.exe [ProgramFilesFolder]\EMC\PowerPath [ProgramFiles (X86)]\EMC\PowerPath

expat.dll [ProgramFilesFolder]\EMC\RSA\CST\lib [ProgramFiles (X86)]\EMC\RSA\CST\lib

kmclient_shared.dll [ProgramFilesFolder]\EMC\RSA\Rkm_Client\lib [ProgramFiles (X86)]\EMC\RSA\Rkm_Client\lib

kmcryptolib.dll [ProgramFilesFolder]\EMC\RSA\Rkm_Client\lib [ProgramFiles (X86)]\EMC\RSA\Rkm_Client\lib

kmsvcshlib.dll [ProgramFilesFolder]\EMC\RSA\Rkm_Client\lib [ProgramFiles (X86)]\EMC\RSA\Rkm_Client\lib

liblber_dynamic.dll [ProgramFilesFolder]\EMC\RSA\CST\lib [ProgramFiles (X86)]\EMC\RSA\CST\lib

libldap_dynamic.dll [ProgramFilesFolder]\EMC\RSA\CST\lib [ProgramFiles (X86)]\EMC\RSA\CST\lib

osysrt.dll [ProgramFilesFolder]\EMC\RSA\CST\lib [ProgramFiles (X86)]\EMC\RSA\CST\lib

osysrtxml.dll [ProgramFilesFolder]\EMC\RSA\CST\lib [ProgramFiles (X86)]\EMC\RSA\CST\lib

powervt.exe [ProgramFilesFolder]\EMC\PowerPath [ProgramFiles (X86)]\EMC\PowerPath

rkm_init.conf.tmpl [ProgramFilesFolder]\EMC\RSA\Rkm_Client\config [ProgramFiles(X86)]\EMC\RSA\Rkm_Client\config

rkm_keyclass.conf.tmpl [ProgramFilesFolder]\EMC\RSA\Rkm_Client\config [ProgramFiles(X86)]\EMC\RSA\Rkm_Client\config

rkm_svc.conf.tmpl [ProgramFilesFolder]\EMC\RSA\Rkm_Client\config [ProgramFiles(X86)]\EMC\RSA\Rkm_Client\config

rsa_ck.sig [WindowsFolder]\System32\drivers [WindowsFolder]\System32\drivers




Index

AAdministrator

configuration, loading 39configuration, saving 38device properties 60local host 65, 66remote host 65, 67result pane 59scope pane 59

Ccertification, WHQL 86CLARiiON storage systems 16complete install 24console settings, saving 69custom install 24

Ddocumentation, related 11

EEMC Licensing Tool 41emcpreg command 41

Ffeature level installation 21

Iinstallation

additional features at a later time 29CD-ROM, loading from 22

installation (continued)complete install 24custom install 24feature level 21first-time installation 16, 29interactive installation 28postinstallation 31Powerlink, downloading from 22service pack 37silent installation 25typical install 24Windows Server Core 2008 21

Llicense key 18

MMicrosoft Cluster Server. See MSCSMicrosoft Management Console. See MMCMMC (Microsoft Management Console) with

PowerPath snap-in 57MSCS (Microsoft Cluster Server)

moving resources 74, 75PowerPath integration 73

multiple versions of PowerPath 34

Ooperating system, upgrade 40

Ppatches. See service pack


92

Index

powermt display 37powermt save 37

Rremoving PowerPath 47

additional features at a later time 52interactive removal 51silent removal 49

Sservice pack 37Symmetrix storage systems 16

Ttraybar monitor program 70typical install 24

UUAC (User Account Control) 70uninstalling PowerPath 47upgrading

before you upgrade 33operating system upgrade 40procedures for 35

User Account Control. See UAC

VVCS (Veritas Cluster Server)

PowerPath install 79Veritas Cluster Server. See VCS

WWHQL certification 86Windows Server 2008 operating system,

upgrading 40Windows Server 2008 R2 operating system,

upgrading 40Windows Server Core 2008 installation 21


Date post:	03-May-2018
Category:	Documents
Upload:	vubao
View:	226 times
Download:	2 times