Installing PowerPath - communities.bmc.com PowerPath 15 1 Invisible Body Tag This chapter describes procedures to install and upgrade EMC® PowerPath® software on a Windows host

Installing PowerPath 15

1Invisible Body Tag

This chapter describes procedures to install and upgrade EMC®

PowerPath® software on a Windows host. This chapter includes the following sections:

� Before you install................................................................................ 16� Installing PowerPath ......................................................................... 21� After you install.................................................................................. 29� Upgrading PowerPath....................................................................... 30� Installing a PowerPath patch ........................................................... 33� Installing an earlier version of PowerPath ..................................... 36� Upgrading Windows operating systems........................................ 37� Coexistence with third-party path management software .......... 38� EMC licensing tool............................................................................. 39

Installing PowerPath

16 EMC PowerPath for Windows Version 5.0 Installation and Administration Guide


Before you install

The sequence of steps to configure a storage system and install PowerPath on a host depends on the storage system you use.

EMC Symmetrix storage systems

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

EMC CLARiiON storage systems

PowerPath installation is an integral part of an EMC CLARiiON®

setup and configuration procedure.

To properly install PowerPath on a host with a CLARiiON CX-series array, refer to the EMC Installation Roadmap for CX3-Series, CX-Series, AX-Series, and FC-Series Storage Systems. The roadmap provides step-by-step instructions for installing PowerPath and other CLARiiON software. To obtain the latest versions of CLARiiON CX-series documentation, log in to the EMC Powerlink website.

CLARiiON AX-series installation, planning, and troubleshooting documents are located on the AX-series support website. For information on accessing the site, refer to the support documentation that shipped with your storage system. Refer to these documents for prescribed installation information only when AX-series storage systems are used.

First-time PowerPath installations

Remove any version of EMC Navisphere® Application Transparent Failover (ATF) installed on the host.

CAUTION!

The procedure for migrating from ATF or CLARiiON Driver Extension (CDE) to PowerPath is not straightforward and could result in data loss if not performed correctly. We strongly recommend that EMC Professional Services perform the migration. If you nevertheless decide to perform the migration yourself, the

Before you install 17


Removing ATF or CDE Software Before Installing Other Failover Software document has more information. This document is available only on the EMC Powerlink website.

Obtaining up-to-date information

Before you install PowerPath on the host, check the EMC Powerlink website for the most current PowerPath information:

� Release notes, which are updated periodically and posted on Powerlink.

� Patches and notices, review the patch ReadMe files to determine which patches (if any) you want to install after PowerPath, and whether those patches have any added prerequisites that must be met before you install PowerPath.

� Check Microsoft-certified drivers, as the packages are released on Powerlink as they are available. To check whether a PowerPath driver is signed, refer to the procedure in Appendix A, “WHQL Certification.”

Choose a convenient time

Installing PowerPath requires you to reboot the host. Plan to install or upgrade PowerPath when a reboot will cause minimal disruption to your site.

Locating the license key

The PowerPath license registration key is on the License Key Card that you received from EMC. Take note of the following regarding licenses:

� Installing PowerPath on a host connected to a CLARiiON AX-series array does not require a license. PowerPath provides full support with or without a PowerPath license when the host is connected to a CLARiiON AX-series array.

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



� Type the registration number exactly as written on the card. To reduce common typographical errors, the License Key field accepts either uppercase or lowercase letters, and certain numbers and letters are interchangeable. Specifically, an entry of the alphabetic letters O, I, S, and B is equivalent to an entry of the numbers, 0, 1, 5, and 8.

If you have additional questions about entering licenses, consult the online help file by pressing F1 from the EMC Licensing Tool.You must have Internet Explorer 5.0 or higher to view these files. If you do not have this browser installed, you may still view the help file, EmcLicTool.chm, directly from the \help folder on the PowerPath installation CD.

Preparing the host and storage system

To prepare the host and storage system:

