HP Serviceguard Guidelines for Migrating a Cluster with Cold Install, Checklist for Migration

Page 368

CAUTION: You must reboot all the nodes from their original disks before restarting the cluster; do not try to restart the cluster with some nodes booted from the upgraded disks and some booted from the pre-upgrade disks.

Guidelines for Migrating a Cluster with Cold Install

There may be circumstances when you prefer to do a cold install of the HP-UX operating system rather than an upgrade. A cold install erases the existing operating system and data and then installs the new operating system and software; you must then restore the data.

CAUTION: The cold install process erases the existing software, operating system, and data. If you want to retain any existing software, make sure you back up that software before migrating.

Checklist for Migration

Use the following as a checklist to prepare the migration.

CAUTION: This is a checklist, not a precise set of steps.

1.Back up the data, including databases, user and application data, volume group configurations, etc.

NOTE: Data on shared disks, or on local disks in volumes that are not are touched by the HP-UX installation process, will not normally be erased by the cold install; you can re-import this data after the cold install. If you intend to do this, you must do the following before you do the cold install:

•For LVM: create a map file for each LVM volume group and save it as part of your backup.

•For VxVM: deport disk groups (halting the package should do this).

See “Creating the Storage Infrastructure and file systems with LVM, VxVM and CVM” (page 177) for more information.

2.Halt the cluster applications, and then halt the cluster.

3.Do a cold install of the HP-UX operating system. For more information on the cold install process, see the HP-UX Installation and Update Guide for the target version of HP-UX at http:// www.hp.com/go/hpux-core-docs.

4.Install any additional required software that did not come with your version of the HP-UX Operating Environment.

5.Install Serviceguard. The Serviceguard version must be compatible with the version of HP-UX installed in item 3 of this list. See the Serviceguard/SGeRAC/SMS/Serviceguard Manager Plug-in Compatibility and Feature Matrix, at http://www.hp.com/go/hpux-serviceguard-docs.

6.Recreate any user accounts needed for the cluster applications.

7.Recreate the cluster as described in Chapter 5: “Building an HA Cluster Configuration” (page 158).

8.Restart the cluster.

9.Reinstall the applications.

10.Restore or re-import the data.

11.Recreate and run the cluster packages as described in Chapter 6: “Configuring Packages and Their Services ” (page 227).

368 Software Upgrades

