powerpath For Linux - Dell Emc€¦ · PowerPath for Linux Version 4.4 and Point Releases Release Notes describes the operating system versions and patches needed to support PowerPath,

EMC CorporationCorporate Headquarters:

PowerPathfor LinuxVersion 4.4

INSTALLATION GUIDEP/N 300-002-580

REV A02

Hopkinton, MA 01748-9103

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

ii

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

Published February, 2006

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

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software 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.

PowerPath for Linux Installation Guide

Contents

Preface.............................................................................................................................. v

Chapter 1 Installing PowerPathBefore You Install ............................................................................. 1-2

Obtain Current Information.................................................... 1-2Locate Your License.................................................................. 1-2Check Storage Systems ............................................................ 1-3Check Hosts............................................................................... 1-4Configure Kernel ...................................................................... 1-5Check PowerPath Major Number .......................................... 1-8Install Linux Patches ................................................................ 1-8IA64 Systems Only ................................................................... 1-8

Installing PowerPath ....................................................................... 1-9Install PowerPath...................................................................... 1-9Register PowerPath ................................................................ 1-10Unmount CD-ROM ................................................................ 1-12Complete Post-Installation Tasks......................................... 1-12

After You Install ............................................................................. 1-13Upgrading PowerPath .................................................................. 1-16

Before You Upgrade PowerPath........................................... 1-16Upgrade Procedure ................................................................ 1-17

Chapter 2 Removing PowerPathBefore You Remove PowerPath ..................................................... 2-2Removing PowerPath...................................................................... 2-2After You Remove PowerPath ....................................................... 2-3

PowerPath for Linux Installation Guide iii

Contents

Chapter 3 TroubleshootingRecovering from a Failed PowerPath Installation ...................... 3-2No Visible Pseudo Devices............................................................. 3-3Missing or Deleted Files ................................................................. 3-4Incorrect PowerPath Configuration.............................................. 3-5Problems Booting the Host............................................................. 3-5System Hangs................................................................................... 3-6

Unsupported HBA Drivers ..................................................... 3-6Other Causes ............................................................................. 3-6

Appendix A Upgrading Linux with PowerPath InstalledUpgrading Linux with PowerPath Installed ............................. A-2

Red Hat AS/ES 4.0 .................................................................. A-2SLES 9.0..................................................................................... A-2

Index................................................................................................................................ i-1

PowerPath for Linux Installation Guideiv

Preface

As part of its effort to continuously improve and enhance the performance and capabilities of the EMC product line, EMC periodically releases new versions of PowerPath. Therefore, some functions described in this manual may not be supported by all versions of PowerPath or the storage system hardware it supports. For the most up-to-date information on product features, refer to your product release notes.

If a PowerPath feature does not function properly or as described in this manual, please contact the EMC Customer Support Center for assistance. Refer to Where to Get Help on page ix in this Preface for contact information.

This guide describes how to install and remove PowerPath for Linux Version 4.4.x.

Audience andPrerequisites

This guide is intended for storage administrators and other information system professionals responsible for installing and maintaining PowerPath 4.4.x in a Linux environment.

In addition to understanding PowerPath, administrators should be familiar with the host operating system where PowerPath runs and the applications used with PowerPath.

PowerPath for Linux Installation Guide v

vi

Preface

Content Overview This guide has the following chapters and appendix:

◆ Chapter 1, “Installing PowerPath,”describes how to install and upgrade PowerPath software.

◆ Chapter 2, “Removing PowerPath,”describes how to remove PowerPath software.

◆ Chapter 3, “Troubleshooting,”describes what to do in the event of missing or deleted files, an incorrect PowerPath configuration, or other periodically encountered problems.

◆ Appendix A, “Upgrading Linux with PowerPath Installed,” describes how to upgrade or rebuild a Linux kernel on a host with PowerPath installed.

PowerPathand Related

Documentation

Here is the complete PowerPath documentation set; all manuals are available from EMC Corporation:

◆ PowerPath Product Guide◆ PowerPath Quick Reference◆ PowerPath for AIX Installation and Administration Guide◆ PowerPath for HP-UX Installation and Administration Guide◆ PowerPath for Linux Installation Guide◆ PowerPath for Solaris Installation and Administration Guide◆ PowerPath for Windows Installation and Administration Guide◆ EMC PowerPath for AIX Release Notes◆ EMC PowerPath for HP-UX Release Notes◆ EMC PowerPath for Solaris Release Notes◆ EMC PowerPath for Linux Release Notes◆ EMC PowerPath for Windows Release Notes

These PowerPath manuals are updated periodically. Electronic versions of the updated manuals are available on the Powerlink website: http://Powerlink.EMC.com.


http://powerlink.emc.com

Preface

Related DocumentationIf your environment includes Symmetrix storage systems, refer also to the EMC host connectivity guide, which are available on the Powerlink website.