� Verify that your environment meets the requirements found in the following:

• EMC PowerPath for Windows Release Notes which describes minimum hardware and software requirements for the host and supported storage systems.

• EMC PowerPath Product Guide which describes the host-storage system interconnection topologies that PowerPath supports.

� Verify that Microsoft MPIO framework 1.17 or later is installed.

• If the MPIO framework is not installed on the host, the PowerPath installer installs MPIO framework 1.17.

• If a version of the MPIO framework less than 1.17 is installed on the host, the PowerPath installer prompts you to upgrade to version 1.17. If you do not upgrade, the PowerPath installation aborts.

• If a version of the MPIO framework greater than 1.17 is installed on the host, the PowerPath installer notifies you and then continues with the installation.

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

Before you install 19


� Configure HBA drivers. Be sure to follow the HBA driver configuration guidelines outlined by EMC. Refer to the E-Lab Interoperability Navigator, available on the Powerlink website and product documentation. The use of improper settings can cause erratic failover behavior, such as greatly increased I/O delays.

� For hosts connected to storage arrays via a Fibre Channel switch (that is, a fabric), configure the HBAs by using persistent binding for SCSI target IDs.

� Do not connect multiple paths from the HBAs to the storage system interface ports, hubs, switches, or zone multiple paths until you have installed PowerPath and shut down the host.

Booting from a storage array device

The following documents provide for instructions on configuring a storage array device as the boot device:

� EMC Fibre Channel with Emulex Host Bus Adapters in the Windows Environment (P/N 300-001-157), available on the Emulex website:

http://www.emulex.com/emc/support/pdfs/win.pdf

� EMC Fibre Channel iSCSI with QLogic Host Bus Adapters in the Windows Environment (P/N 300-001-164), available on the Qlogic website:

http://download.qlogic.com/drivers/47512/QLogic_Windows_6_28_06.pdf

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

Prepare clustered environment

If you are installing PowerPath in a clustered environment, Chapter 4, ”PowerPath in an MSCS Cluster,” provides information on installing PowerPath in a new or existing cluster.



Preparing the browser

� Verify that you have the correct browser installed. You may view the help files directly from the installation CD.

� Check the online help for the EMC Licensing Tool for help on registering PowerPath. If you do not already have a license in the registry, the EMC Licensing Tool displays during the installation as described in Installing PowerPath software. Access online help for this application from the Help button or F1 key. If you do not have the correct browser installed, you can run this help file directly from the installation CD. The “EMC licensing tool” on page 39 provides additional information on this topic.




You can install PowerPath either by using InstallShield or the command line.

Note: You must have administrative rights to install PowerPath.

CAUTION!

Close all host applications before installing or upgrading to PowerPath 5.0. This is necessary to maintain the integrity of the system and user data while low level disk drivers are installed or upgraded. Failure to do so could result in data loss or corruption of data.

Using the InstallShield

Use this procedure to install PowerPath using InstallShield.

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

Loading the CD-ROM To load the CD-ROM:

1. Insert the PowerPath installation CD-ROM.

• If autoplay is enabled, your browser launches and displays the Getting Started page.

• You can install the software from the Installation section by clicking the appropriate link for your operating system. To proceed with the installation:

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

b. Click OK.

c. Proceed to step 2 of the “Installing PowerPath software” on page 22 section.

• If autoplay is not enabled, proceed to step 2.

2. From the Start menu, select Run.



Installing PowerPathsoftware

To install PowerPath software:

1. In the Run window, either browse to or enter the name of the PowerPath installation program and click OK.

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

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

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

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

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

5. Type your name and organization on the Customer Information screen and click Next.

6. Click Next to install PowerPath in the default directory, and proceed to step 7.

Note: EMC recommends that you install PowerPath in the default directory. 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 (specified by the %SYSTEMROOT% environment variable). PowerPath will not function correctly if it is installed in this directory.

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



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

