HACMP

Configuring HACMP Using the Standard Configuration Path
Using the options under the Initialization and Standard Configuration SMIT menu, you can
add the basic components of the HACMP cluster to the HACMP Configuration Database
(ODM) in a few steps. This configuration path significantly automates the discovery and
selection of configuration information and chooses default behaviors.
The prerequisites and default settings of this path are:
• Connectivity for communication must already be established between all cluster nodes.
Automatic discovery of cluster information runs by default. That is, once you have
configured communication interfaces/devices and established communication paths to
other nodes, HACMP automatically collects HACMP-related information and
automatically configures the cluster nodes and networks based on physical connectivity.
All discovered networks are added to the cluster configuration. This helps you in the
configuration process.
To understand how HACMP maintains the security of incoming connections, see the
section Managing Cluster Security and Inter-Node Communications in this chapter.
• IP aliasing is used as the default mechanism for binding service IP labels/addresses to
network interfaces. For more information, see the chapter on Planning Cluster Network
Connectivity in the Planning Guide.
• You can configure the most common types of resources. Customization of resource group
fallover/fallback behavior supports the most common scenarios.
Chapter 3: Configuring an HACMP Cluster (Standard) takes you through the configuration
process if you plan to use the Initialization and Standard Configuration path in SMIT. Once
you have configured the basic components, you can use the Extended Configuration path to
customize your configuration.