HP Serviceguard manual Examples of Cluster and Package States, Failover and Failback Policies

Page 265

Failover and Failback Policies

Failover packages can be configured with one of two values for the failover_policy parameter (page 237), as displayed in the output of cmviewcl -v:

•configured_node. The package fails over to the next node in the node_name list in the package configuration file (page 235).

•min_package_node. The package fails over to the node in the cluster that has the fewest running packages.

Failover packages can also be configured with one of two values for the failback_policy parameter (page 238), and these are also displayed in the output of cmviewcl -v:

•automatic: Following a failover, a package returns to its primary node when the primary node becomes available again.

•manual: Following a failover, a package will run on the adoptive node until moved back to its original node by a system administrator.

Examples of Cluster and Package States

The following sample output from the cmviewcl -vcommand shows status for the cluster in the sample configuration.

Normal Running Status

Everything is running normally; both nodes in the cluster are running, and the packages are in their primary locations.

CLUSTER	STATUS
example	up
NODE	STATUS	STATE
ftsys9	up	running

Network_Parameters:
INTERFACE	STATUS	PATH	NAME
PRIMARY	up	56/36.1	lan0
STANDBY	up	60/6	lan1
PACKAGE	STATUS	STATE	AUTO_RUN	NODE
pkg1	up	running	enabled	ftsys9

Policy_Parameters:

POLICY_NAME CONFIGURED_VALUE

Failover configured_node

Failback manual

Script_Parameters:
ITEM	STATUS	MAX_RESTARTS	RESTARTS	NAME
Service	up	0	0	service1
Service	up	0	0	sfm_disk_monitor
Subnet	up	0	0	15.13.168.0
Generic Resource	up			sfm_disk

Node_Switching_Parameters:
NODE_TYPE		STATUS	SWITCHING	NAME
Primary		up	enabled	ftsys9	(current)
Alternate		up	enabled	ftsys10
NODE	STATUS	STATE
ftsys10	up	running
Network_Parameters:
INTERFACE	STATUS	PATH	NAME
PRIMARY	up	28.1	lan0
STANDBY	up	32.1	lan1
PACKAGE	STATUS	STATE	AUTO_RUN	NODE
pkg2	up	running	enabled	ftsys10

Reviewing Cluster and Package Status 265