Note: The EMC Licensing Tool does not display when PowerPath is being installed on a host connected to a CLARiiON AX-series array. Proceed to step 10.

8. When prompted by the EMC Licensing Tool, enter your 24-digit registration number in the License Key field. Click Add, and then click OK.

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

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

10. When the setup wizard asks whether you want to reboot the host, click No.

11. From the Start menu, select Shut Down.

12. In the Shut Down Windows dialog box, select Shut Down from the list, and click OK.

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

Installing from the CLI

PowerPath supports two types of CLI installations:

� Silent installations — Unattended PowerPath installation that uses command-line parameters which do not require any user input.

� Interactive installations — Attended PowerPath installation that requires user input.

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



CAUTION!

All host applications must be closed before installing or upgrading to PowerPath 5.0. This is necessary to maintain the integrity of the system and user data while low level disk drivers are installed or upgraded correctly. Failure to do so could result in data loss or corruption of data.

Silent installation Note: PowerPath installation aborts if you attempt to install it on a host that has a version of MPIO framework below 1.17. To install PowerPath on a host with a version of MPIO framework below 1.17, specify the UPGRADE_MPIO = 1 property described in Table 2 on page 25.

To perform a silent PowerPath installation, type the appropriate command in a single line.

On a Windows 2000 host<drive>:\W2000\EMCPP.<platform>.5.0.<x>.GA.exe /s /v"/q /L*v <Path to

log file> <Property=PropertyValue> <Property=PropertyValue>"

On a Windows 2003 host<drive>:\W2003\EMCPP.<platform>.5.0.<x>.GA.exe /s /v"/q / L*v <Path to


where:

• <drive> is the CD drive letter, for example, C.• <platform> is W2000 or W2003_32 or W2003_x64 or

W2003_IA64.• <x> is the release level, for example, 0.• <Path to log file> is the complete path to the log file, for

example, C:\logs\PPremove.log.• <Property=PropertyValue> is one or more optional

properties.

Table 1 describes the variables used in the syntax.

Table 1 Silent installation variables (1 of 2)

Variable Function

/s Indicates a silent installation.



Table 2 describes the optional properties.

All properties must be in capital letters or the information will not be passed to installer.

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

/v Directs InstallShield to pass the following information string (enclosed in quotes) to the Microsoft Installer (MSI).

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

/L*v <file> Directs the Microsoft Installer to write verbose output to the file specified with this option. The target directory for the log file must exist before starting a silent installation using the logging option (as required by the Windows installer engine).

Table 1 Silent installation variables (2 of 2)

Variable Function

Table 2 Properties

Properties Description

LICENSENUM=<license key> The value must be a valid license or no license will be saved.

INSTALL_DRIVE=<drive> The drive on which PowerPath will be installed. By default, PowerPath is installed on the C: drive.

• The installation only uses 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 If NO_REBOOT=1, the host will not reboot after PowerPath is installed.

UPGRADE_MPIO = 1 This is used to upgrade the existing framework version on the host, if a lower version of MPIO framework is installed on the host a.

a. Silent upgrade from PowerPath iSCSI 1.1 and PowerPath 4.6 requires UPGRADE_MPIO = 1 switch



Examples of silent installationsThe following are all valid command lines for silent installations on:

On a Windows 2000 host

On a Windows 2000 host, the command performs the following functions:

� Silent installation logging� Sets the PowerPath License� Sets the PowerPath install drive� Disables reboot at completion

ExampleEMCPP.W2000_5.0.0.GA.exe /s /v"/q /L*v C:\logs\PPsetup.log

LICENSENUM=0000-0000-0000-0000-0000-0000 INSTALL_DRIVE=Z NO_REBOOT=1"


On a Windows Server 2003 32-bit host, the command performs the following functions:

� Silent installation logging� Sets the PowerPath license� Sets the PowerPath install drive� Disables reboot at completion

