Page 1
PowerPath for UNIX
Version 4.0
INSTALLATION AND
ADMINISTRATION GUIDE
P/N 300-000-978
REV A03
EMC Corporation
Corporate Headquarters
Hopkinton, MA 01748-9103
(800) 424-EMC2
http://www.EMC.com
:
Page 2
Copyright © 1997-2003 EMC Corporation. All rights reserved.
Printed July, 2003
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.
Trademark Information
FairCom and c-tree Plus are trademarks of FairCom Corporation and are registered in the United
States and other countries.
All other trademarks used herein are the property of their respective owners.
ii
PowerPath for UNIX Installation and Administration Guide
Page 3
Contents
Preface............................................................................................................................. ix
Chapter 1 Installing PowerPath
Before You Install............................................................................. 1-2
Obtain Up-To-Date Information............................................. 1-2
Choose a Convenient Time ..................................................... 1-2
Locate Your License Key ......................................................... 1-3
Prepare the Host and Storage System ................................... 1-3
Prepare For a Clustered Environment................................... 1-5
Installing PowerPath 4.0 ................................................................. 1-6
Upgrading to PowerPath 4.0........................................................ 1-10
About Upgrading ................................................................... 1-10
Upgrading From PowerPath 3.0.x or 2.1............................. 1-11
Troubleshooting the Upgrade............................................... 1-15
After You Install ............................................................................. 1-16
Register PowerPath on the Host........................................... 1-16
Remove the CD-ROM ............................................................ 1-17
Reboot the Host....................................................................... 1-17
Verify the PowerPath Installation........................................ 1-18
Verify the PowerPath Commands Are in Your Path ......... 1-19
Verify PowerPath Devices Are Configured on the Host... 1-19
Reconfigure Applications to Use emcpower Devices ....... 1-20
Installing the PowerPath Volume Manager VCS Agent .......... 1-21
Error Messages............................................................................... 1-23
Chapter 2 PowerPath in a Cluster Environment
PowerPath in a Legato 5.1 (or later) AAM Cluster..................... 2-2
Installing PowerPath in a New AAM Cluster ...................... 2-2
PowerPath for UNIX Installation and Administration Guide
iii
Page 4
Contents
Integrating/ Upgrading PowerPath Into an Existing AAM
5.1 (or later) Cluster.................................................................. 2-3
PowerPath in a Sun Cluster 2.2 ..................................................... 2-4
Installing PowerPath in a New Sun Cluster 2.2................... 2-4
Integrating/ Upgrading PowerPath Into an Existing Sun
Cluster 2.2.................................................................................. 2-5
PowerPath in a Sun Cluster 3.0 ..................................................... 2-6
Installing PowerPath in a New Sun Cluster 3.0................... 2-6
Integrating/ Upgrading PowerPath Into an Existing Sun
Cluster 3.0.................................................................................. 2-7
PowerPath in a VERITAS Cluster Server Cluster ....................... 2-8
Installing PowerPath in a New VCS Cluster........................ 2-8
Integrating/ Upgrading PowerPath Into an Existing VCS
Cluster...................................................................................... 2-10
Configuring VCS to Recognize PowerPath Volume Manager
Resources................................................................................. 2-11
Setting Major and Minor Numbers............................................. 2-13
Chapter 3 Configuring a PowerPath Boot Device on Solaris
Introduction...................................................................................... 3-2
Configuring a PowerPath Native Device as the Boot Device ... 3-3
Partitioning the Boot Device................................................... 3-3
Creating Filesystems ................................................................ 3-4
Installing a Bootblk................................................................... 3-5
Copying Required Files........................................................... 3-5
Modifying OpenBoot ............................................................... 3-7
Setting Up the Boot Alias ........................................................ 3-7
Moving the Boot Device to an emcpower Device....................... 3-8
Recovery Procedure ................................................................. 3-9
Removing PowerPath Control Over a Boot Device.................. 3-11
Chapter 4 Removing PowerPath
Before Removing PowerPath......................................................... 4-2
Removing PowerPath ..................................................................... 4-3
Removing the PowerPath Volume Manager VCS Agent........... 4-6
Chapter 5 PowerPath Administration on Solaris
PowerPath and CLARiiON Storage Systems .............................. 5-2
Ensuring a Sufficient Stack Size..................................................... 5-2
Booting a Host With Built-In Fibre Channel Ports...................... 5-2
Rebooting and Custom Settings .................................................... 5-3
iv
PowerPath for UNIX Installation and Administration Guide
Page 5
Contents
Boot Device Support....................................................................... 5-3
R1/R2 Boot Failover Support........................................................ 5-4
R1/R2 Supported Configurations ......................................... 5-4
R1/R2 Boot Procedure ............................................................ 5-4
Device Naming................................................................................ 5-5
Native Devices.......................................................................... 5-5
Pseudo Devices......................................................................... 5-6
Selecting a Device Naming Convention............................... 5-6
Reconfiguring PowerPath Devices Online................................ 5-10
Dynamic Reconfiguration............................................................ 5-12
Adding an HBA to a PowerPath Configuration................ 5-12
Removing an HBA From a PowerPath Configuration..... 5-13
Upgrading Solaris ......................................................................... 5-15
Upgrading to Solaris 9 with Solaris Live Upgrade........... 5-15
powercf Configuration Utility..................................................... 5-17
File Location............................................................................ 5-17
Executing powercf ................................................................. 5-17
emcp.conf File......................................................................... 5-17
Syntax ...................................................................................... 5-17
Arguments .............................................................................. 5-18
Error Messages .............................................................................. 5-18
Appendix A Files Changed By PowerPath
Files Created or Modified by PowerPath Installation ............. A-2
/etc............................................................................................ A-2
/basedir/EMCpower/bin....................................................... A-3
/basedir/EMCpower/driver ................................................. A-3
/kernel/drv ............................................................................. A-5
/basedir/EMCpower/lib........................................................ A-6
/basedir/EMCpower/man/man1........................................ A-8
/basedir/EMCpower/scripts................................................. A-9
/usr/bin ................................................................................... A-9
/usr/man/man1..................................................................... A-9
Solaris Files Modified by PowerPath Installation............ A-10
Files Created or Modified by VCS Agent Installation ........... A-11
/basedir/VRTSvcs/EMC...................................................... A-11
/basedir/VRTSvcs/bin/EMCvg......................................... A-11
/etc/VRTSvcs/conf/config ................................................ A-11
/usr/lib .................................................................................. A-11
PowerPath for UNIX Installation and Administration Guide
v
Page 6
Contents
Appendix B Customer Support
Overview of Detecting and Resolving Problems ...................... B-2
Troubleshooting the Problem ....................................................... B-3
Before Calling the Customer Support Center ............................ B-4
Documenting the Problem ........................................................... B-5
Reporting a New Problem ............................................................ B-6
Sending Problem Documentation ............................................... B-7
Index................................................................................................................................ i-1
vi
PowerPath for UNIX Installation and Administration Guide
Page 7
Tables
Tables
5-1 Native Devices versus emcpower Devices ............................................... 5-8
5-2 Support for Native and Pseudo Devices ................................................... 5-9
PowerPath for UNIX Installation and Administration Guide
vii
Page 8
Tab les
viii
PowerPath for UNIX Installation and Administration Guide
Page 9
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 the PowerPath software. Therefore, some functions described in
this manual may not be supported by all versions of the PowerPath products
or the storage-system hardware they support. For the most up-to-date
information on product features, see the PowerPath release notes.
If a 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 xiii for contact information.
Audience and
Prerequisites
This guide describes the features and functionality of EMC
PowerPath
Version 4.0 .
This manual is part of the PowerPath documentation set. It is
intended for use by storage administrators and other information
system professionals responsible for using, installing, and
maintaining PowerPath.
Readers of this manual are expected to be familiar with the Solaris
operating system, storage-system management, and the applications
used with PowerPath.
PowerPath for UNIX Installation and Administration Guide
ix
Page 10
Preface
Organization Here is an overview of the information contained in this guide:
◆ Chapter 1, Installing PowerPath, describes how to install
PowerPath on a Solaris host, how to upgrade from an earlier
version of PowerPath, and how to install the PowerPath Volume
Manager VCS Agent.
◆ Chapter 2, PowerPath in a Cluster Environment, describes how to
install and configure PowerPath in Sun Cluster, Legato AAM, and
VERITAS Cluster Server environments.
◆ Chapter 3, Configuring a PowerPath Boot Device on Solaris,
describes how to configure a PowerPath device as the boot
device.
◆ Chapter 4, Removing PowerPath, describes how to remove
PowerPath from a Solaris host.
◆ Chapter 5, PowerPath Administration on Solaris, discusses Solaris
issues and administrative tasks.
◆ Appendix A, Files Changed By PowerPath, lists files that are created
or modified by PowerPath installation and upgrade.
◆ Appendix B, Customer Support, reviews the EMC process for
detecting and resolving software problems, and provides
essential questions you should answer before contacting the EMC
Customer Support Center.
x
PowerPath for UNIX Installation and Administration Guide
Page 11
Preface
Related
Documentation
Here is the complete set of PowerPath documentation; all manuals
are available from EMC Corporation:
◆ PowerPath Product Guide, EMC P/N 300-000-979
◆ PowerPath for UNIX Volume Manager User’s Guide, EMC P/N
300-000-992
◆ PowerPath for UNIX Installation and Administration Guide, EMC
P/N 300-000-978
◆ PowerPath for UNIX Quick Reference, EMC P/N 300-000-981
◆ PowerPath for UNIX Volume Manager Quick Reference, EMC P/N
300-000-982
◆ Installing and Configuring Emcpower Devices With Solaris
Applications, P/N 300-000-786 (electronic version only)
◆ EMC PowerPath Release Notes, EMC P/N 300-000-980
These documents are updated periodically. Electronic versions of
the updated manuals are available on the Powerlink website:
http://powerlink.emc.com.
Symmetrix users should also refer to the EMC Host Connectivity
Guides, which are available on the Powerlink website.
CLARiiON users should also refer to the following manuals:
◆ EMC Host Connectivity Guides
◆ EMC Installation Roadmap for CX-Series and FC-Series Storage
Systems, EMC P/N 069001166
◆ EMC ControlCenter Navisphere Manager Version 6.X Administrator’s
Guide, EMC P/N 069001125
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 UNIX Installation and Administration Guide
xi
Page 12
Preface
Conventions Used in
This Guide
!
EMC uses the following conventions for notes, cautions, warnings,
and danger notices.
A note presents information that is important, but not hazard-related.
CAUTION
A caution contains information essential to avoid damage to the
system or equipment. The caution may apply to hardware or
software.
Typographical Conventions
EMC uses the following type style conventions in this guide:
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
xii
Courier,
italic
Courier
Arguments used in examples of command line
syntax.
System prompts and displays and specific
filenames or complete paths. For example:
working root directory [/user/emc]:
c:\Program Files\EMC\Symapi\db
Courier,
bold
PowerPath for UNIX Installation and Administration Guide
◆ User entry. For example:
symmpoll -p
◆ Options in command line syntax
Page 13
Where to Get Help For questions about technical support, call your local sales office or
service provider.
If you have a valid EMC service contract, contact EMC Customer
Service at:
United States: (800) 782-4362 (SVC-4EMC)
Canada: (800) 543-4782 (543-4SVC)
Worldwide: (508) 497-7901
Follow the voice menu prompts to open a service call and select the
applicable product support.
Sales and Customer Service Contacts
For the list of EMC sales locations, please access the EMC home page
at:
http://www.emc.com/contact/
For additional information on the EMC products and services
available to customers and partners, refer to the EMC Powerlink
website at:
http://powerlink.emc.com
Preface
EMC Support Matrix
For information about products and technologies qualified for use
with the EMC software described in this manual, go to this EMC Web
page:
http://www.emc.com/horizontal/interoperability
Choose the link to EMC Interoperability Support Matrices, and 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 techpub_comments@EMC.com with your opinions of
this guide.
PowerPath for UNIX Installation and Administration Guide
xiii
Page 14
Preface
xiv
PowerPath for UNIX Installation and Administration Guide
Page 15
Invisible Body Tag
1
Installing PowerPath
This chapter describes how to install PowerPath 4.0 on a Solaris host
and how to upgrade from an earlier version of PowerPath. The
chapter also describes how to install the PowerPath Volume Manager
VCS Agent for a VERITAS Cluster Server (VCS) environment.
The PowerPath Volume Manager Legato Agent is not part of the PowerPath
4.0 package. See the appropriate Legato documentation for information on
installing and configuring that agent.
◆ Before You Install ...............................................................................1-2
◆ Installing PowerPath 4.0 ...................................................................1-6
◆ Upgrading to PowerPath 4.0..........................................................1-10
◆ After You Install ...............................................................................1-16
◆ Installing the PowerPath Volume Manager VCS Agent.............1-21
◆ Error Messages.................................................................................1-23
Installing PowerPath
1-1
Page 16
Installing PowerPath
1
Before You Install
The sequence in which you configure the storage and install
PowerPath® depends on the storage system you use:
Symmetrix
Symmetrix system. Verify that the Symmetrix system is working
properly, then install PowerPath using the instructions in this guide.
CLARiiON
part of a CLARiiON setup and configuration procedure. To properly
install PowerPath on a host with a CLARiiON 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.
The rest of this section describes what to do before you install
PowerPath on the host.
Obtain Up-To-Date Information
Check the Powerlink website (http://powerlink.emc.com) for the
most current information:
®
storage systems. Install PowerPath after you set up the
®
storage systems. PowerPath installation is an integral
Choose a Convenient Time
1-2
PowerPath for UNIX Installation and Administration Guide
❑ Release notes — We update the PowerPath release notes
periodically and post them on the Web.
❑ 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.
Installing PowerPath requires you to reboot the host. Plan to install or
upgrade PowerPath when a reboot will cause minimal disruption to
your site.
Page 17
Locate Your License Key
The PowerPath license registration key is on the License Key Card
delivered with the PowerPath media kit.
If you are upgrading from an earlier version of PowerPath, you need not
reregister; PowerPath will use your old key.
Prepare the Host and Storage System
To prepare the host and storage system:
❑ Verify that your environment meets the requirements in:
❑ Environment and System Requirements section of the EMC
PowerPath Release Notes. That section describes minimum
hardware and software requirements for the host and
supported storage systems.
❑ Chapter 3, PowerPath Configuration Requirements, in the
PowerPath Product Guide. That chapter describes the
host-storage system interconnection topologies that
PowerPath supports.
Installing PowerPath
1
❑ Set up the SCSI target and LUN or Fibre Channel port and LUN
addresses. Refer to the EMC Host Connectivity Guides or
Installation Roadmap for FC-Series Storage Systems.
In the
/etc/system file, make sure the timeout value is set to 60
seconds. This minimizes path failover time without
compromising online storage-system microcode or base code
upgrades. The entry must be a hexadecimal number:
set sd: sd_io_time = 0x3C
❑ Use the Solaris format utility to format, partition, and label the
unused storage system devices such that each unused device has
a partition 2 that occupies the entire device. Do not, however, use
or mount these devices before installing PowerPath.
Before You Install
1-3
Page 18
Installing PowerPath
1
❑ Uninstall any earlier version of PowerPath.
The PowerPath installation program exits if it detects an existing
version of PowerPath.
Important: Before you uninstall the earlier version, save your
configuration using the
documentation for the earlier version for further uninstallation
instructions.
You need not reboot the host after you uninstall the earlier version of
PowerPath. You must, however, reboot the host after you install
PowerPath 4.0.
❑ Configure HBA drivers.
CAUTION
Be sure to follow HBA 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.
powermt save command. Refer to the
1-4
❑ For hosts connected to storage arrays via a Fibre Channel switch
(that is, a fabric), configure the HBAs using persistent binding for
SCSI target IDs.
CAUTION
Failure to do so could result in loss or corruption of data.
For information about persistent binding, refer to the Host
Connectivity Guide for Sun Solaris, the HBA driver documentation,
and the
.conf file for your HBA type.
❑ Optionally, configure the host to send warnings to the console.
By default, warning messages are sent only to the log file. To see
warnings on the console:
1. Add the following line to the
localX.Warn /dev/sysmsg
where X is a value that is not used by any other local setting
in
/etc/syslog.conf.
PowerPath for UNIX Installation and Administration Guide
/etc/syslog.conf file:
Page 19
Installing PowerPath
For example:
local0.Warn /dev/sysmsg
The separator between localX.Warn and /dev/sysmsg must be a
tab character.
2. Set the RAD_LOG_FACILITY environment variable to
LOG_LOCALX, where X is the number you used in the local
setting of the
/etc/syslog.conf file.
1
For example, for
setenv RAD_LOG_FACILITY LOG_LOCAL0
For sh, enter:
RAD_LOG_FACILITY=LOG_LOCAL0; export RAD_LOG_FACILITY
Prepare For a Clustered Environment
If you are installing PowerPath in a clustered environment:
❑ Prepare the cluster environment.
Refer to Chapter 2, PowerPath in a Cluster Environment, for
information on installing PowerPath in a new or existing cluster.
❑ Find a major number that can be assigned to the PowerPath
driver,
number that is unused by any host in the cluster. The installation
will prompt you for this number.
Setting the major number is necessary only if you intend to use NFS
mounted file systems on PowerPath Volume Manager volumes in your
cluster. For more information, refer to Setting Major and Minor Numbers
on page 2-13.
To find a unique major number:
emcp, on every host in the cluster. This must be a unique
csh, enter:
1. Enter the following command on every host in the cluster:
sort -n +1 /etc/name_to_major
2. Note the highest major number on every node.
Then, when the installation prompts for a major number, use a
number that is higher than all of these.
Before You Install
1-5
Page 20
Installing PowerPath
1
Installing PowerPath 4.0
This section describes how to install, or reinstall, PowerPath 4.0 when
no earlier version of PowerPath has been installed on the host.
If you are upgrading to PowerPath 4.0 from PowerPath 3.0.x or 2.1,
refer instead to Upgrading to PowerPath 4.0 on page 1-10.
Mount the CD-ROM 1. Log in as root.
2. Insert the CD-ROM into the CD-ROM drive.
If the CD mounts automatically, continue with Install the Software,
which follows.
If the CD does not mount automatically, you must mount it
manually. Continue with step 3.
3. Mount the CD on your file system. 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:
1-6
mount -F hsfs -r /dev/dsk/c0t2d0s0 /cdrom/cdrom0
Install the Software 1. If you do not have a graphics terminal, run the script filename
command to record
pkgadd completes, use CTRL-D to stop recording the output.)
2. Change to the
pkgadd output in the specified file. (After
/
mount_point
/UNIX/SOLARIS directory. For
example, enter:
cd /cdrom/cdrom0/UNIX/SOLARIS
3. Start the installation program. Enter:
/usr/sbin/pkgadd -d .
PowerPath for UNIX Installation and Administration Guide
Page 21
Installing PowerPath
4. You see the following prompt:
The following packages are available:
1 EMCpower EMC PowerPath
2 EMCvg EMC Enterprise Cluster PowerPath Volume
Select package(s) you wish to process (or 'all' to
process all packages). (default: all) [?,??,q]:
(all) 4.0.0_bxxx
Manager VCS Agent
(sparc) 1.0
Enter 1 and press ENTER.
5. You are prompted for the directory where the PowerPath
program files will be installed:
Enter package base directory (default: /opt,?):
Press ENTER to accept the default base directory (/opt), or type the
path to an alternate base directory and press
ENTER.
1
PowerPath installs its files in /
process creates the EMCpower subdirectory. Make a note of the name and
location of the PowerPath base directory for future reference.
6. You are prompted for the directory where the log files will reside:
Enter directory for logging (default: /
Press ENTER to accept the default (/
type the path to an alternate log files directory and press
You must specify a local file system.
7. You see the following prompt:
Install for cluster environment [y,n,q,?] (default: n):
• If you are installing PowerPath on a standalone system, press
ENTER. Go to step 10.
• If you are installing PowerPath in a clustered environment,
y and press ENTER. Continue with step 8.
enter
basedir
basedir
basedir
/EMCpower; the installation
/EMCpower/log):
/EMCpower/log), or
ENTER.
Installing PowerPath 4.0
1-7
Page 22
Installing PowerPath
1
8. You are prompted for a major number that can be assigned to the
PowerPath device driver (
Assign major number for the device driver [?]:
Enter a major number and press ENTER. You must specify a major
number that is not used by any host in the cluster.
The installation will assign this major number to the PowerPath driver.
Specify this major number during PowerPath installation on every other
host in the cluster.
9. You are prompted to confirm the major number:
Major major will be assigned to the device driver [y,n,q,?] (default: y):
Press ENTER to confirm the major number.
If you have already installed PowerPath 4.0 on the host and are now
reinstalling the PowerPath 4.0 software, you see the following prompt:
Configuration for PowerPath 4.0 exists - want to upgrade
[y,n,q,?] (default: y):
emcp) on every host in the cluster:
1-8
NTER to preserve your PowerPath configuration.
Press E
Enter n and press ENTER to overwrite your PowerPath configuration.
10. You see the following prompt:
This package contains scripts which will be executed
with super-user permission during the process of
installing this package.
Do you want to continue with the installation of
<EMCpower> [y,n,?]
Enter y and press ENTER.
PowerPath for UNIX Installation and Administration Guide
Page 23
Installing PowerPath
11. The screen displays information about the installation, ending
with:
----------------------------------------------------
* EMCpower installation:
*
* Installation is successful.
*
* If you have a license key card, register now. Then
* REBOOT the host to complete the remaining steps of the
* installation. Refer to the PowerPath for UNIX
* Installation and Administration Guide for more
* information.
------------------------------------------------------
Installation of <EMCpower> was successful.
The following packages are available:
1 EMCpower EMC PowerPath
(all) 4.0.0_bxxx
2 EMCvg EMC Enterprise Cluster PowerPath Volume
Manager VCS Agent
(sparc) 1.0
Select package(s) you wish to process (or 'all' to
process all packages). (default: all) [?,??,q]:
1
• If you are installing PowerPath for a VCS cluster and you
want to install the PowerPath Volume Manager VCS Agent
now, enter
2 and press ENTER. Continue with Install the VCS
Agent Software, step 5, on page 1-22.
• Otherwise, enter
q and press ENTER.
PowerPath is now installed on the host. You must register
PowerPath, reboot the host, and perform other administrative tasks
before PowerPath can run on the host. Refer to After You Install on
page 1-16 for postinstallation information and procedures.
Installing PowerPath 4.0
1-9
Page 24
Installing PowerPath
1
Upgrading to PowerPath 4.0
This section describes how to upgrade to PowerPath 4.0 from an
earlier version of PowerPath.
About Upgrading
Uninstalling the Earlier
Ver sion
Licenses The upgrade preserves your existing PowerPath license. You need
You can upgrade to PowerPath 4.0 from the following releases:
◆ PowerPath 3.0.x
◆ PowerPath 2.1
To upgrade from PowerPath 1.5 or 2.0, you must first upgrade to PowerPath
2.1 or 3.0.x and then upgrade to PowerPath 4.0.
After upgrading from PowerPath 2.0 to PowerPath 2.1 or 3.0.x, you must
restore your configuration by running the following command:
powermt load file=/etc/powermt.custom.pre-pp2.1.0. Then
upgrade to PowerPath 4.0.
Before upgrading to PowerPath 4.0, you must uninstall the earlier
version of PowerPath. Follow the instructions in the documentation
for that version. Note, however, that you need not reboot the host after you
uninstall the earlier version.
Upgrading from PowerPath 2.1: Before you uninstall PowerPath 2.1, search
the file /etc/profile for the following string: end of additions. If you
find that string, replace it with the following string: done additions.
not reenter license information.
1-10
Configuration Files With the release of PowerPath 4.0, PowerPath configuration files
have changed in both content and number. The upgrade converts
your PowerPath 3.0.x or 2.1 configuration files to the newer formats.
The old configuration files are saved in
PowerPath for UNIX Installation and Administration Guide
/etc/emc/emcpxarchive.
Page 25
Installing PowerPath
Upgrading From PowerPath 3.0.x or 2.1
Mount the CD-ROM 1. Log in as root.
2. Insert the CD-ROM into the CD-ROM drive.
If the CD mounts automatically, continue with Install the Software,
which follows.
If the CD does not mount automatically, you must mount it
manually. Continue with step 3.
3. Mount the CD on your file system. 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
Install the Software 1. If you do not have a graphics terminal, run the script filename
command to record
pkgadd completes, use CTRL-D to stop recording the output.)
pkgadd output in the specified file. (After
1
2. Change to the
/
mount_point
/UNIX/SOLARIS directory. For
example, enter:
cd /cdrom/cdrom0/UNIX/SOLARIS
3. Start the installation program. Enter:
/usr/sbin/pkgadd -d .
4. You see the following prompt:
The following packages are available:
1 EMCpower EMC PowerPath
2 EMCvg EMC Enterprise Cluster PowerPath Volume
Select package(s) you wish to process (or 'all' to
process all packages). (default: all) [?,??,q]:
(all) 4.0.0_bxxx
Manager VCS Agent
(sparc) 1.0
Enter 1 and press ENTER.
Upgrading to PowerPath 4.0
1-11
Page 26
Installing PowerPath
1
5. You are prompted for the directory where the PowerPath
program files will be installed:
Enter package base directory (default: /opt,?):
Press ENTER to accept the default base directory (/opt), or type the
path to an alternate base directory and press
ENTER.
PowerPath installs its files in /
process creates the EMCpower subdirectory. Make a note of the name and
location of the PowerPath base directory for future reference.
6. You are prompted for the directory where the log files will reside:
Enter directory for logging (default: /
Press ENTER to accept the default (/
type the path to an alternate log files directory and press
You must specify a local file system.
7. You see the following prompt:
Install for cluster environment [y,n,q,?] (default: n):
• If you are installing PowerPath on a standalone system, press
ENTER. Go to step 10.
• If you are installing PowerPath in a clustered environment,
y and press ENTER. Continue with step 8.
enter
8. You are prompted for a major number that can be assigned to the
PowerPath device driver (
Assign major number for the device driver [?]:
emcp) on every host in the cluster:
Enter a major number and press ENTER. You must specify a major
number that is not used by any host in the cluster.
basedir
basedir
basedir
/EMCpower; the installation
/EMCpower/log):
/EMCpower/log), or
ENTER.
1-12
The installation will assign this major number to the PowerPath driver.
Specify this major number during PowerPath installation on every other
host in the cluster.
PowerPath for UNIX Installation and Administration Guide
Page 27
Installing PowerPath
9. You are prompted to confirm the major number:
Major major will be assigned to the device driver [y,n,q,?] (default: y):
Press ENTER to confirm the major number.
10. You see the following prompt:
Configuration for PowerPath version exists - want to
upgrade [y,n,q,?] (default: y):
where version is either 3.0.x or 2.x.
Press
ENTER to upgrade.
11. You see the following prompt:
This package contains scripts which will be executed
with super-user permission during the process of
installing this package.
Do you want to continue with the installation of
<EMCpower> [y,n,?]
Enter y and press ENTER.
1
Upgrading to PowerPath 4.0
1-13
Page 28
Installing PowerPath
1
12. The screen displays information about the installation. Provided
the upgrade is successful (that is, conversion of the configuration
files succeeds) the display ends with:
----------------------------------------------------------------------* EMCpower installation:
*
* Installation is successful.
*
* Please REBOOT the host to complete the remaining steps of the installation.
* Refer to the PowerPath for UNIX Installation and Administration Guide for more
* information.
-----------------------------------------------------------------------
The following packages are available:
1 EMCpower EMC PowerPath
2 EMCvg EMC Enterprise Cluster PowerPath Volume
Select package(s) you wish to process (or 'all' to
process all packages). (default: all) [?,??,q]:
(all) 4.0.0_bxxx
Manager VCS Agent
(sparc) 1.0
Important: If the display indicates that conversion of the configuration
files failed, refer to Troubleshooting the Upgrade on page 1-15.
1-14
• If you are installing PowerPath for a VCS cluster and you
want to install the PowerPath Volume Manager VCS Agent
now, enter
2 and press ENTER. Continue with Install the VCS
Agent Software, step 5, on page 1-22.
• Otherwise, enter
q and press ENTER.
PowerPath 4.0 is now installed on the host. You must reboot the host
and perform other administrative tasks before PowerPath can run on
the host. Refer to After You Install on page 1-16 for postinstallation
information and procedures.
PowerPath for UNIX Installation and Administration Guide
Page 29
Installing PowerPath
1
Troubleshooting the Upgrade
Upgrading to PowerPath 4.0 could fail for the following reasons:
◆ The PowerPath 3.0.x or 2.1 configuration files are corrupted.
◆ You inadvertently chose not to upgrade; that is, you answered n
instead of
Configuration for PowerPath version exists - want to
upgrade [y,n,q,?] (default: y):
y to the following prompt:
The following sections describe what to do under these
circumstances.
If files are corrupted
If the PowerPath 3.0.x or 2.1 configuration files are corrupted, your
custom configuration is no longer available after you install
PowerPath 4.0. If any of your applications are configured with
PowerPath pseudo devices, you must reconfigure those applications.
Refer to Installing and Configuring Emcpower Devices With Solaris
Applications, which is available on the Powerlink website
(
http://powerlink.emc.com).
If you chose not to upgrade
If you inadvertently answer no to the upgrade prompt, before you
reboot the host:
1. Run the
emcpupgrade check command to check whether upgrade
is possible. Enter:
emcpupgrade check -f /etc/emc/emcpxarchive/powermt.custom.saved
If the check fails, the upgrade cannot take place. Contact EMC
Customer Support.
If the check succeeds, continue with step 2.
2. Run the
emcpupgrade convert command to convert the
PowerPath 3.0.x or 2.1 configuration files to the PowerPath 4.0
format. Enter:
emcpupgrade convert -f /etc/emc/emcpxarchive/powermt.custom.saved
3. Run the emcpupgrade validate command to verify that the
conversion succeeded. Enter:
emcpupgrade validate
For information about the emcpupgrade utility, refer to Chapter 5 of
the PowerPath Product Guide.
Upgrading to PowerPath 4.0
1-15
Page 30
Installing PowerPath
1
After You Install
After installing the PowerPath software:
❑ Register PowerPath on the host (first-time installation only).
❑ Remove the CD-ROM.
❑ Reboot the host.
❑ Verify the PowerPath installation.
❑ Verify the PowerPath commands are in your path.
❑ Verify that PowerPath devices are configured on the host.
❑ Optionally, reconfigure applications to use emcpower devices.
The following sections describe these procedures.
Register PowerPath on the Host
If you have previously registered an earlier version of PowerPath on the host,
PowerPath will use your old key; you need not reregister. (Note, however,
that if your previous registration was for evaluation purposes, and the
registration has expired, you must reregister before you reboot the host).
To register the PowerPath software:
1. Enter:
/etc/emcpreg -install
You see the following output:
============ EMC PowerPath Registration =============
Do you have a new registration key or keys to enter? [n]
2. Type y and press ENTER.
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):
1-16
PowerPath for UNIX Installation and Administration Guide
Page 31
Installing PowerPath
3. Enter the PowerPath registration key and press ENTER.
If you entered a valid key, you see the following output:
1 key(s) successfully added.
Key successfully installed.
Key (Enter if done):
4. Press ENTER. You see the following output:
1 key(s) successfully registered.
Registering PowerPath after you install the software and before you reboot
the host sets the appropriate default load balancing and failover policy. If you
reboot the host before you register PowerPath, you must run the
powermt set policy to reset the load balancing and failover policy. Refer
to the PowerPath Product Guide or the powermt(1) man page for more
information on powermt set policy.
1
Remove the CD-ROM
Reboot the Host
1. If the CD-ROM volume management daemon vold is running,
unmount and eject the CD-ROM. Enter:
eject
and remove it from the drive.
2. If
vold is not running, unmount the CD-ROM. For example,
enter:
umount /cdrom/cdrom0
and, after the CD-ROM unmounts, eject it and remove it from the
drive.
Reboot the host. Enter:
reboot -- -r
Registering PowerPath after you install the software and before you reboot
the host sets the appropriate default load balancing and failover policy. (Refer
to Register PowerPath on the Host on page 1-16.) If you reboot the host before
you register PowerPath, you must run the powermt set policy to reset the
load balancing and failover policy. Refer to the PowerPath Product Guide or the
powermt(1) man page for more information on powermt set policy.
After You Install
1-17
Page 32
Installing PowerPath
1
Verify the PowerPath Installation
1. Verify that PowerPath is installed properly on the host. Enter:
pkginfo -l EMCpower
You should see output like the following:
PKGINST: EMCpower
NAME: EMC PowerPath
CATEGORY: system
ARCH: sparc
VERSION: 4.0.0_bxxx
BASEDIR: /opt
VENDOR: EMC
PSTAMP: cambridge951018123443
INSTDATE: Mar 14 2003 08:36
STATUS: completely installed
FILES: 292 installed pathnames
2. If you installed the PowerPath Volume Manager VCS Agent,
verify that the agent is installed properly on the host. Enter:
5 shared pathnames
17 directories
139 executables
137622 blocks used (approx)
1-18
pkginfo -l EMCvg
You should see output similar to this:
PKGINST: EMCvg
NAME: EMC Enterprise Cluster PowerPath Volume Manager VCS Agent
CATEGORY: system
ARCH: sparc
VERSION: 1.0
VENDOR: EMC Corporation
DESC: EMC Enterprise Cluster PowerPath Volume Manager VCS Agent
PSTAMP: 1.0 EMC: 1.0.0.xxx
INSTDATE: Nov 20 2002 15:31
EMAIL: support@emc.com
STATUS: completely installed
FILES: 29 installed pathnames
8 shared pathnames
14 directories
10 executables
273 blocks used (approx)
PowerPath for UNIX Installation and Administration Guide
Page 33
Installing PowerPath
3. Verify that the PowerPath and PowerPath Volume Manager
kernel extensions are loaded on the host. Enter:
modinfo | grep -i emc
You should see output like the following:
30 125c08b 74a05 255 1 emcp (PP Driver 4.0.0)
31 127ec94 18c1e - 1 emcpmp (PP MP Ext 4.0.0)
32 1295a42 21ac2 - 1 emcpmpc (PP MPC Ext 4.0.0)
33 12b4f4c c905c - 1 emcpsapi (PP SAPI Ext 4.0.0)
34 134f510 11e1d - 1 emcpcg (PP CG Ext 4.0.0)
35 13608a5 2410 - 1 emcphr (PP HR Ext 4.0.0)
36 136276d 46bc6 - 1 emcpsm (PV SM Ext 4.0.0)
39 13a4aa9 5b8b4 - 1 emcpsc (PV SC Ext 4.0.0)
40 7816a000 5461f - 1 emcpevm (PV EVM Ext 4.0.0)
41 13e957d 22acd - 1 emcpdpm (PV DPM Ext 4.0.0)
42 7811b2e6 273 - 1 emcpioc (PP PIOC 4.0.0)
1
Verify the Powe rPa th Commands Are in Your Pa th
Verify PowerPath Devices Are Configured on the Host
Pseudo name=emcpower0a
Symmetrix ID=000000003269;
Logical device ID=048
state=alive; policy=SymmOpt; priority=0; queued-IOs=0
===================================================================
------------ Hosts ----------- - Sys - - I/O Paths - --- Stats ---### HW Path I/0 Path Interf. Mode State Q-IOs Errors
===================================================================
2300 sbus@f/QLGC,isp@2 c2t1d0 SA 16aB active alive 0 0
2301 sbus@f/QLGC,isp@2 c1t1d0 SA 16aA active alive 0 0
2302 sbus@f/QLGC,isp@2 c3t1d0 SA 16bB active alive 0 0
Check that the PowerPath commands are in your path. PowerPath
installation modifies the
the PowerPath setup scripts, which modify the
LD_LIBRARY_PATH, LD_LIBRARY_PATH_64, and MANPATH variables on
/etc/profile and /etc/.login files to run
PATH,
the host.
If you find that the PowerPath commands are not in your path, check
the
/.profile, /.login, and /.cshrc scripts to see if they are
overwriting the changes made by the PowerPath setup scripts.
To verify that PowerPath devices are configured on the host:
1. Enter:
powermt display dev=all
You should see output like the following:
After You Install
1-19
Page 34
Installing PowerPath
1
2. If the output of powermt display dev=all indicates that some
storage system logical devices are not configured as PowerPath
devices:
a. Configure any missing logical devices. Enter:
powercf -q
powermt config
b. Rerun powermt display dev=all to confirm that
– These logical devices are configured as emcpower devices.
– The correct failover and load balancing policy is set. (For
information about
see the PowerPath Product Guide.)
If you plan to enable R1/R2 boot disk failover, see R1/R2 Boot
Failover Support on page 5-4.
c. If the failover and load balancing policy is not set correctly,
run the command
applies to your storage systems.
powermt and load-balancing policies,
powermt set policy, setting the policy that
Reconfigure Applications to Use emcpower Devices
1-20
PowerPath for UNIX Installation and Administration Guide
If you plan to use native names (recommended) with a volume
manager, file system application, or database manager, you can
ignore this section. PowerPath load balancing and failover
functionality are enabled with no further action on your part.
However, if you plan to use emcpower devices with a third-party
volume manager, file system application, or database manager,
you must reconfigure the application to use emcpower devices.
Refer to Installing and Configuring Emcpower Devices With Solaris
Applications, which is available on the Powerlink website
(
http://powerlink.emc.com).
For more information on native and pseudo names, refer to Device
Naming on page 5-5. If you are unsure whether to use emcpower or
native names, contact the EMC Customer Support Center.
Page 35
Installing the PowerPath Volume Manager VCS Agent
You can install the VCS Agent at the time you install PowerPath, or
you can install the agent separately. This section describes how to
install the agent separately.
Mount the CD-ROM 1. Log in as root.
2. Insert the CD-ROM into the CD-ROM drive.
If the CD mounts automatically, continue with Install the Software,
which follows.
If the CD does not mount automatically, you must mount it
manually. Continue with step 3.
3. Mount the CD on your file system. 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
Installing PowerPath
1
Install the VCS Agent
Software
1. If you do not have a graphics terminal, run the script filename
command to record
pkgadd completes, use CTRL-D to stop recording the output.)
2. Change to the
pkgadd output in the specified file. (After
/
mount_point
/UNIX/SOLARIS directory. For
example, enter:
cd /cdrom/cdrom0/UNIX/SOLARIS
3. Start the installation program. Enter:
/usr/sbin/pkgadd -d .
Installing the PowerPath Volume Manager VCS Agent
1-21
Page 36
Installing PowerPath
1
4. You see the following prompt:
The following packages are available:
1 EMCpower EMC PowerPath
2 EMCvg EMC Enterprise Cluster PowerPath Volume
Select package(s) you wish to process (or 'all' to
process all packages). (default: all) [?,??,q]:
Enter 2 and press ENTER.
5. The installation program displays the following prompt if it
detects files on the host that conflict with files it will install:
Do you want to install these conflicting files [y, n, ?, q]
Enter y and press ENTER.
6. The screen displays information about the installation, ending
with the following prompt:
Installation of <EMCvg> was successful.
The following packages are available:
1 EMCpower EMC PowerPath
2 EMCvg EMC Enterprise Cluster PowerPath Volume
Select package(s) you wish to process (or 'all' to
process all packages). (default: all) [?,??,q]:
(all) 4.0.0_bxxx
Manager VCS Agent
(sparc) 1.0
(all) 4.0.0_bxxx
Manager VCS Agent
(sparc) 1.0
1-22
7. Enter q and press ENTER.
The PowerPath Volume Manager VCS Agent is now installed on the
host.
PowerPath for UNIX Installation and Administration Guide
Page 37
To verify that the agent is installed properly on the host, enter:
pkginfo -l EMCvg
You should output similar to this:
PKGINST: EMCvg
NAME: EMC Enterprise Cluster PowerPath Volume Manager VCS Agent
CATEGORY: system
ARCH: sparc
VERSION: 1.0
VENDOR: EMC Corporation
DESC: EMC Enterprise Cluster PowerPath Volume Manager VCS Agent
PSTAMP: 1.0 EMC: 1.0.0.xxx
INSTDATE: Nov 20 2002 15:31
EMAIL: support@emc.com
STATUS: completely installed
FILES: 29 installed pathnames
8 shared pathnames
14 directories
10 executables
273 blocks used (approx)
Refer to Configuring VCS to Recognize PowerPath Volume Manager
Resources on page 2-11, for information on configuring the agent.
Installing PowerPath
1
Error Messages
Error, warning, and informational messages returned by the
PowerPath installation process are described in the PowerPath Product
Guide, Chapter 6, PowerPath Messages.
Error Messages
1-23
Page 38
Installing PowerPath
1
1-24
PowerPath for UNIX Installation and Administration Guide
Page 39
Invisible Body Tag
2
PowerPath in a Cluster
Environment
This chapter describes how to install and configure PowerPath in
Solaris cluster environments. For more general information on
clustering, refer to the Symmetrix High Availability Environment
Product Guide or the Installation Roadmap for FC-Series Storage Systems.
PowerPath Volume Manager is currently supported in Legato Automated
Availability Manager (AAM) and VERITAS Cluster Server (VCS) clusters
only.
◆ PowerPath in a Legato 5.1 (or later) AAM Cluster .......................2-2
◆ PowerPath in a Sun Cluster 2.2........................................................2-4
◆ PowerPath in a Sun Cluster 3.0........................................................2-6
◆ PowerPath in a VERITAS Cluster Server Cluster..........................2-8
◆ Setting Major and Minor Numbers ...............................................2-13
PowerPath in a Cluster Environment
2-1
Page 40
PowerPath in a Cluster Environment
2
PowerPath in a Legato 5.1 (or later) AAM Cluster
This section describes how to:
◆ Install PowerPath and Legato Automated Availability Manager
(AAM) in a new cluster, that is, where neither the PowerPath nor
the AAM software is installed on any host to be included in the
cluster.
◆ Integrate PowerPath into an existing AAM cluster.
Installing PowerPath in a New AAM Cluster
To install and configure PowerPath and AAM 5.1 (or later) when
neither PowerPath nor AAM is installed:
1. Prepare the cluster environment. Refer to the EMC Host
Connectivity Guides or the Installation Roadmap for FC-Series Storage
Systems and the relevant AAM documentation.
2. Use the Solaris
format utility to verify that all storage system
devices are seen by each host.
3. Install PowerPath on all nodes. Refer to Chapter 1, Installing
PowerPath.
4. Install AAM 5.1 (or later) on all nodes. Refer to the relevant AAM
documentation.
5. Add PowerPath Volume Manager resources to AAM resource
groups. Refer to the relevant AAM documentation.
6. If the AAM agent is not already started, start the agent on each
node in the cluster, using either the
ft_startup command or the
Management Console.
7. Verify that the resource group is up and running, and use either
the
ftcli command ListResourceGroups or the Management
Console to verify that the resource group can fail over to all nodes
in the cluster.
8. Set a common minor number for every PowerPath Volume
Manager volume in the cluster. Refer to Setting Major and Minor
Numbers on page 2-13 for information on setting the minor
number.
2-2
PowerPath for UNIX Installation and Administration Guide
Page 41
PowerPath in a Cluster Environment
Integrating/ Upgrading PowerPath Into an Existing AAM 5.1 (or later) Cluster
To integrate PowerPath into an existing AAM 5.1 (or later) cluster,
follow these steps on each cluster node, one node at a time:
2
1. Stop cluster services on the node using either the
ft_shutdown
command or the Management Console.
2. Install or upgrade PowerPath on the node. Refer to Chapter 1,
Installing PowerPath.
3. Start cluster services on the node using either the
ft_startup
command or the Management Console, and wait for the node to
be fully reintegrated into the cluster.
PowerPath in a Legato 5.1 (or later) AAM Cluster
2-3
Page 42
PowerPath in a Cluster Environment
2
PowerPath in a Sun Cluster 2.2
This section describes how to:
◆ Install PowerPath and Sun Cluster 2.2 in a new cluster, that is,
where neither the PowerPath nor the Sun Cluster 2.2 software is
installed on any host to be included in the cluster.
◆ Integrate PowerPath into an existing Sun Cluster 2.2 cluster.
Installing PowerPath
in a New Sun Cluster
2.2
To install and configure PowerPath and Sun Cluster 2.2 when neither
PowerPath nor Sun Cluster 2.2 is installed:
1. Prepare the cluster environment. Refer to the EMC Host
Connectivity Guides or the Installation Roadmap for FC-Series Storage
Systems and the relevant Sun Cluster documentation.
Make sure VxVM DMP is disabled. (Refer to Installing and Configuring
emcpower Devices with Solaris Applications, available on the Powerlink
website.)
2. Use the Solaris format utility to verify that all storage system
devices are seen by each host.
3. Install PowerPath on all nodes. Refer to Chapter 1, Installing
PowerPath.
4. Install Sun Cluster 2.2 on all nodes. Refer to the relevant Sun
Cluster documentation.
5. If necessary, configure the quorum device on all nodes.
You cannot use a VCMDB device as the quorum device.
6. Initialize the root disk group on all nodes.
7. Initialize PowerPath devices on all nodes.
2-4
8. Start cluster services on the master node.
9. Designate/create shared disk groups on the master node.
10. Create logical volumes from the designated shared disks.
11. Create a logical host.
12. Start cluster services on the other (non-master) nodes.
PowerPath for UNIX Installation and Administration Guide
Page 43
PowerPath in a Cluster Environment
Integrating/ Upgrading PowerPath Into an Existing Sun Cluster 2.2
To integrate PowerPath into an existing Sun Cluster 2.2, follow these
steps on each cluster node, one node at a time:
2
1. Stop cluster services on the node using the
scadmin stopnode
command.
2. Make sure VxVM DMP is disabled.
3. Install or upgrade PowerPath on the node. Refer to Chapter 1,
Installing PowerPath.
4. Start cluster services on the node using the
scadmin startnode
command, and wait for the node to be fully reintegrated into the
cluster.
PowerPath in a Sun Cluster 2.2
2-5
Page 44
PowerPath in a Cluster Environment
2
PowerPath in a Sun Cluster 3.0
This section describes how to:
◆ Install PowerPath and Sun Cluster 3.0 in a new cluster, that is,
where neither the PowerPath nor the Sun Cluster 3.0 software is
installed on any host to be included in the cluster.
◆ Integrate PowerPath into an existing Sun Cluster 3.0 cluster.
Installing PowerPath
in a New Sun Cluster
3.0
To install and configure PowerPath and Sun Cluster 3.0 when neither
PowerPath nor Sun Cluster 3.0 is installed:
1. Prepare the cluster environment. Refer to the EMC Host
Connectivity Guides or the Installation Roadmap for FC-Series Storage
Systems and the relevant Sun Cluster documentation.
2. Install PowerPath on all nodes. Refer to Chapter 1, Installing
PowerPath.
3. Install Sun Cluster 3.0 on all nodes. Refer to the relevant Sun
Cluster documentation.
4. Configure the quorum device on all nodes.
You cannot use gatekeepers and VCMDB devices as quorum devices.
5. Initialize the root disk group on all nodes.
6. Initialize PowerPath devices on all nodes.
7. Start cluster services on the master node.
8. Designate/create shared disk groups on the master node.
9. Create logical volumes from the designated shared disks.
10. Register the disk group.
2-6
11. Start cluster services on the other (non-master) nodes.
PowerPath for UNIX Installation and Administration Guide
Page 45
PowerPath in a Cluster Environment
Integrating/ Upgrading PowerPath Into an Existing Sun Cluster 3.0
To integrate PowerPath into an existing Sun Cluster 3.0, follow these
steps on each cluster node, one node at a time.
1. Stop cluster services on the node. Enter:
boot -x
2. Install or upgrade PowerPath on the node. Refer to Chapter 1,
Installing PowerPath.
3. Start cluster services on the node. Enter:
reboot
Wait for the node to be fully reintegrated into the cluster before
proceeding to the next node.
2
PowerPath in a Sun Cluster 3.0
2-7
Page 46
PowerPath in a Cluster Environment
2
PowerPath in a VERITAS Cluster Server Cluster
This section describes how to:
◆ Install PowerPath and VCS in a new cluster, that is, where neither
the PowerPath nor the VCS software is installed on any host to be
included in the cluster.
◆ Integrate PowerPath into an existing VCS cluster.
Installing PowerPath in a New VCS Cluster
For new installations of VxVM, use native
initialize emcpower devices for VxVM using
c#t#d# devices. Do not
powervxvm.
If emcpower devices already exist in a VxVM disk group that is being
added as a resource group to VCS, those devices should remain in the
disk group as emcpower devices for as long as they comprise active
VxVM logical volumes.
To install PowerPath and VCS when neither PowerPath nor VCS is
installed on any host:
1. On each host to be included in the cluster:
a. Prepare the cluster hardware, making the necessary
networking and disk connections among the hosts and the
storage system. Refer to the EMC Host Connectivity Guides or
the Installation Roadmap for FC-Series Storage Systems and the
relevant VERITAS Cluster Server documentation for more
information.
b. Use the Solaris
format utility to verify that all storage system
devices are seen by each host.
c. Install PowerPath and, if you are using PowerPath Volume
Manager in the cluster, the PowerPath Volume Manager VCS
Agent. Refer to Chapter 1, Installing PowerPath. Verify that
PowerPath can see all the devices.
2-8
d. Install any applications.
e. Install the VCS software, following the installation procedure
described in the relevant VERITAS Cluster Server
documentation. Initially configure VCS to run without a
service group.
If you are using PowerPath Volume Manager in the cluster,
proceed with step 2. If you are not using PowerPath Volume
Manager, go to step 3.
PowerPath for UNIX Installation and Administration Guide
Page 47
PowerPath in a Cluster Environment
2. If you are using PowerPath Volume Manager, configure VCS to
recognize the PowerPath Volume Manager VCS Agent as a
resource type by editing the
/etc/VRTSvcs/conf/config/main.cf file on one host in the
cluster. Refer to Configuring VCS to Recognize PowerPath Volume
Manager Resources on page 2-11.
3. On each node in the cluster, define the resources (for example,
PowerPath Volume Manager volume groups or VxVM volumes)
that make up the service group. (You will configure the service
group in step 4.)
4. On one host in the cluster (if you are using PowerPath Volume
Manager in the cluster, this should be the host where you edited
main.cf in step 2; otherwise, this can be any host):
a. Configure the service group by adding the resources you
defined in step 3 to the
/etc/VRTSvcs/conf/config/main.cf
file. The disk or logical device resources should use native
c#t#d# devices.
Using a disk for service group heartbeat instead of a network is
subject to restrictions. Not all disks can be used. Consult the
VERITAS documentation.
2
b. Start cluster services on the host.
c. If you are using PowerPath Volume Manager, verify that VCS
recognizes the PowerPath Volume Manager VCS Agent as a
resource type. Enter:
hatype -list | grep EMC
EMCvg should be listed in the command output.
5. Start cluster services on each remaining node in the cluster. These
hosts rebuild their local configuration files from the
main.cf file
you edited in step 4.a.
PowerPath in a VERITAS Cluster Server Cluster
2-9
Page 48
PowerPath in a Cluster Environment
2
6. On each node in the cluster:
a. Verify that the service group is up and running, and use either
the VCS GUI or the
group can successfully fail over to all hosts in the cluster.
b. Set a common minor number for every PowerPath Volume
Manager volume in the cluster. Refer to Setting Major and
Minor Numbers on page 2-13 for information on setting the
minor number.
c. Add other service groups as needed.
hagrp command to verify that the service
Integrating/ Upgrading PowerPath Into an Existing VCS Cluster
To integrate PowerPath into an existing VCS cluster:
1. On each node in the cluster, stop cluster services on the node
using the
hastop -local -evacuate command.
2. On each node in the cluster, install or upgrade PowerPath on the
node, and, if you are using PowerPath Volume Manager, install
the PowerPath Volume Manager VCS Agent. Refer to Chapter 1,
Installing PowerPath.
3. If you are using PowerPath Volume Manager, configure VCS to
recognize the PowerPath Volume Manager VCS Agent as a
resource type by editing the
/etc/VRTSvcs/conf/config/main.cf file on one node in the
cluster. Refer to Configuring VCS to Recognize PowerPath Volume
Manager Resources on page 2-11.
4. Use the
where you changed the
hastart command to start cluster services on the node
main.cf file, and wait for the node to be
fully reintegrated into the cluster.
5. Use
hastart to start the remaining nodes in the cluster, waiting
for each node to be fully integrated into the cluster before running
hastart on the next node.
2-10
PowerPath for UNIX Installation and Administration Guide
Page 49
PowerPath in a Cluster Environment
2
Configuring VCS to Recognize PowerPath Volume Manager Resources
Figure 2-1 EMCvg Resource Type Definition
After the PowerPath Volume Manager VCS Agent has been installed
on a host, you must configure VCS to recognize the agent. To do so,
edit the VCS configuration file,
main.cf, to include the EMCTypes.cf
file.
The
EMCTypes.cf file, which is installed on the host during
installation of the PowerPath Volume Manager VCS Agent, defines
the
EMCvg resource type. The EMCvg resource type describes a
PowerPath Volume Manager volume group to VCS.
Figure 2-1 shows the definition of the
type EMCvg (
static int NumThreads = 1
static int OnlineRetryLimit = 5
static int OnlineTimeout = 300
static str ArgList[] = { VgName, OpenOption, VgRename,
VgNewName, RemovePath, StorageElements, VolumeNames}
NameRule = rad_ + "$symdg_name"
str VgName
str OpenOption = RW
str VgRename
str VgNewName
str RemovePath
str StorageElements[]
str VolumeNames[]
)
EMCvg resource type.
Refer to the PowerPath for UNIX Volume Manager User’s Guide for a
description of the attributes in the
EMC recommends that you leave the OnlineTimeout parameter for VERITAS
Cluster Server (VCS) at the default value, 300 seconds. If the volume groups
configured as EMCvg resources contain more than approximately 500
volumes, set OnlineTimeout to 600 seconds.
These values are guidelines only. The threshold for increasing the value of the
OnlineTimeout parameter is highly configuration dependent, influenced
primarily by the structure of the volumes. Experiment with different values
to determine the optimal settings for your configuration.
PowerPath in a VERITAS Cluster Server Cluster
EMCvg resource type.
2-11
Page 50
PowerPath in a Cluster Environment
2
Editing main.cf to
Include EMCTypes.cf
Edit the /etc/VRTSvcs/conf/config/main.cf file on one node. The
changes are propagated to the other nodes in the cluster when you
start VCS on those nodes.
You do not need to perform this procedure if GeoSpan 2.0 is installed on the
host.
To edi t the main.cf file:
1. Verify that the PowerPath Volume Manager VCS Agent is
installed on the host. Enter:
pkginfo -l EMCvg
2. Save the current /etc/VRTSvcs/conf/config/main.cf file to a
backup location. For example, enter:
cp /etc/VRTSvcs/conf/config/main.cf /etc/VRTSvcs/conf/config/main.cf.orig
3. Add the following line to the beginning of
/etc/VRTSvcs/conf/config/main.cf:
include "EMCTypes.cf"
4. Verify that there are no errors in the edited main.cf file. Enter:
hacf -verify config
If the verification is successful, no output is displayed. Otherwise,
note the error and correct it in the
main.cf file.
2-12
PowerPath for UNIX Installation and Administration Guide
Page 51
Setting Major and Minor Numbers
With NFS in a cluster environment:
◆ The PowerPath driver, emcp, must use the same major number on
every node in the cluster.
◆ Every PowerPath Volume Manager volume in the cluster must
use the same minor number on every node in the cluster.
Otherwise, you may need to restart NFS clients when failover or
failback occurs.
PowerPath in a Cluster Environment
2
Setting a Common
Major number
Setting a Common
Minor Number
You set a common major number for every host in the cluster during
PowerPath installation (refer to Chapter 1, Installing PowerPath).
Minor numbers are assigned as follows:
◆ When you create a PowerPath Volume Manager volume, a minor
number is assigned to that volume on the host where the volume
is created.
◆ When you then test failover on the nodes in the cluster, a minor
number is established for every failover host in the cluster.
After you test failover, and before you start to use the new volume,
you must ensure that the volume has the same minor number on
every node in the cluster. To do so, use the following procedure:
The commands in this procedure work whether the volume is imported or
deported. Note, however, that deports must be done without using the
-removePaths option.
1. On each node in the cluster, run the powervol getminor
command to determine the minor number assigned to the
volume on that node. Refer to the
information on
powervol getminor.
2. If step 1 reveals inconsistent minor numbers, use the
powervol(1) man page for
emcpminor
command to find one minor number that can be used for the
volume on every host. Refer to the
information on
emcpminor.
emcpminor(1) man page for
While running emcpminor, avoid running any other commands that
might claim minor numbers.
Setting Major and Minor Numbers
2-13
Page 52
PowerPath in a Cluster Environment
2
3. On every node in the cluster (except any node that is already
using the minor number), run the
to set the minor number you chose in step 2. Refer to the
powervol(1) man page for information on powervol setminor.
The powervol setminor command fails if the volume is open for I/O.
It also fails if the minor number is in use, unless you specify the
-autoselect option.
powervol setminor command
2-14
PowerPath for UNIX Installation and Administration Guide
Page 53
Invisible Body Tag
3
Configuring a
PowerPath Boot Device
on Solaris
This chapter describes how to configure a PowerPath device as the
boot device for a Solaris host and how to remove PowerPath control
over a storage system boot device.
◆ Introduction ........................................................................................3-2
◆ Configuring a PowerPath Native Device as the Boot Device......3-3
◆ Moving the Boot Device to an emcpower Device .........................3-8
◆ Removing PowerPath Control Over a Boot Device ....................3-11
Configuring a PowerPath Boot Device on Solaris
3-1
Page 54
Configuring a PowerPath Boot Device on Solaris
3
Introduction
On some storage systems, you can use either a PowerPath native
device or an emcpower device as a boot device—the device that
contains the startup image. (Refer to the EMC Support Matrix to see
whether your storage system supports PowerPath boot devices.)
Once the root is mounted, using a PowerPath device as the boot
device provides load balancing and path failover for the boot device.
Native devices, however, do not provide boot time boot path failover.
The HBA on the emcpower device must support booting in FCODE.
Examples are the Sun Fast-Wide-Differential adapter and Ultra-SCSI adapter.
The following sections describe how to configure a PowerPath native
device as the boot device and then move the boot device to an
emcpower device.
3-2
PowerPath for UNIX Installation and Administration Guide
Page 55
Configuring a PowerPath Boot Device on Solaris
Configuring a PowerPath Native Device as the Boot Device
3
Partitioning the Boot Device
Partition the boot device.
1. Use the
format command to verify that the sizes of the partitions
on the storage system device chosen for the Solaris installation are
large enough to copy the current OS partitions. Examine the
partitions of the host source drive where the current OS resides:
a. At the
b. When prompted choose disk 0, press
c. At the
d. At the
%> prompt, enter format and press ENTER.
ENTER.
format> prompt, enter partition and press ENTER.
partition> prompt, enter print and press ENTER.
Sample output:
Part Tag Flag
0
1
2 backup um
3 unassigned wm
4 unassigned wm
5 unassigned wm
6 usr wm
7 home wm
root wm
swap wm
Cylinders Size
0-335 24.69 MB
336-792 1169.59 MB
0-5846 2.12GB
0
0
0
739-2305 561.40 MB
2306-5846
1.28GB
0
0
0
2. Select the storage system device on which to install the Solaris
operating system as follows:
a. At the
partition prompt, enter quit and press ENTER to return
to the format menu.
b. At the
format prompt, enter disk and press ENTER.
Configuring a PowerPath Native Device as the Boot Device
3-3
Page 56
Configuring a PowerPath Boot Device on Solaris
3
Information similar to the following is displayed:
AVAILABLE SELECTIONS
...
1. c0t0d0 <SUN4,2G cyl 3880 alt 2 hd 16 sec 135>
/pci@1f,4000/scsi@3/sd@0,0
2. c3t0d0 <EMC-SYMMETRIX-5265 cyl 4088 alt 2 hd 15 sec
64> /pci@1f,4000/QLGC,qla@4/sd@0,0
...
specify disk (enter its number):
c. Enter 2 and press ENTER.
3. Repartition the storage system device (if necessary) to model the
partition information from the host source drive in order to match
the drive configuration:
Creating Filesystems
a. At the
b. At the
format prompt, enter partition and press ENTER.
partition prompt, enter modify and press ENTER.
c. After the partition in the storage system device has been
created, enter
modify and press ENTER at the format prompt.
d. Verify that the partition size allocated is greater than or equal
to the size you specified.
Create filesystems on the required partitions in the designated
storage system boot device.
The following example shows a subset of the filesystems you would
create when copying the OS to a Symmetrix device of Target 0 LUN 0
on controller 3:
newfs /dev/rdsk/c3t0d0s0
newfs /dev/rdsk/c3t0d0s6
newfs /dev/rdsk/c3t0d0s7
To use a different storage system device, change t0d0 to
tStorage_Device_target_numberdLUN_number. To use a different
controller, change
root partition (slice 0) and the
create other partitions (
current layout. Use the
c3 to ccontroller_number. You must create both the
/usr partition (slice 6). You should also
/export/home, /var, /opt) to mirror the
newfs command to create the filesystems.
3-4
PowerPath for UNIX Installation and Administration Guide
Page 57
Configuring a PowerPath Boot Device on Solaris
3
Installing a Bootblk
Install a bootblk (the information required by the host to boot the
operating system) on the root partition of the storage system boot
device.
1. Use the
workstation. This determines the directory in
uname -a command to determine the architecture of the
/usr/platform
where the bootblk will be found. The following example shows
sun4u as the architecture, and subdirectory for /usr/platform.
Example: At the
%> prompt, enter uname -a and press ENTER to
display a line similar to the following:
SunOS patriot 5.8 Generic_108528-15 sun4u Sparc SUNW,Ultra-60
2. At the %> prompt, enter a command like the following to install a
bootblk onto the storage system boot device:
/usr/sbin/installboot /usr/platform/sun4u/lib/fs/ufs/bootblk\
/dev/rdsk/ccontroller_numbertstorage_system_device_target_numberd0s0
For example, enter the following command to install a bootblk onto a
boot device of Target 0 LUN 0 on controller 3:
/usr/sbin/installboot /usr/platform/sun4u/lib/fs/ufs/bootblk /dev/rdsk/c3t0d0s0
Copying Required Files
Use ufsdump and ufsrestore to copy the required files and
directories from the host source drive to the storage system boot
device.
1. At the
2. Use the
%> prompt, enter mount /dev/dsk/c3t0d0s0 /mnt and
press
ENTER to mount the root directory of the storage system
device to
/mnt.
ufsdump command to create the required directory
structure on the new storage system device and copy the files.
In the following example, the current operating system is located
on
/dev/dsk/c0t0d0.
Example: At the
press
ENTER:
ufsdump 0f - /dev/dsk/c0t0d0s0 |( cd /mnt; ufsrestore rf - )
%> prompt, enter the following command and
When the above command completes, the storage system device
(c3t0d0s0) will have the complete image of the root partition.
Configuring a PowerPath Native Device as the Boot Device
3-5
Page 58
Configuring a PowerPath Boot Device on Solaris
3
3. In the /mnt/etc directory update the vfstab file to indicate the
storage system boot device address to be mounted during boot.
Modify all partitions that will be located on the storage system
boot device.
a. At the
b. At the
%> prompt, enter cd /mnt/etc and press ENTER.
%> prompt, enter vi vfstab and press ENTER.
Example — Before modification:
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
/dev/dsk/c0t0d0s1 - - swap - no /dev/dsk/c0t0d0s0 /dev/rdsk/c0t0d0s0 / ufs 1 no /dev/dsk/c0t0d0s6 /dev/rdsk/c0t0d0s6 /usr ufs 1 no swap - /tmp tmpfs - yes -
Example — After modification:
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
#
/dev/dsk/c3t0d0s1 - - swap - no /dev/dsk/c3t0d0s0 /dev/rdsk/c3t0d0s0 / ufs 1 no /dev/dsk/c3t0d0s6 /dev/rdsk/c3t0d0s6 /usr ufs 1 no swap - /tmp tmpfs - yes -
To increase system performance, you can leave the swap partition on the
internal boot drive by leaving the fourth line
(/dev/dsk/c0t0d0s1 - - swap- no -) unchanged.
4. At the %> prompt, enter umount /mnt and press ENTER to unmount
the root partition.
3-6
5. Repeat steps 1, 2, and 4 for the
directory:
a. At the
b. At the
ufsdump 0f - /dev/dsk/c0t0d0s6 | ( cd /mnt; ufsrestore rf -)
%> prompt, enter mount /dev/dsk/c3t0d0s6 /mnt and
press
ENTER.
%> prompt, enter the following command and press
ENTER:
c. At the %> prompt, enter umount /mnt and press ENTER.
6. Repeat steps 1, 2, and 4 for any other partitions to be mounted
from the storage system boot device.
PowerPath for UNIX Installation and Administration Guide
/usr partition. In the current root
Page 59
Configuring a PowerPath Boot Device on Solaris
3
Modifying OpenBoot
If you use Refer to
Emulex HBAs
QLogic HBAs
JNI HBAs
EMC Fibre Channel with Emulex Host Bus Adapters in the Solaris Host Environment
http://emulex.com/ts/docoem/emc/pdfs/Sol_501a.pdf
EMC Fibre Channel with QLogic Host Bus Adapters in the Solaris Environment
http://download.qlogic.com/drivers/5419/QLogic_Solaris.pdf
EMC Symmetrix Fibre Channel with JNI Emerald Host Bus Adapters in the Solaris Environment
http://www.jni.com/Drivers/Files/Solaris/FCE2-6412/emc/JNI_Em_Solaris.pdf
EMC Symmetrix Fibre Channel with JNI Tachyon Host Bus Adapters in the Solaris Environment
http://www.jni.com/Drivers/Files/Solaris/FC64-1063/emc/JNI_Tach_Solaris.pdf
EMC Symmetrix Fibre Channel with JNI Emerald 4 Host Bus Adapters in the Solaris Environment
http://www.jni.com/Drivers/Files/Solaris/FCX2-6562/emc/JNI_Em4_Solaris.pdf
Setting Up the Boot Alias
You need modify OpenBoot only if you use Fibre Channel HBAs.
The procedure for modifying OpenBoot depends on your HBAs.
Refer to the following documentation:
Set up a new alias for your new boot disk. At the OK> prompt:
1. Enter
nvalias your_alias your_device and press ENTER.
Example:
nvalias storagedisk /pci@1f,4000/QLGC,qla@4/sd@0,0
2. Enter nvstore and press ENTER to store your new boot name.
3. Enter
setenv boot-device storagedisk and press ENTER to
change the boot device to the new alias.
4. Enter
5. Enter
6. Enter
setenv auto-boot? false and press ENTER.
reset -all.
boot.
Configuring a PowerPath Native Device as the Boot Device
3-7
Page 60
Configuring a PowerPath Boot Device on Solaris
3
Moving the Boot Device to an emcpower Device
To move a boot device from a native device to an emcpower device:
1. Boot from the native device.
2. Install PowerPath. Refer to Chapter 1, Installing PowerPath.
3. Locate the native device from which you are booting, and
correlate this device to an emcpower device. Enter:
/etc/powermt display dev=all
The output is similar to the following:
Pseudo name=emcpower6a
Symmetrix ID=000000005543
Logical device ID=0001
state=alive; policy=SymmOpt; priority=0; queued-IOs=0
==============================================================================
---------------- Host --------------- - Stor - -- I/O Path - -- Stats --### HW Path I/O Paths Interf. Mode State Q-IOs Errors
==============================================================================
1281 pci@4/QLGC,qla@1 c6t0d252s0 FA 3aA active alive 0 0
1283 pci@6/QLGC,qla@1 c8t0d252s0 FA 3aA active alive 0 0
3-8
Scroll through the output until you locate the native device used
as the boot device; for example,
native device corresponds to
4. Identify the device node that corresponds to the emcpower
device. Enter:
ls –l /dev/dsk/emcpower6a
The output is similar to the following:
lrwxrwxrwx 1 root other 33 May 30 17:42 /dev/dsk/emcpower6a ->
../../devices/pseudo/emcp@6:a,blk
Looking at the output, you can see that /pseudo/emcp@6:a,blk
corresponds to
emcpower6a. You will use this value in step 6.
5. Make backup copies of the
so that, if necessary, you can restore the host to its pre-PowerPath
settings. Enter:
cp /etc/system /etc/system.no_EMCpower
cp /etc/vfstab /etc/vfstab.no_EMCpower
PowerPath for UNIX Installation and Administration Guide
c1t6d0s0. In this example, this
emcpower6a.
/etc/system and /etc/vfstab files
Page 61
Configuring a PowerPath Boot Device on Solaris
6. Using a text editor such as vi, make the following changes to the
/etc/system file:
3
Recovery Procedure
• Add this line above the
forceload: drv/sd
forceload: drv/emcp statement:
• Add this line below the forceload: drv/emcp statement:
rootdev: /pseudo/emcp@6:a,blk
The /etc/system file now includes the following lines:
forceload: drv/sd
forceload: drv/emcp
rootdev: /pseudo/emcp@6:a,blk
7. Using a text editor such as vi, edit the /etc/vfstab file,
replacing each native partition (
c#t#d#s#) for the boot device
with an emcpower partition name. In this example, you would
replace
/dev/dsk and /dev/rdsk entries.
c1t6d0s0 with emcpower6a. You must change both the
8. Restart the host. Enter:
reboot
If you cannot boot the host after configuring the PowerPath device as
the boot device, you may have made a typing error when editing the
/etc/system and /etc/vfstab files. To recover:
1. Insert the Solaris Operating System CD-ROM into the host’s
CD-ROM drive.
2. At the
ok prompt, enter:
boot cdrom –s
3. Mount the storage system boot device that is experiencing the
problem. For example, enter:
mount /dev/dsk/c1t6d0s0 /a
4. Enter:
TERM=sun-cmd
export TERM
5. Check the /etc/system and /etc/vfstab files against the
changes you made to these files when you set up multipathing to
the storage system boot device. Use a text editor such as
vi to
correct any problems you find.
Moving the Boot Device to an emcpower Device
3-9
Page 62
Configuring a PowerPath Boot Device on Solaris
3
6. Shut down the host. Enter:
shutdown –y –g5 –i0
7. At the ok prompt, enter:
eject
8. Remove the Solaris Operating System CD-ROM from the host’s
CD-ROM drive.
9. Reboot the host. Enter:
boot
3-10
PowerPath for UNIX Installation and Administration Guide
Page 63
Configuring a PowerPath Boot Device on Solaris
Removing PowerPath Control Over a Boot Device
If your PowerPath installation uses a storage system device as the
boot device, use the following procedure to remove PowerPath 4.0
control over the boot device:
1. Determine whether the boot path from the host to the storage
system has changed since the storage system boot device was
configured.
3
a. Examine the
/etc/vfstab.no_EMCpower file to identify the
native name for the boot device; for example, c1t6d0s0. Enter:
cat /etc/vfstab.no_EMCpower
b. Determine the boot path associated with this native device.
For example, enter:
ls -al /dev/dsk/c1t6d0s0
An example of a boot path is
/pci@1f,4000/scsi@4/disk@6,0.
c. Compare the boot path from step 1.b. with the original boot
path. Enter:
cat /etc/nvramrc.orig
2. If the boot path listed in step 1.b. differs from that in the
nvramrc.orig file, update the boot path to reflect the value listed
in step 1.b. For example, enter:
eeprom nvramrc=”devalias storagedisk /pci@1f,4000/scsi@4/disk@6,0”
3. Verify that the boot path was changed to the new value. Enter:
eeprom
4. Restore the versions of /etc/system and /etc/vfstab that do
not contain references to PowerPath. Enter:
cp /etc/system.no_EMCpower /etc/system
cp /etc/vfstab.no_EMCpower /etc/vfstab
Removing PowerPath Control Over a Boot Device
3-11
Page 64
Configuring a PowerPath Boot Device on Solaris
3
5. If you did not reboot the host after removing PowerPath, do so
now. Enter:
reboot -- -r
Important: If you plan to reinstall PowerPath 4.0, or upgrade to a later
version of PowerPath, you need not reboot the host at this time.
If the host fails to boot, refer to Recovery Procedure on page 3-9 for
suggested actions.
3-12
PowerPath for UNIX Installation and Administration Guide
Page 65
Invisible Body Tag
4
Removing PowerPath
This chapter describes how to remove PowerPath and the PowerPath
Volume Manager VCS Agent from a Solaris host.
◆ Before Removing PowerPath ...........................................................4-2
◆ Removing PowerPath........................................................................4-3
◆ Removing the PowerPath Volume Manager VCS Agent.............4-6
Removing PowerPath
4-1
Page 66
Removing PowerPath
4
Before Removing PowerPath
Before you remove PowerPath from the host:
❑ Check the Powerlink website (
http://powerlink.emc.com) for
the most current information. We update the PowerPath release
notes periodically and post them on the Powerlink website.
❑ Stop any application and shut down any database that is using
emcpower devices or a PowerPath Volume Manager volume.
Unmount any file system mounted on a PowerPath Volume
Manager volume.
❑ If you are removing PowerPath from the host entirely (that is, you are
not planning to reinstall PowerPath), remove all PowerPath
Volume Manager volumes and volume groups allocated on the
host:
Run the
powervadm list command to determine whether any
volumes and volume groups are allocated on the host. If volumes
and volume groups are allocated, destroy them. Refer to
Destroying a Volume and Destroying a Volume Group in the
PowerPath for UNIX Volume Manager User’s Guide.
❑ If you have a database partition, discontinue use of PowerPath
devices as follows:
1. Stop the database manager.
2. Unmount PowerPath devices.
3. Edit the appropriate database configuration files so they no
longer refer to emcpower devices.
4-2
❑ If your PowerPath installation uses a storage system device as the
boot device, remove PowerPath control over the boot device.
Refer to Removing PowerPath Control Over a Boot Device on
page 3-11.
PowerPath for UNIX Installation and Administration Guide
Page 67
Removing PowerPath
Follow these steps to remove PowerPath from a Solaris host:
1. Log in as root.
2. Start the uninstall program. Enter:
3. Enter y and press ENTER to remove the package.
Removing PowerPath
4
/usr/sbin/pkgrm EMCpower
The screen displays information like this:
The following package is currently installed:
EMCpower EMC PowerPath
(all) 4.0.0_bxxx
Do you want to remove this package? [y,n,?,q]
The screen displays the following information:
## Removing installed package instance <EMCpower>
This package contains scripts which will be executed
with super-user permission during the process of
removing this package.
Do you want to continue with the removal of this package
[y,n,?,q]
4. Enter y and press ENTER to continue with deinstallation.
The screen displays information about the removal process,
ending with:
---------------------------------------------------------------* EMCpower successfully removed.
*
* REBOOT the host to complete the remaining step of the removal.
*
* This reboot may be deferred if you are about to install a
* newer PowerPath product.
*---------------------------------------------------------------## Updating system information.
Removal of <EMCpower> was successful.
If you are removing PowerPath from the host entirely, proceed
with step 5.
Otherwise, proceed with step 6.
Removing PowerPath
4-3
Page 68
Removing PowerPath
4
5. The removal process saves the following files in
/etc/emc/emcpxarchive, with the .400.saved extension:
•
/kernel/drv/emcp.conf
•
/etc/powermt.custom
•
/etc/emcp_registration
• /etc/emcp_devicesDB.dat
• /etc/emcp_devicesDB.idx
• /etc/PPVM_config
• /etc/PPVM_config_bak
If the removal program detects existing files with the .400.saved
extension on the host, it overwrites these files. It does not overwrite
saved files that have a different format, for example,
powermt.custom.saved.
If you are removing PowerPath from the host entirely (that is, you are
not planning to re-install PowerPath):
a. Enter the following command to remove these files:
/etc/emcpv_cleanup
4-4
This command removes the PowerPath license and all supporting
files.
emcpv_cleanup issues the following warning:
Warning: Attempt to remove saved configuration
files for PowerPath version versionNumber. Removing
these files will result in loss of saved
configuration and upgrade features. Proceed with
caution!!
Do you want to continue [y,n,?] (default: n):
b. Enter y and press ENTER.
The uninstall program asks for confirmation:
Are you sure [y,n,?] (default: n):
c. Enter y and press ENTER.
PowerPath for UNIX Installation and Administration Guide
Page 69
Removing PowerPath
6. Reboot the host. Enter:
reboot -- -r
Important: If you plan to reinstall PowerPath 4.0, or upgrade to a later
version of PowerPath, you need not reboot the host at this time.
4
Removing PowerPath
4-5
Page 70
Removing PowerPath
4
Removing the PowerPath Volume Manager VCS Agent
CAUTION
Do not try to remove the EMCvg package while VCS cluster is up
and running.
Complete the following steps to remove the PowerPath Volume
Manager VCS Agent:
1. Log in as root.
2. Close the VCS configuration file. Enter:
haconf -dump -makero
3. Save the current /etc/VRTSvcs/conf/config/main.cf file to a
backup location. For example, enter:
cp /etc/VRTSvcs/conf/config/main.cf /etc/VRTSvcs/conf/config/main.cf.orig
4. Identify all EMCvg resources. Enter:
hares -display -type EMCvg
4-6
5. Delete each EMCvg resource that you identified. Enter:
hares -delete
resource_name
6. Delete the EMCvg resource type. Enter:
hatype -delete EMCvg
7. Verify the configuration changes. Enter:
hacf -verify config
If the verification is successful, no output is displayed. Otherwise,
note the error and correct it in the
8. Remove the PowerPath Volume Manager VCS agent package.
Enter:
/usr/sbin/pkgrm EMCvg
PowerPath for UNIX Installation and Administration Guide
main.cf file.
Page 71
Removing PowerPath
The screen displays information like this:
The following package is currently installed:
1 EMCvg EMC Enterprise Cluster PowerPath
Volume Manager VCS Agent
(sparc) 1.0
Do you want to remove this package? [y,n,?,q]
9. Enter y and press ENTER to remove the package.
The screen displays the following information:
## Removing installed package instance <EMCvg>
Do you want to continue with the removal of this package
[y,n,?,q]
10. Enter y and press ENTER to continue with deinstallation.
The screen displays information about the removal process,
ending with:
Removal of <EMCvg> was successful.
4
Removing the PowerPath Volume Manager VCS Agent
4-7
Page 72
Removing PowerPath
4
4-8
PowerPath for UNIX Installation and Administration Guide
Page 73
PowerPath
Administration on
Solaris
visible Body Tag
This chapter discusses PowerPath issues and administrative tasks
specific to Solaris.
5
Throughout this chapter, many procedural steps use
powermt
commands. For detailed descriptions of these commands, refer to the
PowerPath Product Guide.
◆ PowerPath and CLARiiON Storage Systems.................................5-2
◆ Ensuring a Sufficient Stack Size.......................................................5-2
◆ Booting a Host With Built-In Fibre Channel Ports........................5-2
◆ Rebooting and Custom Settings.......................................................5-3
◆ Boot Device Support..........................................................................5-3
◆ R1/R2 Boot Failover Support...........................................................5-4
◆ Device Naming...................................................................................5-5
◆ Reconfiguring PowerPath Devices Online...................................5-10
◆ Dynamic Reconfiguration...............................................................5-12
◆ Upgrading Solaris ............................................................................5-15
◆ powercf Configuration Utility........................................................5-17
◆ Error Messages .................................................................................5-18
PowerPath Administration on Solaris
5-1
Page 74
PowerPath Administration on Solaris
5
PowerPath and CLARiiON Storage Systems
PowerPath events or actions that entail LUN trespasses (for example,
SP failovers or
disk driver to log warning and/or error messages. You can ignore
these messages, as PowerPath intercepts them and hides them from
the application sending the I/O.
For more information on CLARiiON configuration requirements,
refer to the EMC Installation Roadmap for CX-Series and FC-Series
Storage Systems and the EMC Host Connectivity Guide for Sun Solaris,
available on the Powerlink website.
The Host Connectivity Guide describes how to edit the
/kernel/drv/sd.conf file to suppress ODS device overlap error
messages. Note that this workaround is invalid for Sun Cluster 2.2
configurations.
powermt restore commands) can cause the Solaris
Ensuring a Sufficient Stack Size
If you install an application that resets the stack size (for example,
VxVM or VxFS) after you install PowerPath, make sure that
lwp_default_stksize and rpcmod:svc_run_stksize are set to at
least 0x6000 on a Solaris 7, 8, or 9 system, and at least 0x4000 on a
Solaris 2.6 system. Other applications may reset the stack sizes to
values insufficient for PowerPath.
Booting a Host With Built-In Fibre Channel Ports
If you boot a Solaris host with all socal host adapters to storage
system volumes disconnected or dysfunctional, PowerPath will not
configure any socal host adapter paths. After physically restoring the
5-2
PowerPath for UNIX Installation and Administration Guide
Page 75
PowerPath Administration on Solaris
socal connections, run the following commands to restore the paths
in PowerPath:
On hosts running this OS Run these commands
5
Solaris 7, 8, and 9
Solaris 2.6
Rebooting and Custom Settings
On every reboot, all saved custom files
(
/etc/powermt.custom.[0-2]) are incremented by one version. Thus,
at any time, the custom configurations from the last three reboots are
available.
You can ascertain from the custom file timestamps which version of
the custom file contains the last valid settings saved prior to a reboot.
To restore a custom configuration, enter the following commands:
/etc/powermt load file=/etc/powermt.custom.<desired version>
/etc/powermt save
Although you can restore an earlier powermt.custom file, it is not
currently possible to restore an earlier emcp_devicesDB file.
devfsadm
powercf -q
powermt config
drvconfig; disks; devlinks
powercf -q
powermt config
Boot Device Support
Solaris can boot from either a native device or pseudo device. Only
pseudo devices (emcpower devices), however, support booting with
failed paths. Refer to Chapter 3, Configuring a PowerPath Boot Device
on Solaris, for more information.
Rebooting and Custom Settings
5-3
Page 76
PowerPath Administration on Solaris
5
R1/R2 Boot Failover Support
R1/R2 Supported Configurations
If a storage system device corresponding to a bootable emcpower
device is mirrored via SRDF
®
, it is possible in the event of a server
failure at the local storage system to fail over the boot disk to the
remote mirror disk and then boot the server on an identical remote
host.
Contact EMC Customer Support for assistance when configuring
R1/R2 boot disk failover.
EMC supports the following specific R1/R2 configurations:
◆ Each boot host is connected to only one Symmetrix.
◆ The two hosts must have identical hardware.
◆ All R1 devices reside on one Symmetrix, Symmetrix A, and are
visible only to a single host, Host A.
◆ All R2 devices reside on a separate Symmetrix, Symmetrix B, and
are visible only to the identical host in reserve, Host B.
◆ Each R1 device has only one mirror. (Concurrent SRDF is not
supported.)
◆ Neither host has non-mirrored devices, BCVs, or gatekeepers.
◆ SRDF is managed from either of the following two facilities:
• EMC ControlCenter Management Server
• Symmetrix Service Processor
R1/R2 Boot Procedure
5-4
R1/R2 boot support assumes that the systems are configured to boot
from an emcpower device. If you plan to enable R1/R2 boot disk
failover, after you install PowerPath, run the
while booted on the R1 copy of the boot disk.This will update the
emcp.conf file so that each entry contains both an R1 and an R2
Symmetrix volume ID for the pseudo (emcpower) device.
PowerPath for UNIX Installation and Administration Guide
powercf -Z command
Page 77
Device Naming
PowerPath Administration on Solaris
When the host on the R2 side boots, it is connected to a different
Symmetrix system and set of volume IDs. Therefore, the
and
powermt.custom files (which are identical to the R1 files since
emcp.conf
the boot disk is identical) are modified to create a valid mapping
between the emcpower device and native path device for both R1 and
R2 locations. Having both the R1 and R2 Symmetrix volume IDs in
the
emcp.conf file ensures a valid mapping between the pseudo
devices and the underlying native path device. PowerPath will
determine which Symmetrix volume IDs are valid (that is, the visible
ones) and will act accordingly when either the R1or the R2 host is
booted.
PowerPath for Solaris presents PowerPath-enabled storage system
logical devices to the operating system by all their native devices plus
a single PowerPath-specific pseudo device. Applications and
operating system services can use any of these devices—native or
pseudo—to access a PowerPath-enabled storage system logical
device.
5
Native Devices
A native device describes a device special file of one of the following
forms:
◆ Block device—/dev/dsk/c#t#d#s#
◆ Raw device—/dev/rdsk/c#t#d#s#
where:
◆ The c # is the instance number for the interface card.
◆ The t # is the target address of the storage system logical device
on the bus.
◆ The d # is the storage system logical device at the target.
◆ The s # is the slice, ranging from 0 to 7.
Device Naming
5-5
Page 78
PowerPath Administration on Solaris
5
Pseudo Devices
Selecting a Device Naming Convention
A pseudo device describes a device special file of one of the following
forms:
◆ Block device—/dev/dsk/emcpower#[a-h]
◆ Raw device—/dev/rdsk/emcpower#[a-h]
where:
◆ # is the disk number.
◆ [a-h] is the slice.
Slices in Sys V identifiers are designated s0, s1, s2, and so on. They
correspond exactly to emcpower slices designated a, b, c, and so on.
Therefore, if device
c0t0d0s2 corresponds to slice emcpower0c.
c0t0d0 corresponds to device emcpower0, slice
After PowerPath is installed, a host has both native devices and
emcpower devices enabled and available for use. Both native devices
and emcpower devices can be active simultaneously on a host.
Native devices are preferable for most installations. Native devices
offer the following advantages:
◆ If PowerPath is installed, VxVM automatically scans for and
recognizes native devices when it (VxVM) is installed. (Pseudo
devices must be referenced manually when initializing disks for
use with VxVM.)
◆ If both PowerPath and VxVM are installed, VxVM automatically
scans for and recognizes native devices when volumes are
imported. (With pseudo devices, extra manual steps are required
to set up disk groups that can be imported.)
5-6
◆ VxVM provides unqualified support for native names. (VxVM
supports pseudo names with the following qualification: pseudo
names cause VxVM 3.2 to generate warnings in some
circumstances. This is a recognized VERITAS bug, 85455, and
EMC has a documented workaround. For details, see
http://seer.support.veritas.com/docs/242612.htm.)
◆ Existing applications, like volume managers and DBMSs, need
not be modified to provide PowerPath multipathing and path
failover functionality, because they can directly access PowerPath
logical devices through native devices. (With pseudo devices,
existing applications need to be modified to use this
functionality.)
PowerPath for UNIX Installation and Administration Guide
Page 79
PowerPath Administration on Solaris
Pseudo (emcpower) devices offer the following advantages:
◆ There is only one pseudo device name for each multipathed
logical device. (There are multiple native device names for each
multipathed logical device, which is harder to manage.)
◆ Pseudo device names are easier to manage because there is a
one-to-one relationship between pseudo device names and
logical volumes. (Native device names are based on HBA, target,
and device assignments as recognized at system startup.)
◆ Implementing PowerPath’s boot-time, boot-path failover feature
requires pseudo devices.
◆ Operations of Sun Microsystem’s Dynamic Reconfiguration (DR)
feature are transparent to applications using pseudo devices.
(With native devices, these operations are not transparent:
c#t#d#s
#
paths are removed, which can be disruptive to
applications using those paths.) Refer to Dynamic Reconfiguration
on page 5-12 for information on using DR to add and remove
HBAs in a PowerPath environment.
5
Device Naming
5-7
Page 80
PowerPath Administration on Solaris
5
Table 5-1 summarizes the functional differences between native
devices and emcpower devices in the Solaris environment.
Table 5-1 Native Devices versus emcpower Devices
Function Native Device Pseudo Device
✔
I/O failover
I/O load balancing
Booting: boot-path failover
✔
No
✔
✔
✔
Reboot (reconfiguration)
Support for VxVM sliced
disks
Support for VxVM simple
disks
Support for Solaris disk
partitions (slices)
Support for interaction
with VxVM DMP (Dynamic
MultiPathing)
(When using PowerPath
4.0.0, you can manage a
CLARiiON
system with either
PowerPath or DMP, but
not both.)
DR transparency Limitations —
®
storage
✔
(Partial support)
If a path is missing, PowerPath
does not create a
“replacement”
device.
✔
No
✔
✔
✔
paths are removed, which can
be disruptive to applications
using those paths.
c#t#d#
c#t#d#s#
✔
(Full support)
✔
✔
✔
✔
5-8
IOCTL deterministic path
selection
PowerPath’s No Redirect
load-balancing and
failover policy (transparent
mode)
PowerPath for UNIX Installation and Administration Guide
✔
(PowerPath selects the
specific path.)
Native devices deliver I/O to the
path where it would go if
PowerPath were not installed. If
that path fails, I/Os fail.
No (PowerPath selects an
arbitrary path.)
Pseudo devices select a
configured path for all
subsequent I/O. If that path
fails, I/O to the pseudo
device fails.
Page 81
Table 5-2 indicates when native and pseudo devices are supported,
and which device naming conventions we prefer in environments
with specified software requirements. If no preference is specified,
both supported options are equally good.
Table 5-2 Support for Native and Pseudo Devices
PowerPath Administration on Solaris
5
Are Native
Software Requirements
Boot Requirements
Boot-time failover—Symmetrix and CLARiiON No
Volume Managers
VxVM 3.1.1 and later
• New installations of PowerPath
(DMP always is fully configured and enabled)
• Existing installations of PowerPath
VxVM 3.1 and earlier
• New installations of PowerPath
(DMP may be enabled or disabled)
• Existing installations of PowerPath
Other volume managers (including Sun’s
DiskSuite, raw devices, filesystems on raw
devices, and raw table spaces)
• If DR is used
• If DR is not used
Devices
Supported?
✔
✔
✔
✔
✔
✔
(Preferred)
(Preferred)
Are Pseudo
Devices
Supported?
✔
(For the root
filesystem)
✔
✔
✔
✔
✔
(Preferred)
✔
Device Naming
5-9
Page 82
PowerPath Administration on Solaris
5
Reconfiguring PowerPath Devices Online
Whenever the physical configuration of the storage system or the
host changes, you must reconfigure the PowerPath devices to avoid
data loss.
Configuration changes that require you to reconfigure PowerPath
devices include:
◆ Adding or removing HBAs
◆ Adding, removing, or changing storage system logical devices
◆ Changing the cabling routes between HBAs and storage system
ports
◆ Adding or removing storage system interfaces
!
CAUTION
If you are trying to recover from a SCSI bus ID conflict, you must
reboot the host before completing the following procedure. The
host reboot assures the integrity of the underlying SCSI driver
layers so that PowerPath can find all devices on the bus.
To reconfigure PowerPath devices:
1. Update the
/kernel/drv/sd.conf file to include target/logical
device entries for all multipath storage system logical devices.
2. Create the device nodes. Enter the appropriate command:
On hosts running Enter
Solaris 7, 8, and 9
Solaris 2.6
3. Use the
format command to verify that all devices were created.
4. At the format prompt, enter
devfsadm -C
drvconfig;disks;devlinks
inquiry.
5-10
PowerPath for UNIX Installation and Administration Guide
Page 83
PowerPath Administration on Solaris
The screen displays the emcpower device’s inquiry data; for
example:
Vendor: EMC
Product: SYMMETRIX
Revision: 5x6x
format>
5. Enter quit, to end the format process.
6. Create the new device nodes. Enter:
powercf -q
PowerPath displays the following message as it creates new
devices:
Creating new device nodes
7. Verify that the emcpower devices are accessible. For example,
enter:
format /dev/rdsk/emcpower1a
The screen displays the following information:
FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
repair - repair a defective sector
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
inquiry - show vendor, product and revision
volname - set 8-character volume name
quit
format>
5
8. Display the new device. Enter:
powermt display dev=all
Reconfiguring PowerPath Devices Online
5-11
Page 84
PowerPath Administration on Solaris
5
Dynamic Reconfiguration
The Solaris Dynamic Reconfiguration (DR) feature allows you to add
or remove an HBA from a Solaris system while the system continues
running. You can logically attach and detach system boards from the
operating system without halting and rebooting. For example, with
DR you can detach a board from the operating system, physically
remove and service the board, and then re-insert the board and
re-attach it to the operating system—without halting the operating
system or terminating any user application.
PowerPath supports DR. The following procedures describe how to
use DR to add and remove HBAs in a PowerPath environment.
As you perform these procedures, have available the Sun Dynamic
Reconfiguration documentation for your platform.
If you have a custom PowerPath configuration that you have not yet saved,
run powermt save before completing the procedures in this section, to save
your configuration changes. Run powermt load after completing these
procedures, to restore your configuration.
Adding an HBA to a PowerPath Configuration
5-12
PowerPath for UNIX Installation and Administration Guide
To use DR to add an HBA to a Solaris system in a PowerPath
configuration, follow these steps:
1. Add the new HBA to the system, following the instructions in the
Sun Dynamic Reconfiguration documentation.
2. Configure the new HBA. Enter:
powermt config
Page 85
PowerPath Administration on Solaris
5
Removing an HBA From a PowerPath Configuration
To use DR to remove an HBA from a Solaris host in a PowerPath
configuration, follow these steps:
1. Correlate the
c#t#d#s# device special files of the HBA being
removed with the PowerPath adapter number for that HBA. The
PowerPath adapter number is used in the
powermt remove adapter command later in this procedure.
On 10000 class systems:
• Start the
dr
dr shell. Enter:
The prompt changes to dr>.
• From within the
c#t#d#s# device special files on the I/O board being removed.
dr shell, list the devices and corresponding
For example, for I/O board 1, enter:
drshow 1
The command returns output like the following:
I/O Bus Controllers and Devices for Board 1
----------- I/O Bus 1 : Slot 0 : esp0 ----------
device opens name usage
------ ----- ---- ----sd838 4 /dev/dsk/c2t0d1s2 /test
...
drshow
displays all device special files that point to HBAs on
the I/O board. In the example above, board 1 Slot 0 has a
single device (HBA) attached named c2t0d1s2.
•Press
CTRL-D to exit the dr shell.
• Associate the device special file (identified above with
drshow) with a PowerPath adapter number. Enter:
powermt display dev=all
Dynamic Reconfiguration
5-13
Page 86
PowerPath Administration on Solaris
5
The command returns output like the following:
pseudo name=emcpower0a
Symmetrix ID=000000003269;
logical device ID=048
state=alive; policy=SymmOpt; priority=0; queued-IOs=0
==================================================================
------------- Hosts ----------- - Sys - - I/O Paths - --- Stats -### HW Path I/0 Path Interf. Mode State Q-IOs Errors
==================================================================
0 psbus@b/QLGC,isp@0 c2t0d1 SA 16aB active alive 0 0
In the output, locate device c2t0d1. Notice that the adapter
number for c2t0d1 is 0; therefore, 0 is the adapter number you
use as an argument to
powermt remove hba in step 2.
2. Use
powermt remove adapter to remove the HBA from the
PowerPath configuration. Enter:
powermt remove hba=#
where # corresponds to the PowerPath adapter number identified
in step 1.
3. Disconnect the HBA, following the instructions in the Sun
Dynamic Reconfiguration documentation.
5-14
PowerPath for UNIX Installation and Administration Guide
Page 87
Upgrading Solaris
PowerPath 4.0 supports Solaris Live Upgrade, which lets you
upgrade the operating system without uninstalling PowerPath.
Solaris Live Upgrade is supported for upgrades to Solaris 9 only. If you are
upgrading to an earlier version of Solaris, you must uninstall PowerPath
before you upgrade the OS and then reinstall PowerPath after the upgrade.
Upgrading to Solaris 9 with Solaris Live Upgrade
The PowerPath 4.0 package includes a script, sol9_liveup.sh,
located in the
directory (for example,
script before you activate Solaris 9.
Solaris Live Upgrade does not work when booting off emcpower devices.
To upgrade to Solaris 9:
scripts subdirectory of the PowerPath 4.0 installation
/opt/EMCpower/scripts). You must run this
PowerPath Administration on Solaris
5
1. Ensure that the HBA driver is supported with Solaris 9.
Otherwise, Solaris Live Upgrade will not work.
2. Install PowerPath 4.0 on the host.
3. Optionally, save the
Solaris Live Upgrade may replace
sd.conf file.
sd.conf with a default sd.conf
file, causing devices to become inaccessible. If those devices are system
critical devices, the new boot image will not work.
Solaris Live Upgrade saves a copy of the
/kernel/drv/sd.conf.~version (where version is the Solaris version
sd.conf file in
from which you are upgrading; for example, if you are upgrading from
Solaris 8, the file name is
to save
sd.conf before you start the upgrade.
sd.conf.~8.) Nevertheless, you might want
4. Install Solaris Live Upgrade on the host.
5. Create an inactive boot environment. Follow the instructions in
the Solaris 9 Installation Guide.
6. Upgrade the inactive boot environment. Follow the instructions
in the Solaris 9 Installation Guide.
Upgrading Solaris
5-15
Page 88
PowerPath Administration on Solaris
5
7. Run the sol9_liveup.sh script and then activate the inactive
boot environment:
a. Mount the root of the inactive boot environment to a directory
such as
/mnt.
b. Run the script
cd /install_dir/EMCpower/scripts
./sol9_liveup.sh /mnt
sol9_liveup.sh. Enter:
where install_dir is the base install location of the EMCpower
package. For example, if the base install directory is
cd /opt/EMCpower/scripts
./sol9_liveup.sh /mnt
opt, enter:
c. Continue with the procedure documented in the Solaris 9
Installation Guide.
Troubleshooting
If Solaris Live Upgrade replaces the
sd.conf file with a default sd.conf,
the new boot image may not work. In this case, replace the default
sd.conf with either the file Solaris Live Upgrade automatically
saved in
/kernel/drv/sd.conf.~version or the file you saved before
starting the upgrade procedure. (See step 3, above.)
If you fail to run
sol9_liveup.sh before activating Solaris 9, the new
boot image will not work. In this case:
1. Boot from the older Solaris boot area.
2. Mount the Solaris 9 boot area.
3. Run
sol9_liveup.sh in the Solaris 9 boot area.
5-16
4. Boot Solaris 9.
PowerPath for UNIX Installation and Administration Guide
Page 89
powercf Configuration Utility
During system boot on Solaris hosts, the powercf utility configures
PowerPath devices by scanning HBAs for both single-ported and
multiported storage system logical devices. (A multiported logical
device shows up on two or more HBAs with the same storage system
subsystem/device identity. The identity comes from the serial
number for the logical device.) For each storage system logical device
found in the scan of the HBAs,
emcpower device entry in the
path and an alternate primary path to that device.
PowerPath Administration on Solaris
5
powercf creates a corresponding
emcp.conf file, and it saves a primary
File Location
Executing powercf
emcp.conf File
After PowerPath is installed, you need to run
powercf only when the
physical configuration of the storage system or the host changes.
Configuration changes that require you to reconfigure PowerPath
devices include the following:
◆ Adding or removing HBAs
◆ Adding, removing, or changing storage system logical devices
◆ Changing the cabling routes between HBAs and storage system
ports
◆ Adding or removing storage system interfaces
Refer to Reconfiguring PowerPath Devices Online on page 5-10 for
instructions on reconfiguring PowerPath devices on Solaris.
The powercf utility resides in the /etc directory.
You must have superuser privileges to use powercf.
To run
powercf on a Solaris host, type the command, plus any
options, at the shell prompt.
The /kernel/drv/emcp.conf file lists the primary and alternate path
to each storage system logical device and the storage system device
serial number for that logical device. The
updates the existing
emcp.conf file or creates a new one if it does not
powercf -q command
already exist.
Syntax
powercf -q|-Z
powercf Configuration Utility
5-17
Page 90
PowerPath Administration on Solaris
5
Arguments
Error Messages
powercf scans HBAs for single-ported and multiported storage
system logical devices and compares those logical devices with
PowerPath device entries in
-q
emcp.conf.
Runs powercf in quiet mode.
powercf -q updates the emcp.conf file by removing PowerPath
devices not found in the HBA scan and adding new PowerPath
devices that were found. It saves a primary and an alternate path
to each PowerPath device.
powercf -q runs automatically during system boot.
-Z
Configures an SRDF-enabled server to be bootable from an R2
mirror of a Symmetrix-based emcpower boot disk by a remote
host.
powercf -Z should be run manually whenever such a server's
Symmetrix volume configuration changes due to the addition or
deletion of volumes.
PowerPath reports any errors, diagnostic messages, and failover
recovery messages to the system console and to the file
/var/adm/messages. Refer to the PowerPath Product Guide for a
complete list of PowerPath error messages.
5-18
PowerPath for UNIX Installation and Administration Guide
Page 91
Invisible Body Tag
A
Files Changed By
PowerPath
This appendix lists files that are created or modified by PowerPath
installation and upgrade.
◆ Files Created or Modified by PowerPath Installation .................A-2
◆ Files Created or Modified by VCS Agent Installation ...............A-11
Files Changed By PowerPath
A-1
Page 92
A
Files Changed By PowerPath
Files Created or Modified by PowerPath Installation
The following files are created (or, where indicated, modified) when
PowerPath is installed on a Solaris host:
/etc
This directory contains PowerPath CLI commands and utilities:
◆ S87powervxvm
◆ cgmt
◆ emc/bin/emcp_discover <symbolic link>
◆ emc/bin/emcp_purge <symbolic link>
◆ emc/bin/inquiry.pp
◆ emcpcvt <symbolic link>
◆ emcpmgr
◆ emcpreg
◆ emcpupgrade
◆ emcpvcleanup
◆ powercf
◆ powermt
◆ powerprotect
◆ powervsvs
◆ powervshm
◆ powervxvm
◆ powermt.custom
◆ emcp_registration
◆ emcp_devicesDB.dat
◆ emcp_devicesDB.idx
◆ emcpower_mode-dir
◆ emcpv_cleanup
◆ PPVM_config
◆ PPVM_config_bak
◆ rc2.d/S02configcgs
◆ rcS.d/S24powerstartup
◆ rcS.d/S63powershift
A-2
PowerPath for UNIX Installation and Administration Guide
Page 93
/
basedir
Files Changed By PowerPath
A
/EMCpower/bin
This directory contains 32- and 64-bit versions of the PowerPath
Volume Manager CLI commands:
◆ 64 <symbolic link>
◆ emcpminor <symbolic link>
◆ emcpminor_32
◆ powervadm <symbolic link>
◆ powervadm_32
◆ powervg <symbolic link>
◆ powervg_32
◆ powervmeta <symbolic link>
◆ powervmeta_32
◆ powervol <symbolic link>
◆ powervol_32
◆ powervperf <symbolic link>
◆ powervperf_32
◆ sparcv9/emcpminor <symbolic link>
◆ sparcv9/emcpminor_64
◆ sparcv9/powervadm <symbolic link>
◆ sparcv9/powervadm_64
◆ sparcv9/powervg <symbolic link>
◆ sparcv9/powervg_64
◆ sparcv9/powervmeta <symbolic link>
◆ sparcv9/powervmeta_64
◆ sparcv9/powervol <symbolic link>
◆ sparcv9/powervol_64
◆ sparcv9/powervperf <symbolic link>
◆ sparcv9/powervperf_64
/
basedir
/EMCpower/driver
This directory contains 32- and 64-bit versions of the PowerPath
kernel files:
◆ 64 <symbolic link>
◆ emcp <symbolic link>
◆ emcp_32
◆ emcp_32_5_9
◆ emcp_5_9 <symbolic link>
◆ emcpcg <symbolic link>
◆ emcpcg_32
◆ emcpcg_32_5_9
Files Created or Modified by PowerPath Installation
A-3
Page 94
A
Files Changed By PowerPath
◆ emcpcg_5_9 <symbolic link>
◆ emcpdpm <symbolic link>
◆ emcpdpm_32
◆ emcpdpm_32_5_9
◆ emcpdpm_5_9 <symbolic link>
◆ emcpevm <symbolic link>
◆ emcpevm_32
◆ emcpevm_32_5_9
◆ emcpevm_5_9 <symbolic link>
◆ emcphr <symbolic link>
◆ emcphr_32
◆ emcphr_32_5_9
◆ emcphr_5_9 <symbolic link>
◆ emcpioc <symbolic link>
◆ emcpioc_32
◆ emcpioc_32_5_9
◆ emcpioc_5_9 <symbolic link>
◆ emcpmp <symbolic link>
◆ emcpmp_32
◆ emcpmp_32_5_9
◆ emcpmp_5_9 <symbolic link>
◆ emcpmpc <symbolic link>
◆ emcpmpc_32
◆ emcpmpc_32_5_9
◆ emcpmpc_5_9 <symbolic link>
◆ emcpsapi <symbolic link>
◆ emcpsapi_32
◆ emcpsapi_32_5_9
◆ emcpsapi_5_9 <symbolic link>
◆ emcpsc <symbolic link>
◆ emcpsc_32
◆ emcpsc_32_5_9
◆ emcpsc_5_9 <symbolic link>
◆ emcpsm <symbolic link>
◆ emcpsm_32
◆ emcpsm_32_5_9
◆ emcpsm_5_9 <symbolic link>
◆ emcpte <symbolic link>
◆ emcpte_32
◆ emcpte_32_5_9
◆ emcpte_5_9 <symbolic link>
◆ sparcv9/emcp <symbolic link>
◆ sparcv9/emcp_5_9 <symbolic link>
◆ sparcv9/emcp_64
◆ sparcv9/emcp_64_5_9
◆ sparcv9/emcpcg <symbolic link>
◆ sparcv9/emcpcg_5_9 <symbolic link>
A-4
PowerPath for UNIX Installation and Administration Guide
Page 95
◆ sparcv9/emcpcg_64
◆ sparcv9/emcpcg_64_5_9
◆ sparcv9/emcpdpm <symbolic link>
◆ sparcv9/emcpdpm_5_9 <symbolic link>
◆ sparcv9/emcpdpm_64
◆ sparcv9/emcpdpm_64_5_9
◆ sparcv9/emcpevm <symbolic link>
◆ sparcv9/emcpevm_5_9 <symbolic link>
◆ sparcv9/emcpevm_64
◆ sparcv9/emcpevm_64_5_9
◆ sparcv9/emcphr <symbolic link>
◆ sparcv9/emcphr_5_9 <symbolic link>
◆ sparcv9/emcphr_64
◆ sparcv9/emcphr_64_5_9
◆ sparcv9/emcpioc <symbolic link>
◆ sparcv9/emcpioc_5_9 <symbolic link>
◆ sparcv9/emcpioc_64
◆ sparcv9/emcpioc_64_5_9
◆ sparcv9/emcpmp <symbolic link>
◆ sparcv9/emcpmp_5_9 <symbolic link>
◆ sparcv9/emcpmp_64
◆ sparcv9/emcpmp_64_5_9
◆ sparcv9/emcpmpc <symbolic link>
◆ sparcv9/emcpmpc_5_9 <symbolic link>
◆ sparcv9/emcpmpc_64
◆ sparcv9/emcpmpc_64_5_9
◆ sparcv9/emcpsapi <symbolic link>
◆ sparcv9/emcpsapi_5_9 <symbolic link>
◆ sparcv9/emcpsapi_64
◆ sparcv9/emcpsapi_64_5_9
◆ sparcv9/emcpsc <symbolic link>
◆ sparcv9/emcpsc_5_9 <symbolic link>
◆ sparcv9/emcpsc_64
◆ sparcv9/emcpsc_64_5_9
◆ sparcv9/emcpsm <symbolic link>
◆ sparcv9/emcpsm_5_9 <symbolic link>
◆ sparcv9/emcpsm_64
◆ sparcv9/emcpsm_64_5_9
◆ sparcv9/emcpte <symbolic link>
◆ sparcv9/emcpte_5_9 <symbolic link>
◆ sparcv9/emcpte_64
◆ sparcv9/emcpte_64_5_9
Files Changed By PowerPath
A
/kernel/drv
This directory contains the PowerPath configuration file emcp.conf.
Files Created or Modified by PowerPath Installation
A-5
Page 96
A
Files Changed By PowerPath
/
basedir
/EMCpower/lib
This directory contains 32- and 64-bit versions of the PowerPath
libraries:
◆ 64 <symbolic link>
◆ libdpmh.so <symbolic link>
◆ libdpmh_32.so
◆ libdpmhmt.so <symbolic link>
◆ libdpmhmt_32.so
◆ libdpmu.so <symbolic link>
◆ libdpmu_32.so
◆ libdpmumt.so <symbolic link>
◆ libdpmumt_32.so
◆ libemcp.so <symbolic link>
◆ libemcp_32.so
◆ libemcp_lic_rtl.so <symbolic link>
◆ libemcp_lic_rtl_32.so
◆ libemcp_mp_rtl.so <symbolic link>
◆ libemcp_mp_rtl_32.so
◆ libemcpcg.so <symbolic link>
◆ libemcpcg_32.so
◆ libemcpmp.so <symbolic link>
◆ libemcpmp_32.so
◆ libemcpmt.so <symbolic link>
◆ libemcpmt_32.so
◆ libemcpvapi.so <symbolic link>
◆ libemcpvapi_32.so
◆ libemcpvapimt.so <symbolic link>
◆ libemcpvapimt_32.so
◆ libevm.so <symbolic link>
◆ libevm_32.so
◆ libevmmt.so <symbolic link>
◆ libevmmt_32.so
◆ libgm.so <symbolic link>
◆ libgm_32.so
◆ libgmmt.so <symbolic link>
◆ libgmmt_32.so
◆ libmp_32.so <symbolic link>
◆ libom.so <symbolic link>
◆ libom_32.so
◆ libommt.so <symbolic link>
◆ libommt_32.so
A-6
PowerPath for UNIX Installation and Administration Guide
Page 97
Files Changed By PowerPath
◆ libpn.so <symbolic link>
◆ libpn_32.so
◆ libradcommon.so <symbolic link>
◆ libradcommon_32.so
◆ libradcommonmt.so <symbolic link>
◆ libradcommonmt_32.so
◆ libraddebug.so <symbolic link>
◆ libraddebug_32.so
◆ libraddebugmt.so <symbolic link>
◆ libraddebugmt_32.so
◆ libsc.so <symbolic link>
◆ libsc_32.so
◆ libscmt.so <symbolic link>
◆ libscmt_32.so
◆ libsm.so <symbolic link>
◆ libsm_32.so
◆ libsmmt.so <symbolic link>
◆ libsmmt_32.so
◆ sparcv9/libdpmh.so <symbolic link>
◆ sparcv9/libdpmh_64.so
◆ sparcv9/libdpmhmt.so <symbolic link>
◆ sparcv9/libdpmhmt_64.so
◆ sparcv9/libdpmu.so <symbolic link>
◆ sparcv9/libdpmu_64.so
◆ sparcv9/libdpmumt.so <symbolic link>
◆ sparcv9/libdpmumt_64.so
◆ sparcv9/libemcp.so <symbolic link>
◆ sparcv9/libemcp_64.so
◆ sparcv9/libemcp_lic_rtl.so <symbolic link>
◆ sparcv9/libemcp_lic_rtl_64.so
◆ sparcv9/libemcp_mp_rtl.so <symbolic link>
◆ sparcv9/libemcp_mp_rtl_64.so
◆ sparcv9/libemcpcg.so <symbolic link>
◆ sparcv9/libemcpcg_64.so
◆ sparcv9/libemcpmp.so <symbolic link>
◆ sparcv9/libemcpmp_64.so
◆ sparcv9/libemcpmt.so <symbolic link>
◆ sparcv9/libemcpmt_64.so
◆ sparcv9/libemcpvapi.so <symbolic link>
◆ sparcv9/libemcpvapi_64.so
◆ sparcv9/libemcpvapimt.so <symbolic link>
◆ sparcv9/libemcpvapimt_64.so
◆ sparcv9/libevm.so <symbolic link>
A
Files Created or Modified by PowerPath Installation
A-7
Page 98
A
Files Changed By PowerPath
◆ sparcv9/libevm_64.so
◆ sparcv9/libevmmt.so <symbolic link>
◆ sparcv9/libevmmt_64.so
◆ sparcv9/libgm.so <symbolic link>
◆ sparcv9/libgm_64.so
◆ sparcv9/libgmmt.so <symbolic link>
◆ sparcv9/libgmmt_64.so
◆ sparcv9/libmp_64.so <symbolic link>
◆ sparcv9/libom.so <symbolic link>
◆ sparcv9/libom_64.so
◆ sparcv9/libommt.so <symbolic link>
◆ sparcv9/libommt_64.so
◆ sparcv9/libpn.so <symbolic link>
◆ sparcv9/libpn_64.so
◆ sparcv9/libradcommon.so <symbolic link>
◆ sparcv9/libradcommon_64.so
◆ sparcv9/libradcommonmt.so <symbolic link>
◆ sparcv9/libradcommonmt_64.so
◆ sparcv9/libraddebug.so <symbolic link>
◆ sparcv9/libraddebug_64.so
◆ sparcv9/libraddebugmt.so <symbolic link>
◆ sparcv9/libraddebugmt_64.so
◆ sparcv9/libsc.so <symbolic link>
◆ sparcv9/libsc_64.so
◆ sparcv9/libscmt.so <symbolic link>
◆ sparcv9/libscmt_64.so
◆ sparcv9/libsm.so <symbolic link>
◆ sparcv9/libsm_64.so
◆ sparcv9/libsmmt.so <symbolic link>
◆ sparcv9/libsmmt_64.so
A-8
/
basedir
/EMCpower/man/man1
This directory contains the PowerPath Volume Manager man pages:
◆ powervadm.1
◆ powervg.1
◆ powervintro.1
◆ powervmeta.1
◆ powervol.1
◆ powervperf.1
PowerPath for UNIX Installation and Administration Guide
Page 99
/
basedir
/EMCpower/scripts
/usr/bin
/usr/man/man1
Files Changed By PowerPath
A
This directory contains PowerPath scripts:
◆ emcpv_cleanup
◆ emcpv_cron_remove.sh
◆ emcpv_cron_setup.sh
◆ emcpv_logchecker
◆ emcpv_setup.csh
◆ emcpv_setup.sh
◆ emcpv_slv2devinfo
◆ sol9_liveup.sh
This directory contains powervini, the PowerPath Volume Manager
initialization file.
This directory contains the PowerPath man pages:
◆ emcp_discover.1 <symbolic link>
◆ emcp_purge.1 <symbolic link>
◆ emcpminor.1
◆ emcpreg.1
◆ emcpupgrade.1
◆ powercf.1
◆ powermt.1
Files Created or Modified by PowerPath Installation
A-9
Page 100
A
Files Changed By PowerPath
Solaris Files Modified by PowerPath Installation
Installing PowerPath on a Solaris host modifies the:
◆ /etc/system configuration file:
• Adds forceload statements for the PowerPath driver and
miscellaneous kernel modules.
• Adds set statements for kernel
default kernel stack sizes and avoid stack overflow panics.
◆ /etc/.login and /etc/profile scripts so that it runs the
PowerPath setup script at system boot.
• The installation program adds the following line to the
/etc/.login script:
source /
base_directory
• The installation programs add the following line to the
/etc/profile script:
. /
base_directory
stksize variables to increase
/EMCpower/scripts/emcpv_setup.csh
/EMCpower/scripts/emcpv_setup.sh
A-10
PowerPath for UNIX Installation and Administration Guide
Loading...