Comparison of Volume Managers | HP Serviceguard instruction

Redundant Heartbeat Subnets

HP recommends that you configure all subnets that connect cluster nodes as heartbeat networks; this increases protection against multiple faults at no additional cost.

For CVM 4.1 and later, the minimum recommended configurations are:

1)dual (multiple) heartbeat networks

2)single heartbeat network with standby LAN card(s)

Comparison of Volume Managers

The following table summarizes the advantages and disadvantages of the volume managers.

86 Understanding Serviceguard Software Components

Image 86

HP Serviceguard manual Comparison of Volume Managers, Redundant Heartbeat Subnets

Contents

Managing Serviceguard Twentieth Edition Legal Notices Contents Contents Planning and Documenting an HA Cluster Contents Building an HA Cluster Configuration 158 Contents Configuring Packages and Their Services 227 Contents Cluster and Package Maintenance 261 279 Troubleshooting Your Cluster 321 Contents 349 Integrating HA Applications with Serviceguard 354Software Upgrades 357 377 Blank Planning Worksheets 369Migrating from LVM to VxVM Data Storage 374 IPv6 Network Support 378 Index 398 Using Serviceguard Manager 385396 Publishing History Publishing History Preface Securing Serviceguard and other Serviceguard white papers Related Publications Serviceguard at a Glance What is Serviceguard? Failover Shows what happens in a failover situation About Veritas CFS and CVM from Symantec Typical Cluster After Failover Using Serviceguard Manager Using SAM Usr/sbin/sam -w What are the Distributed Systems Administration Utilities?Roadmap for Configuring Clusters and Packages Tasks in Configuring a Serviceguard Cluster Understanding Serviceguard Hardware Configurations Redundancy of Cluster Components Redundant Network Components Rules and Restrictions Redundant Ethernet Configuration Redundant LANs For legacy packages, see Configuring Cross-Subnet Failover Cross-Subnet ConfigurationsConfiguration Tasks Restrictions For More Information Supported Disk Interfaces Redundant Disk StorageReplacing Failed Network Cards Disk Mirroring Disk Arrays using RAID Levels and Multiple Data PathsData Protection About Multipathing Replacing Failed Disk Mechanisms Monitoring LVM Disks Through Event Monitoring ServiceMonitoring VxVM and CVM Disks Replacing Failed I/O Cards Sample Scsi Disk Configurations Mirrored Disks Connected for High Availability Sample Fibre Channel Disk Configuration Cluster with High Availability Disk Array Redundant Power Supplies Larger Clusters Active/Standby Model Point to Point Connections to Storage Devices Eight-Node Cluster with XP or EMC Disk Array Serviceguard Daemons Understanding Serviceguard Software ComponentsServiceguard Architecture Configuration Daemon cmclconfd Cluster Daemon cmcld Syslog Log Daemon cmlogd Cluster Logical Volume Manager Daemon cmlvmdFile Management Daemon cmfileassistd Cluster Object Manager Daemon cmomd Network Manager Daemon cmnetd Service Assistant Daemon cmservicedQuorum Server Daemon qs Lock LUN Daemon cmdisklockd Proxy Daemon cmproxyd Configuring the ClusterHow the Cluster Manager Works CFS Components Heartbeat Messages Manual Startup of Entire Cluster Cluster Quorum to Prevent Split-Brain Syndrome Automatic Cluster StartupDynamic Cluster Re-formation Cluster Lock Use of a Lock LUN or LVM Lock Disk as the Cluster Lock Lock Requirements Dual Lock Disk Use of the Quorum Server as the Cluster LockSingle Lock Disk or LUN No Cluster Lock Quorum Server Operation Non-failover Packages How the Package Manager WorksPackage Types Failover Packages Deciding When and Where to Run and Halt Failover Packages Failover Packages’ Switching Behavior Before Package Switching Package Configuration Data Automatic Rotating Standby Rotating Standby Configuration before Failover Configurednode Policy Packages after Failover Failback Policy Automatic Failback Configuration After Failover Using Older Package Configuration Files Using the Generic Resources Monitoring Service Understanding 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 Groups How Packages Run What Makes a Package Run? Before the Control Script Starts Legacy Package Time Line Showing Important Events During Run Script Execution Package Time Line Legacy Package Normal and Abnormal Exits from the Run Script Service Startup with cmrunservWhile Services are Running When a Package is Halted with a Command During Halt Script Execution Legacy Package Time Line for Halt Script Execution Normal and Abnormal Exits from the Halt Script Package Control Script Error and Exit ConditionsError Conditions and Package Movement for Failover Packages How the Network Manager Works Stationary and Relocatable IP Addresses Adding and Deleting Relocatable IP Addresses Types of IP Addresses Monitoring LAN Interfaces and Detecting Failure Link Level Load Sharing Local Switching Cluster Before Local Network Switching Where interface is the primary interface Cmmodnet -e interface Remote Switching Monitoring LAN Interfaces and Detecting Failure IP Level Reasons To Use IP Monitoring How the IP Monitor Works Failure 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 Failures Cmmodnet -e lan2 Example 2 If There Is No Local SwitchingAutomatic Port Aggregation Support for HP-UX Vlan Vlan ConfigurationsWhat is VLAN? Types of Redundant Storage Volume Managers for Data StorageConfiguration Restrictions Additional Heartbeat Requirements White papers About Device File Names Device Special FilesExamples of Mirrored Storage Physical Disks Within Shared Storage Units Multiple Devices Configured in Volume Groups Examples of Storage on Disk Arrays Multiple Paths to LUNs Veritas Volume Manager VxVM Types of Volume ManagerHP-UX Logical Volume Manager LVM Propagation of Disk Groups in VxVM Propagation of Disk Groups with CVM Veritas Cluster Volume Manager CVMCluster Startup Time with CVM For heartbeat requirements, see Redundant Heartbeat Subnets Comparison of Volume Managers Redundant Heartbeat Subnets Pros and Cons of Volume Managers with Serviceguard Responses to Failures System Reset When a Node FailsWhat Happens when a Node Times Out Example Responses to Hardware Failures Responses to Package and Service Failures Responses to Package and Generic Resources Failures Service Restarts Network Communication Failure General Planning Serviceguard Memory RequirementsPlanning and Documenting an HA Cluster Planning for Expansion Sample Cluster Configuration Hardware Planning LAN Information SPU InformationNetwork Information Nnn.nnn.nnn.nnn Under Cluster Configuration Parameters Scsi Addressing in Cluster Configuration Disk I/O Information Diskinfo Power Supply Planning Hardware Configuration Worksheet Power Supply Configuration Worksheet Cluster Lock Planning Quorum Server Worksheet Using a Quorum ServerCluster Lock Disk and Re-formation Time Using Generic Resources to Monitor Volume Groups LVM Planning Using EMS to Monitor Volume Groups LVM Worksheet For more information, see Using the EMS HA MonitorsCVM and VxVM Planning Cluster Configuration Planning CVM and VxVM Worksheet Points To Note Where cDSFs ResideAbout Cluster-wide Device Special Files cDSFs Limitations of cDSFs LVM Commands and cDSFsAbout Easy Deployment Limitations of Easy Deployment Heartbeat Subnet and Cluster Re-formation TimeAdvantages of Easy Deployment Rules and Restrictions for IPv6-Only Mode What Is IPv4-only Mode?What Is IPv6-Only Mode? Localhost ipv6-localhost ipv6-loopback IPV6 or ANY What Is Mixed Mode?Recommendations for IPv6-Only Mode Cluster configuration file Cluster Configuration ParametersRules and Restrictions for Mixed Mode Name of the cluster as it will appear in the output Planning 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 Server See also About Hostname Address Families IPv4-Only Hpux-serviceguard-docs under HP ServiceguardIPv6-Only, and Mixed Mode page 106 for important Sitepreferred or Configuration file see Configuring PackagesTheir Services page 227 and these in turn must Configuration Planning page 125 must be specified Cluster Is Running Cluster 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 serviced See IPv6 Address Types Also What Happens when You Change the QuorumConfiguration Online page 49 for important information Lock LUN page 189 for more information Failbackpolicy When You Change the Quorum Configuration OnlineCluster is running, see Updating the Cluster Lock Disk See About Package Weights page 144 for more Planning and Documenting an HA Cluster 69, Monitoring LAN Interfaces and Detecting See also What Happens when a Node Times Out88, Cluster Daemon cmcld page 41, IP-Level Failures When a network interface card has failed Default isConfiguration file specifies one of two ways to decide How Serviceguard will handle the recovery of the primary See 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 Access CVM 4.1 and later without CFS CVM 4.1 and later with CFS About the Volume Monitor Using the Volume Monitor Or --log-file Or --helpOr --version Or --log-level Usr/sbin/cmvolmond /dev/vg01/lvol1 /dev/vg01/lvol2 VolumepathPlanning for NFS-mounted File Systems Usr/sbin/cmvolmond -t 10 /dev/vg00/lvol1 Package Configuration Planning Choosing Switching and Failover Behavior Package Failover Behavior Extended generic resource Parameters for Configuring Generic ResourcesConfiguring a Generic Resource Cmmakepkg -i $SGCONF/pkg1/pkg1.conf -m sg/genericresource Cmcheckconf -v -P $SGCONF/pkg1/pkg1.conf Cmapplyconf -P $SGCONF/pkg1/pkg1.conf Cmgetresource -r sfmdisk Cmviewcl -v -f line -p pkg1 grep genericresourceCmrunpkg pkg1 Cmsetresource -r sfmdisk -s up Parameters for Configuring EMS Resources Online Reconfiguration of Generic Resources Rules for Simple Dependencies About Package DependenciesSimple Dependencies Assume that we want to make pkg1 depend on pkg2 Planning 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 Dependencies What Happens when a Package Fails Rules for differentnode and anynode Dependencies Configuring Weights and Capacities About Package WeightsPackage Weights and Node Capacities Cmmakepkg 1m manpage Nodename node1 Capacityname packagelimit Weightname packagelimit weightvalueSimple Method For pkg2 Defining Capacities Comprehensive MethodPoints to Keep in Mind Clustername cluster23 Nodename node1 Nodename node2 Defining Weights Defining Default Weights Weightname B Weightvalue Weightname a WeightvalueWeightname B Weightvalue Weightname a Rules and Guidelines Cmquerycl 1m manpage About 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 flag Configuring a Package to Fail Over across Subnets Example Implications for Application Deployment Configuring monitoredsubnetaccess Configuring a Package Next StepsConfiguring nodename Configuring ipsubnetnode Planning for Changes in Cluster Size Where Serviceguard Files Are Kept Building an HA Cluster ConfigurationInstalling and Updating Serviceguard Preparing Your Systems Configuring the Cluster Creating cDSFs for a Group of Nodes Creating Cluster-wide Device Special Files cDSFsBefore You Start Etc/cmcluster.conf Cmpreparecl -n nodename -n nodename Csshsetup -r node2Csshsetup -r -f /etc/cmcluster/sshhosts Cmpreparecl -n node1 -n node2 -n node3 -n node4 Adding a Node to a cDSF Group Using Easy DeploymentDisplaying the cDSF Configuration Removing a Node from a cDSF Group Cmquerycl -N $SGCONF/mynetwork Using Easy Deployment Commands to Configure the ClusterFor example Preparing Your Systems Building an HA Cluster Configuration PVG bus1 /dev/cdisk/disk14 /dev/cdisk/disk15 Format for entries in cmclnodelist is as follows Configuring Root-Level AccessAllowing Root Access to an Unconfigured Node Ensuring that the Root User on Another Node Is Recognized About identd Any of the aliases. Examples Configuring Name ResolutionOfficial hostname, as defined by hosts 4, for example Safeguarding against Loss of Name Resolution Services Ensuring Consistency of Kernel Configuration For NIS, enter two lines Tuning Network and Kernel Parameters Enabling the Network Time Protocol Creating Mirrors of Root Logical Volumes Make the new disk a boot disk Choosing Cluster Lock Disks Backing Up Cluster Lock Disk Information Setting 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 example Excluding Devices from Probing Defining the Lock LUN Setting Up and Running the Quorum Server Creating a Storage Infrastructure with LVM Using the Generic Resources Disk Monitor Using the EMS Disk Monitor Using Mirrored Individual Data Disks Creating Volume Groups Creating File Systems Creating Logical VolumesSetting Logical Volume Timeouts Lvchange -t 60 /dev/vg01/lvol1 Deactivating the Volume Group Distributing Volume Groups to Other NodesVerify the configuration Distributing the Volume Group Create a directory to mount the disk Deactivate the volume group on ftsys10Still on ftsys9, copy the map file to ftsys10 Creating a Storage Infrastructure with VxVM Making Physical Volume Group Files ConsistentCreating Additional Volume Groups Converting Disks from LVM to VxVM Creating Disk Groups Initializing Disks for VxVMInitializing Disks Previously Used by LVM Deporting Disk Groups Re-Importing Disk Groups Here 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 ftsys10 Specifying the Address Family for the Cluster Hostnames Cmquerycl OptionsSpeeding up the Process Specifying the Address Family for the Heartbeat Generating a Network Template File Specifying a Lock DiskSpecifying the Cluster Lock Full Network Probing Vgchange -c y /dev/vglock Specifying a Lock LUNCmquerycl -v -n ftsys9 -n ftsys10 See also Choosing Cluster Lock Disks Cmquerycl -q QSHost QSAddr -n ftsys9 -n ftsys10 -C Specifying a Quorum ServerObtaining Cross-Subnet Information Will produce the output such as the following Configuring the Cluster Controlling Access to the Cluster Specifying Maximum Number of Configured PackagesModifying the Membertimeout Parameter Identifying Heartbeat Subnets How Access Roles Work Access Roles Levels of Access Setting up Access-Control Policies Monitor Fulladmin Packageadmin Userrole must be one of these three values Username root Username john Userhost bitRole Conflicts Package versus Cluster Roles Adding Volume GroupsVerifying the Cluster Configuration Distributing the Binary Configuration File Differences between Legacy CFS and Modular CFS Storing Volume Group and Cluster Lock Configuration DataModular CFS packages v/s Legacy CFS packages Operational commands for Legacy CFS and Modular CFS Delete a mount point, check point, or snapshot in a package Cfscluster status Cfscluster config -t 900 -sPreparing the Cluster and the System Multi-node Package Cfsdgadm add logdata all=sw Creating the Disk GroupsCreating the Disk Group Cluster Packages Cfsdgadm display Cfsdgadm showpackage logdata Creating VolumesUse the vxprint command to verify Vxprint logfiles Cmmakepkg -m sg/cfsall /etc/cmcluster/cfspkg1.ascii Create a package configuration fileFor instructions on creating modular CFS packages, see Cmapplyconf -P /etc/cmcluster/cfspkg1.ascii Apply the package configuration fileCmcheckconf -P /etc/cmcluster/cfspkg1.ascii Cvmconcurrentdgoperations CmviewclBdf Cfsconcurrentmountunmountoperations See 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 to Cmmakepkg -m sg/cfsall snap1.ascii Create a package configuration file for the snapshot imageVxassist -g cvmdg3 make vol1 100m vxvol -g cvmdg3 startall Information about the mount options, see Mount pointsSnapshotmountoptions Mountvxfs 1m manpage Online reconfiguration of modular CFS package parameters Cmviewcl -v -f line -p cfspkg1 Cmcheckconf -P cfspkg1.ascii Verify the output Apply the configurationCmapplyconf -P cfspkg1.ascii Legacy Style of Packaging Modular Style of Packaging Managing Disk Groups and Mount Points Using Legacy Packages Associate it with the cluster and mount it Creating Checkpoint and Snapshot Packages for CFSFsckptadm -n create check2 /tmp/logdata/logfiles Cfsmount /tmp/checklogfiles Associate it with the cluster It is persistentVxassist -g dg1 make vol1 100m vxvol -g dg1 startall Cfsmount /local/snap1 cmviewcl You 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 CVM Vxdg -s init logdata c0t3d2 Adding Disk Groups to the Package ConfigurationUsr/lib/vxvm/bin/vxdisksetup -i c4t3d4 Mirror Detachment Policies with CVM Checking Cluster Operation with Serviceguard Commands Using Dsau during ConfigurationChecking Cluster Operation with Serviceguard Manager Managing the Running Cluster Preventing Automatic Activation of LVM Volume Groups Setting up Autostart Features Managing a Single-Node Cluster Here is an example of the /etc/rc.config.d/cmcluster fileChanging the System Message Single-Node Operation Deleting the Cluster ConfigurationDisabling identd Change the cmclconfd entry in /etc/inetd.conf to Building an HA Cluster Configuration Configuring Packages and Their Services Choosing Package Modules Types of Package Failover, Multi-Node, System Multi-Node Failoverpolicy Failbackpolicy Ipsubnet Ipaddress Base Package Modules Differences between Failover and Multi-Node PackagesPackage Modules and Parameters Cmmakepkg -m sg/all $SGCONF/sg-all Optional Modules Optional Package ModulesBase Modules Locallanfailoverallowed Package Parameter Explanations Externalscript Cmmakepkg $SGCONF/sg-all Autorun NodefailfastenabledNodename Runscripttimeout Haltscripttimeout Operationsequence SuccessorhalttimeoutScriptlogfile Loglevel Priority Dependencyname Dependencycondition For more information, see About Package Dependencies Dependencylocation Specifies where the dependencycondition must be metWeightname, weightvalue Monitoredsubnet MonitoredsubnetaccessLocallanfailoverallowed Clusterinterconnectsubnet Ipsubnet Ipaddress New for A.11.18 for both modular and legacy packagesIpsubnet Ipsubnetnode ServicenameSee the package configuration file for more examples Ipaddress Servicefailfastenabled ServicecmdServicerestart Servicehalttimeout Genericresourceupcriteria Defines when the status of a generic resource is evaluatedGenericresourceevaluationtype Resourcepollinginterval ResourcenameName of a resource to be monitored Resourcestart Concurrentvgchangeoperations EnablethreadedvgchangeResourceupvalue Cannot lock /etc/lvmconf//lvmlock still trying Vxvolcmd VgchangecmdCvmactivationcmd Vxvmdg KillprocessesaccessingrawdevicesCvmdg Vxvmdgretry Concurrentmountandumountoperations Fsfsckopt -s Fstype vxfsConcurrentfsckoperations Fsmountretrycount Fsdirectory FsnameFsserver Fstype Fsfsckopt FsmountoptFsumountopt Pev Userrole UsernameUserhost Additional Parameters Used Only by Legacy Packages Cmmakepkg Examples Generating the Package Configuration FileBefore You Start Mkdir $SGCONF/pkg1 Editing the Configuration File Next Step Packagetype. Enter failover, multinode, or systemmultinode See About Package Dependencies page 137 for more information Editing the Configuration File Vg vg01 Vg vg02 Verifying and Applying the Package Configuration # vxdg -tfC import dg01 Adding the Package to the ClusterHow Control Scripts Manage VxVM Disk Groups Viewing Dependencies Cluster and Package MaintenanceReviewing Cluster and Package Status Cmviewcl -r A.11.16 Cluster Status Viewing CFS Multi-Node InformationTypes of Cluster and Package States Node Status and State Reviewing Cluster and Package Status Unknown Down Normal Running Status Examples of Cluster and Package StatesFailover and Failback Policies Quorum Server Status CFS Package Status Status After Halting a Package Then run cmviewcl -v, we’ll see If we use the following commandStatus After Moving the Package to Another Node 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 Node Viewing Information about System Multi-Node Packages This output can be seen on both ftsys9 and ftsys10Viewing Information about Unowned Packages Cmviewcl -v -p SG-CFS-pkg Checking Status of the Cluster File System CFSStatus of the Packages in a Cluster File System Status of Legacy CVM Disk Group Packages Status of CFS Modular Disk Group and Mount Point PackagesCmviewcl -v -p mpdg1 Ftsys9 Sw sw Status of Legacy CFS Mount Point Packages Checking the Cluster Configuration and ComponentsFtsys10 Cfsmntadm display -v /tmp/logdata/logfiles User-created files if you specify them Etc/nsswitch.conf Etc/servicesChecking Cluster Components Verifying Cluster Components Cmapplyconf 1m Run cmcheckconf -C Limitations Setting up Periodic Cluster VerificationManaging the Cluster and Nodes See the cron 1m manpage for more information Using 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 ftsys10 Cmrunnode -v ftsys8 Removing Nodes from Participation in a Running ClusterHalting the Entire Cluster Cmhaltnode -f -v ftsys9 Rules and Restrictions Automatically Restarting the ClusterWhat You Can Do Managing the Cluster and Nodes Additional Points To Note Halting the Cluster and Detaching its Packages Halting a Node and Detaching its PackagesHalting a Detached Package Cmrunnode node1 Managing Packages and ServicesStarting a Package Starting a Package that Has Dependencies Using Serviceguard Commands to Start a PackageHalting a Package Halting a Package that Has Dependencies Changing Package Switching with Serviceguard Commands Changing Package Switching BehaviorUsing Serviceguard Commands to Halt a Package Moving a Failover Package Cmmodpkg -d -n lptest3 pkg1 Maintaining a Package Maintenance ModeSee Performing Maintenance Using Maintenance Mode Cluster and Package Maintenance Performing Maintenance Using Maintenance Mode Procedure Excluding Modules in Partial-Startup Maintenance Mode Cmrunpkg -m sg/packageip pkg1 Cmrunpkg -m sg/services -e sg/packageip pkg1 Reconfiguring a ClusterCmrunpkg -e sg/service pkg1 Types of Changes to the Cluster Configuration Change to the Cluster Configuration Previewing the Effect of Cluster Changes What You Can Preview Using Preview mode for Commands and in Serviceguard ManagerMode see Maintaining a Package Maintenance Mode Cmmodpkg -e -t pkg1 You would see output something like this Using cmevalCmeval -v newstate.in Updating the Cluster Lock Disk Configuration Online Updating the Cluster Lock ConfigurationReconfiguring a Halted Cluster Updating the Cluster Lock LUN Configuration Online Adding Nodes to the Cluster While the Cluster is Running Reconfiguring a Running ClusterCmapplyconf -C clconfig.ascii Cmgetconf -c cluster1 temp.ascii Cmquerycl -C clconfig.ascii -c cluster1 -n ftsys8 -n ftsys9 What You Can Do What You Must Keep in Mind Cmquerycl -c cluster1 -C clconfig.ascii Example Adding a Heartbeat LAN Cmgetconf clconfig.ascii Removing a LAN or Vlan Interface from a Node See also Replacing LAN or Fibre Channel Cards Changing the LVM Configuration while the Cluster is RunningChanging the VxVM or CVM Storage Configuration Cmgetconf -c clustername clconfig.ascii Configuring a Legacy PackageCreating the Legacy Package Configuration Mkdir /etc/cmcluster/pkg1 Configuring a Package in StagesEditing the Package Configuration File Cluster and Package Maintenance Creating the Package Control Script Cmmakepkg -s /etc/cmcluster/pkg1/pkg1.sh Customizing the Package Control Script Adding Serviceguard Commands in Customer Defined Functions Support for Additional Products Copying Package Control Scripts with HP-UX commands Verifying the Package ConfigurationDistributing the Configuration Cmcheckconf -v -P /etc/cmcluster/pkg1/pkg1.conf Configuring Cross-Subnet Failover Configuring nodename Creating Subnet-Specific Package Control Scripts Reconfiguring a PackageConfiguring monitoredsubnetaccess IP0 = SUBNET0 IP1 = SUBNET1 Cmgetconf -p pkg1 pkg1.conf Reconfiguring a Package on a Running ClusterMigrating a Legacy Package to a Modular Package Reconfiguring a Package on a Halted Cluster Adding a Package to a Running Cluster Cmapplyconf -v -P app1.conf Deleting a Package from a Running ClusterCmhaltpkg mypkg Cmdeleteconf -p mypkg Unmount the shared file system cfsumount mount point Cmmodpkg -R -s myservice pkg1 Resetting the Service Restart CounterAllowable Package States During Reconfiguration Change servicerestart modular package Types of Changes to Packages Locallanfailoverallowed Change vxvolcmd Cfsmountoptions Responding to Cluster Events Changes that Will Trigger Warnings Single-Node Operation Disabling ServiceguardRemoving Serviceguard from a System Start the Cluster using Serviceguard Manager Troubleshooting Your ClusterTesting Cluster Operation Testing the Package Manager Monitoring Hardware Testing the Cluster ManagerTesting the Network Manager Using EMS Event Monitoring Service Hardware Monitors Using System Fault Management ServiceUsing Event Monitoring Service Hardware Monitors and Persistence Requests Replacing a Faulty Mechanism in an HA Enclosure Using HP Isee HP Instant Support Enterprise EditionReplacing a Faulty Array Mechanism Replacing Disks Replacing a Lock Disk Replacing a Lock LUN Replacing I/O Cards Online Hardware Maintenance with In-line Scsi TerminatorCmdisklock reset /dev/dsk/c0t1d1 Replacing Scsi Host Bus Adapters Replacing LAN or Fibre Channel Cards Offline ReplacementOnline Replacement Replacing a Failed Quorum Server System After Replacing the Card Reviewing Package IP Addresses Troubleshooting ApproachesUsing cmquerycl and cmcheckconf Using cmviewcl Reviewing the System Log File Following is an example of a successful package starting Reviewing Object Manager Log FilesSample System Log Entries Cmreadlog /var/opt/cmom/cmomd.log Using the cmcheckconf Command Reviewing Serviceguard Manager Log FilesReviewing Configuration Files Reviewing the System Multi-node Package Files Reviewing the LAN Configuration Solving ProblemsUsing the cmviewconf Command Serviceguard Command Hangs Nslookup ftsys9 Networking and Security Configuration ErrorsCluster Re-formations Caused by Temporary Conditions System Administration Errors Package Control Script Hangs or Failures Fuser -kulogical-volume umount logical-volume Problems with Cluster File System CFS Llt, gab Vxfen W cvm Cfs Node and Network Failures Problems with VxVM Disk GroupsPackage Movement Errors Force Import and Deport After Node Failure Timeout Problems Troubleshooting the Quorum ServerAuthorization File Problems Access denied to quorum server Messages Enterprise Cluster Master Toolkit Designing Highly Available Cluster Applications Automating Application Operation Define Application Startup and Shutdown Controlling the Speed of Application FailoverInsulate Users from Outages Evaluate the Use of JFS Use Raw VolumesReplicate Non-Data File Systems Minimize Data Loss Design for Multiple Servers Use Restartable TransactionsUse Checkpoints Balance Checkpoint Frequency with Performance Avoid Node-Specific Information Designing Applications to Run on Multiple SystemsDesign for Replicated Data Sites Obtain Enough IP Addresses Avoid Using SPU IDs or MAC AddressesAssign Unique Names to Applications Allow Multiple Instances on Same System Bind to Relocatable IP Addresses Use uname2 With CareBind to a Fixed Port Avoid File Locking Give Each Application its Own Volume GroupUse Multiple Destinations for SNA Applications Call bind before connect Help menu for ndd -h ipstrongesmodel Etc/rc.config.d/nddconf as followsUsr/sbin/route add net default 128.17.17.1 1 source Usr/sbin/route delete net default 128.17.17.1 1 source Restoring Client Connections Be Able to Monitor Applications Handling Application FailuresCreate Applications to be Failure Tolerant Minimizing Planned Downtime Reducing Time Needed for Application Upgrades and PatchesProvide for Rolling Upgrades Do Not Change the Data Layout Between Releases Providing Online Application Reconfiguration Documenting Maintenance Operations Defining Baseline Application Behavior on a Single System Integrating HA Applications with ServiceguardChecklist for Integrating HA Applications Integrating HA Applications in Multiple Systems Testing the Cluster Move it back Special Considerations for Upgrade to Serviceguard A.11.19 Software UpgradesSpecial Considerations for Upgrade to Serviceguard A.11.20 Rolling Upgrade Types of UpgradeHow To Tell when the Cluster Re-formation Is Complete Rolling Upgrade Using DRD Non-Rolling Upgrade Guidelines for Rolling UpgradeRestrictions for DRD Upgrades Non-Rolling Upgrade Using DRD Performing a Rolling Upgrade Limitations of Rolling Upgrades Migrating cmclnodelist entries from A.11.15 or earlier Running the Rolling UpgradeKeeping Kernels Consistent Performing a Rolling Upgrade Using DRD Running the Rolling Upgrade Using DRD Halt the first node, as follows Example of a Rolling UpgradeStep Running Cluster with Packages Moved to Node Node 1 Rejoining the Cluster Repeat the process on node 2. Halt the node, as follows Guidelines for Non-Rolling Upgrade Performing a Non-Rolling Upgrade Steps for a Non-Rolling Upgrade Using DRD Performing a Non-Rolling Upgrade Using DRDLimitations of Non-Rolling Upgrades using DRD Guidelines for Migrating a Cluster with Cold Install Checklist for Migration Worksheet for Hardware Planning Power Supply WorksheetBlank Planning Worksheets LVM Volume Group and Physical Volume Worksheet Quorum Server Worksheet Cluster Configuration Worksheet VxVM Disk Group and Disk Worksheet Package Configuration Worksheet Package Configuration Worksheet Loading VxVM Migrating Volume GroupsMigrating from LVM to VxVM Data Storage Customizing Packages for VxVM Mntdg0202, respectively Restart the package Removing LVM Volume GroupsCustomizing Packages for CVM Migrating from Legacy CFS Packages to Modular CFS Packages Textual Representation of IPv6 Addresses IPv6 Network SupportIPv6 Address Types IPv4 and IPv6 Compatibility IPv6 Address PrefixUnicast Addresses IPv4 Compatible IPv6 Addresses Site-Local Addresses Aggregatable Global Unicast AddressesLink-Local Addresses Multicast Addresses Network Configuration Restrictions Ndd -get /dev/ip6 ip6nddadsolicitcount Example ConfigurationsLocal Primary/Standby LAN Patterns Ndd -set /dev/ip6 ip6nddadsolicitcountn Example Configurations 384 IPv6 Network Support Accessing Serviceguard Manager Using Serviceguard ManagerBefore Using HP Serviceguard Manager Setting Up About the Online Help System Scenario 1 Single cluster management Launching Serviceguard ManagerAccessing Serviceguard Manager Opt/hpsmh/bin/hpsmh autostart System Management Homepage with Serviceguard Manager From the left-hand panel, expand Cluster by Type Expand HP Serviceguard, and click on a Serviceguard clusterSign Membertimeout Maximum and Minimum Values for Parameters Launching Monitoring Scripts Monitoring Script for Generic ResourcesSample scripts Launching Monitoring Scripts Template of a Monitoring Script I L I T Y N C T I O N S Monitoring Script for Generic Resources Template of a Monitoring Script Migrating EMS Resources to Generic Resources Start the package Identify the equivalent SFM style resource monitor Index APA 399 Cvmactivationcmd Firstclusterlockpv LAN INONLYORINOUT, 69 Inout Pollingtarget defined Qsaddr Servicename Vxvmdg