ExampleEMCPP.W2003_32.5.0.0.GA.exe /s /v"/q /L*v C:\logs\PPsetup.log


On a Windows Server 2003 x64-bit host, the command performs the following functions:

� Silent installation with no logging� Sets the PowerPath license� Disables reboot at completion

ExampleEMCPP.W2003_x64.5.0.0.GA.exe /s /v"/q

LICENSENUM=0000-0000-0000-0000-0000-0000 NO_REBOOT=1"

Interactive installation To perform an interactive installation of PowerPath using the CLI, use a command line in the following format (type all on one line):


<drive>:\W2000\EMCPP.<platform>.5.0.<x>.GA.exe /v"/L*v <Path to log

file> <Property=PropertyValue> <Property=PropertyValue>"




<drive>:\W2003\EMCPP.<platform>.5.0.<x>.GA.exe /v"/L*v <Path to log


where:

• <drive> is the CD drive letter, for example, D.• <platform> is W2000 or W2003_32 or W2003_x64 or

W2003_IA64.• <x> is the release level, for example, 0.• <Path to log file> is the complete path to the log file, for

example, C:\logs\PPremove.log.• <Property=PropertyValue> is one or more optional

properties.


See Table 2 on page 25 for a description of the optional properties.

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

Examples of interactive installationsThe following are all valid command lines for interactive installations:



� Silent installation logging� Sets the PowerPath License� Sets the PowerPath install drive� Disables reboot at completion

Table 3 Interactive installation variables

Variable Function


/L*v <file> Directs the Microsoft Installer to write verbose output to the file specified with this option. The target directory for the log file must exist before starting an interactive installation using the logging option (as required by the Windows installer engine).



ExampleEMCPP.W2000_5.0.0.GA.exe /v" /L*v C:\logs\PPsetup.log



On a Windows Server 2003 32-bit host, the command performs the following functions:

� Silent installation logging� Sets the PowerPath license� Sets the PowerPath install drive� Disables reboot at completion

ExampleEMCPP.W2003_32.5.0.0.GA.exe /v"/L*v C:\logs\PPsetup.log


On a Windows Server 2003 x64-bit host, the command performs the following functions:

� Interactive installation with no logging� Sets the PowerPath license� Disables reboot at completion

ExampleEMCPP.W2003_x64.5.0.0.GA.exe

/v"LICENSENUM=0000-0000-0000-0000-0000-0000 NO_REBOOT=1"

For a new PowerPath installation

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

Do the following:

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

2. Install PowerPath

3. Shut down the host.

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

5. Power on the host.

After you install 29


After you install

This section describes what to do after you install PowerPath on a Windows host:

� With the host shut down, connect the remaining cables from the HBAs to the storage system interface ports, hubs, or switches, or zone multiple paths. For cabling instructions, refer to the product guide for your storage system and, depending on your type of storage system, the host connectivity guides or the EMCInstallation Roadmap for CX3-Series, CX-Series, AX-Series, and FC-Series Storage Systems.

� Power on the host. PowerPath is now fully configured, with multiple paths to logical devices.

� If the environment is Fibre Channel, make sure zones are configured appropriately. The EMC Installation Roadmap for CX3-Series, CX-Series, AX-Series, and FC-Series Storage Systems andthe host connectivity guides provide additional information.

� If you have not already done so, check Powerlink for any patches to PowerPath 4.6.1, and install any required patches.

Verify and save configuration

To verify and save the configuration:

1. Power on the host. PowerPath is fully configured with multiple paths to logical devices and (if appropriate) correct zones when you boot.

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

• powermt display• powermt display dev=all• powermt display ports

3. Save the configuration to the file powermt.custom by running powermt save. The EMC PowerPath Product Guide containsdescriptions of powermt commands.

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



Upgrading PowerPath

You can only upgrade to PowerPath 5.0 from one of the previous PowerPath releases shown in Table 4 below.

Uninstalling previous PowerPath components