Page 367 Page 369
Image 368
Page 367 Page 369
Contents Managing Serviceguard Twentieth Edition Legal Notices Contents Contents Planning and Documenting an HA Cluster Contents Building an HA Cluster Configuration 158 Contents Configuring Packages and Their Services 227 Contents Cluster and Package Maintenance 261 279 Troubleshooting Your Cluster 321 Contents 349 Integrating HA Applications with Serviceguard 354Software Upgrades 357 Blank Planning Worksheets 369 Migrating from LVM to VxVM Data Storage 374377 IPv6 Network Support 378Index 398 Using Serviceguard Manager 385396 Publishing History Publishing HistoryPreface Securing Serviceguard and other Serviceguard white papers Related PublicationsServiceguard at a Glance What is Serviceguard?Failover Shows what happens in a failover situationAbout Veritas CFS and CVM from Symantec Typical Cluster After FailoverUsing Serviceguard Manager Using SAMUsr/sbin/sam -w What are the Distributed Systems Administration Utilities?Roadmap for Configuring Clusters and Packages Tasks in Configuring a Serviceguard Cluster Understanding Serviceguard Hardware Configurations Redundancy of Cluster ComponentsRedundant Network Components Rules and RestrictionsRedundant Ethernet Configuration Redundant LANsCross-Subnet Configurations Configuration TasksFor legacy packages, see Configuring Cross-Subnet Failover RestrictionsFor More Information Supported Disk Interfaces Redundant Disk StorageReplacing Failed Network Cards Disk Arrays using RAID Levels and Multiple Data Paths Data ProtectionDisk Mirroring About MultipathingMonitoring LVM Disks Through Event Monitoring Service Monitoring VxVM and CVM DisksReplacing Failed Disk Mechanisms Replacing Failed I/O CardsSample Scsi Disk Configurations Mirrored Disks Connected for High AvailabilitySample Fibre Channel Disk Configuration Cluster with High Availability Disk ArrayRedundant Power Supplies Larger ClustersActive/Standby Model Point to Point Connections to Storage DevicesEight-Node Cluster with XP or EMC Disk Array Serviceguard Daemons Understanding Serviceguard Software ComponentsServiceguard Architecture Configuration Daemon cmclconfd Cluster Daemon cmcldCluster Logical Volume Manager Daemon cmlvmd File Management Daemon cmfileassistdSyslog Log Daemon cmlogd Cluster Object Manager Daemon cmomdService Assistant Daemon cmserviced Quorum Server Daemon qsNetwork Manager Daemon cmnetd Lock LUN Daemon cmdisklockdConfiguring the Cluster How the Cluster Manager WorksProxy Daemon cmproxyd CFS ComponentsHeartbeat Messages Manual Startup of Entire ClusterAutomatic Cluster Startup Dynamic Cluster Re-formationCluster Quorum to Prevent Split-Brain Syndrome Cluster LockUse of a Lock LUN or LVM Lock Disk as the Cluster Lock Lock RequirementsDual Lock Disk Use of the Quorum Server as the Cluster LockSingle Lock Disk or LUN No Cluster Lock Quorum Server OperationHow the Package Manager Works Package TypesNon-failover Packages Failover PackagesDeciding When and Where to Run and Halt Failover Packages Failover Packages’ Switching BehaviorBefore Package Switching Package Configuration Data Automatic Rotating StandbyRotating Standby Configuration before Failover Configurednode Policy Packages after Failover Failback PolicyAutomatic Failback Configuration After Failover Using Older Package Configuration Files Using the Generic Resources Monitoring ServiceUnderstanding Serviceguard Software Components Using the Event Monitoring Service Using the EMS HA MonitorsSee also Using Generic Resources to Monitor Volume Groups See also Using EMS to Monitor Volume GroupsHow Packages Run What Makes a Package Run?Before the Control Script Starts Legacy Package Time Line Showing Important EventsDuring Run Script Execution Package Time Line Legacy PackageNormal and Abnormal Exits from the Run Script Service Startup with cmrunservWhile Services are Running When a Package is Halted with a Command During Halt Script ExecutionLegacy Package Time Line for Halt Script Execution Normal and Abnormal Exits from the Halt Script Package Control Script Error and Exit ConditionsError Conditions and Package Movement for Failover Packages How the Network Manager Works Stationary and Relocatable IP AddressesAdding and Deleting Relocatable IP Addresses Types of IP AddressesMonitoring LAN Interfaces and Detecting Failure Link Level Load SharingLocal Switching Cluster Before Local Network Switching Where interface is the primary interface Cmmodnet -e interfaceRemote Switching Monitoring LAN Interfaces and Detecting Failure IP LevelReasons To Use IP Monitoring How the IP Monitor WorksFailure and Recovery Detection Times Example 1 If Local Switching is Configured Reporting Link-Level and IP-Level FailuresConstraints and Limitations See also Reporting Link-Level and IP-Level FailuresCmmodnet -e lan2 Example 2 If There Is No Local SwitchingAutomatic Port Aggregation Support for HP-UX Vlan Vlan ConfigurationsWhat is VLAN? Volume Managers for Data Storage Configuration RestrictionsTypes of Redundant Storage Additional Heartbeat RequirementsWhite papers About Device File Names Device Special FilesExamples of Mirrored Storage Physical Disks Within Shared Storage Units Multiple Devices Configured in Volume Groups Examples of Storage on Disk ArraysMultiple Paths to LUNs Types of Volume Manager HP-UX Logical Volume Manager LVMVeritas Volume Manager VxVM Propagation of Disk Groups in VxVMVeritas Cluster Volume Manager CVM Cluster Startup Time with CVMPropagation of Disk Groups with CVM For heartbeat requirements, see Redundant Heartbeat SubnetsComparison of Volume Managers Redundant Heartbeat SubnetsPros and Cons of Volume Managers with Serviceguard System Reset When a Node Fails What Happens when a Node Times OutResponses to Failures ExampleResponses to Hardware Failures Responses to Package and Service Failures Responses to Package and Generic Resources FailuresService Restarts Network Communication FailureServiceguard Memory Requirements Planning and Documenting an HA ClusterGeneral Planning Planning for ExpansionSample Cluster Configuration Hardware PlanningSPU Information Network InformationLAN Information Nnn.nnn.nnn.nnnUnder Cluster Configuration Parameters Scsi Addressing in Cluster ConfigurationDisk I/O Information DiskinfoPower Supply Planning Hardware Configuration WorksheetPower Supply Configuration Worksheet Cluster Lock PlanningQuorum Server Worksheet Using a Quorum ServerCluster Lock Disk and Re-formation Time Using Generic Resources to Monitor Volume Groups LVM PlanningUsing EMS to Monitor Volume Groups LVM Worksheet For more information, see Using the EMS HA MonitorsCVM and VxVM Planning Cluster Configuration Planning CVM and VxVM WorksheetPoints To Note Where cDSFs ResideAbout Cluster-wide Device Special Files cDSFs Limitations of cDSFs LVM Commands and cDSFsAbout Easy Deployment Limitations of Easy Deployment Heartbeat Subnet and Cluster Re-formation TimeAdvantages of Easy Deployment What Is IPv4-only Mode? What Is IPv6-Only Mode?Rules and Restrictions for IPv6-Only Mode Localhost ipv6-localhost ipv6-loopbackIPV6 or ANY What Is Mixed Mode?Recommendations for IPv6-Only Mode Cluster Configuration Parameters Rules and Restrictions for Mixed ModeCluster configuration file Name of the cluster as it will appear in the outputPlanning and Documenting an HA Cluster Happens when You Change the Quorum Configuration Go/hpux-serviceguard-docs under HP ServiceguardIPv4-Only,IPv6-Only, and Mixed Mode page 106 for 99 and Specifying a Quorum ServerSee also About Hostname Address Families IPv4-Only Hpux-serviceguard-docs under HP ServiceguardIPv6-Only, and Mixed Mode page 106 for important Sitepreferred or Configuration file see Configuring PackagesTheir Services page 227 and these in turn must Configuration Planning page 125 must be specified Cluster Is RunningCluster Configuration Planning You cannot change the heartbeat configuration while CVM/CFS on HP Serviceguard A.11.20 AprilProtocols and services. RPC assumes that each network To that LAN, to risk timeout without being servicedAlso What Happens when You Change the Quorum Configuration Online page 49 for important informationSee IPv6 Address Types Lock LUN page 189 for more informationFailbackpolicy When You Change the Quorum Configuration OnlineCluster is running, see Updating the Cluster Lock Disk See About Package Weights page 144 for more Planning and Documenting an HA Cluster See also What Happens when a Node Times Out 88, Cluster Daemon cmcld page 41,69, Monitoring LAN Interfaces and Detecting IP-Level FailuresDefault is Configuration file specifies one of two ways to decideWhen a network interface card has failed How Serviceguard will handle the recovery of the primarySee Monitoring LAN Interfaces and Detecting Failure IP Planning and Documenting an HA Cluster Package Configuration Planning Cluster Configuration Next StepLogical Volume and File System Planning Access Control Policies also known as Role Based AccessCVM 4.1 and later without CFS CVM 4.1 and later with CFS About the Volume Monitor Using the Volume MonitorOr --help Or --versionOr --log-file Or --log-levelVolumepath Planning for NFS-mounted File SystemsUsr/sbin/cmvolmond /dev/vg01/lvol1 /dev/vg01/lvol2 Usr/sbin/cmvolmond -t 10 /dev/vg00/lvol1Package Configuration Planning Choosing Switching and Failover Behavior Package Failover BehaviorParameters for Configuring Generic Resources Configuring a Generic ResourceExtended generic resource Cmmakepkg -i $SGCONF/pkg1/pkg1.conf -m sg/genericresourceCmcheckconf -v -P $SGCONF/pkg1/pkg1.conf Cmapplyconf -P $SGCONF/pkg1/pkg1.confCmviewcl -v -f line -p pkg1 grep genericresource Cmrunpkg pkg1Cmgetresource -r sfmdisk Cmsetresource -r sfmdisk -s upParameters for Configuring EMS Resources Online Reconfiguration of Generic ResourcesAbout Package Dependencies Simple DependenciesRules for Simple Dependencies Assume that we want to make pkg1 depend on pkg2Planning and Documenting an HA Cluster Dragging Rules for Simple Dependencies Planning and Documenting an HA Cluster Extended Dependencies See Rules for differentnode and anynode Dependencies Rules for Exclusionary DependenciesWhat Happens when a Package Fails Rules for differentnode and anynode DependenciesAbout Package Weights Package Weights and Node CapacitiesConfiguring Weights and Capacities Cmmakepkg 1m manpageWeightname packagelimit weightvalue Simple MethodNodename node1 Capacityname packagelimit For pkg2Defining Capacities Comprehensive MethodPoints to Keep in Mind Clustername cluster23 Nodename node1 Nodename node2Defining Weights Defining Default WeightsWeightname B Weightvalue Weightname a WeightvalueWeightname B Weightvalue Weightname a Rules and Guidelines Cmquerycl 1m manpageAbout External Scripts Pevmonitoringinterval Using Serviceguard Commands in an External Script Determining Why a Package Has Shut Down About Cross-Subnet FailoverLasthaltfailed Cmviewcl -v -f line displays a lasthaltfailed flagConfiguring a Package to Fail Over across Subnets Example Implications for Application DeploymentConfiguring a Package Next Steps Configuring nodenameConfiguring monitoredsubnetaccess Configuring ipsubnetnodePlanning for Changes in Cluster Size Building an HA Cluster Configuration Installing and Updating ServiceguardWhere Serviceguard Files Are Kept Preparing Your Systems Configuring the ClusterCreating Cluster-wide Device Special Files cDSFs Before You StartCreating cDSFs for a Group of Nodes Etc/cmcluster.confCsshsetup -r node2 Csshsetup -r -f /etc/cmcluster/sshhostsCmpreparecl -n nodename -n nodename Cmpreparecl -n node1 -n node2 -n node3 -n node4Using Easy Deployment Displaying the cDSF ConfigurationAdding a Node to a cDSF Group Removing a Node from a cDSF GroupCmquerycl -N $SGCONF/mynetwork Using Easy Deployment Commands to Configure the ClusterFor example Preparing Your Systems Building an HA Cluster Configuration PVG bus1 /dev/cdisk/disk14 /dev/cdisk/disk15 Format for entries in cmclnodelist is as follows Configuring Root-Level AccessAllowing Root Access to an Unconfigured Node Ensuring that the Root User on Another Node Is Recognized About identdAny of the aliases. Examples Configuring Name ResolutionOfficial hostname, as defined by hosts 4, for example Safeguarding against Loss of Name Resolution Services Ensuring Consistency of Kernel Configuration For NIS, enter two linesTuning Network and Kernel Parameters Enabling the Network Time ProtocolCreating Mirrors of Root Logical Volumes Make the new disk a boot diskChoosing Cluster Lock Disks Backing Up Cluster Lock Disk InformationSetting Up a Lock LUN Creating a Disk Partition on an HP Integrity System Usr/sbin/idisk -w -p -f partition.txt /dev/rdsk/c1t4d0Usr/sbin/idisk -w -p -f partition.txt /dev/rdisk/disk12 This will create three device files, for exampleExcluding Devices from Probing Defining the Lock LUNSetting Up and Running the Quorum Server Creating a Storage Infrastructure with LVMUsing the Generic Resources Disk Monitor Using the EMS Disk MonitorUsing Mirrored Individual Data Disks Creating Volume GroupsCreating Logical Volumes Setting Logical Volume TimeoutsCreating File Systems Lvchange -t 60 /dev/vg01/lvol1Distributing Volume Groups to Other Nodes Verify the configurationDeactivating the Volume Group Distributing the Volume GroupCreate a directory to mount the disk Deactivate the volume group on ftsys10Still on ftsys9, copy the map file to ftsys10 Making Physical Volume Group Files Consistent Creating Additional Volume GroupsCreating a Storage Infrastructure with VxVM Converting Disks from LVM to VxVMCreating Disk Groups Initializing Disks for VxVMInitializing Disks Previously Used by LVM Deporting Disk Groups Re-Importing Disk GroupsConfiguring the Cluster Clearimport at System Reboot TimeHere is an example of the command enter it all one line Cmquerycl -v -C $SGCONF/clust1.conf -n ftsys9 -n ftsys10Cmquerycl Options Speeding up the ProcessSpecifying the Address Family for the Cluster Hostnames Specifying the Address Family for the HeartbeatSpecifying a Lock Disk Specifying the Cluster LockGenerating a Network Template File Full Network ProbingSpecifying a Lock LUN Cmquerycl -v -n ftsys9 -n ftsys10Vgchange -c y /dev/vglock See also Choosing Cluster Lock DisksSpecifying a Quorum Server Obtaining Cross-Subnet InformationCmquerycl -q QSHost QSAddr -n ftsys9 -n ftsys10 -C Will produce the output such as the followingConfiguring the Cluster Specifying Maximum Number of Configured Packages Modifying the Membertimeout ParameterControlling Access to the Cluster Identifying Heartbeat SubnetsHow Access Roles Work Access RolesLevels of Access Setting up Access-Control PoliciesMonitor Fulladmin Packageadmin Userrole must be one of these three valuesUsername root Username john Userhost bitRole Conflicts Package versus Cluster Roles Adding Volume GroupsVerifying the Cluster Configuration Distributing the Binary Configuration File Differences between Legacy CFS and Modular CFS Storing Volume Group and Cluster Lock Configuration DataModular CFS packages v/s Legacy CFS packages Operational commands for Legacy CFS and Modular CFS Delete a mount point, check point, or snapshot in a package Cfscluster status Cfscluster config -t 900 -sPreparing the Cluster and the System Multi-node Package Creating the Disk Groups Creating the Disk Group Cluster PackagesCfsdgadm add logdata all=sw Cfsdgadm displayCreating Volumes Use the vxprint command to verifyCfsdgadm showpackage logdata Vxprint logfilesCmmakepkg -m sg/cfsall /etc/cmcluster/cfspkg1.ascii Create a package configuration fileFor instructions on creating modular CFS packages, see Cmapplyconf -P /etc/cmcluster/cfspkg1.ascii Apply the package configuration fileCmcheckconf -P /etc/cmcluster/cfspkg1.ascii Cmviewcl BdfCvmconcurrentdgoperations CfsconcurrentmountunmountoperationsCmmakepkg -m sg/cfsall /etc/cmcluster/ckpt1.ascii Package. For more information, see the manpageSee the mountvxfs 1m manpage Current primary, a primary migration is triggered toCmmakepkg -m sg/cfsall snap1.ascii Create a package configuration file for the snapshot imageVxassist -g cvmdg3 make vol1 100m vxvol -g cvmdg3 startall Mount points SnapshotmountoptionsInformation about the mount options, see Mountvxfs 1m manpageOnline reconfiguration of modular CFS package parameters Cmviewcl -v -f line -p cfspkg1 Cmcheckconf -P cfspkg1.asciiVerify the output Apply the configurationCmapplyconf -P cfspkg1.ascii Legacy Style of Packaging Modular Style of Packaging Managing Disk Groups and Mount Points Using Legacy Packages Creating Checkpoint and Snapshot Packages for CFS Fsckptadm -n create check2 /tmp/logdata/logfilesAssociate it with the cluster and mount it Cfsmount /tmp/checklogfilesIt is persistent Vxassist -g dg1 make vol1 100m vxvol -g dg1 startallAssociate it with the cluster Cfsmount /local/snap1 cmviewclYou need to do the tasks described in the following sections Initializing the Veritas Volume Manager Preparing the Cluster for Use with CVMIdentifying the Master Node Initializing Disks for CVMAdding Disk Groups to the Package Configuration Usr/lib/vxvm/bin/vxdisksetup -i c4t3d4Vxdg -s init logdata c0t3d2 Mirror Detachment Policies with CVMUsing Dsau during Configuration Checking Cluster Operation with Serviceguard ManagerChecking Cluster Operation with Serviceguard Commands Managing the Running ClusterPreventing Automatic Activation of LVM Volume Groups Setting up Autostart FeaturesManaging a Single-Node Cluster Here is an example of the /etc/rc.config.d/cmcluster fileChanging the System Message Deleting the Cluster Configuration Disabling identdSingle-Node Operation Change the cmclconfd entry in /etc/inetd.conf toBuilding an HA Cluster Configuration Configuring Packages and Their Services Choosing Package Modules Types of Package Failover, Multi-Node, System Multi-NodeFailoverpolicy Failbackpolicy Ipsubnet Ipaddress Differences between Failover and Multi-Node Packages Package Modules and ParametersBase Package Modules Cmmakepkg -m sg/all $SGCONF/sg-allOptional Modules Optional Package ModulesBase Modules Locallanfailoverallowed Package Parameter Explanations ExternalscriptCmmakepkg $SGCONF/sg-all Autorun NodefailfastenabledNodename Runscripttimeout HaltscripttimeoutSuccessorhalttimeout ScriptlogfileOperationsequence LoglevelPriority DependencynameDependencycondition For more information, see About Package DependenciesDependencylocation Specifies where the dependencycondition must be metWeightname, weightvalue Monitoredsubnetaccess LocallanfailoverallowedMonitoredsubnet ClusterinterconnectsubnetIpsubnet Ipaddress New for A.11.18 for both modular and legacy packagesIpsubnet Servicename See the package configuration file for more examplesIpsubnetnode IpaddressServicecmd ServicerestartServicefailfastenabled ServicehalttimeoutGenericresourceupcriteria Defines when the status of a generic resource is evaluatedGenericresourceevaluationtype Resourcename Name of a resource to be monitoredResourcepollinginterval ResourcestartEnablethreadedvgchange ResourceupvalueConcurrentvgchangeoperations Cannot lock /etc/lvmconf//lvmlock still tryingVxvolcmd VgchangecmdCvmactivationcmd Killprocessesaccessingrawdevices CvmdgVxvmdg VxvmdgretryFsfsckopt -s Fstype vxfs ConcurrentfsckoperationsConcurrentmountandumountoperations FsmountretrycountFsname FsserverFsdirectory FstypeFsmountopt FsumountoptFsfsckopt PevUsername UserhostUserrole Additional Parameters Used Only by Legacy PackagesGenerating the Package Configuration File Before You StartCmmakepkg Examples Mkdir $SGCONF/pkg1Editing the Configuration File Next StepPackagetype. Enter failover, multinode, or systemmultinode See About Package Dependencies page 137 for more informationEditing the Configuration File Vg vg01 Vg vg02 Verifying and Applying the Package Configuration # vxdg -tfC import dg01 Adding the Package to the ClusterHow Control Scripts Manage VxVM Disk Groups Cluster and Package Maintenance Reviewing Cluster and Package StatusViewing Dependencies Cmviewcl -r A.11.16Viewing CFS Multi-Node Information Types of Cluster and Package StatesCluster Status Node Status and StateReviewing Cluster and Package Status Unknown DownNormal Running Status Examples of Cluster and Package StatesFailover and Failback Policies Quorum Server Status CFS Package StatusStatus After Halting a Package Then run cmviewcl -v, we’ll see If we use the following commandStatus After Moving the Package to Another Node Status After Auto Run is Enabled Output of the cmviewcl command is now as followsAfter we halt ftsys10 with the following command Status After Halting a NodeViewing Information about System Multi-Node Packages This output can be seen on both ftsys9 and ftsys10Viewing Information about Unowned Packages Cmviewcl -v -p SG-CFS-pkg Checking Status of the Cluster File System CFSStatus of the Packages in a Cluster File System Status of CFS Modular Disk Group and Mount Point Packages Cmviewcl -v -p mpdg1Status of Legacy CVM Disk Group Packages Ftsys9 Sw swChecking the Cluster Configuration and Components Ftsys10Status of Legacy CFS Mount Point Packages Cfsmntadm display -v /tmp/logdata/logfilesUser-created files if you specify them Etc/nsswitch.conf Etc/servicesChecking Cluster Components Verifying Cluster Components Cmapplyconf 1mRun cmcheckconf -C Setting up Periodic Cluster Verification Managing the Cluster and NodesLimitations See the cron 1m manpage for more informationStarting the Cluster When all Nodes are Down Adding Previously Configured Nodes to a Running ClusterUsing Serviceguard Commands to Start the Cluster Cmruncl -v -n ftsys9 -n ftsys10Removing Nodes from Participation in a Running Cluster Halting the Entire ClusterCmrunnode -v ftsys8 Cmhaltnode -f -v ftsys9Rules and Restrictions Automatically Restarting the ClusterWhat You Can Do Managing the Cluster and Nodes Additional Points To Note Halting the Cluster and Detaching its Packages Halting a Node and Detaching its PackagesHalting a Detached Package Cmrunnode node1 Managing Packages and ServicesStarting a Package Using Serviceguard Commands to Start a Package Halting a PackageStarting a Package that Has Dependencies Halting a Package that Has DependenciesChanging Package Switching Behavior Using Serviceguard Commands to Halt a PackageChanging Package Switching with Serviceguard Commands Moving a Failover PackageCmmodpkg -d -n lptest3 pkg1 Maintaining a Package Maintenance ModeSee Performing Maintenance Using Maintenance Mode Cluster and Package Maintenance Performing Maintenance Using Maintenance Mode ProcedureExcluding Modules in Partial-Startup Maintenance Mode Cmrunpkg -m sg/packageip pkg1Reconfiguring a Cluster Cmrunpkg -e sg/service pkg1Cmrunpkg -m sg/services -e sg/packageip pkg1 Types of Changes to the Cluster ConfigurationChange to the Cluster Configuration Previewing the Effect of Cluster ChangesUsing Preview mode for Commands and in Serviceguard Manager Mode see Maintaining a Package Maintenance ModeWhat You Can Preview Cmmodpkg -e -t pkg1You would see output something like this Using cmevalCmeval -v newstate.in Updating the Cluster Lock Configuration Reconfiguring a Halted ClusterUpdating the Cluster Lock Disk Configuration Online Updating the Cluster Lock LUN Configuration OnlineReconfiguring a Running Cluster Cmapplyconf -C clconfig.asciiAdding Nodes to the Cluster While the Cluster is Running Cmgetconf -c cluster1 temp.asciiCmquerycl -C clconfig.ascii -c cluster1 -n ftsys8 -n ftsys9 What You Can DoWhat You Must Keep in Mind Cmquerycl -c cluster1 -C clconfig.ascii Example Adding a Heartbeat LANCmgetconf clconfig.ascii Removing a LAN or Vlan Interface from a NodeSee also Replacing LAN or Fibre Channel Cards Changing the LVM Configuration while the Cluster is RunningChanging the VxVM or CVM Storage Configuration Cmgetconf -c clustername clconfig.ascii Configuring a Legacy PackageCreating the Legacy Package Configuration Mkdir /etc/cmcluster/pkg1 Configuring a Package in StagesEditing the Package Configuration File Cluster and Package Maintenance Creating the Package Control Script Cmmakepkg -s /etc/cmcluster/pkg1/pkg1.shCustomizing the Package Control Script Adding Serviceguard Commands in Customer Defined Functions Support for Additional ProductsVerifying the Package Configuration Distributing the ConfigurationCopying Package Control Scripts with HP-UX commands Cmcheckconf -v -P /etc/cmcluster/pkg1/pkg1.confConfiguring Cross-Subnet Failover Configuring nodenameReconfiguring a Package Configuring monitoredsubnetaccessCreating Subnet-Specific Package Control Scripts IP0 = SUBNET0 IP1 = SUBNET1Cmgetconf -p pkg1 pkg1.conf Reconfiguring a Package on a Running ClusterMigrating a Legacy Package to a Modular Package Reconfiguring a Package on a Halted Cluster Adding a Package to a Running ClusterDeleting a Package from a Running Cluster Cmhaltpkg mypkg Cmdeleteconf -p mypkgCmapplyconf -v -P app1.conf Unmount the shared file system cfsumount mount pointCmmodpkg -R -s myservice pkg1 Resetting the Service Restart CounterAllowable Package States During Reconfiguration Change servicerestart modular package Types of Changes to PackagesLocallanfailoverallowed Change vxvolcmd Cfsmountoptions Responding to Cluster Events Changes that Will Trigger WarningsSingle-Node Operation Disabling ServiceguardRemoving Serviceguard from a System Troubleshooting Your Cluster Testing Cluster OperationStart the Cluster using Serviceguard Manager Testing the Package ManagerMonitoring Hardware Testing the Cluster ManagerTesting the Network Manager Using System Fault Management Service Using Event Monitoring ServiceUsing EMS Event Monitoring Service Hardware Monitors Hardware Monitors and Persistence RequestsUsing HP Isee HP Instant Support Enterprise Edition Replacing a Faulty Array MechanismReplacing a Faulty Mechanism in an HA Enclosure Replacing DisksReplacing a Lock Disk Replacing a Lock LUNOnline Hardware Maintenance with In-line Scsi Terminator Cmdisklock reset /dev/dsk/c0t1d1Replacing I/O Cards Replacing Scsi Host Bus AdaptersReplacing LAN or Fibre Channel Cards Offline ReplacementOnline Replacement Replacing a Failed Quorum Server System After Replacing the CardTroubleshooting Approaches Using cmquerycl and cmcheckconf Using cmviewclReviewing Package IP Addresses Reviewing the System Log FileReviewing Object Manager Log Files Sample System Log EntriesFollowing is an example of a successful package starting Cmreadlog /var/opt/cmom/cmomd.logReviewing Serviceguard Manager Log Files Reviewing Configuration FilesUsing the cmcheckconf Command Reviewing the System Multi-node Package FilesSolving Problems Using the cmviewconf CommandReviewing the LAN Configuration Serviceguard Command HangsNslookup ftsys9 Networking and Security Configuration ErrorsCluster Re-formations Caused by Temporary Conditions System Administration Errors Package Control Script Hangs or FailuresFuser -kulogical-volume umount logical-volume Problems with Cluster File System CFS Llt, gab Vxfen W cvm CfsProblems with VxVM Disk Groups Package Movement ErrorsNode and Network Failures Force Import and Deport After Node FailureTroubleshooting the Quorum Server Authorization File ProblemsTimeout Problems Access denied to quorum serverMessages Enterprise Cluster Master Toolkit Designing Highly Available Cluster Applications Automating Application OperationDefine Application Startup and Shutdown Controlling the Speed of Application FailoverInsulate Users from Outages Use Raw Volumes Replicate Non-Data File SystemsEvaluate the Use of JFS Minimize Data LossUse Restartable Transactions Use CheckpointsDesign for Multiple Servers Balance Checkpoint Frequency with PerformanceAvoid Node-Specific Information Designing Applications to Run on Multiple SystemsDesign for Replicated Data Sites Avoid Using SPU IDs or MAC Addresses Assign Unique Names to ApplicationsObtain Enough IP Addresses Allow Multiple Instances on Same SystemBind to Relocatable IP Addresses Use uname2 With CareBind to a Fixed Port Give Each Application its Own Volume Group Use Multiple Destinations for SNA ApplicationsAvoid File Locking Call bind before connectHelp menu for ndd -h ipstrongesmodel Etc/rc.config.d/nddconf as followsUsr/sbin/route add net default 128.17.17.1 1 source Usr/sbin/route delete net default 128.17.17.1 1 source Restoring Client ConnectionsBe Able to Monitor Applications Handling Application FailuresCreate Applications to be Failure Tolerant Reducing Time Needed for Application Upgrades and Patches Provide for Rolling UpgradesMinimizing Planned Downtime Do Not Change the Data Layout Between ReleasesProviding Online Application Reconfiguration Documenting Maintenance OperationsDefining Baseline Application Behavior on a Single System Integrating HA Applications with ServiceguardChecklist for Integrating HA Applications Integrating HA Applications in Multiple Systems Testing the Cluster Move it backSpecial Considerations for Upgrade to Serviceguard A.11.19 Software UpgradesSpecial Considerations for Upgrade to Serviceguard A.11.20 Types of Upgrade How To Tell when the Cluster Re-formation Is CompleteRolling Upgrade Rolling Upgrade Using DRDGuidelines for Rolling Upgrade Restrictions for DRD UpgradesNon-Rolling Upgrade Non-Rolling Upgrade Using DRDPerforming a Rolling Upgrade Limitations of Rolling UpgradesMigrating cmclnodelist entries from A.11.15 or earlier Running the Rolling UpgradeKeeping Kernels Consistent Performing a Rolling Upgrade Using DRD Running the Rolling Upgrade Using DRDHalt the first node, as follows Example of a Rolling UpgradeStep Running Cluster with Packages Moved to Node Node 1 Rejoining the Cluster Repeat the process on node 2. Halt the node, as followsGuidelines for Non-Rolling Upgrade Performing a Non-Rolling UpgradeSteps for a Non-Rolling Upgrade Using DRD Performing a Non-Rolling Upgrade Using DRDLimitations of Non-Rolling Upgrades using DRD Guidelines for Migrating a Cluster with Cold Install Checklist for MigrationWorksheet for Hardware Planning Power Supply WorksheetBlank Planning Worksheets LVM Volume Group and Physical Volume Worksheet Quorum Server WorksheetCluster Configuration Worksheet VxVM Disk Group and Disk WorksheetPackage Configuration Worksheet Package Configuration Worksheet Loading VxVM Migrating Volume GroupsMigrating from LVM to VxVM Data Storage Customizing Packages for VxVM Mntdg0202, respectivelyRestart the package Removing LVM Volume GroupsCustomizing Packages for CVM Migrating from Legacy CFS Packages to Modular CFS Packages Textual Representation of IPv6 Addresses IPv6 Network SupportIPv6 Address Types IPv6 Address Prefix Unicast AddressesIPv4 and IPv6 Compatibility IPv4 Compatible IPv6 AddressesAggregatable Global Unicast Addresses Link-Local AddressesSite-Local Addresses Multicast AddressesNetwork Configuration Restrictions Example Configurations Local Primary/Standby LAN PatternsNdd -get /dev/ip6 ip6nddadsolicitcount Ndd -set /dev/ip6 ip6nddadsolicitcountnExample Configurations 384 IPv6 Network Support Using Serviceguard Manager Before Using HP Serviceguard Manager Setting UpAccessing Serviceguard Manager About the Online Help SystemLaunching Serviceguard Manager Accessing Serviceguard ManagerScenario 1 Single cluster management Opt/hpsmh/bin/hpsmh autostartSystem Management Homepage with Serviceguard Manager From the left-hand panel, expand Cluster by Type Expand HP Serviceguard, and click on a Serviceguard clusterSign Membertimeout Maximum and Minimum Values for ParametersLaunching Monitoring Scripts Monitoring Script for Generic ResourcesSample scripts Launching Monitoring Scripts Template of a Monitoring Script I L I T Y N C T I O N S Monitoring Script for Generic Resources Template of a Monitoring Script Migrating EMS Resources to Generic Resources Start the package Identify the equivalent SFM style resource monitorIndex APA399 Cvmactivationcmd Firstclusterlockpv LAN INONLYORINOUT, 69 Inout Pollingtarget defined Qsaddr Servicename Vxvmdg
Related manuals
Manual 32 pages 5.87 Kb
Top Page Image Contents