HP Serviceguard manual Performing a Non-Rolling Upgrade Using DRD

Page 367

1.Halt all nodes in the cluster: cmhaltcl -f

2.If necessary, upgrade all the nodes in the cluster to the new HP-UX release. (See Step 3 under “Running the Rolling Upgrade” (page 361) for more information.)

3.Upgrade all the nodes in the cluster to the new Serviceguard release. (See Step 3 under “Running the Rolling Upgrade” (page 361) for more information.)

4.Restart the cluster: cmruncl

Performing a Non-Rolling Upgrade Using DRD

Limitations of Non-Rolling Upgrades using DRD

CAUTION: Stricter limitations apply to an upgrade to A.11.19; do not proceed with an upgrade to A.11.19 until you have read and understood the Special Considerations for Upgrade to Serviceguard A.11.19 (page 357).

IMPORTANT: Not all paths that are supported for upgrade are supported for an upgrade using DRD, and there are additional requirements and restrictions for paths that are supported.

Do not proceed until you have read the “Announcements”, “Compatibility”, and “Installing Serviceguard” sections of the latest version of the Serviceguard release notes, made sure your cluster meets the current requirements, and taken any necessary preparation steps as instructed in the release notes.

You must also make sure you have read and understood the “Restrictions for DRD Upgrades” (page 359).

In addition, all the limitations listed under “Limitations of Non-Rolling Upgrades” (page 366) apply to non-rolling upgrades using DRD. You should also read the “Guidelines for Non-Rolling Upgrade” (page 366) before you proceed.

Steps for a Non-Rolling Upgrade Using DRD

Use the following steps for a non-rolling software upgrade using DRD:

1.Create a clone root disk for each node.

2.Upgrade each clone disk to the new HP-UX release (if necessary), including Serviceguard (using drd runcmd update-ux), or upgrade Serviceguard alone (using drd runcmd swinstall).

3.Halt all nodes in the cluster: cmhaltcl -f

4.Reboot the nodes from their updated clone root disks.

5.Restart the cluster: cmruncl

6.Verify that the cluster is healthy, the packages can run, and applications are functioning properly.

If the cluster is not healthy or the packages and applications are not functioning properly, and you cannot fix the problems, you can revert to the original (pre-upgrade) cluster by halting the cluster (cmhaltcl), rebooting each node from its original (pre-upgrade) root disk, and restarting the cluster (cmruncl).

Performing a Non-Rolling Upgrade Using DRD 367

