Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home

Managing Serviceguard Fifteenth Edition


Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

HP Part Number: B3936-90122

Published: December 2007

Table of Contents

Printing History
1 Serviceguard at a Glance
What is Serviceguard?
About Veritas CFS and CVM from Symantec
Using Serviceguard Manager
Monitoring Clusters with Serviceguard Manager
Administering Clusters with Serviceguard Manager
Configuring Clusters with Serviceguard Manager
Starting Serviceguard Manager
Using SAM
What are the Distributed Systems Administration Utilities?
A Roadmap for Configuring Clusters and Packages
2 Understanding Serviceguard Hardware Configurations
Redundancy of Cluster Components
Redundant Network Components
Rules and Restrictions
Redundant Ethernet Configuration
Cross-Subnet Configurations
Replacing Failed Network Cards
Redundant Disk Storage
Supported Disk Interfaces
Data Protection
Monitoring of Disks Through Event Monitoring Service
Replacement of Failed Disk Mechanisms
Replacement of Failed I/O Cards
Sample SCSI Disk Configurations
Sample Fibre Channel Disk Configuration
Redundant Power Supplies
Larger Clusters
Active/Standby Model
Point to Point Connections to Storage Devices
3 Understanding Serviceguard Software Components
Serviceguard Architecture
Serviceguard Daemons
How the Cluster Manager Works
Configuration of the Cluster
Heartbeat Messages
Manual Startup of Entire Cluster
Automatic Cluster Startup
Dynamic Cluster Re-formation
Cluster Quorum to Prevent Split-Brain Syndrome
Cluster Lock
Use of a Lock LUN or LVM Lock Disk as the Cluster Lock
Use of the Quorum Server as the Cluster Lock
No Cluster Lock
How the Package Manager Works
Package Types
Using Older Package Configuration Files
Using the Event Monitoring Service
Using the EMS HA Monitors
How Packages Run
What Makes a Package Run?
Before the Control Script Starts
During Run Script Execution
Normal and Abnormal Exits from the Run Script
Service Startup with cmrunserv
While Services are Running
When a Service, Subnet, or Monitored Resource Fails, or a Dependency is Not Met
When a Package is Halted with a Command
During Halt Script Execution
Normal and Abnormal Exits from the Halt Script
How the Network Manager Works
Stationary and Relocatable IP Addresses
Adding and Deleting Relocatable IP Addresses
Monitoring LAN Interfaces and Detecting Failure
Automatic Port Aggregation
VLAN Configurations
Volume Managers for Data Storage
Types of Redundant Storage
About Device File Names (Device Special Files)
Examples of Mirrored Storage
Examples of Storage on Disk Arrays
Types of Volume Manager
HP-UX Logical Volume Manager (LVM)
Veritas Volume Manager (VxVM)
Veritas Cluster Volume Manager (CVM)
Comparison of Volume Managers
Responses to Failures
System Reset When a Node Fails
Responses to Hardware Failures
Responses to Package and Service Failures
Service Restarts
Network Communication Failure
4 Planning and Documenting an HA Cluster
General Planning
Serviceguard Memory Requirements
Planning for Expansion
Hardware Planning
SPU Information
Network Information
Setting SCSI Addresses for the Largest Expected Cluster Size
Disk I/O Information
Hardware Configuration Worksheet
Power Supply Planning
Power Supply Configuration Worksheet
Cluster Lock Planning
Cluster Lock Disk and Re-formation Time
Planning for Expansion
Using a Quorum Server
LVM Planning
LVM Worksheet
CVM and VxVM Planning
CVM and VxVM Worksheet
Cluster Configuration Planning
Heartbeat Subnet and Re-formation Time
Cluster Configuration Parameters
Cluster Configuration: Next Step
Package Configuration Planning
Logical Volume and File System Planning
Planning Veritas Cluster Volume Manager (CVM) and Cluster File System (CFS)
Planning for Expansion
Choosing Switching and Failover Behavior
Parameters for Configuring EMS Resources
About Package Dependencies
About External Scripts
About Cross-Subnet Failover
Configuring a Package: Next Steps
Planning for Changes in Cluster Size
5 Building an HA Cluster Configuration
Preparing Your Systems
Installing and Updating Serviceguard
Learning Where Serviceguard Files Are Kept
Configuring Root-Level Access
Configuring Name Resolution
Ensuring Consistency of Kernel Configuration
Enabling the Network Time Protocol
Tuning Network and Kernel Parameters
Creating Mirrors of Root Logical Volumes
Choosing Cluster Lock Disks
Setting Up a Lock LUN
Setting Up and Running the Quorum Server
Creating the Storage Infrastructure and Filesystems with LVM and VxVM
Creating a Storage Infrastructure with LVM
Creating a Storage Infrastructure with VxVM
Configuring the Cluster
cmquerycl Options
Specifying a Lock Disk
Specifying a Lock LUN
Specifying a Quorum Server
Obtaining Cross-Subnet Information
Identifying Heartbeat Subnets
Specifying Maximum Number of Configured Packages
Modifying Cluster Timing Parameters
Controlling Access to the Cluster
Adding Volume Groups
Verifying the Cluster Configuration
Distributing the Binary Configuration File
Creating a Storage Infrastructure with Veritas Cluster File System (CFS)
Creating the Storage Infrastructure and Filesystems with Veritas Cluster Volume Manager (CVM)
Using DSAU during Configuration
Managing the Running Cluster
Checking Cluster Operation with Serviceguard Manager
Checking Cluster Operation with Serviceguard Commands
Preventing Automatic Activation of LVM Volume Groups
Setting up Autostart Features
Changing the System Message
Managing a Single-Node Cluster
Disabling identd
Deleting the Cluster Configuration
6 Configuring Packages and Their Services
Choosing Package Modules
Types of Package: Failover, Multi-Node, System Multi-Node
Package Modules and Parameters
Generating the Package Configuration File
Before You Start
cmmakepkg Examples
Next Step
Editing the Configuration File
Verifying and Applying the Package Configuration
Adding the Package to the Cluster
How Control Scripts Manage VxVM Disk Groups
Configuring Veritas System Multi-node Packages
Configuring Veritas Multi-node Packages
7 Cluster and Package Maintenance
Reviewing Cluster and Package Status
Reviewing Cluster and Package Status with the cmviewcl Command
Managing the Cluster and Nodes
Starting the Cluster When all Nodes are Down
Adding Previously Configured Nodes to a Running Cluster
Removing Nodes from Participation in a Running Cluster
Halting the Entire Cluster
Automatically Restarting the Cluster
Managing Packages and Services
Starting a Package
Halting a Package
Moving a Failover Package
Changing Package Switching Behavior
Reconfiguring a Cluster
Updating the Cluster Lock Configuration
Reconfiguring a Halted Cluster
Reconfiguring a Running Cluster
Configuring a Legacy Package
Creating the Legacy Package Configuration
Creating the Package Control Script
Verifying the Package Configuration
Distributing the Configuration
Configuring Cross-Subnet Failover
Reconfiguring a Package
Migrating a Legacy Package to a Modular Package
Reconfiguring a Package on a Running Cluster
Reconfiguring a Package on a Halted Cluster
Adding a Package to a Running Cluster
Deleting a Package from a Running Cluster
Resetting the Service Restart Counter
Allowable Package States During Reconfiguration
Responding to Cluster Events
Single-Node Operation
Disabling Serviceguard
Removing Serviceguard from a System
8 Troubleshooting Your Cluster
Testing Cluster Operation
Start the Cluster using Serviceguard Manager
Testing the Package Manager
Testing the Cluster Manager
Testing the Network Manager
Monitoring Hardware
Using Event Monitoring Service
Using EMS (Event Monitoring Service) Hardware Monitors
Hardware Monitors and Persistence Requests
Using HP ISEE (HP Instant Support Enterprise Edition)
Replacing Disks
Replacing a Faulty Array Mechanism
Replacing a Faulty Mechanism in an HA Enclosure
Replacing a Lock Disk
Replacing a Lock LUN
On-line Hardware Maintenance with In-line SCSI Terminator
Replacing I/O Cards
Replacing SCSI Host Bus Adapters
Replacing LAN or Fibre Channel Cards
Off-Line Replacement
On-Line Replacement
After Replacing the Card
Replacing a Failed Quorum Server System
Troubleshooting Approaches
Reviewing Package IP Addresses
Reviewing the System Log File
Reviewing Object Manager Log Files
Reviewing Serviceguard Manager Log Files
Reviewing the System Multi-node Package Files
Reviewing Configuration Files
Reviewing the Package Control Script
Using the cmcheckconf Command
Using the cmscancl Command
Using the cmviewconf Command
Reviewing the LAN Configuration
Solving Problems
Serviceguard Command Hangs
Cluster Re-formations
System Administration Errors
Problems with Cluster File System (CFS)
Problems with VxVM Disk Groups
Package Movement Errors
Node and Network Failures
Troubleshooting Quorum Server
A Serviceguard Commands
B Enterprise Cluster Master Toolkit
C Designing Highly Available Cluster Applications
Automating Application Operation
Insulate Users from Outages
Define Application Startup and Shutdown
Controlling the Speed of Application Failover
Replicate Non-Data File Systems
Use Raw Volumes
Evaluate the Use of JFS
Minimize Data Loss
Use Restartable Transactions
Use Checkpoints
Design for Multiple Servers
Design for Replicated Data Sites
Designing Applications to Run on Multiple Systems
Avoid Node-Specific Information
Avoid Using SPU IDs or MAC Addresses
Assign Unique Names to Applications
Use uname(2) With Care
Bind to a Fixed Port
Bind to Relocatable IP Addresses
Give Each Application its Own Volume Group
Use Multiple Destinations for SNA Applications
Avoid File Locking
Restoring Client Connections
Handling Application Failures
Create Applications to be Failure Tolerant
Be Able to Monitor Applications
Minimizing Planned Downtime
Reducing Time Needed for Application Upgrades and Patches
Providing Online Application Reconfiguration
Documenting Maintenance Operations
D Integrating HA Applications with Serviceguard
Checklist for Integrating HA Applications
Defining Baseline Application Behavior on a Single System
Integrating HA Applications in Multiple Systems
Testing the Cluster
E Software Upgrades
Types of Upgrade
Rolling Upgrade
Non-Rolling Upgrade
Migration with Cold Install
Guidelines for Rolling Upgrade
Performing a Rolling Upgrade
Limitations of Rolling Upgrades
Before You Start
Running the Rolling Upgrade
Keeping Kernels Consistent
Migrating cmclnodelist entries from A.11.15 or earlier
Example of a Rolling Upgrade
Step 1.
Step 2.
Step 3.
Step 4.
Step 5.
Guidelines for Non-Rolling Upgrade
Migrating Cluster Lock PV Device File Names
Other Considerations
Performing a Non-Rolling Upgrade
Limitations of Non-Rolling Upgrades
Steps for Non-Rolling Upgrades
Guidelines for Migrating a Cluster with Cold Install
Checklist for Migration
F Blank Planning Worksheets
Worksheet for Hardware Planning
Power Supply Worksheet
Quorum Server Worksheet
LVM Volume Group and Physical Volume Worksheet
VxVM Disk Group and Disk Worksheet
Cluster Configuration Worksheet
Package Configuration Worksheet
G Migrating from LVM to VxVM Data Storage
Loading VxVM
Migrating Volume Groups
Customizing Packages for VxVM
Customizing Packages for CVM
Removing LVM Volume Groups
H IPv6 Network Support
IPv6 Address Types
Textual Representation of IPv6 Addresses
IPv6 Address Prefix
Unicast Addresses
IPv4 and IPv6 Compatibility
Network Configuration Restrictions
IPv6 Relocatable Address and Duplicate Address Detection Feature
Local Primary/Standby LAN Patterns
Example Configurations
I Maximum and Minimum Values for Cluster and Package Configuration Parameters