If you are upgrading to PowerPath 5.0 from a previous version of PowerPath, follow these guidelines:

� If you are currently running an older version of PowerPath not listed in Table 4, it is recommended you uninstall that version of PowerPath (for example, PowerPath 2.1.3) and perform a fresh installation of PowerPath 5.0.

� If you are currently running any of the PowerPath versions listed in Table 4, you can directly upgrade the host to PowerPath 5.0 without uninstalling the listed version. Do not uninstall the existing version of PowerPath on the host before upgrading to PowerPath 5.0.

� If an eFIX or Hot Fix from an earlier version is installed on the host, then be sure to uninstall the eFIX or Hot Fix of that earlier version of PowerPath before installing PowerPath 5.0.

� If you are running PowerPath 4.3.x, 4.4.x, or 4.5.x, remove all third party devices before upgrading to PowerPath 5.0.

Table 4 Upgrading from previous PowerPath releases

PowerPath Platform PowerPath Version PowerPath iSCSI Version

Windows 2000 Advanced Server

4.1.0, 4.1.1, 4.3.0 4.3.1, 4.4.0, 4.4.1, 4.5.0, and 4.5.1

Not supported.

Windows Server 2003, x86-based version

4.1.0, 4.1.1, 4.3.0 4.3.1, 4.4.0, 4.4.1, 4.5.0, 4.5.1, 4.6.0, and 4.6.1

1.1

Windows Server 2003, Itanium-based version

4.1.0, 4.1.1, 4.3.0 4.3.1, 4.4.0, 4.4.1, 4.5.0, 4.51, 4.6.0, and 4.6.1

Not supported.

Windows Server 2003, x64-based version

4.4.1, 4.5.0, 4.5.1, 4.6.0, and 4.6.1

Not supported.

Upgrading PowerPath 31


� Ensure that all host applications are closed before upgrading to PowerPath 5.0. Failure to do so could result in data loss or corruption of data.

Before upgrading PowerPath

CAUTION!

You must close all applications before upgrading to PowerPath 5.0. Failure to do so could result in data loss or corruption of data.

Note the following items before upgrading to PowerPath 5.0:

� Check Powerlink for the most current information. EMC updates release notes periodically and posts them on Powerlink.

� PowerPath 5.0 requires Microsoft MPIO framework 1.17 or later.

• If the MPIO framework is not installed on the host, the PowerPath installer installs MPIO framework 1.17.

• If a version of the MPIO framework less than 1.17 is installed on the host, the PowerPath installer prompts you to upgrade to version 1.17. If you do not upgrade, the PowerPath installation aborts.

• If a version of the MPIO framework greater than 1.17 is installed on the host, the PowerPath installer notifies you and then continues with the installation.

� Run the powermt save command to ensure that you have saved the latest PowerPath configuration information.

� Stop powermt display if it is running. The EMC PowerPath Product Guide provides additional information on powermt display

� Upgrading to PowerPath 5.0 preserves license, registration, and configuration information. You do not need to reenter the license on a host that has a valid PowerPath license. If you have a valid PowerPath iSCSI 1.1 license key installed, then it will be converted to a PowerPath Base license. A PowerPath Base license provides the same protection as a PowerPath iSCSI license key.

� Do not uninstall the existing version of PowerPath on the host before upgrading to PowerPath 5.0.

� If an eFIX or Hot Fix from an earlier version is installed on the host, then be sure to uninstall the eFIX or Hot Fix of that earlier version of PowerPath before installing PowerPath 5.0.



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

� Stop all I/O and close all applications that access storage devices.

Upgrade procedure You can upgrade PowerPath using InstallShield or from the command line.

Note: You must have administrative rights to upgrade PowerPath.

Using the InstallShield Follow the procedure in “Using the InstallShield” on page 21 to upgrade to PowerPath using InstallShield. Note the following differences:

� If the upgrade procedure detects the powermt.custom file on the host, it prompts you to save or delete this file. If your hardware configuration has not changed, keep the existing file. If your hardware configuration has changed, delete the existing powermt.custom file.

� If you have a valid PowerPath iSCSI 1.1 license key installed, then it will be converted to a PowerPath Base license. A PowerPath Base license provides the same protection as a PowerPath iSCSI license key.

� Reboot the host when prompted by the PowerPath installer.

From the command line

Follow the procedure in “Installing from the CLI” on page 23 to upgrade from the command line. You do not need to include the LICENSENUM property if the host already has a valid PowerPath license.

Installing a PowerPath patch 33


Installing a PowerPath patch

Every patch release is accompanied by a readme file that describes how to install the patch. Before you install a patch, PowerPath 5.0 for Windows 2000 or Windows Server 2003 must be installed on the host.

Patches and configuration files

PowerPath stores configuration information in a file that may be loaded at boot time. When using the PowerPath Administrator, the configuration file can be saved only under the default filename. After a patch is applied, the format of the configuration file may change so it is no longer backward compatible.

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

Note: If an eFIX or Hot Fix from an earlier version is installed on a host, then be sure to uninstall the eFIX or Hot Fix of that earlier version of PowerPath before installing the patch. The PowerPath base product does not need to be uninstalled, just the eFIX or Hot Fix. Reboot the host after removing the eFIX or Hot Fix and prior to installing PowerPath. A reboot is also required after installing the PowerPath patch is applied or installed.

Saving and loading configurations from the command line interface (powermt)

To save and load configurations with the powermt utility, follow these steps:

1. Before installing a patch, back up your old configuration file. Use the backup to restore your configuration if you uninstall the patch later. The EMC PowerPath Product Guide provides additional information.

2. After installing a patch and verifying the configuration is correct, save your configuration. This ensures the configuration file is updated to the current format. The EMC PowerPath Product Guide provides additional information.



Saving and loading configurations from the PowerPath Administrator

To save and load configurations from PowerPath Administrator, follow these steps:

1. Before installing a patch, back up your configuration file. Use the backup to restore your configuration if you uninstall the patch later. "“Saving configurations”", and “Loading configurations” on page 35, provide additional information.

2. After installing a patch and verifying the configuration is correct, save your configuration. This ensures the configuration file is updated to the current format. "“Saving configurations”"provides additional information.

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

Note: PowerPath configuration files are distinct from the Microsoft Management Console (MMC) configuration files. If you close the MMC window, MMC prompts you to save the MMC settings. These settings are not the same as the EMC PowerPath Administrator settings. Saving the MMC console settings does not save your PowerPath configuration changes; therefore, these changes will be lost unless you follow the next 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-click the root node and select All Tasks, Save Config for Reboot.

To save the configuration with a different name, select Save Config as. In the Save As dialog box, navigate to your desired directory, enter a filename, and click Save.

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

Installing a PowerPath patch 35


Loading configurationsYou can load the last known reboot state or alternatively, a previously saved EMC PowerPath Administrator configuration file. Use the following procedure to load a configuration:

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

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

Note: The first time you run EMC PowerPath Administrator, there is a default configuration. If you make changes to this configuration using the EMC PowerPath Administrator that you want to keep, save the configuration.

To load the last known reboot state, right click the root node and select All Tasks, Load Reboot Config.



Installing an earlier version of PowerPath

If you want to install an older version of PowerPath:

1. Ensure you disconnect redundant paths from the host to the storage system. “Disconnect redundant paths to the storage system” on page 43 provides additional information.

2. Remove PowerPath 5.0 using the PPREMOVE=2 option of the silent installations. “Silent removal” on page 44 provides additional information.

3. Install the older version of PowerPath using the instructions in the installation guide for that release.

Upgrading Windows operating systems 37


Upgrading Windows operating systems

You can upgrade your Windows operating system from Windows 2000 to Windows Server 2003.