If your environment includes CLARiiON storage systems, refer also to the following manuals:

◆ EMC host connectivity guides

◆ EMC Installation Roadmap for CX-Series and FC-Series Storage Systems

◆ EMC Navisphere Manager Version 6.X Administrator’s Guide

If your environment includes other vendors’ storage systems, refer to the appropriate documentation from your vendor.

Another related EMC enterprise storage publication is the EMC Support Matrix, available on the Web. Go to this page:

http://www.emc.com/horizontal/interoperability

Choose the link to EMC Interoperability Support Matrices, and then the link to EMC Support Matrix.

PowerPath for Linux Installation Guide vii


viii

Preface

TypographicConventions in this

Manual

This manual uses the following conventions for notes and cautions:

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

CAUTION!A caution contains information essential to avoiding damage to hardware or software.

This manual uses the following type style conventions:

AVANT GARDE

Keystrokes

Palatino, bold

◆ Dialog box, button, icon, and menu items in text◆ Selections you can make from the user interface,

including buttons, icons, options, and field names

Palatino, italic

◆ New terms or unique word usage in text ◆ Command line arguments when used in text◆ Book titles

Courier,

italic

Arguments used in examples of command line syntax.

Courier System prompts and displays and specific filenames or complete paths. For example:

/etc/opt/emcpower

Courier,

bold

User entry. For example:

symmpoll -p


Preface

Where to Get Help Obtain technical support by calling your local EMC sales office. For a list of EMC locations, go to this EMC website:

http://www.emc.com/contact/

For service, call EMC Customer Service:

Follow the voice menu prompts to open a service call.

For additional information about EMC products and services available to customers and partners, refer to the EMC Powerlink website:

http://Powerlink.EMC.com

or contact your vendor.

For information about products and technologies qualified for use with the EMC software described in this manual, go to this EMC Web page:


Choose the link to EMC Interoperability Support Matrices, then the link to EMC Support Matrix.

Your Comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Please send a message to [email protected] with your opinions of this guide.

USA (800) 782-4362 (SVC-4EMC)

Canada: (800) 543-4782 (543-4SVC)

Worldwide: (508) 497-7901

PowerPath for Linux Installation Guide ix

http://www.emc.com/contact/



x

Preface


1Invisible Body Tag

This chapter describes how to install PowerPath 4.4.x on a Linux host. The chapter covers the following topics:

◆ Before You Install ...............................................................................1-2◆ Installing PowerPath .........................................................................1-9◆ After You Install ...............................................................................1-13

Installing PowerPath

Installing PowerPath 1-1

1-2


Before You InstallThis section describes how to prepare a Linux host for an EMC® PowerPath® installation.

Obtain Current Information

Obtain current information from the Powerlink™ website.

❑ PowerPath Release Notes — We update release notes periodically and post them on Powerlink. Release Notes are cumulative. They include information about every PowerPath point release, the latest system and environment requirements (including requirements for OS patches), and the latest information about known limitations. Review the Release Notes to determine which point release (if any) you want to install after you initially install PowerPath.

