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.
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.
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 ...............................................
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 ............
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..........................................
Contents Appendix B Customer Support Overview of Detecting and Resolving Problems ...................... Troubleshooting the Problem ....................................................... Before Calling the Customer Support Center ............................ Documenting the Problem ........................................................... Reporting a New Problem ............................................................ Sending Problem Documentation ...............................................
Tables Tables 5-1 5-2 Native Devices versus emcpower Devices ............................................... 5-8 Support for Native and Pseudo Devices ...................................................
Tables viii PowerPath for UNIX Installation and Administration Guide
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.
Preface Organization x 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.
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 De
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.
Preface 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.
Preface xiv PowerPath for UNIX Installation and Administration Guide
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.
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® storage systems. Install PowerPath after you set up the Symmetrix system. Verify that the Symmetrix system is working properly, then install PowerPath using the instructions in this guide. CLARiiON® storage systems. PowerPath installation is an integral part of a CLARiiON setup and configuration procedure.
Installing PowerPath 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.
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 powermt save command. Refer to 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.
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.
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.
Installing PowerPath 4. You see the following prompt: 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]: Enter 1 and press ENTER. 5.
Installing PowerPath 1 8. You are prompted for a major number that can be assigned to the PowerPath device driver (emcp) on every host in the cluster: 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.
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.
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 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.
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.
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 /basedir/EMCpower; the installation process creates the EMCpower subdirectory. Make a note of the name and location of the PowerPath base directory for future reference. 6.
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.
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.
Installing PowerPath 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 y to the following prompt: Configuration for PowerPath version exists - want to upgrade [y,n,q,?] (default: y): The following sections describe what to do under these circumstances. If files are corrupted If the PowerPath 3.0.x or 2.
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.
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.
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: NAME: CATEGORY: ARCH: VERSION: BASEDIR: VENDOR: PSTAMP: INSTDATE: STATUS: FILES: EMCpower EMC PowerPath system sparc 4.0.0_bxxx /opt EMC cambridge951018123443 Mar 14 2003 08:36 completely installed 292 installed pathnames 5 shared pathnames 17 directories 139 executables 137622 blocks used (approx) 2.
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 31 32 33 34 35 36 39 40 41 42 125c08b 127ec94 1295a42 12b4f4c 134f510 13608a5 136276d 13a4aa9 7816a000 13e957d 7811b2e6 Verify the PowerPath Commands Are in Your Path 74a05 255 1 emcp (PP Driver 4.0.0) 18c1e - 1 emcpmp (PP MP Ext 4.0.0) 21ac2 - 1 emcpmpc (PP MPC Ext 4.0.0) c905c - 1 emcpsapi (PP SAPI Ext 4.0.
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 powermt and load-balancing policies, see the PowerPath Product Guide.
Installing PowerPath 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.
Installing PowerPath 1 4. You see the following prompt: 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]: Enter 2 and press ENTER. 5.
Installing PowerPath To verify that the agent is installed properly on the host, enter: pkginfo -l EMCvg You should output similar to this: PKGINST: NAME: CATEGORY: ARCH: VERSION: VENDOR: DESC: PSTAMP: INSTDATE: EMAIL: STATUS: FILES: EMCvg EMC Enterprise Cluster PowerPath Volume Manager VCS Agent system sparc 1.0 EMC Corporation EMC Enterprise Cluster PowerPath Volume Manager VCS Agent 1.0 EMC: 1.0.0.xxx Nov 20 2002 15:31 support@emc.
Installing PowerPath 1 1-24 PowerPath for UNIX Installation and Administration Guide
2 Invisible Body Tag 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.
PowerPath in a Cluster Environment 2 PowerPath in a Legato 5.1 (or later) AAM Cluster This section describes how to: Installing PowerPath in a New AAM Cluster ◆ 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. To install and configure PowerPath and AAM 5.
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: 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.
PowerPath in a Cluster Environment 2 PowerPath in a Sun Cluster 2.2 This section describes how to: Installing PowerPath in a New Sun Cluster 2.2 ◆ 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. To install and configure PowerPath and Sun Cluster 2.2 when neither PowerPath nor Sun Cluster 2.
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: 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.
PowerPath in a Cluster Environment 2 PowerPath in a Sun Cluster 3.0 This section describes how to: Installing PowerPath in a New Sun Cluster 3.0 ◆ 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. To install and configure PowerPath and Sun Cluster 3.0 when neither PowerPath nor Sun Cluster 3.
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.
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. For new installations of VxVM, use native c#t#d# devices. Do not initialize emcpower devices for VxVM using powervxvm.
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.
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 hagrp command to verify that the service 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.
PowerPath in a Cluster Environment Configuring VCS to Recognize PowerPath Volume Manager Resources 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.
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 edit 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.
PowerPath in a Cluster Environment 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 3. On every node in the cluster (except any node that is already using the minor number), run the powervol setminor command 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.
3 Invisible Body Tag 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 .........................
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.
Configuring a PowerPath Boot Device on Solaris Configuring a PowerPath Native Device as the Boot Device 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 %> prompt, enter format and press ENTER. b.
Configuring a PowerPath Boot Device on Solaris 3 Information similar to the following is displayed: AVAILABLE SELECTIONS ... 1. c0t0d0 /pci@1f,4000/scsi@3/sd@0,0 2. c3t0d0 /pci@1f,4000/QLGC,qla@4/sd@0,0 ... specify disk (enter its number): c. Enter 2 and press ENTER. 3.
Configuring a PowerPath Boot Device on Solaris 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 uname -a command to determine the architecture of the workstation. This determines the directory in /usr/platform where the bootblk will be found. The following example shows sun4u as the architecture, and subdirectory for /usr/platform.
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 %> prompt, enter cd /mnt/etc and press ENTER. b. At the %> prompt, enter vi vfstab and press ENTER.
Configuring a PowerPath Boot Device on Solaris Modifying OpenBoot 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: If you use Refer to Emulex HBAs EMC Fibre Channel with Emulex Host Bus Adapters in the Solaris Host Environment http://emulex.com/ts/docoem/emc/pdfs/Sol_501a.pdf QLogic HBAs EMC Fibre Channel with QLogic Host Bus Adapters in the Solaris Environment http://download.qlogic.
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.
Configuring a PowerPath Boot Device on Solaris 6. Using a text editor such as vi, make the following changes to the /etc/system file: • Add this line above the forceload: drv/emcp statement: forceload: drv/sd • 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.
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.
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. a. Examine the /etc/vfstab.no_EMCpower file to identify the native name for the boot device; for example, c1t6d0s0.
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.
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 .............
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.
Removing PowerPath Removing PowerPath Follow these steps to remove PowerPath from a Solaris host: 1. Log in as root. 2. Start the uninstall program. Enter: /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] 3. Enter y and press ENTER to remove the package.
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.
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.
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.
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 Do you want to continue with the removal of this package [y,n,?,q] 10. Enter y and press ENTER to continue with deinstallation.
Removing PowerPath 4 4-8 PowerPath for UNIX Installation and Administration Guide
5 PowerPath Administration on Solaris visible Body Tag This chapter discusses PowerPath issues and administrative tasks specific to Solaris. 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 .......................................................
PowerPath Administration on Solaris 5 PowerPath and CLARiiON Storage Systems PowerPath events or actions that entail LUN trespasses (for example, SP failovers or powermt restore commands) can cause the Solaris 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.
PowerPath Administration on Solaris socal connections, run the following commands to restore the paths in PowerPath: On hosts running this OS Run these commands Solaris 7, 8, and 9 devfsadm powercf -q powermt config Solaris 2.6 drvconfig; disks; devlinks powercf -q powermt config 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.
PowerPath Administration on Solaris 5 R1/R2 Boot Failover Support 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.
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 emcp.conf and powermt.custom files (which are identical to the R1 files since 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.
PowerPath Administration on Solaris 5 Pseudo Devices 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.
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.
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 5-8 ✔ Reboot (reconfiguration) ✔ (Partial support) If a path is missing, PowerPath does not create a “replacement” c#t#d# device.
PowerPath Administration on Solaris 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.
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.
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.
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.
PowerPath Administration on Solaris 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 shell. Enter: dr The prompt changes to dr>.
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.
PowerPath Administration on Solaris 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.
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 sol9_liveup.sh. Enter: cd /install_dir/EMCpower/scripts ./sol9_liveup.sh /mnt where install_dir is the base install location of the EMCpower package. For example, if the base install directory is opt, enter: cd /opt/EMCpower/scripts ./sol9_liveup.sh /mnt c.
PowerPath Administration on Solaris 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.
PowerPath Administration on Solaris 5 Arguments powercf scans HBAs for single-ported and multiported storage system logical devices and compares those logical devices with PowerPath device entries in emcp.conf. -q 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.
A Invisible Body Tag 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 ...............
Files Changed By PowerPath A 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: ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ A-2 S87powervxvm cgmt emc/bin/emcp_discover emc/bin/emcp_purge emc/bin/inquiry.
Files Changed By PowerPath A /basedir/EMCpower/bin This directory contains 32- and 64-bit versions of the PowerPath Volume Manager CLI commands: ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ 64 emcpminor emcpminor_32 powervadm powervadm_32 powervg powervg_32 powervmeta powervmeta_32 powervol powervol_32 powervperf powervperf_32 sparcv9/emcpminor sparcv9/emcpminor_64 sparcv9/p
Files Changed By PowerPath A ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ A-4 emcpcg_5_9 emcpdpm emcpdpm_32 emcpdpm_32_5_9 emcpdpm_5_9 emcpevm emcpevm_32 emcpevm_32_5_9 emcpevm_5_9 emcphr emcphr_32 emcphr_32_5_9 emcphr_5_9 emcpioc emcpioc_32 emcpioc_32_5_9 emcpioc_5_9 emcpmp emcpmp_32 emcpmp_32_5_9
Files Changed By PowerPath A ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ sparcv9/emcpcg_64 sparcv9/emcpcg_64_5_9 sparcv9/emcpdpm sparcv9/emcpdpm_5_9 sparcv9/emcpdpm_64 sparcv9/emcpdpm_64_5_9 sparcv9/emcpevm sparcv9/emcpevm_5_9 sparcv9/emcpevm_64 sparcv9/emcpevm_64_5_9 sparcv9/emcphr sparcv9/emcphr_5_9 sparcv9/emcphr_64 sparcv9/emcphr_64_5_9 sparcv9/emcpioc
Files Changed By PowerPath A /basedir/EMCpower/lib This directory contains 32- and 64-bit versions of the PowerPath libraries: ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ A-6 64 libdpmh.so libdpmh_32.so libdpmhmt.so libdpmhmt_32.so libdpmu.so libdpmu_32.so libdpmumt.so libdpmumt_32.so libemcp.so libemcp_32.so libemcp_lic_rtl.so libemcp_lic_rtl_32.
Files Changed By PowerPath A ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ libpn.so libpn_32.so libradcommon.so libradcommon_32.so libradcommonmt.so libradcommonmt_32.so libraddebug.so libraddebug_32.so libraddebugmt.so libraddebugmt_32.so libsc.so libsc_32.so libscmt.so libscmt_32.so libsm.so libsm_32.so libsmmt.
Files Changed By PowerPath A ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ sparcv9/libevm_64.so sparcv9/libevmmt.so sparcv9/libevmmt_64.so sparcv9/libgm.so sparcv9/libgm_64.so sparcv9/libgmmt.so sparcv9/libgmmt_64.so sparcv9/libmp_64.so sparcv9/libom.so sparcv9/libom_64.so sparcv9/libommt.so sparcv9/libommt_64.so sparcv9/libpn.so sparcv9/libpn_64.so sparcv9/libradcommon.
Files Changed By PowerPath A /basedir/EMCpower/scripts 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 /usr/bin This directory contains powervini, the PowerPath Volume Manager initialization file. /usr/man/man1 This directory contains the PowerPath man pages: ◆ ◆ ◆ ◆ ◆ ◆ ◆ emcp_discover.1 emcp_purge.1 emcpminor.1 emcpreg.
Files Changed By PowerPath A 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 stksize variables to increase 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.
Files Changed By PowerPath A Files Created or Modified by VCS Agent Installation The following files are created when the PowerPath Volume Manager VCS Agent is installed on a Solaris host. /basedir/VRTSvcs/EMC ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ bin/EMCvgAgent lib/libEMCvg.so messages.EMC scripts/_abortOnline scripts/_getResAttr scripts/_getResAttrLocal scripts/_getTypeAttr scripts/_isResExist scripts/_setChldResAttr scripts/_setResAttr scripts/_setTypeAttr types/EMCVgTypes.
Files Changed By PowerPath A A-12 PowerPath for UNIX Installation and Administration Guide
B nvisible Body Tag Customer Support This appendix reviews the EMC process for detecting and resolving software problems, and provides essential questions that you should answer before contacting the EMC Customer Support Center. This appendix covers the following topics: ◆ ◆ ◆ ◆ ◆ ◆ Overview of Detecting and Resolving Problems ......................... B-2 Troubleshooting the Problem .......................................................... B-3 Before Calling the Customer Support Center ...............
Customer Support B Overview of Detecting and Resolving Problems EMC software products are supported directly by the EMC Customer Support Center in the United States. EMC uses the following process to resolve customer problems with its software products (Figure B-1). Problem Detection Refer to this Customer Support Appendix for Instructions Collect Problem Information as Directed Contact the EMC Customer Support Center: (800) SVC-4EMC U.S.
Customer Support Troubleshooting the Problem Please perform the relevant diagnostic steps before you contact the EMC Customer Support Center: 1. Read the documentation carefully. 2. Reconstruct the events leading up to the problem and describe them in writing. 3. Run some test cases to reproduce the problem.
Customer Support B Before Calling the Customer Support Center Have the following information available before calling the Customer Support Center or your support representative (if one has been assigned to you): ❑ Your company name ❑ Your name ❑ Your phone number ❑ For an existing problem, the problem tracking system ID, if one was previously assigned to the problem by a support representative B-4 PowerPath for UNIX Installation and Administration Guide
Customer Support Documenting the Problem If the EMC Customer Support Center requests information regarding the problem, please document it completely, making sure to include the following information: ❑ Your company name and address ❑ Your name ❑ Your telephone number ❑ The importance of the problem, so that it can be assigned a priority level To expedite the processing of your support request, you can photocopy this list and include it with the package.
Customer Support B Reporting a New Problem For a new problem, please provide the following information: ❑ Release level of the software that you are running ❑ Software installation parameters ❑ Host type on which you are running ❑ Operating system you are running and its release number ❑ Functions of the software that you are running ❑ Whether you can reproduce the problem ❑ Previous occurrences of the problem ❑ Whether the software has ever worked correctly ❑ Time period that the software did work proper
Customer Support Sending Problem Documentation Use one of the following methods to send documentation of the problem to the EMC Customer Support Center: ◆ E-mail ◆ FTP ◆ U.S. mail to the following address: EMC Customer Support Center 45 South Street Hopkinton, MA 01748-9103 If the problem was assigned a number or a specific support representative, please include that information in the address as well.
Customer Support B B-8 PowerPath for UNIX Installation and Administration Guide
Index Symbols Error messages installation 1-23 ODS device overlap 5-2 Solaris 5-2, 5-18 /etc/.login file 1-19 /etc/profile file 1-19 A F AAM. See Legato AAM format utility, Solaris 1-3 C Clusters. See Legato AAM, Sun Cluster 2.2, Sun Cluster 3.
Index M Major number 1-5, 1-8, 1-12, 2-13 Minor number 2-13 N Naming conventions Solaris 5-5 Native devices Solaris 5-5 P powercf configuration utility (Solaris) 5-17 Powerlink website B-3 PowerPath boot device, Solaris configuring 3-2 troubleshooting 3-9 PowerPath devices emcpower 5-6 native Solaris 5-5 reconfiguring online Solaris 5-10 PowerPath error messages installation 1-23 Solaris 5-18 PowerPath Volume Manager Legato Agent 1-1 PowerPath Volume Manager VCS Agent configuring VCS for 2-11 files A-11
Index agent, PowerPath Volume Manager. See PowerPath Volume Manager VCS Agent EMCvg resource type 2-11 installing with PowerPath 2-8 integrating PowerPath into 2-10 VERITAS Cluster Server.
Index i-4 PowerPath for UNIX Installation and Administration Guide