EMC PowerPath for Windows Release Notes provides information on the required patches on different operating systems, supported versions of PowerPath, and any other system information that may apply to the operating system you plan to install.

Upgrading from Windows 2000 systems

To upgrade your Windows 2000 operating system to Windows 2003, choose the scenario that applies:

� If you are running PowerPath versions 3.0.5 to 4.1.1 on Windows 2000 and want to upgrade to the Windows Server 2003 platform, the EMC PowerPath Windows Server 2003 Upgrade Package Release Notes on Powerlink provides additional information.

Note: The PowerPath Windows Server 2003 Upgrade Package alleviates the need for the removing and reinstalling PowerPath to perform the operating system upgrade.

� If you are running PowerPath versions 4.3 or later on Windows 2000 and want to upgrade to the Windows Server 2003 platform, install the Windows Server 2003 operating system following the instructions in your Microsoft documentation.



Coexistence with third-party path management software

PowerPath 5.0 can coexist with third-party path management software such as:

� Hitachi Dynamic Link Manager (HDLM)

� IBM Subsystem Device Driver (SDD)

� HP StorageWorks Secure Path

� HP StorageWorks Auto Path XP Virtual Array

PowerPath cannot co-manage devices with third-party path management software.

EMC licensing tool 39


EMC licensing tool

Use the EMC Licensing Tool to register PowerPath and other EMC products. The EMC Licensing Tool is displayed during PowerPath installation (except when the host is connected to a CLARiiON AX-series array). To manage licenses, you may launch it at any time by selecting PowerPath Licensing Tool from Start > Programs >EMCmenu.

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

Note: You must have Internet Explorer 5.0 or higher to view the online help files from the EMC Licensing Tool by pressing F1. If you do not have this browser installed, you may still view the help file directly from the online help file, EMCLicTool.chm, resident on the PowerPath CD under the \help directory.



Removing PowerPath 41

2Invisible Body Tag

This chapter describes how to remove the PowerPath software from a Windows host. This chapter includes the following sections:

� Before you remove PowerPath......................................................... 42� Removing PowerPath from a Windows host................................. 43

Removing PowerPath


Removing PowerPath

Before you remove PowerPath

Before you remove PowerPath from the host:

� Check Powerlink or contact EMC Customer Support for the most current information. EMC updates release notes periodically and posts them on the Powerlink.

� Stop any application actively sending I/O. In addition, close any remaining applications and client files to avoid warning messages when rebooting after the uninstall.

Note: You will be unable to uninstall PowerPath if you are running PowerPath 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.

Removing PowerPath from a Windows host 43

Removing PowerPath

Removing PowerPath from a Windows host

CAUTION!

Data corruption is possible if multiple paths remain on a system after PowerPath has been removed. Make sure that you remove any redundant paths during the uninstall process, following the instructions in this section.

You can remove PowerPath:

� Using the Add/Remove Programs wizard.

� From the command line.

Removing PowerPath using Add/Remove programs

To uninstall PowerPath using Add/Remove Programs, follow these steps:

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

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

3. When prompted to remove PowerPath, click Yes.

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

Disconnect redundant paths to the storage system

Before you reboot, shut down the host and disconnect redundant paths from the host to the storage system:

1. From the Start menu, select Shut Down.

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

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

Note: SAN (Fabric) configurations may have multiple logical configurations per physical connection. Ensure that no redundant zoned paths exist.

4. Reboot the host. PowerPath is completely removed from the host.


Removing PowerPath

Removing PowerPath from the command line

You can remove PowerPath from the command line:

� Silently, which requires no user input.

� Interactively, which requires user input.

Note: Disconnect redundant cables from the HBAs to the storage system interface ports after PowerPath has been removed and before the host is rebooted. SAN (Fabric) configurations may have multiple logical configurations per physical connection. Ensure that no redundant zoned paths exist.