TIP: The EMC Powerlink website has the latest versions of PowerPath software and documentation.(http://Powerlink.EMC.com.)

❑ EMC Issue Tracker — Issue Tracker is an application that allows you to search for known problems and defects in EMC software. You can use Issue Tracker to find:

• Descriptions of PowerPath bugs existing on any PowerPath-supported host platform.

• Workarounds for existing bugs.

We update this database regularly between scheduled releases and patch releases. Issue Tracker is available on the Powerlink website.

❑ PowerPath upgrades and patches — You can download PowerPath patch software from Powerlink.

❑ PowerPath documentation — We update this installation guide and the PowerPath Product Guide whenever we release new features with a patch.

Locate Your License ❑ Locate your registration number. The registration number is on the License Key Card that EMC sends you.




Check Storage Systems

The sequence of steps for configuring a storage system and installing PowerPath on a host depends on which storage system you use.

❑ Symmetrix® storage systems — Install PowerPath after you set up and verify that the Symmetrix is working properly. Then, install PowerPath using the instructions in this book.

❑ CLARiiON® storage systems:

PowerPath installation is an integral part of a 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 CX-Series and FC-Series Storage Systems. There you will find 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 Powerlink website: http://Powerlink.EMC.com.

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

❑ First-time PowerPath installations — Remove any version of Navisphere® Application Transparent Failover (ATF) installed on a host that supports this application.

Note: The procedure for migrating from ATF or 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, refer to Removing ATF or CDE Software Before Installing Other Failover Software for more information. This document is available only on the EMC Powerlink web site.

❑ If it is running, stop the Navisphere agent before installing either the full release or a patch release of PowerPath. Enter:

/etc/init.d/naviagent stop

Before You Install 1-3


1-4


❑ Third-party storage systems — Install PowerPath after you set up and verify that the third-party storage system is working properly. Then, install PowerPath using the instructions in this book.

Check Hosts Before installing PowerPath on any Linux host, ensure that the host meets the following requirements:

TIP: The Support Matrix is available in two formats on http://Powerlink.EMC.com.

E-Lab Navigator (formerly ESN Builder) is a Web-based, searchable database configurator.

The Interoperability/Support Matrices link lets you download the Support Matrix as an Acrobat.pdf file.

❑ The Environment and System Requirements section of the EMC PowerPath for Linux Version 4.4 and Point Releases Release Notes describes the operating system versions and patches needed to support PowerPath, and differences between the host-storage system interconnection topologies specified in the EMC Support Matrix and specific PowerPath requirements.

❑ Ensure that the storage-system logical devices are configured for PowerPath support. Refer to the EMC Host Connectivity Guides for both Symmetrix and CLARiiON systems. Also refer to the Installation Roadmap for CX-Series and FC-Series Storage Systems for CLARiiON systems.

❑ Ensure that there is only one path per logical device. (Once PowerPath is installed, more than one path per logical device is permitted.) If necessary, disconnect the cable on the host and not on the array.

❑ Make sure that the root partition has at least 120MB of free space.

Note: If you attempt to install PowerPath on a host that lacks sufficient space, installation fails as expected. RPM, however, returns a misleading message about the amount of space needed to install PowerPath. Refer to “Recovering from a Failed PowerPath Installation” on page 3-2 for more information.

❑ Stop I/O to native devices.

❑ Configure the HBA BIOS and drivers if you have not already done so.

CAUTION!Be sure to follow the HBA BIOS and driver configuration guidelines outlined by EMC in the EMC Support Matrix and product documentation. Using improper settings can cause erratic failover behavior, such as greatly increased I/O delays.


http://www.emc.com/horizontal/interoperability/matrices/EMCSupportMatrix.pdf


Configure Kernel Make the Linux kernel changes described in this section before you install PowerPath. Review the requirements and do all that apply in your configuration. If you do not know which HBA or fibre drivers support PowerPath with your host, refer to the EMC Support Matrix on the Powerlink website.

❑ If you load the HBA driver as a module, install its binary file in its location in /lib/modules/‘uname -r‘/drivers/scsi.

• For both Red Hat and SuSE distributions, the valid module names (depending on the HBA installed) are:

– qla2300

– qla4010

– lpfc

• If, according to the EMC Support Matrix on the Powerlink website, for your distribution and the HBA model, the fibre driver does not need to be rebuilt (the version of the driver supplied in your distribution is supported), this copying step is unnecessary.

❑ If you have a fibre driver, ensure that it is loaded before you install PowerPath. Use the lsmod command to list the modules that are currently loaded. The output should include fibre drivers.

❑ If you use QLogic HBAs, you need to disable failover for those HBAs. Add the following line to the /etc/modprobe.conf file on RHEL and to /etc/modprobe.conf.local on SLES:

options qla2xxx ql2xfailover=0 ConfigRequired=0


1-6


Modify Configuration FilesMake changes to your configuration files according to the following instructions for your distribution.

For Red Hat DistributionsMake the following changes as appropriate in the /etc/modprobe.conf file.

The HBA driver used to access EMC devices can be statically loaded in the kernel or loaded into the kernel as a module.

❑ If you want to build the HBA driver into the RAM disk, ensure that the HBA driver is always loaded after the internal SCSI adapter driver as specified by the /etc/modprobe.conf file.

For example, in the following file, the QLogic qla2300 driver is always loaded after all internal SCSI drivers are loaded:

alias eth0 eepro100alias scsi_hostadapter1 aic7xxxalias scsi_hostadapter2 aic7xxxalias scsi_hostadapter3 aic7xxxalias scsi_hostadapter4 qla2300

Note: In the line above, the module name could be qla2300, qla4010, or lpfc, depending on the installed HBA.

❑ Enable the max_scsi_luns parameter in /etc/modprobe.conf if the host is connected to a either a CLARiiON storage array or an EMC Invista system.

In the default Red Hat kernel, CONFIG_SCSI_MULTI_LUN is disabled. As a result, if the LUN 0 disappears from the storage group and the host is rebooted or the driver is unloaded and reloaded, the host will see only the ghost LUNs (with ArrayCommPath disabled) or the LUNZ (with ArrayCommPath enabled).



For example, the max_scsi_luns parameter is enabled in the following modprobe.conf file:

alias parport_lowlevel parport_pcalias scsi_hostadapter sym53c8xxalias scsi_hostadapter1 qla2300alias scsi_hostadapter2 qla2300alias eth0 tlanoptions scsi_mod max_scsi_luns=256

For SuSE DistributionsMake the following changes as appropriate in the /etc/sysconfig/kernel file.

❑ The HBA driver used to access EMC devices can be statically loaded in the kernel or loaded into the kernel as a module. If you want to build the HBA driver into the RAM disk, ensure that the HBA driver is always loaded after the internal SCSI adapter driver as specified by the /etc/sysconfig/kernel file.

For example, in the following file, qla2300 is always loaded after all internal SCSI drivers are loaded:

INITRD_MODULES="scsi_mod sd_mod cciss reiserfs qla2300"

Note: In the line above, the module name could be qla2300, qla4010, or lpfc, depending on the installed HBA.

Note: When loading HBA drivers into the RAM disk, make sure that the HBA module name used in /etc/sysconfig/kernel is the same as that used in the /etc/modprobe.conf file.

Save Kernel Changes Save your kernel and back up your system.

Red Hat Distributions1. Run the ls -l /boot command to determine which initrd file

is being used. Run the uname -r command to display the kernel version.

2. Enter:

/sbin/mkinitrd -f -v <initrd> <kernel version>

where <initrd> corresponds to the configuration identified in step 1.


1-8


SuSE Distributions1. Run the ls -l /boot command to determine which initrd and

vmlinuz files are being used. Run the uname -r command to display the kernel version.

2. Enter:

/sbin/mk_initrd -k <vmlinuz> -i <initrd>

where <vmlinuz> and <initrd> correspond to the configuration identified in step 1.

Check PowerPath Major NumberEnsure that major number 120, which is used by the PowerPath driver, is not already in use.

Install Linux Patches The Linux kernel and fibre drivers supported by your version of PowerPath must be installed and running.

IA64 Systems Only If you are going to install PowerPath on an IA64 system, then you must install the following packages on that system before installing PowerPath 4.4.0.

Note: PowerPath 4.4.1 does not support IA64 platforms.

Distribution Packages

RHEL 4.0a ia32el-1.1-20.ia64.rpm (or later)glibc-2.3.4-2.i686.rpm (or later)

SLES 9 SP1b ia32el-5.3-2.6 (or later)glibc-x86-9-200411051902 (or later)

a. Available on Red Hat’s Compatibility Layer Disc.

b. These packages should be installed by default on SLES 9. Check to make sure these packages are installed before installing PowerPath, and install them if necessary.



Installing PowerPathThis section describes how to install PowerPath 4.4.x on a Linux host.

Take note of the following before installing PowerPath:

◆ You do not need to reboot the host after installing PowerPath 4.4.x.

◆ Refer to “Recovering from a Failed PowerPath Installation” on page 3-2 for information on recovering from a failed PowerPath installation.

Install PowerPath To install PowerPath:

1. Log in as root.

Installing from CD-ROMIf you are installing from the PowerPath CD-ROM, complete steps 2 through 5, and then continue with step 8.

2. Insert the PowerPath installation CD-ROM into the CD-ROM drive.

3. Create the directory /cdrom to be the mount point for the CD-ROM. Enter:

mkdir /cdrom

4. Mount the PowerPath CD on /cdrom. Enter:

mount -o ro /dev/cdrom /cdrom

5. Change directories to the directory for your operating system.

For SLES, enter:

cd /cdrom/LINUX/2.6/pp4.4/sles

For RHEL, enter:

cd /cdrom/LINUX/2.6/pp4.4/rhel

Installing from a Compressed ArchiveIf you are installing from the PowerPath archive, complete steps 6 and 7, and then continue with step 8.

6. Download the PowerPath 4.4.x archive from http://Powerlink.EMC.com > Resources/Tools > CS Support > Downloads and Patches > Downloads D-R > PowerPath for Linux.


1-10


7. Untar the PowerPath archive:

tar -xzf EMCpower.LINUX.4.4.<release_level>.<build_number>.tar.gz

Install PowerPath8. Install PowerPath. Enter:

rpm -i EMCpower.LINUX-4.4.<release_level>-<build_number>.<package_name>.rpm

where <package_name> is:


Register PowerPath Take note of the following regarding PowerPath registration:

◆ Installing PowerPath on a host connected to a CLARiiON AX-series array does not require a license. PowerPath provides full functionality with or without a PowerPath license when the host is connected to a CLARiiON AX-series array. Therefore, you do not need to run the emcpreg -install command when installing PowerPath on a host connected to a CLARiiON AX-series array.

◆ If you do not register the PowerPath software during PowerPath installation (on a host connect to any storage system other than a CLARiiON AX-series array), and then subsequently reboot the host, the load balancing and failover policy is set to Basic Failover. If this happens, you must register PowerPath using the emcpreg -install command and then run the powermt set policy command to reset the policy as appropriate. Refer to the PowerPath Product Guide for more information.

Package Name Description

sles.x86_64 PowerPath 4.4.x on SLES x86_64 platforms.

sles.ia64 PowerPath 4.4.x on SLES IA64 platforms.

sles.i386 PowerPath 4.4.x on SLES i386 platforms.

rhel.x86_64 PowerPath 4.4.x on RHEL and x86_64 platforms.

rhel.ia64 PowerPath 4.4.x on RHEL IA64 platforms.

rhel.i386 PowerPath 4.4.x on RHEL and i386 platforms.



To register the PowerPath license:

1. Enter:

emcpreg -install

You see the following output:

=========== EMC PowerPath Registration ===========Do you have a new registration key or keys to enter? [n]

2. Enter:

y

You see the following output:

Enter the registration key(s) for your product(s),one per line, pressing Enter after each key.After typing all keys, press Enter again.

Key (Enter if done):

3. Enter the 24-character alphanumeric sequence found on the License Key Card delivered with the PowerPath media kit, and press ENTER.

If you enter a valid registration key, you see the following output:

1 Key(s) successfully added.

Key successfully installed:

If you enter an invalid registration key, the screen displays an error message and prompts you to enter a valid key. Refer to the PowerPath Product Guide for a list of error messages returned by the emcpreg license registration utility.

4. Press ENTER. You see the following output:

1 key(s) successfully registered.

5. Start PowerPath. Enter:

/etc/init.d/PowerPath start

Note: Use only the above script to load and unload the PowerPath modules.


1-12


Unmount CD-ROM If you used a CD-ROM, unmount it:

1. Change to the root directory. Unmount the CD. Enter:

cd /umount /cdrom

2. Remove the CD-ROM from the CD-ROM drive.

Complete Post-Installation TasksPowerPath installation is now finished. Refer to “After You Install” on page 1-13 for postinstallation information and instructions.



After You InstallAfter installing PowerPath:

❑ Verify that your PowerPath capabilities are correct.

❑ Reconfigure device mappings.

❑ If you load the HBA driver as a module, verify that all PowerPath extensions are loaded.

Verify Your PowerPath Capabilities Are CorrectVerify that your PowerPath capabilities match your license. For example, run the powermt display dev=all command and make sure the load balancing and failover policies are correct.

Note: If the load balancing policy does not match your expectations for your license level, check the license registration. Refer to the man pages for the emcpreg and powermt utilities for clarification on licenses and load balancing policies.

Refer to the PowerPath Product Guide or the powermt(1) man page for more information about load balancing and failover policies and the powermt display command.

Reconfiguring Device MappingsConsult the man page for the powermt command and look for the display dev=all option to view current device mappings. When reconfiguring the device mappings on an array, you should pay careful attention to the resulting configuration. Device names on the host are assigned dynamically during the loading of the HBA driver. Therefore, any changes to the configuration may result in changes in the pre-existing device naming association. For example, this may render some existing mount table inaccurate if you do not update the mount points to correspond to the new device configuration and its device naming association.

After You Install 1-13

1-14


Verify Extensions Are LoadedIf you load the HBA driver as a module (not as a static kernel driver), verify that all extensions are loaded.

Enter:

lsmod

Provided you built the HBA driver as a module, the HBA driver name appears in the lsmod output, below the PowerPath drivers (which begin with “emc”). For example:

Module Size Used byemcphr 29528 0emcpmpap 129496 0emcpmpaa 95360 0emcpmpc 122168 64emcpmp 78004 0emcp 615120 5 emcphr,emcpmpap,emcpmpaa,emcpmpc,emcpmplibnss 80052 5 emcpmpap,emcpmpaa,emcpmpc,emcpmp,emcpemcplib 18304 0usbserial 48240 0autofs 33280 5parport_pc 53568 1lp 27908 0parport 56520 2 parport_pc,lpedd 26008 0joydev 26816 0sg 53920 0st 57500 0sr_mod 33316 0ide_cd 54788 0cdrom 55196 2 sr_mod,ide_cdnvram 25736 0ohci_hcd 37124 0sworks_agp 25760 0agpgart 48300 1 sworks_agpspeedstep_lib 20352 0freq_table 21504 0thermal 28936 0processor 34496 1 thermalfan 20484 0button 22672 0battery 25092 0ac 21252 0ipv6 326908 25evdev 26240 0usbcore 129244 4 usbserial,ohci_hcde1000 102020 0subfs 24448 2reiserfs 276432 2dm_mod 72192 0



xfs 614360 1exportfs 22656 1 xfsdmapi 66592 1 xfsqla2300 140160 0qla2xxx 283336 65 qla2300mptscsih 52120 0mptbase 60384 1 mptscsihsd_mod 37376 64scsi_mod 132292 7 emcp,sg,st,sr_mod,qla2xxx,mptscsih,sd_mod

The /etc/modprobe.conf.pp file should look like the following:

###BEGINPPinclude modprobe.conf.pp###ENDPPalias ppemcp emcpalias ppemcpmp emcpmpalias ppemcpmpc emcpmpcalias ppemcpmpaa emcpmpaaalias ppemcpioc emcpiocoptions emcp managedclass=invista,ess,hitachi,hpxp,hphsx

After You Install 1-15

1-16


Upgrading PowerPathYou can only upgrade to a version of PowerPath 4.4.x from an earlier version of PowerPath 4.4.x. You cannot upgrade from a version earlier than PowerPath 4.4.0.

Before You Upgrade PowerPath

◆ Check the Powerlink website (http://Powerlink.EMC.com) for the most current information. EMC updates release notes periodically and post them on Powerlink.

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

◆ Stop powermt display if it is running. Refer to the PowerPath Product Guide or the powermt(1) man page for information about powermt display.

◆ Stop I/O to native and PowerPath pseudo devices, and unmount these devices before upgrading.

◆ Make sure that you load the HBA drivers before upgrading PowerPath. If the HBA drivers are not loaded, your custom PowerPath settings will be lost during the upgrade process.

◆ If the default major and minor numbers associated with a native device (for example, /dev/sda) have been changed, upgrading to PowerPath 4.4.x fails to preserve pseudo-to-native device mappings and device policy/priority settings. To avoid this problem:

1. With the earlier version of PowerPath 4.4.x installed, run the powermt display dev=all command and redirect the output to a file.

2. Run the /etc/init.d/PowerPath stop command.

3. Delete all the native devices listed in the powermt log file created in step 1.

4. Use the mknod command to recreate the native devices with the default major/minor numbers.

5. Run the /etc/init.d/PowerPath start command.

◆ CLARiiON systems only: Stop the Navisphere agent.




Upgrade Procedure Take note of the following before upgrading PowerPath:

◆ You do not need to reboot the host after upgrading to PowerPath.

◆ Do not use the -i option to upgrade from an earlier version of PowerPath. Using the -i option creates multiple PowerPath entries in the Linux RPM database, which can cause ongoing maintenance problems. If you inadvertently use the -i option to upgrade PowerPath, follow the procedure in “Correcting Multiple PowerPath Entries in the RPM Database” on page 5-5 to correct the problem.

◆ Refer to “Troubleshooting a PowerPath Upgrade” on page 5-4 if you encounter any problems while upgrading PowerPath.

Upgrading to PowerPath 4.4.xTo upgrade to PowerPath 4.4.x:

1. Download the PowerPath 4.4.x archive from http://Powerlink.EMC.com > Resources/Tools > CS Support > Downloads and Patches > Downloads D-R > PowerPath for Linux.

2. Untar the PowerPath archive. Enter:

tar -xzf EMCpower.LINUX.4.4.<release_level>.<build_number>.tar.gz

3. Install PowerPath. Enter:

rpm -Uv EMCpower.LINUX-4.4.<release_level>-<build_number>.<package_name>.rpm

where <package_name> is:


Package Name Description

sles.x86_64 PowerPath 4.4.x on SLES x86_64 platforms.

sles.ia64 PowerPath 4.4.x on SLES IA64 platforms.

sles.i386 PowerPath 4.4.x on SLES i386 platforms.

rhel.x86_64 PowerPath 4.4.x on RHEL and x86_64 platforms.

rhel.ia64 PowerPath 4.4.x on RHEL IA64 platforms.

rhel.i386 PowerPath 4.4.x on RHEL and i386 platforms.

Upgrading PowerPath 1-17

1-18


4. Perform the post-installation tasks in “After You Install” on page 1-13.


2Invisible Body Tag

This chapter describes how to remove PowerPath 4.4.x from a Linux host. The chapter covers the following topics:

◆ Before You Remove PowerPath .......................................................2-2◆ Removing PowerPath........................................................................2-2◆ After You Remove PowerPath .........................................................2-3

Removing PowerPath

Removing PowerPath 2-1

2-2

Removing PowerPath

Before You Remove PowerPathBefore you remove PowerPath from the host:

❑ If the powermt display every= command is running in a loop, cancel the command. (Refer to the PowerPath Product Guide or the powermt(1) man page for information about powermt display.)

❑ Make sure no PowerPath devices are in use; for example, unmount a mounted file system.

❑ Stop the Navisphere agent (CLARiiON only).

❑ Manually remove references to PowerPath pseudo devices from system configuration files such as /etc/fstab.

❑ If you removed a PowerPath-managed native device file (that is, /dev/sd[a-z][a-z]) while PowerPath was loaded, you must use the mknod command to recreate that native device file with its default major/minor numbers before trying to unload or uninstall PowerPath.

Removing PowerPath1. Log in as root.

2. Display the package name. Enter:

rpm -qa | grep EMCpower.LINUX

3. Remove the software. Enter:

rpm -e EMCpower.LINUX-4.4.<release_level>-<build_number>

Note: If the PowerPath uninstall program displays a message saying that it could not unload the emcp module, run the lsmod | grep emcp command to determine if any PowerPath modules are loaded on the host. If so, reboot the host after the uninstallation completes to unload the modules.


Removing PowerPath

Saved Configuration FilesThe PowerPath 4.4.x uninstall process saves the PowerPath configuration files in the /etc/emc/archive directory. If necessary, you can use these configuration files to restore the PowerPath 4.4 configuration on the host, or upgrade to a later version of PowerPath without PowerPath 4.4.x installed on the host while re-using the 4.4 configuration.

After You Remove PowerPathAfter PowerPath has been successfully uninstalled, if you had previously used emcpower devices, you must manually remove references to PowerPath pseudo devices (emcpower devices) from system configuration files such as /etc/fstab, /etc/auto.master, and /etc/*auto*.

After You Remove PowerPath 2-3

2-4

Removing PowerPath


3Invisible Body Tag

This chapter describes how to fix installation and other problems that you may encounter with PowerPath. The chapter covers the following topics:

◆ Recovering from a Failed PowerPath Installation.........................3-2◆ No Visible Pseudo Devices ...............................................................3-3◆ Missing or Deleted Files....................................................................3-4◆ Incorrect PowerPath Configuration ................................................3-5◆ Problems Booting the Host ...............................................................3-5◆ System Hangs .....................................................................................3-6

Troubleshooting

Troubleshooting 3-1

3-2

Troubleshooting

Recovering from a Failed PowerPath InstallationIf PowerPath installation fails, correct any error conditions reported by the install program. Then complete each item in the following checklist. After completing the checklist, install PowerPath following the instructions in Chapter 1, “Installing PowerPath”.

❑ Edit the /etc/init.d/boot.localfs file on SuSE or the /etc/rc.sysinit file on Red Hat and remove the following lines:

# Configure and initialize PowerPath.if [ -f /etc/init.d/PowerPath ];

then /etc/init.d/PowerPath startfi

If the RPM installation succeeds yet the error message indicating that the patch failed is displayed, you should verify that the /etc/init.d/boot or /etc/rc.sysinit file contains the lines above.

❑ Edit the /etc/modprobe.conf file and remove the following lines:

###BEGINPPinclude /etc/modprobe.conf.pp###ENDPP

❑ Enter the following command to determine if the PowerPath modules are loaded:

lsmod | grep emc

If the modules are loaded, enter the following command to unload them:

/etc/init.d/PowerPath stop

❑ Rename the /etc/init.d/PowerPath file. Enter:

mv /etc/init.d/PowerPath /etc/init.d/PowerPath.saved

❑ Remove the PowerPath entry in the RPM database (if it exists). Enter the following commands to remove the entry:

rpm -qa | grep EMCpower.LINUXrpm -ev EMCpower.LINUX-4.4.<release_level>-<build_number>


Troubleshooting

Note: If this command fails, use the rpm -ev --noscripts command.

rm -r /etc/opt/emcpower

Note: Make sure that you have unloaded the PowerPath modules and renamed the /etc/init.d/PowerPath file before running these commands.

❑ Check the /etc/opt/emcpower/EMCpower.LINUX-4.4/log file for additional information about the failure.

No Visible Pseudo DevicesOnce you install, register, and start PowerPath, you should see devices in the output of the powermt display command. If you do not see any devices, do the following:

1. Stop PowerPath. Enter:


Note: Use only the above script for loading and unloading PowerPath modules.

2. If it is not present already, add the following line to the /etc/modprobe.conf.pp file:

install emcp /sbin/modprobe <hba_module_name>;/sbin/modprobe emcp --ignore-install

3. Restart PowerPath. Enter:


4. Ensure that all of the PowerPath modules listed in “Verify Extensions Are Loaded” on page 1-14 are loaded, in addition to the HBA driver.

No Visible Pseudo Devices 3-3

3-4

Troubleshooting

Missing or Deleted FilesIf PowerPath files are missing or deleted after installation, PowerPath may not run correctly (or at all). If this happens, remove and then reinstall PowerPath:



Note: Use only the above script for EMC PowerPath module loading and unloading.

2. Remove PowerPath. Enter:

rpm -qa | grep EMCpower.LINUXrpm -ev EMCpower.LINUX-4.4.<release_level>-<build_number>

Note: If this command fails, use the rpm -ev --noscripts command.

3. Remove /etc/opt/emcpower. Enter:

rm -rf /etc/opt/emcpower

CAUTION!Remove the emcpower directory only if you cannot restore the deleted or corrupted files from backups.

4. Reinstall PowerPath. Refer to “Installing PowerPath” on page 1-9 for more information.


Troubleshooting

Incorrect PowerPath ConfigurationIf the Navisphere agent (or any application that holds devices open) is running when you try to configure PowerPath devices, the configuration will be incorrect.

To resolve this problem:

1. Stop the Navisphere agent and any other application that may be holding devices open.



Note: Use only the above script for EMC PowerPath module loading and unloading.

3. Restart PowerPath. Enter:


4. Restart the applications you stopped in step 1.

Problems Booting the HostIf you have previously used emcpower devices and subsequently uninstalled PowerPath without removing these emcpower devices, the host system fails to boot properly.

Manually remove references to PowerPath pseudo devices (emcpower devices) from system configuration files such as /etc/fstab, /etc/auto.master, and /etc/*auto*.

Incorrect PowerPath Configuration 3-5

3-6

Troubleshooting

System HangsSystem hangs may be caused by a number of reasons. This section offers solutions to some scenarios you may encounter.

Unsupported HBA Drivers

If your computer hangs after you install PowerPath or after the first time you reboot after installation, check the EMC Support Matrix and verify that your fibre driver is currently supported.

Note: The EMC Support Matrix, which is updated every month, is published at the Powerlink website: http://Powerlink.EMC.com.

The driver version that may have come with your Linux distribution might not be supported by EMC. In this case, use the following recovery procedure:

1. Detach all connections to the storage system before booting.

2. Reboot to a <safe> kernel and remove the qla entry from the /etc/modprobe.conf or /etc/sysconfig/kernel file.

3. If a RAM disk is used, rebuild it.

4. Reboot the host with the new RAM disk.

5. Build the supported driver and incorporate it into a new RAM disk as desired.

6. Reattach the connections to the storage system.

7. Reboot the host with the storage attached.

Other Causes If your computer hangs and you have the correct HBA drivers, check the Issue Tracker application on Powerlink (http://Powerlink.EMC.com) for other possible causes.


Anvisible Body Tag

This appendix describes how to upgrade a Linux kernel on a host with PowerPath installed.

◆ Upgrading Linux with PowerPath Installed.................................A-2

Upgrading Linux withPowerPath Installed

Upgrading Linux with PowerPath Installed A-1

A-2

Upgrading Linux with PowerPath Installed

Upgrading Linux with PowerPath InstalledUpgrading a Linux kernel results in the deletion of the installed PowerPath drivers. Procedures for upgrading Linux with PowerPath installed differ based on which Linux distribution you have.

Note: Before upgrading to a new version of Linux, check the EMC Support Matrix to verify that that version of Linux has been qualified with PowerPath.

◆ To upgrade errata for Red Hat AS/ES 4.0, refer to “Red Hat AS/ES 4.0”.

◆ To upgrade errata for SLES 9.0, refer to “SLES 9.0”.

Red Hat AS/ES 4.0 To upgrade Linux on Red Hat AS/ES 4.0:

1. Install the new errata version.

2. Boot to the new kernel.

3. Reinstall the supported HBA driver.

4. Replace the PowerPath package to copy the PowerPath drivers to the new Linux kernel directory. Use the following command to replace PowerPath after you have upgraded your Linux kernel:

rpm -Uvh --replacepkgs EMCpower.LINUX-4.4.<release_level>-<build_number>.<package_name>.rpm

SLES 9.0 For SLES 9.0, PowerPath must be uninstalled before any kernel upgrades. To upgrade Linux on SLES 9.0:

1. Uninstall PowerPath, refer to Chapter 2, “Removing PowerPath”.

2. Upgrade your host to the current errata or service packs (including reboot).

3. Reinstall PowerPath, refer to Chapter 1, “Installing PowerPath”.


Index

CCLARiiON storage systems

setting up 1-3Configuration, troubleshooting 3-5

DDeleted files, troubleshooting 3-4Documentation, related vi

EEMC Powerlink website ixEMC Support Matrix ixemcpreg 1-11

FFiles, deleted or missing 3-4

GGhost LUNs 1-6

IInstalling PowerPath

installation procedure 1-9post-installation instructions 1-13pre-installation instructions 1-2

LLinux, upgrading A-2Loading modules 1-5, 1-6, 1-7, 1-13, 3-3, 3-4, 3-5lsmod command 1-14

LUNZ 1-6

MMissing files, troubleshooting 3-4modprobe.conf file 1-6

NNavisphere agent, stopping 1-3

PPost-installation instructions 1-13Powerlink website ixpowermt command 1-13, 1-16, 2-2Pre-installation instructions 1-2

RRegistration key 1-11Restarting PowerPath 1-11rpm 2-2, 3-2, 3-4

SStarting PowerPath 1-11

TTroubleshooting

deleted or missing files 3-4PowerPath configuration 3-5

PowerPath for Linux Installation Guide i-1

i-2

Index

UUnloading modules 1-5, 1-6, 1-7, 3-3, 3-4, 3-5Upgrading Linux A-2Upgrading PowerPath 1-16

This is My Newest Special Variable Title

Documents

powerpath For Linux - Dell Emc€¦ · PowerPath for Linux Version 4.4 and Point Releases Release Notes describes the operating system versions and patches needed to support PowerPath,