EMC 300-000-978 REV A03 manual Setting Major and Minor Numbers

Page 51

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.

Setting a Common You set a common major number for every host in the cluster during

Major number PowerPath installation (refer to Chapter 1, Installing PowerPath).

Setting a Common Minor numbers are assigned as follows:

Minor Number

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

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 powervol(1) man page for information on powervol getminor.

2. If step 1 reveals inconsistent minor numbers, use the emcpminor command to find one minor number that can be used for the volume on every host. Refer to the emcpminor(1) man page for information on emcpminor.

While running emcpminor, avoid running any other commands that might claim minor numbers.

Setting Major and Minor Numbers

2-13

 

 

2

Image 51
Contents Version PowerPath for UnixCopyright 1997-2003 EMC Corporation. All rights reserved Contents Integrating/ Upgrading PowerPath Into an Existing AAM Chapter Configuring a PowerPath Boot Device on SolarisChapter Removing PowerPath Chapter PowerPath Administration on SolarisAppendix a Files Changed By PowerPath Appendix B Customer Support Tables TablesTables Viii Audience and Prerequisites PrefacePreface Related Documentation EMC uses the following type style conventions in this guide Command line arguments when used in textArguments used in examples of command line Options in command line syntaxSales and Customer Service Contacts Xiv Installing PowerPath Before You Install Obtain Up-To-Date InformationChoose a Convenient Time Prepare the Host and Storage System Locate Your License KeyFailure to do so could result in loss or corruption of data Configure HBA driversTo find a unique major number Prepare For a Clustered EnvironmentFor example For sh, enterStart the installation program. Enter Installing PowerPathYou see the following prompt You are prompted to confirm the major number Press Enter to confirm the major numberEnter y and press Enter 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 UpgradeAfter You Install Register PowerPathOn the Host Remove Reboot the HostYou should see output similar to this Verify the PowerPath InstallationIf you installed the PowerPath Volume Manager VCS Agent You should see output like the followingModinfo grep -i emc Reconfigure Emcpower DevicesApplications to Use 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 Manager Resources Configuring VCS toPowerPath Volume RecognizeAdd 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 pressOpenBoot Setting Up the Boot AliasModifying 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 PowerPathEnter the following command to remove these files Emcpvcleanup issues the following warningRemoval 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 PowerPath and CLARiiON Storage Systems Booting a Host With Built-In Fibre Channel PortsEnsuring a Sufficient Stack Size Boot Device Support Rebooting and Custom SettingsR1/R2 Supported Configurations R1/R2 Boot Procedure R1/R2 Boot Failover SupportBlock device- /dev/dsk/c # t # d # s # Device NamingNative Devices FormsPseudo Devices Selecting a DeviceNaming Convention 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 Usr/bin Basedir/EMCpower/scriptsThis directory contains PowerPath scripts This directory contains the PowerPath man pagesInstallation programs add the following line to Solaris Files Modified by PowerPath InstallationBasedir/VRTSvcs/bin/EMCvg Files Created or Modified by VCS Agent InstallationEtc/VRTSvcs/conf/config Basedir/VRTSvcs/EMCPowerPath 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