List of Figures

1-1 Typical Cluster Configuration
1-2 Typical Cluster After Failover
1-3 Tasks in Configuring a Serviceguard Cluster
2-1 Redundant LANs
2-2 Mirrored Disks Connected for High Availability
2-3 Cluster with High Availability Disk Array
2-4 Cluster with Fibre Channel Switched Disk Array
2-5 Eight-Node Active/Standby Cluster
2-6 Eight-Node Cluster with XP or EMC Disk Array
3-1 Serviceguard Software Components
3-2 Lock Disk or Lock LUN Operation
3-3 Quorum Server Operation
3-4 Package Moving During Failover
3-5 Before Package Switching
3-6 After Package Switching
3-7 Rotating Standby Configuration before Failover
3-8 Rotating Standby Configuration after Failover
3-9 CONFIGURED_NODE Policy Packages after Failover
3-10 Automatic Failback Configuration before Failover
3-11 Automatic Failback Configuration After Failover
3-12 Automatic Failback Configuration After Restart of Node 1
3-13 Legacy Package Time Line Showing Important Events
3-14 Package Time Line
3-15 Legacy Package Time Line for Halt Script Execution
3-16 Cluster Before Local Network Switching
3-17 Cluster After Local Network Switching
3-18 Local Switching After Cable Failure
3-19 Aggregated Networking Ports
3-20 Physical Disks Within Shared Storage Units
3-21 Mirrored Physical Disks
3-22 Multiple Devices Configured in Volume Groups
3-23 Physical Disks Combined into LUNs
3-24 Multiple Paths to LUNs
3-25 Multiple Paths in Volume Groups
4-1 Sample Cluster Configuration
5-1 Access Roles
E-1 Running Cluster Before Rolling Upgrade
E-2 Running Cluster with Packages Moved to Node 2
E-3 Node 1 Upgraded to new HP-UX version
E-4 Node 1 Rejoining the Cluster
E-5 Running Cluster with Packages Moved to Node 1
E-6 Running Cluster After Upgrades
H-1 Example 1: IPv4 and IPv6 Addresses in Standby Configuration
H-2 Example 1: IPv4 and IPv6 Addresses after Failover to Standby
H-3 Example 2: IPv4 and IPv6 Addresses in Standby Configuration
H-4 Example 2: IPv4 and IPv6 Addresses After Failover to Standby
Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© Hewlett-Packard Development Company, L.P.