Manuals / HP / Computer Equipment / Software

HP Serviceguard manual Building an HA Cluster Configuration

Models: Serviceguard

1 407

Download 407 pages 39.81 Kb

Page 226

It is recommended that you do not proceed with the configuration operation unless you are sure these nodes are permanently unavailable.Do you want to continue?

Reply Yes to remove the configuration. Later, if the inaccessible node becomes available, you should run the cmdeleteconf command on that node to remove the configuration file.

226 Building an HA Cluster Configuration

Image 226

HP Serviceguard manual Building an HA Cluster Configuration

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 377 Blank Planning Worksheets 369Migrating from LVM to VxVM Data Storage 374 IPv6 Network Support 378396 Using Serviceguard Manager 385Index 398 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 SAMRoadmap for Configuring Clusters and Packages What are the Distributed Systems Administration Utilities?Usr/sbin/sam -w Tasks in Configuring a Serviceguard Cluster Understanding Serviceguard Hardware Configurations Redundancy of Cluster ComponentsRedundant Network Components Rules and RestrictionsRedundant Ethernet Configuration Redundant LANsFor legacy packages, see Configuring Cross-Subnet Failover Cross-Subnet ConfigurationsConfiguration Tasks RestrictionsFor More Information Replacing Failed Network Cards Redundant Disk StorageSupported Disk Interfaces Disk Mirroring Disk Arrays using RAID Levels and Multiple Data PathsData Protection About MultipathingReplacing Failed Disk Mechanisms Monitoring LVM Disks Through Event Monitoring ServiceMonitoring VxVM and CVM Disks 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 Architecture Understanding Serviceguard Software ComponentsServiceguard Daemons Configuration Daemon cmclconfd Cluster Daemon cmcldSyslog Log Daemon cmlogd Cluster Logical Volume Manager Daemon cmlvmdFile Management Daemon cmfileassistd Cluster Object Manager Daemon cmomdNetwork Manager Daemon cmnetd Service Assistant Daemon cmservicedQuorum Server Daemon qs Lock LUN Daemon cmdisklockdProxy Daemon cmproxyd Configuring the ClusterHow the Cluster Manager Works CFS ComponentsHeartbeat Messages Manual Startup of Entire ClusterCluster Quorum to Prevent Split-Brain Syndrome Automatic Cluster StartupDynamic Cluster Re-formation Cluster LockUse of a Lock LUN or LVM Lock Disk as the Cluster Lock Lock RequirementsSingle Lock Disk or LUN Use of the Quorum Server as the Cluster LockDual Lock Disk No Cluster Lock Quorum Server OperationNon-failover Packages How the Package Manager WorksPackage Types 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 See also Using Generic Resources to Monitor Volume Groups Using the Event Monitoring ServiceUsing the EMS HA Monitors 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 PackageWhile Services are Running Service Startup with cmrunservNormal and Abnormal Exits from the Run Script When a Package is Halted with a Command During Halt Script ExecutionLegacy 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 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 Constraints and Limitations Example 1 If Local Switching is ConfiguredReporting Link-Level and IP-Level Failures 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 Types of Redundant Storage Volume Managers for Data StorageConfiguration Restrictions Additional Heartbeat RequirementsExamples of Mirrored Storage About Device File Names Device Special FilesWhite papers Physical Disks Within Shared Storage Units Multiple Devices Configured in Volume Groups Examples of Storage on Disk ArraysMultiple Paths to LUNs Veritas Volume Manager VxVM Types of Volume ManagerHP-UX Logical Volume Manager LVM Propagation of Disk Groups in VxVMPropagation of Disk Groups with CVM Veritas Cluster Volume Manager CVMCluster Startup Time with CVM For heartbeat requirements, see Redundant Heartbeat SubnetsComparison of Volume Managers Redundant Heartbeat SubnetsPros and Cons of Volume Managers with Serviceguard Responses to Failures System Reset When a Node FailsWhat Happens when a Node Times Out ExampleResponses to Hardware Failures Responses to Package and Service Failures Responses to Package and Generic Resources FailuresService Restarts Network Communication FailureGeneral Planning Serviceguard Memory RequirementsPlanning and Documenting an HA Cluster Planning for ExpansionSample Cluster Configuration Hardware PlanningLAN Information SPU InformationNetwork 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 PlanningCluster Lock Disk and Re-formation Time Using a Quorum ServerQuorum Server Worksheet Using Generic Resources to Monitor Volume Groups LVM PlanningUsing EMS to Monitor Volume Groups CVM and VxVM Planning For more information, see Using the EMS HA MonitorsLVM Worksheet Cluster Configuration Planning CVM and VxVM WorksheetAbout 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 Rules and Restrictions for IPv6-Only Mode What Is IPv4-only Mode?What Is IPv6-Only Mode? Localhost ipv6-localhost ipv6-loopbackRecommendations for IPv6-Only Mode What Is Mixed Mode?IPV6 or ANY Cluster configuration file Cluster Configuration ParametersRules and Restrictions for Mixed Mode Name of the cluster as it will appear in the outputPlanning and Documenting an HA Cluster IPv4-Only,IPv6-Only, and Mixed Mode page 106 for Happens when You Change the Quorum ConfigurationGo/hpux-serviceguard-docs under HP Serviceguard 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 Configuration Planning page 125 must be specified Cluster Is RunningCluster Configuration Planning Protocols and services. RPC assumes that each network You cannot change the heartbeat configuration whileCVM/CFS on HP Serviceguard A.11.20 April To that LAN, to risk timeout without being servicedSee IPv6 Address Types Also What Happens when You Change the QuorumConfiguration Online page 49 for important information 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 69, Monitoring LAN Interfaces and Detecting See also What Happens when a Node Times Out88, Cluster Daemon cmcld page 41, IP-Level FailuresWhen a network interface card has failed Default isConfiguration file specifies one of two ways to decide How Serviceguard will handle the recovery of the primarySee Monitoring LAN Interfaces and Detecting Failure IP Planning and Documenting an HA Cluster Logical Volume and File System Planning Package Configuration PlanningCluster Configuration Next Step 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 --log-file Or --helpOr --version Or --log-levelUsr/sbin/cmvolmond /dev/vg01/lvol1 /dev/vg01/lvol2 VolumepathPlanning for NFS-mounted File Systems Usr/sbin/cmvolmond -t 10 /dev/vg00/lvol1Package Configuration Planning Choosing Switching and Failover Behavior Package Failover BehaviorExtended generic resource Parameters for Configuring Generic ResourcesConfiguring a Generic Resource Cmmakepkg -i $SGCONF/pkg1/pkg1.conf -m sg/genericresourceCmcheckconf -v -P $SGCONF/pkg1/pkg1.conf Cmapplyconf -P $SGCONF/pkg1/pkg1.confCmgetresource -r sfmdisk Cmviewcl -v -f line -p pkg1 grep genericresourceCmrunpkg pkg1 Cmsetresource -r sfmdisk -s upParameters for Configuring EMS Resources Online Reconfiguration of Generic ResourcesRules for Simple Dependencies About Package DependenciesSimple 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 DependenciesConfiguring Weights and Capacities About Package WeightsPackage Weights and Node Capacities Cmmakepkg 1m manpageNodename node1 Capacityname packagelimit Weightname packagelimit weightvalueSimple Method For pkg2Points to Keep in Mind Comprehensive MethodDefining Capacities Clustername cluster23 Nodename node1 Nodename node2Defining Weights Defining Default WeightsWeightname B Weightvalue Weightname a Weightname a WeightvalueWeightname B Weightvalue Rules and Guidelines Cmquerycl 1m manpageAbout External Scripts Pevmonitoringinterval Using Serviceguard Commands in an External Script Lasthaltfailed Determining Why a Package Has Shut DownAbout Cross-Subnet Failover Cmviewcl -v -f line displays a lasthaltfailed flagConfiguring a Package to Fail Over across Subnets Example Implications for Application DeploymentConfiguring monitoredsubnetaccess Configuring a Package Next StepsConfiguring nodename Configuring ipsubnetnodePlanning for Changes in Cluster Size Where Serviceguard Files Are Kept Building an HA Cluster ConfigurationInstalling and Updating Serviceguard Preparing Your Systems Configuring the ClusterCreating cDSFs for a Group of Nodes Creating Cluster-wide Device Special Files cDSFsBefore You Start Etc/cmcluster.confCmpreparecl -n nodename -n nodename Csshsetup -r node2Csshsetup -r -f /etc/cmcluster/sshhosts Cmpreparecl -n node1 -n node2 -n node3 -n node4Adding a Node to a cDSF Group Using Easy DeploymentDisplaying the cDSF Configuration 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 Ensuring that the Root User on Another Node Is Recognized About identdOfficial hostname, as defined by hosts 4, for example Configuring Name ResolutionAny of the aliases. Examples 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 Usr/sbin/idisk -w -p -f partition.txt /dev/rdisk/disk12 Creating a Disk Partition on an HP Integrity SystemUsr/sbin/idisk -w -p -f partition.txt /dev/rdsk/c1t4d0 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 File Systems Creating Logical VolumesSetting Logical Volume Timeouts Lvchange -t 60 /dev/vg01/lvol1Deactivating the Volume Group Distributing Volume Groups to Other NodesVerify the configuration 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 a Storage Infrastructure with VxVM Making Physical Volume Group Files ConsistentCreating Additional Volume Groups Converting Disks from LVM to VxVMInitializing Disks Previously Used by LVM Initializing Disks for VxVMCreating Disk Groups Deporting Disk Groups Re-Importing Disk GroupsHere is an example of the command enter it all one line Configuring the ClusterClearimport at System Reboot Time Cmquerycl -v -C $SGCONF/clust1.conf -n ftsys9 -n ftsys10Specifying the Address Family for the Cluster Hostnames Cmquerycl OptionsSpeeding up the Process Specifying the Address Family for the HeartbeatGenerating a Network Template File Specifying a Lock DiskSpecifying the Cluster Lock Full Network ProbingVgchange -c y /dev/vglock Specifying a Lock LUNCmquerycl -v -n ftsys9 -n ftsys10 See also Choosing Cluster Lock DisksCmquerycl -q QSHost QSAddr -n ftsys9 -n ftsys10 -C Specifying a Quorum ServerObtaining Cross-Subnet Information Will produce the output such as the followingConfiguring the Cluster Controlling Access to the Cluster Specifying Maximum Number of Configured PackagesModifying the Membertimeout Parameter Identifying Heartbeat SubnetsHow Access Roles Work Access RolesLevels of Access Setting up Access-Control PoliciesMonitor Fulladmin Packageadmin Userrole must be one of these three valuesRole 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 Cfsdgadm add logdata all=sw Creating the Disk GroupsCreating the Disk Group Cluster Packages Cfsdgadm displayCfsdgadm showpackage logdata Creating VolumesUse the vxprint command to verify 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 Cvmconcurrentdgoperations CmviewclBdf CfsconcurrentmountunmountoperationsSee the mountvxfs 1m manpage Cmmakepkg -m sg/cfsall /etc/cmcluster/ckpt1.asciiPackage. For more information, see the 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 Information about the mount options, see Mount pointsSnapshotmountoptions Mountvxfs 1m manpageOnline reconfiguration of modular CFS package parameters Cmviewcl -v -f line -p cfspkg1 Cmcheckconf -P cfspkg1.asciiCmapplyconf -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 Associate it with the cluster and mount it Creating Checkpoint and Snapshot Packages for CFSFsckptadm -n create check2 /tmp/logdata/logfiles Cfsmount /tmp/checklogfilesAssociate it with the cluster It is persistentVxassist -g dg1 make vol1 100m vxvol -g dg1 startall Cfsmount /local/snap1 cmviewclYou need to do the tasks described in the following sections Identifying the Master Node Initializing the Veritas Volume ManagerPreparing the Cluster for Use with CVM Initializing Disks for CVMVxdg -s init logdata c0t3d2 Adding Disk Groups to the Package ConfigurationUsr/lib/vxvm/bin/vxdisksetup -i c4t3d4 Mirror Detachment Policies with CVMChecking Cluster Operation with Serviceguard Commands Using Dsau during ConfigurationChecking Cluster Operation with Serviceguard Manager Managing the Running ClusterPreventing Automatic Activation of LVM Volume Groups Setting up Autostart FeaturesChanging the System Message Here is an example of the /etc/rc.config.d/cmcluster fileManaging a Single-Node Cluster Single-Node Operation Deleting the Cluster ConfigurationDisabling identd 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 Base Package Modules Differences between Failover and Multi-Node PackagesPackage Modules and Parameters Cmmakepkg -m sg/all $SGCONF/sg-allBase Modules Optional Package ModulesOptional Modules Locallanfailoverallowed Package Parameter Explanations ExternalscriptCmmakepkg $SGCONF/sg-all Nodename NodefailfastenabledAutorun Runscripttimeout HaltscripttimeoutOperationsequence SuccessorhalttimeoutScriptlogfile LoglevelPriority DependencynameDependencycondition For more information, see About Package DependenciesWeightname, weightvalue Specifies where the dependencycondition must be metDependencylocation Monitoredsubnet MonitoredsubnetaccessLocallanfailoverallowed ClusterinterconnectsubnetIpsubnet New for A.11.18 for both modular and legacy packagesIpsubnet Ipaddress Ipsubnetnode ServicenameSee the package configuration file for more examples IpaddressServicefailfastenabled ServicecmdServicerestart ServicehalttimeoutGenericresourceevaluationtype Defines when the status of a generic resource is evaluatedGenericresourceupcriteria Resourcepollinginterval ResourcenameName of a resource to be monitored ResourcestartConcurrentvgchangeoperations EnablethreadedvgchangeResourceupvalue Cannot lock /etc/lvmconf//lvmlock still tryingCvmactivationcmd VgchangecmdVxvolcmd Vxvmdg KillprocessesaccessingrawdevicesCvmdg VxvmdgretryConcurrentmountandumountoperations Fsfsckopt -s Fstype vxfsConcurrentfsckoperations FsmountretrycountFsdirectory FsnameFsserver FstypeFsfsckopt FsmountoptFsumountopt PevUserrole UsernameUserhost Additional Parameters Used Only by Legacy PackagesCmmakepkg Examples Generating the Package Configuration FileBefore You Start 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 How Control Scripts Manage VxVM Disk Groups Adding the Package to the Cluster# vxdg -tfC import dg01 Viewing Dependencies Cluster and Package MaintenanceReviewing Cluster and Package Status Cmviewcl -r A.11.16Cluster Status Viewing CFS Multi-Node InformationTypes of Cluster and Package States Node Status and StateReviewing Cluster and Package Status Unknown DownFailover and Failback Policies Examples of Cluster and Package StatesNormal Running Status Quorum Server Status CFS Package 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 After we halt ftsys10 with the following command Status After Auto Run is EnabledOutput of the cmviewcl command is now as follows 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 Status of Legacy CVM Disk Group Packages Status of CFS Modular Disk Group and Mount Point PackagesCmviewcl -v -p mpdg1 Ftsys9 Sw swStatus of Legacy CFS Mount Point Packages Checking the Cluster Configuration and ComponentsFtsys10 Cfsmntadm display -v /tmp/logdata/logfilesChecking Cluster Components Etc/nsswitch.conf Etc/servicesUser-created files if you specify them Verifying Cluster Components Cmapplyconf 1mRun cmcheckconf -C Limitations Setting up Periodic Cluster VerificationManaging the Cluster and Nodes See the cron 1m manpage for more informationUsing Serviceguard Commands to Start the Cluster Starting the Cluster When all Nodes are DownAdding Previously Configured Nodes to a Running Cluster Cmruncl -v -n ftsys9 -n ftsys10Cmrunnode -v ftsys8 Removing Nodes from Participation in a Running ClusterHalting the Entire Cluster 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 Starting a Package that Has Dependencies Using Serviceguard Commands to Start a PackageHalting a Package Halting a Package that Has DependenciesChanging Package Switching with Serviceguard Commands Changing Package Switching BehaviorUsing Serviceguard Commands to Halt a Package Moving a Failover PackageSee Performing Maintenance Using Maintenance Mode Maintaining a Package Maintenance ModeCmmodpkg -d -n lptest3 pkg1 Cluster and Package Maintenance Performing Maintenance Using Maintenance Mode ProcedureExcluding Modules in Partial-Startup Maintenance Mode Cmrunpkg -m sg/packageip pkg1Cmrunpkg -m sg/services -e sg/packageip pkg1 Reconfiguring a ClusterCmrunpkg -e sg/service pkg1 Types of Changes to the Cluster ConfigurationChange to the Cluster Configuration Previewing the Effect of Cluster ChangesWhat You Can Preview Using Preview mode for Commands and in Serviceguard ManagerMode see Maintaining a Package Maintenance Mode Cmmodpkg -e -t pkg1Cmeval -v newstate.in Using cmevalYou would see output something like this Updating the Cluster Lock Disk Configuration Online Updating the Cluster Lock ConfigurationReconfiguring a Halted Cluster Updating the Cluster Lock LUN Configuration OnlineAdding Nodes to the Cluster While the Cluster is Running Reconfiguring a Running ClusterCmapplyconf -C clconfig.ascii 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 NodeChanging 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 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 ProductsCopying Package Control Scripts with HP-UX commands Verifying the Package ConfigurationDistributing the Configuration Cmcheckconf -v -P /etc/cmcluster/pkg1/pkg1.confConfiguring Cross-Subnet Failover Configuring nodenameCreating Subnet-Specific Package Control Scripts Reconfiguring a PackageConfiguring monitoredsubnetaccess IP0 = SUBNET0 IP1 = SUBNET1Migrating a Legacy Package to a Modular Package Reconfiguring a Package on a Running ClusterCmgetconf -p pkg1 pkg1.conf Reconfiguring a Package on a Halted Cluster Adding a Package to a Running ClusterCmapplyconf -v -P app1.conf Deleting a Package from a Running ClusterCmhaltpkg mypkg Cmdeleteconf -p mypkg Unmount the shared file system cfsumount mount pointAllowable Package States During Reconfiguration Resetting the Service Restart CounterCmmodpkg -R -s myservice pkg1 Change servicerestart modular package Types of Changes to PackagesLocallanfailoverallowed Change vxvolcmd Cfsmountoptions Responding to Cluster Events Changes that Will Trigger WarningsRemoving Serviceguard from a System Disabling ServiceguardSingle-Node Operation Start the Cluster using Serviceguard Manager Troubleshooting Your ClusterTesting Cluster Operation Testing the Package ManagerTesting the Network Manager Testing the Cluster ManagerMonitoring Hardware Using EMS Event Monitoring Service Hardware Monitors Using System Fault Management ServiceUsing Event Monitoring Service Hardware Monitors and Persistence RequestsReplacing a Faulty Mechanism in an HA Enclosure Using HP Isee HP Instant Support Enterprise EditionReplacing a Faulty Array Mechanism Replacing DisksReplacing a Lock Disk Replacing a Lock LUNReplacing I/O Cards Online Hardware Maintenance with In-line Scsi TerminatorCmdisklock reset /dev/dsk/c0t1d1 Replacing Scsi Host Bus AdaptersOnline Replacement Offline ReplacementReplacing LAN or Fibre Channel Cards Replacing a Failed Quorum Server System After Replacing the CardReviewing Package IP Addresses Troubleshooting ApproachesUsing cmquerycl and cmcheckconf Using cmviewcl Reviewing the System Log FileFollowing is an example of a successful package starting Reviewing Object Manager Log FilesSample System Log Entries Cmreadlog /var/opt/cmom/cmomd.logUsing the cmcheckconf Command Reviewing Serviceguard Manager Log FilesReviewing Configuration Files Reviewing the System Multi-node Package FilesReviewing the LAN Configuration Solving ProblemsUsing the cmviewconf Command Serviceguard Command HangsCluster Re-formations Caused by Temporary Conditions Networking and Security Configuration ErrorsNslookup ftsys9 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 CfsNode and Network Failures Problems with VxVM Disk GroupsPackage Movement Errors Force Import and Deport After Node FailureTimeout Problems Troubleshooting the Quorum ServerAuthorization File Problems Access denied to quorum serverMessages Enterprise Cluster Master Toolkit Designing Highly Available Cluster Applications Automating Application OperationInsulate Users from Outages Controlling the Speed of Application FailoverDefine Application Startup and Shutdown Evaluate the Use of JFS Use Raw VolumesReplicate Non-Data File Systems Minimize Data LossDesign for Multiple Servers Use Restartable TransactionsUse Checkpoints Balance Checkpoint Frequency with PerformanceDesign for Replicated Data Sites Designing Applications to Run on Multiple SystemsAvoid Node-Specific Information Obtain Enough IP Addresses Avoid Using SPU IDs or MAC AddressesAssign Unique Names to Applications Allow Multiple Instances on Same SystemBind to a Fixed Port Use uname2 With CareBind to Relocatable IP Addresses Avoid File Locking Give Each Application its Own Volume GroupUse Multiple Destinations for SNA Applications 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 Usr/sbin/route delete net default 128.17.17.1 1 source Restoring Client ConnectionsCreate Applications to be Failure Tolerant Handling Application FailuresBe Able to Monitor Applications Minimizing Planned Downtime Reducing Time Needed for Application Upgrades and PatchesProvide for Rolling Upgrades Do Not Change the Data Layout Between ReleasesProviding Online Application Reconfiguration Documenting Maintenance OperationsChecklist for Integrating HA Applications Integrating HA Applications with ServiceguardDefining Baseline Application Behavior on a Single System Integrating HA Applications in Multiple Systems Testing the Cluster Move it backSpecial Considerations for Upgrade to Serviceguard A.11.20 Software UpgradesSpecial Considerations for Upgrade to Serviceguard A.11.19 Rolling Upgrade Types of UpgradeHow To Tell when the Cluster Re-formation Is Complete Rolling Upgrade Using DRDNon-Rolling Upgrade Guidelines for Rolling UpgradeRestrictions for DRD Upgrades Non-Rolling Upgrade Using DRDPerforming a Rolling Upgrade Limitations of Rolling UpgradesKeeping Kernels Consistent Running the Rolling UpgradeMigrating cmclnodelist entries from A.11.15 or earlier Performing a Rolling Upgrade Using DRD Running the Rolling Upgrade Using DRDStep Example of a Rolling UpgradeHalt the first node, as follows 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 UpgradeLimitations of Non-Rolling Upgrades using DRD Performing a Non-Rolling Upgrade Using DRDSteps for a Non-Rolling Upgrade Using DRD Guidelines for Migrating a Cluster with Cold Install Checklist for MigrationBlank Planning Worksheets Power Supply WorksheetWorksheet for Hardware Planning LVM Volume Group and Physical Volume Worksheet Quorum Server WorksheetCluster Configuration Worksheet VxVM Disk Group and Disk WorksheetPackage Configuration Worksheet Package Configuration Worksheet Migrating from LVM to VxVM Data Storage Migrating Volume GroupsLoading VxVM Customizing Packages for VxVM Mntdg0202, respectivelyCustomizing 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 IPv4 and IPv6 Compatibility IPv6 Address PrefixUnicast Addresses IPv4 Compatible IPv6 AddressesSite-Local Addresses Aggregatable Global Unicast AddressesLink-Local Addresses Multicast AddressesNetwork Configuration Restrictions Ndd -get /dev/ip6 ip6nddadsolicitcount Example ConfigurationsLocal Primary/Standby LAN Patterns Ndd -set /dev/ip6 ip6nddadsolicitcountnExample Configurations 384 IPv6 Network Support Accessing Serviceguard Manager Using Serviceguard ManagerBefore Using HP Serviceguard Manager Setting Up About the Online Help SystemScenario 1 Single cluster management Launching Serviceguard ManagerAccessing Serviceguard Manager 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 Membertimeout Maximum and Minimum Values for ParametersSample 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 Start the package Identify the equivalent SFM style resource monitorIndex APA399 Cvmactivationcmd Firstclusterlockpv LAN INONLYORINOUT, 69 Inout Pollingtarget defined Qsaddr Servicename Vxvmdg