Installing PowerPath on an Solaris Host

 

Topic

Setting up a host environment

Selections

Select a host: Solaris

Select a Solaris task: Installing PowerPath

 

Contents

·             Installing PowerPath software on a Solaris host 3

 


 

 

·        Installing PowerPath software on a Solaris host

 

Overview

This procedure describes how to install PowerPath on a Solaris host.

 

Note: This procedure is specific to the installation of PowerPath version 5.0.x, which is the current shipping version for Solaris 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 Solaris Installation and Administration Guide

 

You can download the guide from EMC Online Support (registration required): https://support.EMC.com

 

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://support.EMC.com.

 

1.   

Mount the PowerPath CD-ROM:

Mount the PowerPath CD-ROM as follows:

a.      Verify that you are logged in as root.

b.      Insert the CD-ROM in the CD-ROM drive.

The CD should mount automatically.  If it does not, then you must mount it manually.  For example, to mount the CD on
/cdrom/cdrom0, enter


               mount -F hsfs -r /dev/dsk/cxtydzs0

     /cdrom/cdrom0

where x, y, and z are values specific to the host’s CD-ROM drive.

For example:

 

mount -F hsfs -r /dev/dsk/c0t2d0s0 /cdrom/cdrom0

 

 

2.   

Install PowerPath

Install the PowerPath software as follows:

 

a.      If you do not have a graphics terminal, run the script filename command to record pkgadd output in the specified file.  (After pkgadd completes, use CTRL-D to stop recording the output.)

b.      Change to the /mount_point/UNIX/SOLARIS directory. 

·         On SPARC hosts, enter:

cd /cdrom/cdrom0/UNIX/SOLARIS

·         On Opteron hosts, enter:

cd /cdrom/cdrom0/UNIX/SOLARIS_i386

c.      Start the installation by entering:

/usr/sbin/pkgadd -d .

Note: the required space and period after the -d parameter.

d.      At the packages available prompt, enter 1 and press Enter.

e.      At the prompt for an installation directory for the program files, press Enter to accept the default base directory (/opt) or type the path to an alternate base directory and press Enter.

Note:  PowerPath installs its files in
/basedir/EMCPower; the installation process creates the EMCPower subdirectory.  Make a note of the name and location of the PowerPath base directory for future reference.

f.       At the prompt to continue the installation, enter y and press Enter.

g.      The screen will display information about the installation. Enter q and press Enter.

 

 

3.   

Register PowerPath

After the installation completes, you must register PowerPath on the host:

 

a.      Locate the PowerPath License Key Card, delivered with the PowerPath media kit, which has your license registration key printed.  

b.   Enter the following command:

/etc/emcpreg –install

c.      At the prompt, type y and press Enter.

d.      At the registration key prompt, enter the PowerPath registration key and press Enter. 

If you enter a valid registration key, you see a success message.

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

e.   Press Enter and you will see the following output:

1 key(s) successfully registered.

f.       If you are registering PowerPath on a Solaris 10 host, then perform these steps. Otherwise, proceed to the next section.

Run the
powermt set policy command to reset the load balancing and failover policy.

Run
powermt save to save the settings in the powermt.custom file.

Refer to the PowerPath 5.0.x Product Guide or the
powermt(1) manpage for more information.

Note:  On Solaris 8 and 9 hosts, rebooting PowerPath after you register the software sets the load balancing and failover policy to the default values. However, Solaris 10 does not require a reboot; therefore, you need to manually set the policy. Refer to the PowerPath 5.0.x Product Guide for more information on setting the load balancing and failover policy.

 

 

4.   

Post activities

After PowerPath is registered on the host, perform the following:

 

a.      Remove the CD-ROM as follows:

·         If the CD-ROM volume management daemon vold is running, unmount and eject the CD-ROM.  Enter the following command and remove the CD-ROM:

eject

·         If vold is not running, unmount the CD-ROM by entering the following command and then ejecting the CD-ROM:

unmount /cdrom/cdrom0

b.      If required by your specific PowerPath version or patch, reboot the host by entering:

      reboot -- -r

Note:
  If the sd or ssd driver does not exist on the host, you will see a forceload failed warning during boot.  You can safely ignore this warning.

 

 

5.   

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 accompanies every patch release.  This file will also state whether you need to reboot the host after the installation of the patch.

 

Install the patch package by entering the following command:

 

patchadd .

 

 

6.   

Check for proper install

Verify that PowerPath is installed properly on the host as follows:

 

a.     Enter the command:

pkginfo -1 EMCpower

You should see output similar to the following:

Note:  When you install PowerPath on an AMD Opteron host, i386 appears in the ARCH row.

PKGINST: EMCpower
NAME: EMC PowerPath
CATEGORY: system
ARCH: sparc
VERSION: 5.0.0_bxxx
BASEDIR: /opt
VENDOR: EMC Corporation
PSTAMP: cambridge951018123443
INSTDATE: Feb 15 2006 08:24
STATUS: completely installed
FILES: 286 installed pathnames
         5 shared pathnames
        38 directories
       121 executables
    107843 blocks used (approx)

b.    Verify that the PowerPath kernel extension is loaded on the host by entering:


     modinfo | grep emc

You should see output similar to the following:

31 7bbfa000 2c28 163 1 emcp (PP Driver 5.0.0)
32 7bb3a000 30ce8 154 1 emcpmpx (PP MPX Ext 5.0.0)
33 1336620 21e60 - 1 emcpsf (PP SF 5.0.0)
34 7ae00000 dada8 - 1 emcpsapi (PP SAPI Ext 5.0.0)
35 12be610 12440 - 1 emcpcg (PP CG Ext 5.0.0)
36 7bb7e6d0 3180 - 1 emcpgpx (PP GPX Ext 5.0.0)
37 7b68fe88 78e8 - 1 emcpdm (PP DM Manager 5.0.0)
38 7b7a7e10 2c8 - 1 emcpioc (PP PIOC 5.0.0)

Note:  The emcpmp, emcpmpc, emcpmpap, and emcpmpaa extensions present in previous releases have been replaced by the emcpmpx extension in PowerPath 5.0.x for Solaris. Furthermore, the HighRoad (emcphr) extension has been removed from PowerPath 5.0.x.

 

7.   

Make paths visible

The operating system must recognize new paths before PowerPath can. Enter the command:

 

   devfsadm

New native devices are created; however, do not use them until PowerPath is configured in the next step of this procedure.

 

 

8.   

Configure PowerPath

Configure PowerPath by running:

 

 powermt config.

 

 

9.   

Check the configuration

Inspect the new PowerPath configuration as follows:

powermt display dev=all.

 

The new path(s) should be displayed with a state of alive.

 

Verify that each HBA sees only the targets (FAs) to which it is zoned.

 

Scan operating system error logs to ensure no errors are logged against the new paths.

Correct any issues detected.

 

10.  

Save the configuration

Save the configuration by running the following command:

 

powermt save

 

 

11.  

Check for missing PowerPath devices

If you must, check for missing PowerPath devices using the following command:

 

powermt display dev=all

 

 

12.  

Configure missing devices

Examine the output to determine if some storage system logical devices are not configured as PowerPath devices.

 

Enter the following commands to configure any missing devices:

 

powercf –q
powermt config

Rerun the powermt display dev=all command to confirm the following:
 

· the logical devices are configured as emcpower devices and the correct failover and load balancing policy is set.

· the expected LUNs are visible and each has the expected number of paths.

 

 

 

7Table of Contents