Page 366 Page 368
Image 367
Page 366 Page 368
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 IPv6 Network Support 378 Blank Planning Worksheets 369Migrating from LVM to VxVM Data Storage 374 377396 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 ConfigurationRestrictions Cross-Subnet ConfigurationsConfiguration Tasks For legacy packages, see Configuring Cross-Subnet FailoverFor More Information Replacing Failed Network Cards Redundant Disk StorageSupported Disk Interfaces About Multipathing Disk Arrays using RAID Levels and Multiple Data PathsData Protection Disk MirroringReplacing Failed I/O Cards Monitoring LVM Disks Through Event Monitoring ServiceMonitoring VxVM and CVM Disks Replacing Failed Disk MechanismsMirrored 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 cmclconfdCluster Object Manager Daemon cmomd Cluster Logical Volume Manager Daemon cmlvmdFile Management Daemon cmfileassistd Syslog Log Daemon cmlogdLock LUN Daemon cmdisklockd Service Assistant Daemon cmservicedQuorum Server Daemon qs Network Manager Daemon cmnetdCFS Components Configuring the ClusterHow the Cluster Manager Works Proxy Daemon cmproxydManual Startup of Entire Cluster Heartbeat MessagesCluster Lock Automatic Cluster StartupDynamic Cluster Re-formation Cluster Quorum to Prevent Split-Brain SyndromeLock 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 LockFailover Packages How the Package Manager WorksPackage Types Non-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 See also Using EMS to Monitor Volume Groups Using the Event Monitoring ServiceUsing the EMS HA Monitors See also Using Generic Resources 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 See also Reporting Link-Level and IP-Level Failures Example 1 If Local Switching is ConfiguredReporting Link-Level and IP-Level Failures Constraints and LimitationsAutomatic Port Aggregation Example 2 If There Is No Local SwitchingCmmodnet -e lan2 What is VLAN? Vlan ConfigurationsSupport for HP-UX Vlan Additional Heartbeat Requirements Volume Managers for Data StorageConfiguration Restrictions Types of Redundant StorageExamples 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 Propagation of Disk Groups in VxVM Types of Volume ManagerHP-UX Logical Volume Manager LVM Veritas Volume Manager VxVMFor heartbeat requirements, see Redundant Heartbeat Subnets Veritas Cluster Volume Manager CVMCluster Startup Time with CVM Propagation of Disk Groups with CVMRedundant Heartbeat Subnets Comparison of Volume ManagersPros and Cons of Volume Managers with Serviceguard Example System Reset When a Node FailsWhat Happens when a Node Times Out Responses to FailuresResponses to Hardware Failures Responses to Package and Generic Resources Failures Responses to Package and Service FailuresNetwork Communication Failure Service RestartsPlanning for Expansion Serviceguard Memory RequirementsPlanning and Documenting an HA Cluster General PlanningHardware Planning Sample Cluster ConfigurationNnn.nnn.nnn.nnn SPU InformationNetwork Information LAN InformationScsi 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 Localhost ipv6-localhost ipv6-loopback What Is IPv4-only Mode?What Is IPv6-Only Mode? Rules and Restrictions for IPv6-Only ModeRecommendations for IPv6-Only Mode What Is Mixed Mode?IPV6 or ANY Name of the cluster as it will appear in the output Cluster Configuration ParametersRules and Restrictions for Mixed Mode Cluster configuration filePlanning and Documenting an HA Cluster 99 and Specifying a Quorum Server Happens when You Change the Quorum ConfigurationGo/hpux-serviceguard-docs under HP Serviceguard IPv4-Only,IPv6-Only, and Mixed Mode page 106 forIPv6-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 To that LAN, to risk timeout without being serviced You cannot change the heartbeat configuration whileCVM/CFS on HP Serviceguard A.11.20 April Protocols and services. RPC assumes that each networkLock LUN page 189 for more information Also What Happens when You Change the QuorumConfiguration Online page 49 for important information See IPv6 Address TypesCluster 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 IP-Level Failures See also What Happens when a Node Times Out88, Cluster Daemon cmcld page 41, 69, Monitoring LAN Interfaces and DetectingHow Serviceguard will handle the recovery of the primary Default isConfiguration file specifies one of two ways to decide When a network interface card has failedSee Monitoring LAN Interfaces and Detecting Failure IP Planning and Documenting an HA Cluster Access Control Policies also known as Role Based Access Package Configuration PlanningCluster Configuration Next Step Logical Volume and File System PlanningCVM 4.1 and later without CFS CVM 4.1 and later with CFS Using the Volume Monitor About the Volume MonitorOr --log-level Or --helpOr --version Or --log-fileUsr/sbin/cmvolmond -t 10 /dev/vg00/lvol1 VolumepathPlanning for NFS-mounted File Systems Usr/sbin/cmvolmond /dev/vg01/lvol1 /dev/vg01/lvol2Package Configuration Planning Package Failover Behavior Choosing Switching and Failover BehaviorCmmakepkg -i $SGCONF/pkg1/pkg1.conf -m sg/genericresource Parameters for Configuring Generic ResourcesConfiguring a Generic Resource Extended generic resourceCmapplyconf -P $SGCONF/pkg1/pkg1.conf Cmcheckconf -v -P $SGCONF/pkg1/pkg1.confCmsetresource -r sfmdisk -s up Cmviewcl -v -f line -p pkg1 grep genericresourceCmrunpkg pkg1 Cmgetresource -r sfmdiskOnline Reconfiguration of Generic Resources Parameters for Configuring EMS ResourcesAssume that we want to make pkg1 depend on pkg2 About Package DependenciesSimple Dependencies Rules for Simple DependenciesPlanning 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 FailsCmmakepkg 1m manpage About Package WeightsPackage Weights and Node Capacities Configuring Weights and CapacitiesFor pkg2 Weightname packagelimit weightvalueSimple Method Nodename node1 Capacityname packagelimitPoints 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 Cmviewcl -v -f line displays a lasthaltfailed flag Determining Why a Package Has Shut DownAbout Cross-Subnet Failover LasthaltfailedImplications for Application Deployment Configuring a Package to Fail Over across Subnets ExampleConfiguring ipsubnetnode Configuring a Package Next StepsConfiguring nodename Configuring monitoredsubnetaccessPlanning for Changes in Cluster Size Preparing Your Systems Configuring the Cluster Building an HA Cluster ConfigurationInstalling and Updating Serviceguard Where Serviceguard Files Are KeptEtc/cmcluster.conf Creating Cluster-wide Device Special Files cDSFsBefore You Start Creating cDSFs for a Group of NodesCmpreparecl -n node1 -n node2 -n node3 -n node4 Csshsetup -r node2Csshsetup -r -f /etc/cmcluster/sshhosts Cmpreparecl -n nodename -n nodenameRemoving a Node from a cDSF Group Using Easy DeploymentDisplaying the cDSF Configuration Adding a Node to 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 This will create three device files, for example Creating a Disk Partition on an HP Integrity SystemUsr/sbin/idisk -w -p -f partition.txt /dev/rdsk/c1t4d0 Usr/sbin/idisk -w -p -f partition.txt /dev/rdisk/disk12Defining 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 DisksLvchange -t 60 /dev/vg01/lvol1 Creating Logical VolumesSetting Logical Volume Timeouts Creating File SystemsDistributing the Volume Group Distributing Volume Groups to Other NodesVerify the configuration Deactivating the Volume GroupStill on ftsys9, copy the map file to ftsys10 Deactivate the volume group on ftsys10Create a directory to mount the disk Converting Disks from LVM to VxVM Making Physical Volume Group Files ConsistentCreating Additional Volume Groups Creating a Storage Infrastructure with VxVMInitializing Disks Previously Used by LVM Initializing Disks for VxVMCreating Disk Groups Re-Importing Disk Groups Deporting Disk GroupsCmquerycl -v -C $SGCONF/clust1.conf -n ftsys9 -n ftsys10 Configuring the ClusterClearimport at System Reboot Time Here is an example of the command enter it all one lineSpecifying the Address Family for the Heartbeat Cmquerycl OptionsSpeeding up the Process Specifying the Address Family for the Cluster HostnamesFull Network Probing Specifying a Lock DiskSpecifying the Cluster Lock Generating a Network Template FileSee also Choosing Cluster Lock Disks Specifying a Lock LUNCmquerycl -v -n ftsys9 -n ftsys10 Vgchange -c y /dev/vglockWill produce the output such as the following Specifying a Quorum ServerObtaining Cross-Subnet Information Cmquerycl -q QSHost QSAddr -n ftsys9 -n ftsys10 -CConfiguring the Cluster Identifying Heartbeat Subnets Specifying Maximum Number of Configured PackagesModifying the Membertimeout Parameter Controlling Access to the ClusterAccess 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 Cfsdgadm display Creating the Disk GroupsCreating the Disk Group Cluster Packages Cfsdgadm add logdata all=swVxprint logfiles Creating VolumesUse the vxprint command to verify Cfsdgadm showpackage logdataFor 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 Cfsconcurrentmountunmountoperations CmviewclBdf CvmconcurrentdgoperationsCurrent primary, a primary migration is triggered to Cmmakepkg -m sg/cfsall /etc/cmcluster/ckpt1.asciiPackage. For more information, see the manpage See the mountvxfs 1m manpageVxassist -g cvmdg3 make vol1 100m vxvol -g cvmdg3 startall Create a package configuration file for the snapshot imageCmmakepkg -m sg/cfsall snap1.ascii Mountvxfs 1m manpage Mount pointsSnapshotmountoptions Information about the mount options, seeOnline 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 Cfsmount /tmp/checklogfiles Creating Checkpoint and Snapshot Packages for CFSFsckptadm -n create check2 /tmp/logdata/logfiles Associate it with the cluster and mount itCfsmount /local/snap1 cmviewcl It is persistentVxassist -g dg1 make vol1 100m vxvol -g dg1 startall Associate it with the clusterYou need to do the tasks described in the following sections Initializing Disks for CVM Initializing the Veritas Volume ManagerPreparing the Cluster for Use with CVM Identifying the Master NodeMirror Detachment Policies with CVM Adding Disk Groups to the Package ConfigurationUsr/lib/vxvm/bin/vxdisksetup -i c4t3d4 Vxdg -s init logdata c0t3d2Managing the Running Cluster Using Dsau during ConfigurationChecking Cluster Operation with Serviceguard Manager Checking Cluster Operation with Serviceguard CommandsSetting 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 Change the cmclconfd entry in /etc/inetd.conf to Deleting the Cluster ConfigurationDisabling identd Single-Node OperationBuilding an HA Cluster Configuration Configuring Packages and Their Services Types of Package Failover, Multi-Node, System Multi-Node Choosing Package ModulesFailoverpolicy Failbackpolicy Ipsubnet Ipaddress Cmmakepkg -m sg/all $SGCONF/sg-all Differences between Failover and Multi-Node PackagesPackage Modules and Parameters Base Package ModulesBase Modules Optional Package ModulesOptional Modules Locallanfailoverallowed Externalscript Package Parameter ExplanationsCmmakepkg $SGCONF/sg-all Nodename NodefailfastenabledAutorun Haltscripttimeout RunscripttimeoutLoglevel SuccessorhalttimeoutScriptlogfile OperationsequenceDependencyname PriorityFor more information, see About Package Dependencies DependencyconditionWeightname, weightvalue Specifies where the dependencycondition must be metDependencylocation Clusterinterconnectsubnet MonitoredsubnetaccessLocallanfailoverallowed MonitoredsubnetIpsubnet New for A.11.18 for both modular and legacy packagesIpsubnet Ipaddress Ipaddress ServicenameSee the package configuration file for more examples IpsubnetnodeServicehalttimeout ServicecmdServicerestart ServicefailfastenabledGenericresourceevaluationtype Defines when the status of a generic resource is evaluatedGenericresourceupcriteria Resourcestart ResourcenameName of a resource to be monitored ResourcepollingintervalCannot lock /etc/lvmconf//lvmlock still trying EnablethreadedvgchangeResourceupvalue ConcurrentvgchangeoperationsCvmactivationcmd VgchangecmdVxvolcmd Vxvmdgretry KillprocessesaccessingrawdevicesCvmdg VxvmdgFsmountretrycount Fsfsckopt -s Fstype vxfsConcurrentfsckoperations ConcurrentmountandumountoperationsFstype FsnameFsserver FsdirectoryPev FsmountoptFsumountopt FsfsckoptAdditional Parameters Used Only by Legacy Packages UsernameUserhost UserroleMkdir $SGCONF/pkg1 Generating the Package Configuration FileBefore You Start Cmmakepkg ExamplesNext 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 Cmviewcl -r A.11.16 Cluster and Package MaintenanceReviewing Cluster and Package Status Viewing DependenciesNode Status and State Viewing CFS Multi-Node InformationTypes of Cluster and Package States Cluster StatusReviewing 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 Status After Halting a Node Status After Auto Run is EnabledOutput of the cmviewcl command is now as follows After we halt ftsys10 with the following commandViewing 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 Ftsys9 Sw sw Status of CFS Modular Disk Group and Mount Point PackagesCmviewcl -v -p mpdg1 Status of Legacy CVM Disk Group PackagesCfsmntadm display -v /tmp/logdata/logfiles Checking the Cluster Configuration and ComponentsFtsys10 Status of Legacy CFS Mount Point PackagesChecking Cluster Components Etc/nsswitch.conf Etc/servicesUser-created files if you specify them Cmapplyconf 1m Verifying Cluster ComponentsRun cmcheckconf -C See the cron 1m manpage for more information Setting up Periodic Cluster VerificationManaging the Cluster and Nodes LimitationsCmruncl -v -n ftsys9 -n ftsys10 Starting the Cluster When all Nodes are DownAdding Previously Configured Nodes to a Running Cluster Using Serviceguard Commands to Start the ClusterCmhaltnode -f -v ftsys9 Removing Nodes from Participation in a Running ClusterHalting the Entire Cluster Cmrunnode -v ftsys8What 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 that Has Dependencies Using Serviceguard Commands to Start a PackageHalting a Package Starting a Package that Has DependenciesMoving a Failover Package Changing Package Switching BehaviorUsing Serviceguard Commands to Halt a Package Changing Package Switching with Serviceguard CommandsSee 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 ModeTypes of Changes to the Cluster Configuration Reconfiguring a ClusterCmrunpkg -e sg/service pkg1 Cmrunpkg -m sg/services -e sg/packageip pkg1Previewing the Effect of Cluster Changes Change to the Cluster ConfigurationCmmodpkg -e -t pkg1 Using Preview mode for Commands and in Serviceguard ManagerMode see Maintaining a Package Maintenance Mode What You Can PreviewCmeval -v newstate.in Using cmevalYou would see output something like this Updating the Cluster Lock LUN Configuration Online Updating the Cluster Lock ConfigurationReconfiguring a Halted Cluster Updating the Cluster Lock Disk Configuration OnlineCmgetconf -c cluster1 temp.ascii Reconfiguring a Running ClusterCmapplyconf -C clconfig.ascii Adding Nodes to the Cluster While the Cluster is RunningWhat 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 FunctionsCmcheckconf -v -P /etc/cmcluster/pkg1/pkg1.conf Verifying the Package ConfigurationDistributing the Configuration Copying Package Control Scripts with HP-UX commandsConfiguring nodename Configuring Cross-Subnet FailoverIP0 = SUBNET0 IP1 = SUBNET1 Reconfiguring a PackageConfiguring monitoredsubnetaccess Creating Subnet-Specific Package Control ScriptsMigrating 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 ClusterUnmount the shared file system cfsumount mount point Deleting a Package from a Running ClusterCmhaltpkg mypkg Cmdeleteconf -p mypkg Cmapplyconf -v -P app1.confAllowable 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 the Package Manager Troubleshooting Your ClusterTesting Cluster Operation Start the Cluster using Serviceguard ManagerTesting the Network Manager Testing the Cluster ManagerMonitoring Hardware Hardware Monitors and Persistence Requests Using System Fault Management ServiceUsing Event Monitoring Service Using EMS Event Monitoring Service Hardware MonitorsReplacing Disks Using HP Isee HP Instant Support Enterprise EditionReplacing a Faulty Array Mechanism Replacing a Faulty Mechanism in an HA EnclosureReplacing a Lock LUN Replacing a Lock DiskReplacing Scsi Host Bus Adapters Online Hardware Maintenance with In-line Scsi TerminatorCmdisklock reset /dev/dsk/c0t1d1 Replacing I/O CardsOnline Replacement Offline ReplacementReplacing LAN or Fibre Channel Cards After Replacing the Card Replacing a Failed Quorum Server SystemReviewing the System Log File Troubleshooting ApproachesUsing cmquerycl and cmcheckconf Using cmviewcl Reviewing Package IP AddressesCmreadlog /var/opt/cmom/cmomd.log Reviewing Object Manager Log FilesSample System Log Entries Following is an example of a successful package startingReviewing the System Multi-node Package Files Reviewing Serviceguard Manager Log FilesReviewing Configuration Files Using the cmcheckconf CommandServiceguard Command Hangs Solving ProblemsUsing the cmviewconf Command Reviewing the LAN ConfigurationCluster 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 CFSForce Import and Deport After Node Failure Problems with VxVM Disk GroupsPackage Movement Errors Node and Network FailuresAccess denied to quorum server Troubleshooting the Quorum ServerAuthorization File Problems Timeout ProblemsMessages 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 Minimize Data Loss Use Raw VolumesReplicate Non-Data File Systems Evaluate the Use of JFSBalance Checkpoint Frequency with Performance Use Restartable TransactionsUse Checkpoints Design for Multiple ServersDesign for Replicated Data Sites Designing Applications to Run on Multiple SystemsAvoid Node-Specific Information Allow Multiple Instances on Same System Avoid Using SPU IDs or MAC AddressesAssign Unique Names to Applications Obtain Enough IP AddressesBind to a Fixed Port Use uname2 With CareBind to Relocatable IP Addresses Call bind before connect Give Each Application its Own Volume GroupUse Multiple Destinations for SNA Applications Avoid File LockingUsr/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 Do Not Change the Data Layout Between Releases Reducing Time Needed for Application Upgrades and PatchesProvide for Rolling Upgrades Minimizing Planned DowntimeDocumenting 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 Rolling Upgrade Using DRD Types of UpgradeHow To Tell when the Cluster Re-formation Is Complete Rolling UpgradeNon-Rolling Upgrade Using DRD Guidelines for Rolling UpgradeRestrictions for DRD Upgrades Non-Rolling UpgradeLimitations 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 IPv4 Compatible IPv6 Addresses IPv6 Address PrefixUnicast Addresses IPv4 and IPv6 CompatibilityMulticast Addresses Aggregatable Global Unicast AddressesLink-Local Addresses Site-Local AddressesNetwork Configuration Restrictions Ndd -set /dev/ip6 ip6nddadsolicitcountn Example ConfigurationsLocal Primary/Standby LAN Patterns Ndd -get /dev/ip6 ip6nddadsolicitcountExample Configurations 384 IPv6 Network Support About the Online Help System Using Serviceguard ManagerBefore Using HP Serviceguard Manager Setting Up Accessing Serviceguard ManagerOpt/hpsmh/bin/hpsmh autostart Launching Serviceguard ManagerAccessing Serviceguard Manager Scenario 1 Single cluster managementSystem 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
Top Page Image Contents