EMC 300-000-978 REV A03 manual R1/R2 Boot Failover Support

Page 76

5

PowerPath Administration on Solaris

R1/R2 Boot Failover Support

R1/R2 Supported Configurations

R1/R2 Boot

Procedure

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

5-4	PowerPath for UNIX Installation and Administration Guide

Image 76

Contents PowerPath for Unix VersionCopyright 1997-2003 EMC Corporation. All rights reserved Contents Chapter Configuring a PowerPath Boot Device on Solaris Chapter Removing PowerPathChapter PowerPath Administration on Solaris Integrating/ Upgrading PowerPath Into an Existing AAMAppendix a Files Changed By PowerPath Appendix B Customer Support Tables TablesTables Viii Preface Audience and PrerequisitesPreface Related Documentation Command line arguments when used in text Arguments used in examples of command lineOptions in command line syntax EMC uses the following type style conventions in this guideSales and Customer Service Contacts Xiv Installing PowerPath Obtain Up-To-Date Information Before You InstallChoose a Convenient Time Locate Your License Key Prepare the Host and Storage SystemConfigure HBA drivers Failure to do so could result in loss or corruption of dataPrepare For a Clustered Environment For exampleFor sh, enter To find a unique major numberInstalling PowerPath Start the installation program. EnterYou see the following prompt Press Enter to confirm the major number You are prompted to confirm the major numberEnter y and press Enter Manager VCS Agent Upgrading to PowerPath Uninstalling the Earlier VersionUpgrading From PowerPath 3.0.x or Enter 1 and press EnterEnter package base directory default /opt,? You are prompted to confirm the major number EMC Troubleshooting the Upgrade If files are corruptedRegister PowerPath After You InstallOn the Host Reboot the Host RemoveVerify the PowerPath Installation If you installed the PowerPath Volume Manager VCS AgentYou should see output like the following You should see output similar to thisModinfo grep -i emc Emcpower Devices ReconfigureApplications to Use Installing the PowerPath Volume Manager VCS Agent Do you want to install these conflicting files y, n, ?, q Error Messages You should output similar to thisPowerPath for Unix Installation and Administration Guide PowerPath in a Cluster Environment PowerPath in a Legato 5.1 or later AAM ClusterPowerPath in a Legato 5.1 or later AAM Cluster Installing PowerPath A New AAM ClusterPowerPath in a Legato 5.1 or later AAM Cluster PowerPath in a Sun Cluster Installing PowerPath in a New Sun ClusterPowerPath in a Sun Cluster PowerPath in a Sun Cluster Stop cluster services on the node. Enter boot PowerPath in a Veritas Cluster Server Cluster Installing PowerPath A New VCS ClusterHatype -list grep EMC Integrating Upgrading PowerPath Into an Existing VCS Cluster Configuring VCS to PowerPath VolumeRecognize Manager ResourcesEditing main.cf to Include EMCTypes.cf Add the following line to the beginningSetting Major and Minor Numbers Minor NumberPowerPath for Unix Installation and Administration Guide Configuring a PowerPath Boot Device On Solaris Introduction Configuring a PowerPath Native Device as the Boot Device Partitioning the Boot DeviceCreating FilesystemsUsr/sbin/installboot /usr/platform/sun4u/lib/fs/ufs/bootblk\ At the % prompt, enter the following command and press Example After modificationSetting Up the Boot Alias OpenBootModifying Moving the Boot Device to an emcpower Device Output is similar to the followingRecovery ProcedureReboot the host. Enter boot Removing PowerPath Control Over a Boot Device An example of a boot path isReboot -- -r Removing PowerPath Before Removing PowerPath Removing PowerPath Screen displays information like thisEmcpvcleanup issues the following warning Enter the following command to remove these filesRemoval process saves the following files 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 Booting a Host With Built-In Fibre Channel Ports PowerPath and CLARiiON Storage SystemsEnsuring a Sufficient Stack Size Rebooting and Custom Settings Boot Device SupportR1/R2 Boot Failover Support R1/R2 Supported Configurations R1/R2 Boot ProcedureDevice Naming Native DevicesForms Block device- /dev/dsk/c # t # d # s #Selecting a Device Pseudo DevicesNaming Convention Device Naming Function Native Device Pseudo Device Volume Managers Reconfiguring PowerPath Devices Online Enter quit, to end the format process Screen displays the following informationDynamic Reconfiguration Adding an HBA to a PowerPath ConfigurationRemoving an HBA From a PowerPath Configuration Command returns output like the followingPowermt remove hba=# Upgrading to Solaris 9 with Solaris Live Upgrade Upgrading SolarisTroubleshooting Powercf Configuration Utility File Location Executing powercf Emcp.conf FilePowerPath device entries in emcp.conf ArgumentsFiles Changed By PowerPath Files Created or Modified by PowerPath Installation EtcBasedir/EMCpower/bin Basedir/EMCpower/driverPowerPath for Unix Installation and Administration Guide Kernel/drv Basedir/EMCpower/lib Files Created or Modified by PowerPath Installation Basedir/EMCpower/man/man1 Basedir/EMCpower/scripts This directory contains PowerPath scriptsThis directory contains the PowerPath man pages Usr/binSolaris Files Modified by PowerPath Installation Installation programs add the following line toFiles Created or Modified by VCS Agent Installation Etc/VRTSvcs/conf/configBasedir/VRTSvcs/EMC Basedir/VRTSvcs/bin/EMCvgPowerPath for Unix Installation and Administration Guide Customer Support Overview of Detecting and Resolving Problems Figure B-1Problem Detection and Resolution ProcessTroubleshooting the Problem Before Calling the Customer Support Center Documenting the Problem Reporting a New Problem Sending Problem Documentation FTPPowerPath for Unix Installation and Administration Guide Symbols IndexVCS Veritas Volume Manager and emcpower devices PowerPath for Unix Installation and Administration Guide