Silent removal To remove PowerPath silently from the command line, use the following syntax (enter the entire command on one line):

On Windows 2000 host

<drive>:\W2000\EMCPP.<platform>.5.0.<x>.GA.exe /s /v"/q /L*v <Path to



<drive>:\W2003\EMCPP.<platform>.5.0.<x>.GA.exe /s /v"/q /L*v <Path to


where:

� <drive> is the CD drive letter, for example, D.� <platform> is W2000 or W2003_32 or W2003_x64 or

W2003_IA64.� <x> is the release level, for example, 0.� <Path to log file> is the complete path to the log file, for

example, C:\logs\PPremove.log.� <Property=PropertyValue> is one or more optional properties.


Removing PowerPath


Table 6 describes the optional properties.

All properties must be in capital letters or the information will not be passed to the installer.

Silent Removal exampleThe following is an example of a silent clean removal with logging enabled, reboot disabled, on Windows 2000 and Windows 2003 32-bit hosts:


ExampleEMCPP.W2000_5.0.0.GA.exe /s /v"/q /L*v C:\logs\PPcleanremoval.log

NO_REBOOT=1 PPREMOVE=CLEAN"

Table 5 Silent removal variables

Variable Function

/s Indicates a silent removal.


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

/L*v <file> Directs the Microsoft Installer to write verbose output to the file specified with this option. The target directory for the log file must exist before starting a silent removal using the logging option (as required by the Windows installer engine).

Table 6 Properties

Property Description

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

Note: Be sure to specify to NO_REBOOT=1. Otherwise,

PowerPath reboots before you can remove the redundant

connections.

PPREMOVE=PP PowerPath is removed, but driver files and corresponding registry entries remain on host.

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


Removing PowerPath


ExampleEMCPP.W2003_32.5.0.0.GA.exe /s /v"/q /L*v C:\logs\PPcleanremoval.log


Interactive removal from the command line

To remove PowerPath interactively from the command line, use the following syntax (enter the entire command on one line):


<drive>:\W2000\EMCPP.<platform>.5.0.<x>.GA.exe /v" /L*v <Path to log



<drive>:\W2003\EMCPP.<platform>.5.0.<x>.GA.exe /v" /L*v <Path to log


where:

� <drive> is the CD drive letter, for example, D.� <platform> is W2000 or W2003_32 or W2003_x64 or

W2003_IA64.� <x> is the release level, for example, 0.� <Path to log file> is the complete path to the log file, for

example, C:\logs\PPremove.log.� <Property=PropertyValue> is one or more optional properties,

described in Table 6 on page 45.


Table 7 Interactive removal variables

Variable Function


/L*v <file> Directs the Microsoft Installer to write verbose output to the file specified with this option. The target directory for the log file must exist before starting an interactive removal using the logging option (as required by the Windows installer engine).


Removing PowerPath

Examples of interactive removalsThe following are all valid command lines for interactive removals:



� Enables interactive removal with logging enabled� Disables reboot

ExampleEMCPP.W2000_5.0.0.GA.exe /v"/L*v C:\logs\PPremove.log NO_REBOOT=1

PPREMOVE=PP"

On Windows 2003

On a Windows 2003 x64-bit host, the command performs the following:

� Enables interactive removal with logging � Disables reboot

ExampleEMCPP.W2003_x64.5.0.0.GA.exe /v"/L*v C:\logs\PPremove.log NO_REBOOT=1

PPREMOVE=PP"

On Windows 2003 32-bit host, the command performs the following:

� Enables interactive clean removal with logging

� Disable reboot disabled

ExampleEMCPP.W2003_32.5.0.0.GA.exe /v"/L*v C:\logs\PPcleanremoval.log



Removing PowerPath

Documents

Installing PowerPath - communities.bmc.com PowerPath 15 1 Invisible Body Tag This chapter describes procedures to install and upgrade EMC® PowerPath® software on a Windows host