Installing PowerPath software on a Windows 2003 host

Overview
This procedure describes how to install PowerPath on Windows Server 2003.

Note:This procedure is specific to the installation of PowerPath versions 4.5 to 5.0, which is the current shipping version for Windows 2003 hosts.  For instructions on installing older versions of PowerPath, refer to the applicable PowerPath installation manual available on PowerLink.

This procedure is based on content from the following EMC manual:
  • PowerPath for Windows Installation and Administration Guide

This document can be obtained from the EMC Powerlink website at:

You must be logged in as the Local System Administrator to proceed.

Verify the following prior to the installation of PowerPath:

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

·        Determine if the PowerPath software you are installing requires the removal or presence of a previous version of PowerPath.  Some full versions require the previous version to be removed while others do not.  Also, some patches require the full version to be present while others require it to be removed.  Refer to the PowerPath Release Notes and/or PowerPath patch readme files for your specific version to determine what needs to be present/removed and if and when a reboot is necessary in order to install your specific PowerPath software version and/or patch. These documents are available on http://Powerlink.EMC.com.

Note:A “failed redundancy” state can occur if PowerPath is installedon a host with mirrored disks. This state only happens if diskmanagement applications (that use the dmadmin service) arerunning when PowerPath is installed. To prevent this, close all disk management applications(including diskmgmt.msc and diskpart.exe) and stop thedmadmin service before installing PowerPath.

If applicable, stop all I/O and close all applications that access storage devices.

MPIO framework considerations:
Note that PowerPath 4.6.x requires Microsoft MPIO framework 1.16 or later.

·        If the MPIO framework is not installed on the host, the PowerPath 4.6.1 installer installs MPIO framework 1.16.; PowerPath 5.0.0 will install 1.17

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

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

Verify single device paths:
Ensure that there is only one logical connection per logical device. If necessary, disconnect all additional HBAs/NICs, hubs, switches other than the primary channels. 

Note: Doing this prevents the host from seeing the same LUN twice before PowerPath is configured.

Insert the PowerPath CD-ROM:
Insert the PowerPath installation CD in the CD-ROM drive and begin the installation. 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. Then either:

  • Select Run this program from its current location and click OK to proceed with the installation.

  • Select Run from the Start menu if autoplay is not enabled.

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

Continue Install:
Complete the information as prompted on the next four screens.

Select your options:
Use the Destination Folder screen to installPowerPath in a directory other than the default directory (ifdesired).

Note: It’s best to install PowerPath in the default directory as no additional action is required to install in the default directory.

·        If you are going to install PowerPath in itsdefault directory (recommended), clickNext and skip the remainder of this step to continue with the next step below.

·        To install PowerPath in a different (non-default) directory,click Change. The setup wizard prompts you to browse toyour destination folder. Select the destination folder, and clickOK.

Caution:Do not specify the Windows System directory for yoursystem (specified by the %SYSTEMROOT% environmentvariable). PowerPath will not function correctly if it isinstalled in this directory.  Click Next.

Continue Install:
In the Ready to Install the Program dialog box, click Install.

Note:If you do not already have a license in the registry, the EMCLicensing Tool displays.

Register PowerPath
When prompted by the EMC Licensing Tool, enter your PowerPath registration number in the License Key field.  Click Add and then OK.

Note: The PowerPath registration numberis printed on the License Key Card, which was delivered with the PowerPath media kit. You may enter multiple registration numbers as PowerPath is supported on different storage systems. If you are upgrading from a previous version, PowerPath saves the existing license key, and no input is required.

Caution: Failing to enter a registration number will result in the installation of PowerPath SE, which is the default policy without a valid PowerPath license. If you fail to enter the registration number during installation, it can be entered at a later point.

Finish:
Click Finish in the next dialog box and when prompted to reboot the host,click No.
Instead, from the Start menu, select Shut Down and then click OK.

Reconnect other I/O interfaces:
Reconnect the additional HBAs/NICs, hubs, switches, etc. that you disconnected earlier.
Power up boot:
Power up the system. PowerPath is fully configured with multiple paths to logical devices at boot up.
Check for patches

If necessary, install any PowerPath patches from the following URL:

http://powerlink.emc.com

Note: A readme file that explains how to install the patch that accompanies every patch release.  This file will also state whether you need to reboot the host after the installation of the patch.

Verify PowerPath sees new paths
The operating system must recognize new paths before PowerPath can do so. Normally, no action is needed; the operating system detects new paths automatically. Depending on the type of HBA installed, you may have to scan for hardware changes in the device manager.  Alternately, reboot.

To verify that PowerPath sees all new HBAs and paths to storage devices, use the following command in the PowerPath utility:

powermt display dev=all

To test and validate any new path(s) with PowerPath functionality, enter:

powermt restore

No comments:

Post a Comment