Image 265

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 Software Upgrades 357 Integrating HA Applications with Serviceguard 354349 Migrating from LVM to VxVM Data Storage 374 Blank Planning Worksheets 369377 IPv6 Network Support 378396 Using Serviceguard Manager 385Index 398 Publishing History Publishing HistoryPreface Related Publications Securing Serviceguard and other Serviceguard white papersWhat is Serviceguard? Serviceguard at a GlanceShows what happens in a failover situation FailoverTypical Cluster After Failover About Veritas CFS and CVM from SymantecUsing SAM Using Serviceguard ManagerRoadmap for Configuring Clusters and Packages What are the Distributed Systems Administration Utilities?Usr/sbin/sam -w Tasks in Configuring a Serviceguard Cluster Redundancy of Cluster Components Understanding Serviceguard Hardware ConfigurationsRules and Restrictions Redundant Network ComponentsRedundant LANs Redundant Ethernet ConfigurationConfiguration Tasks Cross-Subnet ConfigurationsFor legacy packages, see Configuring Cross-Subnet Failover RestrictionsFor More Information Replacing Failed Network Cards Redundant Disk StorageSupported Disk Interfaces Data Protection Disk Arrays using RAID Levels and Multiple Data PathsDisk Mirroring About MultipathingMonitoring VxVM and CVM Disks Monitoring LVM Disks Through Event Monitoring ServiceReplacing Failed Disk Mechanisms Replacing Failed I/O CardsMirrored Disks Connected for High Availability Sample Scsi Disk ConfigurationsCluster with High Availability Disk Array Sample Fibre Channel Disk ConfigurationLarger Clusters Redundant Power SuppliesPoint to Point Connections to Storage Devices Active/Standby ModelEight-Node Cluster with XP or EMC Disk Array Serviceguard Architecture Understanding Serviceguard Software ComponentsServiceguard Daemons Cluster Daemon cmcld Configuration Daemon cmclconfdFile Management Daemon cmfileassistd Cluster Logical Volume Manager Daemon cmlvmdSyslog Log Daemon cmlogd Cluster Object Manager Daemon cmomdQuorum Server Daemon qs Service Assistant Daemon cmservicedNetwork Manager Daemon cmnetd Lock LUN Daemon cmdisklockdHow the Cluster Manager Works Configuring the ClusterProxy Daemon cmproxyd CFS ComponentsManual Startup of Entire Cluster Heartbeat MessagesDynamic Cluster Re-formation Automatic Cluster StartupCluster Quorum to Prevent Split-Brain Syndrome Cluster LockLock Requirements Use of a Lock LUN or LVM Lock Disk as the Cluster LockSingle Lock Disk or LUN Use of the Quorum Server as the Cluster LockDual Lock Disk Quorum Server Operation No Cluster LockPackage Types How the Package Manager WorksNon-failover Packages Failover PackagesFailover Packages’ Switching Behavior Deciding When and Where to Run and Halt Failover PackagesBefore Package Switching Automatic Rotating Standby Package Configuration DataRotating Standby Configuration before Failover Failback Policy Configurednode Policy Packages after FailoverAutomatic Failback Configuration After Failover Using the Generic Resources Monitoring Service Using Older Package Configuration FilesUnderstanding Serviceguard Software Components Using the EMS HA Monitors Using the Event Monitoring ServiceSee also Using Generic Resources to Monitor Volume Groups See also Using EMS to Monitor Volume GroupsWhat Makes a Package Run? How Packages RunLegacy Package Time Line Showing Important Events Before the Control Script StartsPackage Time Line Legacy Package During Run Script ExecutionWhile Services are Running Service Startup with cmrunservNormal and Abnormal Exits from the Run Script During Halt Script Execution When a Package is Halted with a CommandLegacy Package Time Line for Halt Script Execution Error Conditions and Package Movement for Failover Packages Package Control Script Error and Exit ConditionsNormal and Abnormal Exits from the Halt Script Stationary and Relocatable IP Addresses How the Network Manager WorksTypes of IP Addresses Adding and Deleting Relocatable IP AddressesLoad Sharing Monitoring LAN Interfaces and Detecting Failure Link LevelLocal Switching Cluster Before Local Network Switching Cmmodnet -e interface Where interface is the primary interfaceMonitoring LAN Interfaces and Detecting Failure IP Level Remote SwitchingHow the IP Monitor Works Reasons To Use IP MonitoringFailure and Recovery Detection Times Reporting Link-Level and IP-Level Failures Example 1 If Local Switching is ConfiguredConstraints and Limitations See also Reporting Link-Level and IP-Level FailuresAutomatic Port Aggregation Example 2 If There Is No Local SwitchingCmmodnet -e lan2 What is VLAN? Vlan ConfigurationsSupport for HP-UX Vlan Configuration Restrictions Volume Managers for Data StorageTypes of Redundant Storage Additional Heartbeat RequirementsExamples of Mirrored Storage About Device File Names Device Special FilesWhite papers Physical Disks Within Shared Storage Units Examples of Storage on Disk Arrays Multiple Devices Configured in Volume GroupsMultiple Paths to LUNs HP-UX Logical Volume Manager LVM Types of Volume ManagerVeritas Volume Manager VxVM Propagation of Disk Groups in VxVMCluster Startup Time with CVM Veritas Cluster Volume Manager CVMPropagation of Disk Groups with CVM For heartbeat requirements, see Redundant Heartbeat SubnetsRedundant Heartbeat Subnets Comparison of Volume ManagersPros and Cons of Volume Managers with Serviceguard What Happens when a Node Times Out System Reset When a Node FailsResponses to Failures ExampleResponses to Hardware Failures Responses to Package and Generic Resources Failures Responses to Package and Service FailuresNetwork Communication Failure Service RestartsPlanning and Documenting an HA Cluster Serviceguard Memory RequirementsGeneral Planning Planning for ExpansionHardware Planning Sample Cluster ConfigurationNetwork Information SPU InformationLAN Information Nnn.nnn.nnn.nnnScsi Addressing in Cluster Configuration Under Cluster Configuration ParametersDiskinfo Disk I/O InformationHardware Configuration Worksheet Power Supply PlanningCluster Lock Planning Power Supply Configuration WorksheetCluster Lock Disk and Re-formation Time Using a Quorum ServerQuorum Server Worksheet LVM Planning Using Generic Resources to Monitor Volume GroupsUsing EMS to Monitor Volume Groups CVM and VxVM Planning For more information, see Using the EMS HA MonitorsLVM Worksheet CVM and VxVM Worksheet Cluster Configuration PlanningAbout Cluster-wide Device Special Files cDSFs Where cDSFs ResidePoints To Note About Easy Deployment LVM Commands and cDSFsLimitations of cDSFs Advantages of Easy Deployment Heartbeat Subnet and Cluster Re-formation TimeLimitations of Easy Deployment What Is IPv6-Only Mode? What Is IPv4-only Mode?Rules and Restrictions for IPv6-Only Mode Localhost ipv6-localhost ipv6-loopbackRecommendations for IPv6-Only Mode What Is Mixed Mode?IPV6 or ANY Rules and Restrictions for Mixed Mode Cluster Configuration ParametersCluster configuration file Name of the cluster as it will appear in the outputPlanning and Documenting an HA Cluster Go/hpux-serviceguard-docs under HP Serviceguard Happens when You Change the Quorum ConfigurationIPv4-Only,IPv6-Only, and Mixed Mode page 106 for 99 and Specifying a Quorum ServerIPv6-Only, and Mixed Mode page 106 for important Hpux-serviceguard-docs under HP ServiceguardSee also About Hostname Address Families IPv4-Only Their Services page 227 and these in turn must Configuration file see Configuring PackagesSitepreferred or Cluster Is Running Configuration Planning page 125 must be specifiedCluster Configuration Planning CVM/CFS on HP Serviceguard A.11.20 April You cannot change the heartbeat configuration whileProtocols and services. RPC assumes that each network To that LAN, to risk timeout without being servicedConfiguration Online page 49 for important information Also What Happens when You Change the QuorumSee IPv6 Address Types Lock LUN page 189 for more informationCluster is running, see Updating the Cluster Lock Disk When You Change the Quorum Configuration OnlineFailbackpolicy See About Package Weights page 144 for more Planning and Documenting an HA Cluster 88, Cluster Daemon cmcld page 41, See also What Happens when a Node Times Out69, Monitoring LAN Interfaces and Detecting IP-Level FailuresConfiguration file specifies one of two ways to decide Default isWhen 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 Cluster Configuration Next Step Package Configuration PlanningLogical 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 Using the Volume Monitor About the Volume MonitorOr --version Or --helpOr --log-file Or --log-levelPlanning for NFS-mounted File Systems VolumepathUsr/sbin/cmvolmond /dev/vg01/lvol1 /dev/vg01/lvol2 Usr/sbin/cmvolmond -t 10 /dev/vg00/lvol1Package Configuration Planning Package Failover Behavior Choosing Switching and Failover BehaviorConfiguring a Generic Resource Parameters for Configuring Generic ResourcesExtended generic resource Cmmakepkg -i $SGCONF/pkg1/pkg1.conf -m sg/genericresourceCmapplyconf -P $SGCONF/pkg1/pkg1.conf Cmcheckconf -v -P $SGCONF/pkg1/pkg1.confCmrunpkg pkg1 Cmviewcl -v -f line -p pkg1 grep genericresourceCmgetresource -r sfmdisk Cmsetresource -r sfmdisk -s upOnline Reconfiguration of Generic Resources Parameters for Configuring EMS ResourcesSimple Dependencies About Package 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 Rules for Exclusionary Dependencies See Rules for differentnode and anynode DependenciesRules for differentnode and anynode Dependencies What Happens when a Package FailsPackage Weights and Node Capacities About Package WeightsConfiguring Weights and Capacities Cmmakepkg 1m manpageSimple Method Weightname packagelimit weightvalueNodename node1 Capacityname packagelimit For pkg2Points to Keep in Mind Comprehensive MethodDefining Capacities Nodename node2 Clustername cluster23 Nodename node1Defining Default Weights Defining WeightsWeightname B Weightvalue Weightname a Weightname a WeightvalueWeightname B Weightvalue Cmquerycl 1m manpage Rules and GuidelinesAbout External Scripts Pevmonitoringinterval Using Serviceguard Commands in an External Script About Cross-Subnet Failover Determining Why a Package Has Shut DownLasthaltfailed Cmviewcl -v -f line displays a lasthaltfailed flagImplications for Application Deployment Configuring a Package to Fail Over across Subnets ExampleConfiguring nodename Configuring a Package Next StepsConfiguring monitoredsubnetaccess Configuring ipsubnetnodePlanning for Changes in Cluster Size Installing and Updating Serviceguard Building an HA Cluster ConfigurationWhere Serviceguard Files Are Kept Preparing Your Systems Configuring the ClusterBefore You Start Creating Cluster-wide Device Special Files cDSFsCreating cDSFs for a Group of Nodes Etc/cmcluster.confCsshsetup -r -f /etc/cmcluster/sshhosts Csshsetup -r node2Cmpreparecl -n nodename -n nodename Cmpreparecl -n node1 -n node2 -n node3 -n node4Displaying the cDSF Configuration Using Easy DeploymentAdding a Node to a cDSF Group Removing a Node from a cDSF GroupFor example Using Easy Deployment Commands to Configure the ClusterCmquerycl -N $SGCONF/mynetwork Preparing Your Systems Building an HA Cluster Configuration PVG bus1 /dev/cdisk/disk14 /dev/cdisk/disk15 Allowing Root Access to an Unconfigured Node Configuring Root-Level AccessFormat for entries in cmclnodelist is as follows About identd Ensuring that the Root User on Another Node Is RecognizedOfficial hostname, as defined by hosts 4, for example Configuring Name ResolutionAny of the aliases. Examples Safeguarding against Loss of Name Resolution Services For NIS, enter two lines Ensuring Consistency of Kernel ConfigurationEnabling the Network Time Protocol Tuning Network and Kernel ParametersMake the new disk a boot disk Creating Mirrors of Root Logical VolumesBacking Up Cluster Lock Disk Information Choosing Cluster Lock DisksSetting Up a Lock LUN Usr/sbin/idisk -w -p -f partition.txt /dev/rdsk/c1t4d0 Creating a Disk Partition on an HP Integrity SystemUsr/sbin/idisk -w -p -f partition.txt /dev/rdisk/disk12 This will create three device files, for exampleDefining the Lock LUN Excluding Devices from ProbingCreating a Storage Infrastructure with LVM Setting Up and Running the Quorum ServerUsing the EMS Disk Monitor Using the Generic Resources Disk MonitorCreating Volume Groups Using Mirrored Individual Data DisksSetting Logical Volume Timeouts Creating Logical VolumesCreating File Systems Lvchange -t 60 /dev/vg01/lvol1Verify the configuration Distributing Volume Groups to Other NodesDeactivating the Volume Group Distributing the Volume GroupStill on ftsys9, copy the map file to ftsys10 Deactivate the volume group on ftsys10Create a directory to mount the disk Creating Additional Volume Groups Making Physical Volume Group Files ConsistentCreating a Storage Infrastructure with VxVM Converting Disks from LVM to VxVMInitializing Disks Previously Used by LVM Initializing Disks for VxVMCreating Disk Groups Re-Importing Disk Groups Deporting Disk GroupsClearimport at System Reboot Time Configuring the ClusterHere is an example of the command enter it all one line Cmquerycl -v -C $SGCONF/clust1.conf -n ftsys9 -n ftsys10Speeding up the Process Cmquerycl OptionsSpecifying the Address Family for the Cluster Hostnames Specifying the Address Family for the HeartbeatSpecifying the Cluster Lock Specifying a Lock DiskGenerating a Network Template File Full Network ProbingCmquerycl -v -n ftsys9 -n ftsys10 Specifying a Lock LUNVgchange -c y /dev/vglock See also Choosing Cluster Lock DisksObtaining Cross-Subnet Information Specifying a Quorum ServerCmquerycl -q QSHost QSAddr -n ftsys9 -n ftsys10 -C Will produce the output such as the followingConfiguring the Cluster Modifying the Membertimeout Parameter Specifying Maximum Number of Configured PackagesControlling Access to the Cluster Identifying Heartbeat SubnetsAccess Roles How Access Roles WorkSetting up Access-Control Policies Levels of AccessUserrole must be one of these three values Monitor Fulladmin PackageadminRole Conflicts Username john Userhost bitUsername root Verifying the Cluster Configuration Adding Volume GroupsPackage versus Cluster Roles Distributing the Binary Configuration File Modular CFS packages v/s Legacy CFS packages Storing Volume Group and Cluster Lock Configuration DataDifferences between Legacy CFS and Modular CFS Operational commands for Legacy CFS and Modular CFS Delete a mount point, check point, or snapshot in a package Preparing the Cluster and the System Multi-node Package Cfscluster config -t 900 -sCfscluster status Creating the Disk Group Cluster Packages Creating the Disk GroupsCfsdgadm add logdata all=sw Cfsdgadm displayUse the vxprint command to verify Creating VolumesCfsdgadm showpackage logdata Vxprint logfilesFor instructions on creating modular CFS packages, see Create a package configuration fileCmmakepkg -m sg/cfsall /etc/cmcluster/cfspkg1.ascii Cmcheckconf -P /etc/cmcluster/cfspkg1.ascii Apply the package configuration fileCmapplyconf -P /etc/cmcluster/cfspkg1.ascii Bdf CmviewclCvmconcurrentdgoperations CfsconcurrentmountunmountoperationsPackage. For more information, see the manpage Cmmakepkg -m sg/cfsall /etc/cmcluster/ckpt1.asciiSee the mountvxfs 1m manpage Current primary, a primary migration is triggered toVxassist -g cvmdg3 make vol1 100m vxvol -g cvmdg3 startall Create a package configuration file for the snapshot imageCmmakepkg -m sg/cfsall snap1.ascii Snapshotmountoptions Mount pointsInformation about the mount options, see Mountvxfs 1m manpageOnline reconfiguration of modular CFS package parameters Cmcheckconf -P cfspkg1.ascii Cmviewcl -v -f line -p cfspkg1Cmapplyconf -P cfspkg1.ascii Apply the configurationVerify the output Legacy Style of Packaging Modular Style of Packaging Managing Disk Groups and Mount Points Using Legacy Packages Fsckptadm -n create check2 /tmp/logdata/logfiles Creating Checkpoint and Snapshot Packages for CFSAssociate it with the cluster and mount it Cfsmount /tmp/checklogfilesVxassist -g dg1 make vol1 100m vxvol -g dg1 startall It is persistentAssociate it with the cluster Cfsmount /local/snap1 cmviewclYou need to do the tasks described in the following sections Preparing the Cluster for Use with CVM Initializing the Veritas Volume ManagerIdentifying the Master Node Initializing Disks for CVMUsr/lib/vxvm/bin/vxdisksetup -i c4t3d4 Adding Disk Groups to the Package ConfigurationVxdg -s init logdata c0t3d2 Mirror Detachment Policies with CVMChecking Cluster Operation with Serviceguard Manager Using Dsau during ConfigurationChecking Cluster Operation with Serviceguard Commands Managing the Running ClusterSetting up Autostart Features Preventing Automatic Activation of LVM Volume GroupsChanging the System Message Here is an example of the /etc/rc.config.d/cmcluster fileManaging a Single-Node Cluster Disabling identd Deleting the Cluster ConfigurationSingle-Node Operation Change the cmclconfd entry in /etc/inetd.conf toBuilding an HA Cluster Configuration Configuring Packages and Their Services Types of Package Failover, Multi-Node, System Multi-Node Choosing Package ModulesFailoverpolicy Failbackpolicy Ipsubnet Ipaddress Package Modules and Parameters Differences between Failover and Multi-Node PackagesBase Package Modules Cmmakepkg -m sg/all $SGCONF/sg-allBase Modules Optional Package ModulesOptional Modules Locallanfailoverallowed Externalscript Package Parameter ExplanationsCmmakepkg $SGCONF/sg-all Nodename NodefailfastenabledAutorun Haltscripttimeout RunscripttimeoutScriptlogfile SuccessorhalttimeoutOperationsequence LoglevelDependencyname PriorityFor more information, see About Package Dependencies DependencyconditionWeightname, weightvalue Specifies where the dependencycondition must be metDependencylocation Locallanfailoverallowed MonitoredsubnetaccessMonitoredsubnet ClusterinterconnectsubnetIpsubnet New for A.11.18 for both modular and legacy packagesIpsubnet Ipaddress See the package configuration file for more examples ServicenameIpsubnetnode IpaddressServicerestart ServicecmdServicefailfastenabled ServicehalttimeoutGenericresourceevaluationtype Defines when the status of a generic resource is evaluatedGenericresourceupcriteria Name of a resource to be monitored ResourcenameResourcepollinginterval ResourcestartResourceupvalue EnablethreadedvgchangeConcurrentvgchangeoperations Cannot lock /etc/lvmconf//lvmlock still tryingCvmactivationcmd VgchangecmdVxvolcmd Cvmdg KillprocessesaccessingrawdevicesVxvmdg VxvmdgretryConcurrentfsckoperations Fsfsckopt -s Fstype vxfsConcurrentmountandumountoperations FsmountretrycountFsserver FsnameFsdirectory FstypeFsumountopt FsmountoptFsfsckopt PevUserhost UsernameUserrole Additional Parameters Used Only by Legacy PackagesBefore You Start Generating the Package Configuration FileCmmakepkg Examples Mkdir $SGCONF/pkg1Next Step Editing the Configuration FileSee About Package Dependencies page 137 for more information Packagetype. Enter failover, multinode, or systemmultinodeEditing the Configuration File Vg vg01 Vg vg02 Verifying and Applying the Package Configuration How Control Scripts Manage VxVM Disk Groups Adding the Package to the Cluster# vxdg -tfC import dg01 Reviewing Cluster and Package Status Cluster and Package MaintenanceViewing Dependencies Cmviewcl -r A.11.16Types of Cluster and Package States Viewing CFS Multi-Node InformationCluster Status Node Status and StateReviewing Cluster and Package Status Down UnknownFailover and Failback Policies Examples of Cluster and Package StatesNormal Running Status CFS Package Status Quorum Server StatusStatus After Halting a Package Status After Moving the Package to Another Node If we use the following commandThen run cmviewcl -v, we’ll see Output of the cmviewcl command is now as follows Status After Auto Run is EnabledAfter we halt ftsys10 with the following command Status After Halting a NodeViewing Information about Unowned Packages This output can be seen on both ftsys9 and ftsys10Viewing Information about System Multi-Node Packages Status of the Packages in a Cluster File System Checking Status of the Cluster File System CFSCmviewcl -v -p SG-CFS-pkg Cmviewcl -v -p mpdg1 Status of CFS Modular Disk Group and Mount Point PackagesStatus of Legacy CVM Disk Group Packages Ftsys9 Sw swFtsys10 Checking the Cluster Configuration and ComponentsStatus of Legacy CFS Mount Point Packages Cfsmntadm display -v /tmp/logdata/logfilesChecking Cluster Components Etc/nsswitch.conf Etc/servicesUser-created files if you specify them Cmapplyconf 1m Verifying Cluster ComponentsRun cmcheckconf -C Managing the Cluster and Nodes Setting up Periodic Cluster VerificationLimitations See the cron 1m manpage for more informationAdding Previously Configured Nodes to a Running Cluster Starting the Cluster When all Nodes are DownUsing Serviceguard Commands to Start the Cluster Cmruncl -v -n ftsys9 -n ftsys10Halting the Entire Cluster Removing Nodes from Participation in a Running ClusterCmrunnode -v ftsys8 Cmhaltnode -f -v ftsys9What You Can Do Automatically Restarting the ClusterRules and Restrictions Managing the Cluster and Nodes Additional Points To Note Halting a Detached Package Halting a Node and Detaching its PackagesHalting the Cluster and Detaching its Packages Starting a Package Managing Packages and ServicesCmrunnode node1 Halting a Package Using Serviceguard Commands to Start a PackageStarting a Package that Has Dependencies Halting a Package that Has DependenciesUsing Serviceguard Commands to Halt a Package Changing Package Switching BehaviorChanging Package Switching with Serviceguard Commands Moving a Failover PackageSee Performing Maintenance Using Maintenance Mode Maintaining a Package Maintenance ModeCmmodpkg -d -n lptest3 pkg1 Cluster and Package Maintenance Procedure Performing Maintenance Using Maintenance ModeCmrunpkg -m sg/packageip pkg1 Excluding Modules in Partial-Startup Maintenance ModeCmrunpkg -e sg/service pkg1 Reconfiguring a ClusterCmrunpkg -m sg/services -e sg/packageip pkg1 Types of Changes to the Cluster ConfigurationPreviewing the Effect of Cluster Changes Change to the Cluster ConfigurationMode see Maintaining a Package Maintenance Mode Using Preview mode for Commands and in Serviceguard ManagerWhat You Can Preview Cmmodpkg -e -t pkg1Cmeval -v newstate.in Using cmevalYou would see output something like this Reconfiguring a Halted Cluster Updating the Cluster Lock ConfigurationUpdating the Cluster Lock Disk Configuration Online Updating the Cluster Lock LUN Configuration OnlineCmapplyconf -C clconfig.ascii Reconfiguring a Running ClusterAdding Nodes to the Cluster While the Cluster is Running Cmgetconf -c cluster1 temp.asciiWhat You Can Do Cmquerycl -C clconfig.ascii -c cluster1 -n ftsys8 -n ftsys9What You Must Keep in Mind Example Adding a Heartbeat LAN Cmquerycl -c cluster1 -C clconfig.asciiRemoving a LAN or Vlan Interface from a Node Cmgetconf clconfig.asciiChanging the VxVM or CVM Storage Configuration Changing the LVM Configuration while the Cluster is RunningSee also Replacing LAN or Fibre Channel Cards Creating the Legacy Package Configuration Configuring a Legacy PackageCmgetconf -c clustername clconfig.ascii Editing the Package Configuration File Configuring a Package in StagesMkdir /etc/cmcluster/pkg1 Cluster and Package Maintenance Cmmakepkg -s /etc/cmcluster/pkg1/pkg1.sh Creating the Package Control ScriptCustomizing the Package Control Script Support for Additional Products Adding Serviceguard Commands in Customer Defined FunctionsDistributing the Configuration Verifying the Package ConfigurationCopying Package Control Scripts with HP-UX commands Cmcheckconf -v -P /etc/cmcluster/pkg1/pkg1.confConfiguring nodename Configuring Cross-Subnet FailoverConfiguring monitoredsubnetaccess Reconfiguring a PackageCreating Subnet-Specific Package Control Scripts IP0 = SUBNET0 IP1 = SUBNET1Migrating a Legacy Package to a Modular Package Reconfiguring a Package on a Running ClusterCmgetconf -p pkg1 pkg1.conf Adding a Package to a Running Cluster Reconfiguring a Package on a Halted ClusterCmhaltpkg mypkg Cmdeleteconf -p mypkg Deleting a Package from a Running ClusterCmapplyconf -v -P app1.conf Unmount the shared file system cfsumount mount pointAllowable Package States During Reconfiguration Resetting the Service Restart CounterCmmodpkg -R -s myservice pkg1 Types of Changes to Packages Change servicerestart modular packageLocallanfailoverallowed Change vxvolcmd Cfsmountoptions Changes that Will Trigger Warnings Responding to Cluster EventsRemoving Serviceguard from a System Disabling ServiceguardSingle-Node Operation Testing Cluster Operation Troubleshooting Your ClusterStart the Cluster using Serviceguard Manager Testing the Package ManagerTesting the Network Manager Testing the Cluster ManagerMonitoring Hardware Using Event Monitoring Service Using System Fault Management ServiceUsing EMS Event Monitoring Service Hardware Monitors Hardware Monitors and Persistence RequestsReplacing a Faulty Array Mechanism Using HP Isee HP Instant Support Enterprise EditionReplacing a Faulty Mechanism in an HA Enclosure Replacing DisksReplacing a Lock LUN Replacing a Lock DiskCmdisklock reset /dev/dsk/c0t1d1 Online Hardware Maintenance with In-line Scsi TerminatorReplacing I/O Cards Replacing Scsi Host Bus AdaptersOnline Replacement Offline ReplacementReplacing LAN or Fibre Channel Cards After Replacing the Card Replacing a Failed Quorum Server SystemUsing cmquerycl and cmcheckconf Using cmviewcl Troubleshooting ApproachesReviewing Package IP Addresses Reviewing the System Log FileSample System Log Entries Reviewing Object Manager Log FilesFollowing is an example of a successful package starting Cmreadlog /var/opt/cmom/cmomd.logReviewing Configuration Files Reviewing Serviceguard Manager Log FilesUsing the cmcheckconf Command Reviewing the System Multi-node Package FilesUsing the cmviewconf Command Solving ProblemsReviewing the LAN Configuration Serviceguard Command HangsCluster Re-formations Caused by Temporary Conditions Networking and Security Configuration ErrorsNslookup ftsys9 Package Control Script Hangs or Failures System Administration ErrorsFuser -kulogical-volume umount logical-volume Llt, gab Vxfen W cvm Cfs Problems with Cluster File System CFSPackage Movement Errors Problems with VxVM Disk GroupsNode and Network Failures Force Import and Deport After Node FailureAuthorization File Problems Troubleshooting the Quorum ServerTimeout Problems Access denied to quorum serverMessages Enterprise Cluster Master Toolkit Automating Application Operation Designing Highly Available Cluster ApplicationsInsulate Users from Outages Controlling the Speed of Application FailoverDefine Application Startup and Shutdown Replicate Non-Data File Systems Use Raw VolumesEvaluate the Use of JFS Minimize Data LossUse Checkpoints Use Restartable TransactionsDesign for Multiple Servers Balance Checkpoint Frequency with PerformanceDesign for Replicated Data Sites Designing Applications to Run on Multiple SystemsAvoid Node-Specific Information Assign Unique Names to Applications Avoid Using SPU IDs or MAC AddressesObtain Enough IP Addresses Allow Multiple Instances on Same SystemBind to a Fixed Port Use uname2 With CareBind to Relocatable IP Addresses Use Multiple Destinations for SNA Applications Give Each Application its Own Volume GroupAvoid File Locking Call bind before connectUsr/sbin/route add net default 128.17.17.1 1 source Etc/rc.config.d/nddconf as followsHelp menu for ndd -h ipstrongesmodel Restoring Client Connections Usr/sbin/route delete net default 128.17.17.1 1 sourceCreate Applications to be Failure Tolerant Handling Application FailuresBe Able to Monitor Applications Provide for Rolling Upgrades Reducing Time Needed for Application Upgrades and PatchesMinimizing Planned Downtime Do Not Change the Data Layout Between ReleasesDocumenting Maintenance Operations Providing Online Application ReconfigurationChecklist for Integrating HA Applications Integrating HA Applications with ServiceguardDefining Baseline Application Behavior on a Single System Integrating HA Applications in Multiple Systems Move it back Testing the ClusterSpecial Considerations for Upgrade to Serviceguard A.11.20 Software UpgradesSpecial Considerations for Upgrade to Serviceguard A.11.19 How To Tell when the Cluster Re-formation Is Complete Types of UpgradeRolling Upgrade Rolling Upgrade Using DRDRestrictions for DRD Upgrades Guidelines for Rolling UpgradeNon-Rolling Upgrade Non-Rolling Upgrade Using DRDLimitations of Rolling Upgrades Performing a Rolling UpgradeKeeping Kernels Consistent Running the Rolling UpgradeMigrating cmclnodelist entries from A.11.15 or earlier Running the Rolling Upgrade Using DRD Performing a Rolling Upgrade Using DRDStep Example of a Rolling UpgradeHalt the first node, as follows Running Cluster with Packages Moved to Node Repeat the process on node 2. Halt the node, as follows Node 1 Rejoining the ClusterPerforming a Non-Rolling Upgrade Guidelines for Non-Rolling UpgradeLimitations of Non-Rolling Upgrades using DRD Performing a Non-Rolling Upgrade Using DRDSteps for a Non-Rolling Upgrade Using DRD Checklist for Migration Guidelines for Migrating a Cluster with Cold InstallBlank Planning Worksheets Power Supply WorksheetWorksheet for Hardware Planning Quorum Server Worksheet LVM Volume Group and Physical Volume WorksheetVxVM Disk Group and Disk Worksheet Cluster Configuration WorksheetPackage Configuration Worksheet Package Configuration Worksheet Migrating from LVM to VxVM Data Storage Migrating Volume GroupsLoading VxVM Mntdg0202, respectively Customizing Packages for VxVMCustomizing Packages for CVM Removing LVM Volume GroupsRestart the package Migrating from Legacy CFS Packages to Modular CFS Packages IPv6 Address Types IPv6 Network SupportTextual Representation of IPv6 Addresses Unicast Addresses IPv6 Address PrefixIPv4 and IPv6 Compatibility IPv4 Compatible IPv6 AddressesLink-Local Addresses Aggregatable Global Unicast AddressesSite-Local Addresses Multicast AddressesNetwork Configuration Restrictions Local Primary/Standby LAN Patterns Example ConfigurationsNdd -get /dev/ip6 ip6nddadsolicitcount Ndd -set /dev/ip6 ip6nddadsolicitcountnExample Configurations 384 IPv6 Network Support Before Using HP Serviceguard Manager Setting Up Using Serviceguard ManagerAccessing Serviceguard Manager About the Online Help SystemAccessing Serviceguard Manager Launching Serviceguard ManagerScenario 1 Single cluster management Opt/hpsmh/bin/hpsmh autostartSystem Management Homepage with Serviceguard Manager Sign Expand HP Serviceguard, and click on a Serviceguard clusterFrom the left-hand panel, expand Cluster by Type Maximum and Minimum Values for Parameters MembertimeoutSample scripts Monitoring Script for Generic ResourcesLaunching Monitoring 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 Identify the equivalent SFM style resource monitor Start the packageAPA Index399 Cvmactivationcmd Firstclusterlockpv LAN INONLYORINOUT, 69 Inout Pollingtarget defined Qsaddr Servicename Vxvmdg

Related manuals

Manual 32 pages 5.87 Kb