EMC 300-000-978 REV A03 manual Troubleshooting the Upgrade, If files are corrupted

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

 

 

Image 29
Contents Version PowerPath for UnixCopyright 1997-2003 EMC Corporation. All rights reserved Contents Chapter Removing PowerPath Chapter Configuring a PowerPath Boot Device on SolarisChapter PowerPath Administration on Solaris Integrating/ Upgrading PowerPath Into an Existing AAMAppendix a Files Changed By PowerPath Appendix B Customer Support Tables TablesTables Viii Audience and Prerequisites PrefacePreface Related Documentation Arguments used in examples of command line Command line arguments when used in textOptions in command line syntax EMC uses the following type style conventions in this guideSales and Customer Service Contacts Xiv Installing PowerPath Choose a Convenient Time Before You InstallObtain Up-To-Date Information Prepare the Host and Storage System Locate Your License KeyFailure to do so could result in loss or corruption of data Configure HBA driversFor example Prepare For a Clustered EnvironmentFor sh, enter To find a unique major numberStart the installation program. Enter Installing PowerPathYou see the following prompt Enter y and press Enter You are prompted to confirm the major numberPress Enter to confirm the major number Manager VCS Agent Uninstalling the Earlier Version Upgrading to PowerPathEnter 1 and press Enter Upgrading From PowerPath 3.0.x orEnter package base directory default /opt,? You are prompted to confirm the major number EMC If files are corrupted Troubleshooting the UpgradeOn the Host After You InstallRegister PowerPath Remove Reboot the HostIf you installed the PowerPath Volume Manager VCS Agent Verify the PowerPath InstallationYou should see output like the following You should see output similar to thisModinfo grep -i emc Applications to Use ReconfigureEmcpower Devices Installing the PowerPath Volume Manager VCS Agent Do you want to install these conflicting files y, n, ?, q You should output similar to this Error MessagesPowerPath for Unix Installation and Administration Guide PowerPath in a Legato 5.1 or later AAM Cluster PowerPath in a Cluster EnvironmentInstalling PowerPath A New AAM Cluster PowerPath in a Legato 5.1 or later AAM ClusterPowerPath in a Legato 5.1 or later AAM Cluster Installing PowerPath in a New Sun Cluster PowerPath in a Sun ClusterPowerPath in a Sun Cluster PowerPath in a Sun Cluster Stop cluster services on the node. Enter boot Installing PowerPath A New VCS Cluster PowerPath in a Veritas Cluster Server ClusterHatype -list grep EMC Integrating Upgrading PowerPath Into an Existing VCS Cluster PowerPath Volume Configuring VCS toRecognize Manager ResourcesAdd the following line to the beginning Editing main.cf to Include EMCTypes.cfMinor Number Setting Major and Minor NumbersPowerPath for Unix Installation and Administration Guide Configuring a PowerPath Boot Device On Solaris Introduction Partitioning the Boot Device Configuring a PowerPath Native Device as the Boot DeviceFilesystems CreatingUsr/sbin/installboot /usr/platform/sun4u/lib/fs/ufs/bootblk\ Example After modification At the % prompt, enter the following command and pressModifying OpenBootSetting Up the Boot Alias Output is similar to the following Moving the Boot Device to an emcpower DeviceProcedure RecoveryReboot the host. Enter boot An example of a boot path is Removing PowerPath Control Over a Boot DeviceReboot -- -r Removing PowerPath Before Removing PowerPath Screen displays information like this Removing PowerPathRemoval process saves the following files Enter the following command to remove these filesEmcpvcleanup issues the following warning Reboot the host. Enter reboot -- -r Removing the PowerPath Volume Manager VCS Agent Removal of EMCvg was successful PowerPath for Unix Installation and Administration Guide PowerPath Administration on Solaris Ensuring a Sufficient Stack Size PowerPath and CLARiiON Storage SystemsBooting a Host With Built-In Fibre Channel Ports Boot Device Support Rebooting and Custom SettingsR1/R2 Supported Configurations R1/R2 Boot Procedure R1/R2 Boot Failover SupportNative Devices Device NamingForms Block device- /dev/dsk/c # t # d # s #Naming Convention Pseudo DevicesSelecting a Device Device Naming Function Native Device Pseudo Device Volume Managers Reconfiguring PowerPath Devices Online Screen displays the following information Enter quit, to end the format processAdding an HBA to a PowerPath Configuration Dynamic ReconfigurationCommand returns output like the following Removing an HBA From a PowerPath ConfigurationPowermt remove hba=# Upgrading Solaris Upgrading to Solaris 9 with Solaris Live UpgradeTroubleshooting File Location Executing powercf Emcp.conf File Powercf Configuration UtilityArguments PowerPath device entries in emcp.confFiles Changed By PowerPath Etc Files Created or Modified by PowerPath InstallationBasedir/EMCpower/driver Basedir/EMCpower/binPowerPath for Unix Installation and Administration Guide Kernel/drv Basedir/EMCpower/lib Files Created or Modified by PowerPath Installation Basedir/EMCpower/man/man1 This directory contains PowerPath scripts Basedir/EMCpower/scriptsThis directory contains the PowerPath man pages Usr/binInstallation programs add the following line to Solaris Files Modified by PowerPath InstallationEtc/VRTSvcs/conf/config Files Created or Modified by VCS Agent InstallationBasedir/VRTSvcs/EMC Basedir/VRTSvcs/bin/EMCvgPowerPath for Unix Installation and Administration Guide Customer Support Figure B-1Problem Detection and Resolution Process Overview of Detecting and Resolving ProblemsTroubleshooting the Problem Before Calling the Customer Support Center Documenting the Problem Reporting a New Problem FTP Sending Problem DocumentationPowerPath for Unix Installation and Administration Guide Index SymbolsVCS Veritas Volume Manager and emcpower devices PowerPath for Unix Installation and Administration Guide