![]() ![]() ![]() |
Chapter 3: Common Task Summary
This chapter provides you with a brief overview of the basic tasks needed to configure an HACMP for Linux cluster. It contains the following sections:
The HACMP for AIX 5L Administration Guide contains a detailed description of WebSMIT components and how to use them. It also describes in detail all the configuration tasks, including the tasks listed in this chapter.
Features
HACMP for Linux has the following features.
It supports:
Eight nodes in the cluster. The heartbeating function that is carried over interfaces configured on IP-based networks and on serial networks. Also, heartbeating over IP aliases is supported. Ethernet and TokenRing as IP-based networks. RS232 serial network can be configured in the cluster for non-IP heartbeating (highly recommended). The HACMP snapshot function. It allows you to take a snapshot of an existing cluster configuration and recreate an identical cluster in a few steps, by applying the snapshot. IPAT via IP aliasing is supported by default on IP-based cluster networks. HACMP for Linux does not support:
Sites in the cluster. Concurrent resource groups. The AIX 5L LVM (Logical Volume Manager) or NFS filesystems as resources in an HACMP cluster. HACMP for Linux does not keep filesystems or volume groups highly available. However, you can have NFS filesystems mounted on all nodes on which your application may be hosted in the cluster. Mixed clusters of AIX 5L and Linux, or mixed clusters of different distributions of Linux. Dynamic reconfiguration of cluster resources (DARE) is not supported. This means that after making changes to the previously configured cluster components for the changes to make effect, you must restart the cluster services. Configuration Requirements
Before configuring an HACMP for Linux cluster, ensure that the following requirements are met:
All OS-level network configuration is complete. Note that you may need to reconfigure the networks on your servers so that they comply with HACMP’s network requirements. In particular, ensure that the following requirements are met: Install all network cabling to provide the necessary physical connectivity. Configure all network IP interfaces on their boot-time addresses. Ensure that the subnet that you plan to use as a subnet for service IP labels is left unused. That is, none of the IP interfaces are configured to boot to addresses configured on the service subnet. This is required for the IPAT via IP aliasing function of HACMP. You may need to obtain an extra subnet from a networking administrator in your facility.
Include all IP labels that are defined to HACMP on all cluster nodes in the /etc/hosts file on each cluster node. The IP labels must be unique. Install and configure the application to be made highly available with the use of HACMP: Write and save the application start and stop scripts on one of the nodes. The application start and stop scripts constitute an application server that you configure in HACMP as a resource. Identify and include the service IP label required by the application server in the /etc/hosts file on at least one node (this node can serve as a home node for the resource group in which you will include the application). Understanding Cluster Network Requirements and Heartbeating
To avoid a single point of failure, the cluster should have more than one network configured. Often the cluster has both IP and non-IP based networks, which allows HACMP to use different heartbeat paths. Use the Add a Network to the HACMP Cluster WebSMIT panel to configure HACMP IP and point-to-point networks.
You can use any or all of these methods for heartbeat paths:
Point-to-point networks IP-based networks, including heartbeating using IP aliases. Launching the WebSMIT Interface
Use WebSMIT to:
Navigate the running cluster. View and customize graphical displays of networks, nodes and resource group dependencies. View the status of any connected node (with HACMP cluster services running on the nodes). Starting WebSMIT
For instructions on integrating WebSMIT with your Apache server, and for launching WebSMIT, see the /usr/es/sbin/cluster/wsm/README readme file. It contains sample post-install scripts with variables. Each variable is commented with an explanation of its purpose along with the possible values. You can modify the values of the variables to influence the script behavior.
To start WebSMIT:
1. Using a web browser, navigate to the secure URL of your cluster node, for instance enter the URL similar to the following:
https://<server_name>.<domain_name>.com:42267The 42267 is the name of the port for HACMP for Linux. The <domain_name> entry is optional, it is only necessary if you are logging in to a server that is not part of your local network. The system asks you to log in.
2. Log in to the system and press Continue. WebSMIT starts.
WebSMIT Tasks Overview
The main WebSMIT menu in HACMP for Linux contains the following menu items and tabs:
Extended Configuration to configure your cluster. System Management (C-SPOC). C-SPOC (Cluster Single Point of Control) is an HACMP function that lets you run HACMP cluster-wide configuration commands from one node in the cluster. In HACMP for Linux, you can use System Management (C-SPOC) to start and stop the cluster services and to move, bring online and bring offline resource groups. Problem Determination Tools. You can customize cluster verification, view current cluster state, view logs, recover from a cluster event failure, configure error notification methods and perform other troubleshooting tasks. HACMP Documentation. This is the top-level tab that contains a page with links to all online and printable versions of HACMP documentation, including this guide. Here is the top-level HACMP for Linux WebSMIT menu:
Tasks for Configuring a Basic Cluster
You configure an HACMP for Linux cluster using the Extended Configuration path in WebSMIT.
Note: In general, the sections in this guide provide a high-level overview of user interface options. See the HACMP for AIX 5L Administration Guide for detailed procedures, field help, and recommendations for configuring each and every HACMP component.
To configure a basic cluster:
1. On one cluster node, configure a cluster name and add cluster nodes. See:
2. On each cluster node, configure all supporting networks and interfaces: serial networks for heartbeating and IP-based cluster networks for cluster communication.
Also, configure communication devices (that you must have previously defined to the operating system) to HACMP. Configure boot network interfaces (that you must have previously defined to the operating system) to HACMP. Also, configure persistent IP labels for cluster administration purposes. See:
3. On one cluster node, configure cluster resources that will be associated with the application: service IP labels, application servers and application monitors. See:
4. On one cluster node, include resources into resource groups. See Including Resources into Resource Groups.
5. Synchronize the cluster configuration. See Synchronizing the HACMP Cluster Configuration.
6. View the HACMP cluster configuration. See Displaying the HACMP Cluster Configuration.
7. Start the HACMP for Linux cluster services on the cluster nodes. When you do so, HACMP will activate the resource group with the application, and will start monitoring it for high availability. See Starting HACMP Cluster Services.
Defining a Cluster Name
Before starting to configure a cluster:
Make sure that you added all necessary entries to the /etc/hosts file on each machine that will serve as a cluster node. See Planning IP Networks and Network Interfaces. Make sure that WebSMIT is installed and can be started on one of the nodes. See Installing and Configuring WebSMIT. Log in to WebSMIT. See Starting WebSMIT. The only step necessary to configure a cluster is to assign the cluster name. When you assign a name to your cluster in WebSMIT, HACMP associates this name with the HACMP-assigned cluster ID.
To assign a cluster name and configure a cluster:
1. Log in to a URL where WebSMIT is installed. The browser window displays the top-level WebSMIT screen.
2. In WebSMIT, select Extended Configuration > Extended Topology Configuration > Configure an HACMP Cluster > Add/Change/Show an HACMP Cluster and press Continue.
3. Enter field values as follows:
Cluster Name Enter an ASCII text string that identifies the cluster. The cluster name can include alphanumeric characters and underscores, but cannot have a leading numeric. Use no more than 32 characters. Do not use reserved names. For a list of reserved names see List of Reserved Words.
4. Press Continue. If you are changing an existing cluster name, restart HACMP for changes to take effect.
Adding Nodes and Establishing Communication Paths
To add nodes to an HACMP cluster:
1. Log in to a URL where WebSMIT is installed. The browser window displays the top-level WebSMIT screen.
2. In WebSMIT, select Extended Configuration > Extended Topology Configuration > Configure HACMP Nodes > Add a Node to the HACMP Cluster and press Continue.
3. Enter field values as follows:
Once communication paths are established, HACMP adds a new node to the cluster.
4. Repeat this procedure to add up to eight cluster nodes.
5. Proceed to other options in the Extended Configuration panel to configure the resources to be made highly available, and assign resources that are to be managed together by HACMP into resource groups.
Configuring Serial Networks for Heartbeating
To configure a serial network that will be used for heartbeating in an HACMP cluster:
1. Log in to a URL where WebSMIT is installed. The browser window displays the top-level WebSMIT screen.
2. In WebSMIT, select Cluster Configuration and Management > Extended Configuration > Configure HACMP Networks > Add a Network and press Continue.
3. In the selector screen, select Predefined Serial Network Types and the type of network, such as rs232 and press Continue. The Add a Serial Network to HACMP Cluster screen appears.
4. Fill in the fields on the Add a non IP-based Network panel as follows:
Network Name Name the network, using no more than 32 alphanumeric characters and underscores; do not begin the name with a numeric. Do not use reserved names. For a list of reserved names, see List of Reserved Words. Network Type Valid type is RS232.
5. Press Continue to configure this network.
6. Repeat the operation to configure more networks.
For information on testing a serial connection, see Troubleshooting the Serial Connection.
Adding IP-Based Networks
To configure an IP-based cluster network:
1. Log in to a URL where WebSMIT is installed. The browser window displays the top-level WebSMIT screen.
2. In WebSMIT, select Extended Configuration > Configure HACMP Networks > Add a Network to the HACMP Cluster and press Continue.
3. In the selector screen, select Predefined IP-based Network Types, and then select the type of network, such as ether and press Continue. The Add an IP-Based Network to the HACMP Cluster window appears.
In the entry fields, values for the interface name on the local node are already filled in. HACMP discovers them automatically.
4. Enter the information as follows:
5. Press Continue to configure this network.
6. Repeat the operation to configure more networks.
Configuring Communication Interfaces/Devices to HACMP
To configure network interfaces and devices in HACMP for Linux, ensure that communication interfaces and devices are already configured to the operating system
Now you need to configure them to HACMP. See
Configuring Predefined Communication Interfaces to HACMP
The Predefined Communication Interfaces panel provides fields and picklists that enable you to choose configuration options quickly.
While choosing options, make sure that your choices do not conflict with the existing network topology. For example, if your operating system configuration refers to a Token-Ring NIC (Network Interface Card), make sure that HACMP refers to the same type of network interface card (for example, not an Ethernet NIC).
Before defining communication interfaces to HACMP, make sure that:
IP addresses you are defining to HACMP appear in the ifconfig output, as in the following example: #ifconfigeth0 Link encap:Ethernet HWaddr 00:0D:60:1E:C4:E8inet addr:1.1.1.1 Bcast:1.1.1.255 Mask:255.255.255.0You have entered them in the /etc/hosts file on each cluster node. If you are adding boot network interfaces to the HACMP configuration, you need to tell HACMP on what NIC the boot interface is configured in the operating system. Use the ifconfig command to determine that. Note that HACMP discovers this information (and presents it to you in a picklist) for the local node, that is, the node on which you are running the WebSMIT session to add interfaces. However, you need to supply this information to HACMP about remote nodes.
To add predefined network interfaces to the HACMP cluster:
1. Log in to a URL where WebSMIT is installed. The browser window displays the top-level WebSMIT screen.
2. In WebSMIT, select Extended Configuration > Extended Topology Configuration > Configure HACMP Communication Interfaces/Devices > Add Communication Interfaces/Devices and press Continue.
A window appears that lets you add previously defined network interfaces or devices. Press Continue. WebSMIT displays a selector screen.
3. Select Communication Interfaces. The Select a Network Name panel appears.
4. Select a network name. The Add a Communication Interface panel appears.
5. Fill in the fields as follows:
6. Press Continue. You have added the communication interface(s) that were already predefined to the operating system to the HACMP cluster.
7. Verify the configuration by using the ifconfig command. For examples, see Verifying the Networks and Network Interfaces Configuration.
Configuring Boot Interfaces
If you are adding boot network interfaces to the HACMP configuration, you need to tell HACMP on what NIC the boot interface is configured in the operating system. Use the ifconfig command to determine that.
Note that HACMP discovers this information (and presents it in picklists) on the local node, that is, for the node on which you are running the WebSMIT session to add interfaces. However, you need to supply this information to HACMP about remote nodes.
To add boot network interfaces to the HACMP configuration, use the procedure in Configuring Predefined Communication Interfaces to HACMP.
Configuring Predefined Communication Devices to HACMP
To configure predefined serial devices to the HACMP cluster:
1. Log in to a URL where WebSMIT is installed. The browser window displays the top-level WebSMIT screen.
2. In WebSMIT, select Extended Configuration > Extended Topology Configuration > Configure HACMP Communication Interfaces/Devices > Add Communication Interfaces/Devices and press Continue. A panel appears that lets you add previously defined network interfaces or devices.
3. Select the Communications Devices and press Continue. WebSMIT displays the Add a Communications Device window.
4. Select the non IP-based network to which you want to add the devices.
5. Enter the field values as follows:
6. Press Continue after filling in all required fields. HACMP now checks the validity of the device configuration. You may receive warnings if a node cannot be reached.
7. Repeat until each node has all appropriate communication devices defined.
Adding Persistent IP Labels for Cluster Administration Purposes
We highly recommend assigning a persistent node IP label for a network on a node. A persistent label lets you have a node-bound address on a cluster network that you can use for administrative purposes to access a specific node in the cluster.
For instance, when the HACMP cluster services are running, your previously configured service IP labels may be hosted on any node in the cluster at any given time. Therefore, sending a ping command to those labels may not result in reaching a specific node. To guarantee access to a particular node, configure a persistent node IP label.
A persistent node IP label is an IP alias that can be assigned to a network for a specified node. A persistent node IP label:
Always stays on the same node (is node-bound) Becomes available at a node’s boot time and remains configured on that network when HACMP cluster services are stopped on that node. Co-exists with other IP labels present on an interface Does not require installing an additional physical interface on that node Is not part of any resource group. Prerequisites
If you are using persistent node IP labels/addresses, note the following issues:
Configure only one persistent node IP labels individually on each node per each cluster network. On an aliased network (this is the cluster network that is set up to use IPAT via IP Aliasing), a persistent label may be placed on the same subnet as the aliased service label, or it may be configured on an entirely different subnet. However, it must be placed on a different subnet than all boot IP labels on the network. You can remove a persistent IP label from the cluster configuration using the Delete a Persistent Node IP Label/Address WebSMIT panel. However, after the persistent IP label has been removed from the cluster configuration, it is not automatically deleted from the interface on which it was aliased. In order to completely remove the persistent IP label from the node, you should manually remove the alias with the ifconfig down command or reboot the cluster node. To add persistent node IP labels:
1. Log in to a URL where WebSMIT is installed. The browser window displays the top-level WebSMIT screen.
2. In WebSMIT, select Extended Configuration > Extended Topology Configuration > Configure HACMP Persistent Node IP Labels/Addresses > Add a Persistent Node IP Label and press Continue.
3. Enter the field values as follows:
4. Press Continue.
To change or show persistent node IP labels, use the Change/Show a Persistent Node IP label WebSMIT menu. To delete them, use the Delete a Persistent Node IP label menu.
Verifying the Networks and Network Interfaces Configuration
This section contains several examples of outputs and explains how to verify that you properly configured service IP aliases and netmasks to HACMP:
Verifying Service IP Aliases: Example 1
To view the configuration of service IP aliases, use the ifconfig command. Here is an example of the output of the ifconfig command in HACMP for Linux:
In this example:
Boot address is 192.9.201.1 configured on the network interface eth2 Service IP address is 1.1.1.1 In this example, you can see that eth2 is the boot address, and eth2:1 is the service address:
eth2 Link encap:Ethernet HWaddr 00:06:29:B9:1E:7D inet addr:192.9.201.1 Bcast:192.9.201.127 Mask:255.255.255.128 inet6 addr: fe80::206:29ff:feb9:1e7d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:59153 errors:0 dropped:0 overruns:0 frame:0 TX packets:18938 errors:0 dropped:0 overruns:0 carrier:0 collisions:1057 txqueuelen:1000 RX bytes:12670155 (12.0 Mb) TX bytes:3363938 (3.2 Mb) Interrupt:51 Base address:0xec00 eth2:1 Link encap:Ethernet HWaddr 00:06:29:B9:1E:7D inet addr:1.1.1.1 Bcast:1.255.255.255 Mask:255.255.255.128 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:51 Base address:0xec00To disable a network interface or an alias, run the ifdown <interface name> command.
Verifying Network Interfaces Configuration: Example 2
To verify the network interfaces configuration, use the ifconfig command, as in the following example:
eth0 Link encap:Ethernet HWaddr 00:06:29:DC:82:CA inet addr:192.9.201.3 Bcast:192.9.201.127 Mask:255.255.255.128 inet6 addr: fe80::206:29ff:fedc:82ca/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:28080 errors:0 dropped:0 overruns:0 frame:0 TX packets:27980 errors:0 dropped:0 overruns:0 carrier:0 collisions:3158 txqueuelen:1000 RX bytes:4624252 (4.4 Mb) TX bytes:13771958 (13.1 Mb) Interrupt:37 Base address:0xec00 eth1 Link encap:Ethernet HWaddr 00:06:29:B9:1F:71 inet addr:192.9.201.133 Bcast:192.9.201.255 Mask:255.255.255.128 inet6 addr: fe80::206:29ff:feb9:1f71/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5619 errors:1 dropped:0 overruns:0 frame:1 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:412380 (402.7 Kb) TX bytes:568 (568.0 b) Interrupt:51 Base address:0xec00 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:213 errors:0 dropped:0 overruns:0 frame:0 TX packets:213 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:15095 (14.7 Kb) TX bytes:15095 (14.7 Kb) tr0 Link encap:16/4 Mbps Token Ring (New) HWaddr 00:60:94:8A:D3:13 inet addr:9.57.28.5 Bcast:9.57.28.127 Mask:255.255.255.128 inet6 addr: fe80::260:94ff:fe8a:d313/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:4056 Metric:1 RX packets:9143 errors:0 dropped:0 overruns:0 frame:0 TX packets:12880 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:1959859 (1.8 Mb) TX bytes:2909475 (2.7 Mb) Interrupt:38 Base address:0xec00Note that for each NIC there is a line similar to the following:
The address and netmask must match the values you enter in the WebSMIT configuration. After you define the addresses to HACMP, use the Show Cluster Topology WebSMIT screen to verify that these values match the values returned by the ifconfig command.
After the HACMP cluster services start, the service IP address is added to the NIC and the ifconfig output looks similar to the following:
In this configuration:
The boot address is 192.9.201.1 configured on interface eth2, The service IP address is 1.1.1.1 eth2 Link encap:Ethernet HWaddr 00:06:29:B9:1E:7D inet addr:192.9.201.1 Bcast:192.9.201.127 Mask:255.255.255.128 inet6 addr: fe80::206:29ff:feb9:1e7d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:59153 errors:0 dropped:0 overruns:0 frame:0 TX packets:18938 errors:0 dropped:0 overruns:0 carrier:0 collisions:1057 txqueuelen:1000 RX bytes:12670155 (12.0 Mb) TX bytes:3363938 (3.2 Mb) Interrupt:51 Base address:0xec00 eth2:1 Link encap:Ethernet HWaddr 00:06:29:B9:1E:7D inet addr:1.1.1.1 Bcast:1.255.255.255 Mask:255.255.255.128 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:51 Base address:0xec00Configuring Resources to Make Highly Available
In the WebSMIT menu Configure Resources to Make Highly Available, you configure the system’s resources to be known in HACMP. These are the resources that are associated with your application.
You configure resources that are to be shared among the nodes in the cluster, and kept highly available with HACMP, so that if one component fails, another component automatically takes its place.
Configure these resources (in any order):
Service IP label(s). This is the service IP label that an application’s clients use to connect to the application. HACMP ensures the availability of this IP label by recovering this IP label on other nodes as an alias. The IP label recovery is done with IPAT via IP Aliasing function. See Configuring Service IP Labels. Application servers (collections of application start and stop scripts) for the application you are making highly available. You provide scripts for starting and stopping your applications to HACMP. Have these scripts ready and specify their pathnames to HACMP. See Configuring Application Servers. Application monitors for your application. See Configuring Application Monitors. Configuring Service IP Labels
To add service IP labels/addresses as resources to the resource group in your cluster:
1. Log in to a URL where WebSMIT is installed. The browser window displays the top-level WebSMIT screen.
2. In WebSMIT, select Extended Configuration > Extended Resource Configuration > HACMP Extended Resources Configuration > Configure HACMP Service IP Labels/Addresses > Add a Service IP Label/Address and press Continue.
3. Fill in field values as follows:
4. Press Continue after filling in all required fields.
5. Repeat the previous steps until you have configured all service IP labels/addresses for each network, as needed.
Configuring HACMP Application Servers
An application server is a cluster component that is included in the resource group as a cluster resource, and that is used to control an application that must be kept highly available. An application server consists of application start and stop scripts. Configuring an application server does the following:
Associates a meaningful name with the server application. For example, you could give the tax software a name such as taxes. You then use this name to refer to the application server when you define it as a resource. When you set up the resource group, you add an application server as a resource. Points the cluster event scripts to the scripts that they call to start and stop the server application. Allows you to then configure application monitoring for that application server. Note that this section does not discuss how to write the start and stop scripts. See the vendor documentation for specific product information on starting and stopping a particular application.
Configuring Application Servers
To configure an application server on any cluster node:
1. Log in to a URL where WebSMIT is installed. The browser window displays the top-level WebSMIT screen.
2. In WebSMIT, select Extended Configuration > Extended Resource Configuration > HACMP Extended Resources Configuration > Configure HACMP Applications > Configure HACMP Application Servers > Add an Application Server and press Continue.
3. Enter field values as follows:
4. Press Continue to add this information to the HACMP Configuration Database on the local node.
5. Add the application start, stop and notification scripts to every node in the cluster.
Verifying Application Servers
Make sure that the application start, stop and notification scripts exist and are executable on every node in the cluster. Use the cllsserv command.
For example:
ppstest2:~ # /usr/es/sbin/cluster/utilities/cllsserv app_test2_primary /usr/local/app_start /usr/local/app_stop ppstest2:~ # ls -l /usr/local/app_start -rwxr--r-- 1 root root 169 May 10 22:54 /usr/local/app_startConfiguring Application Monitors
Once you configured application servers, HACMP for Linux lets you have application monitors that will check the health of the running application process, or check for the successful start of the application.
To configure application monitors:
1. Log in to a URL where WebSMIT is installed. The browser window displays the top-level WebSMIT screen.
2. In WebSMIT, select Extended Configuration > Extended Resource Configuration > HACMP Extended Resources Configuration > Configure HACMP Applications > Configure HACMP Application Monitoring and press Continue. A selector screen appears for Configure Process Application Monitoring and Configure Custom Application Monitoring.
3. Select the type of monitoring you want and press Continue.
4. Select the application server to which you want to add a monitor.
5. Fill in the field values and press Continue.
For additional reference information on application monitoring, its types, modes, and other information, see the HACMP for AIX 5L Administration Guide.
Including Resources into Resource Groups
Once you configure resources to HACMP, you include them in resource groups so that HACMP can manage them as a single set. For example, if an application depends on the service IP label, you can add it to a single resource group.
HACMP manages the resources in a resource group by bringing the resource groups online and offline on their home node(s), or moving them to other nodes, if necessary for recovery.
Note: For detailed instructions on resource groups, see the HACMP for AIX 5L Administration Guide. This guide contains descriptions of procedures in HACMP SMIT, and the options are identical to those used in WebSMIT in HACMP for Linux.
Resource Group Management: Overview
In the Extended Configuration > Extended Resource Configuration > HACMP Extended Resource Group Configuration WebSMIT screen, you can:
Add a resource group. Change/Show a resource group. The system displays all previously defined resource groups. After selecting a particular resource group, you can view and change the group name, node relationship, and participating nodes (nodelist). You can also change the group’s startup, fallover and fallback policies. Remove a resource group. Change/Show resources for a resource group. Add resources, such as a service IP label for the application, or an application server, to a resource group. HACMP always activates and brings offline these resources on a particular node as a single set. If you want HACMP to activate one set of resources on one node and another set of resources on another node, create separate resource groups for each set. Show all resources by node for a resource group. HACMP for Linux does not allow to change resources dynamically, that is, when HACMP cluster services are running on the nodes. To change the previously added resources, stop the cluster services.
Adding Resources to a Resource Group
To include resources into a resource group:
1. Log in to a URL where WebSMIT is installed. The browser window displays the top-level WebSMIT screen.
2. In WebSMIT, select Extended Configuration > Extended Resource Configuration > HACMP Extended Resources Configuration > Change/Show All Resources and Attributes for a Resource Group and press Continue.
3. Fill in the field values and press Continue. HACMP adds the resources.
For additional information on adding or changing resources in resource groups, and for information on other resource group management tasks, see the Administration Guide.
Synchronizing the HACMP Cluster Configuration
We recommend that you do all the configuration from one node and synchronize the cluster to propagate this information to other nodes.
Use this WebSMIT option to commit and distribute your changes automatically to all of the specified nodes.
To synchronize an HACMP cluster configuration:
1. Log in to a URL where WebSMIT is installed. The browser window displays the top-level WebSMIT screen.
2. In WebSMIT, select Extended Configuration > Extended Verification and Synchronization and press Continue.
If you configured the cluster correctly, HACMP synchronizes the configuration. HACMP issues errors if the configuration is not valid.
Displaying the HACMP Cluster Configuration
You can ask HACMP to show you the status of different configured components. The WebSMIT options for displaying different cluster entities are grouped together with the options for adding them to the cluster.
Here are some examples of the options you have:
Show HACMP Topology by node, by network name, or by communication interface Change/Show Persistent IP Labels Show Cluster Applications and change/show application monitors per application Change/Show Service IP Labels Show all Resources by Node or Resource Groups View cluster logs (In WebSMIT, it is under System Management > Log Viewing and Management) Show Cluster Services (whether running or not). Viewing the Cluster Status
HACMP has a cluster status utility, the /usr/es/sbin/cluster/clstat. It reports the status of key cluster components—the cluster itself, the nodes in the cluster, the network interfaces connected to the nodes, and the resource groups on each node.
clstat is available in WebSMIT at the left side of the top-level menu. It displays an expandable list of cluster components along with their status. The cluster status display window shows information and status (up or down, online, offline or error) on cluster nodes, networks, interfaces, application servers and resource groups. For resource groups, it also shows the node on which the group is currently hosted.
Here is an example of the clstat output in WebSMIT. This is the left-hand side panel of the window:
Here is an example of the ASCII-based output from the clstat command, used on a Linux cluster with nodes named ppstest1 and ppstest2:
ppstest2:~ # /usr/es/sbin/cluster/clstat clstat - HACMP Cluster Status Monitor ------------------------------------- Cluster: test1234 (1148058900) Wed May 17 16:45:41 2006 State: UP Nodes: 4 SubState: STABLE Node: ppstest1 State: UP Interface: tr0 (6) Address: 9.57.28.3 State: UP Resource Group: rg1 State: On line Node: ppstest2 State: UP Interface: tr0 (6) Address: 9.57.28.4 State: UP Resource Group: rg2 State: On line Node: ppstest3 State: UP Interface: tr0 (6) Address: 9.57.28.5 State: UP Node: ppstest4 State: UP Interface: tr0 (6) Address: 9.57.28.6 State: UP Resource Group: rg3 State: On line Resource Group: rg4 State: On lineSystem Management (C-SPOC) Tasks
Use the System Management (C-SPOC) panel in WebSMIT to configure from one node the resources that are shared among nodes. System Management utility of HACMP lets you administer many aspects of the cluster and its components from one Cluster Single Point of Control (C-SPOC). By automating repetitive tasks, C-SPOC eliminates a potential source of errors, and speeds up the cluster maintenance process.
In WebSMIT, you access C-SPOC using the System Management (C-SPOC) menu.
In this panel, you can do the following tasks from one node:
Manage HACMP services, or start and stop cluster services: Cluster Manager (clstrmgr) and Cluster Information (clinfo). HACMP Communication Interface Management. Manage the communication interfaces of existing cluster nodes using C-SPOC. HACMP Resource Group and Application Management Provides menus to manage cluster resource groups and analyze cluster applications. HACMP Log Viewing and Management. Manage, view, and collect HACMP log files and event summaries. Starting HACMP Cluster Services
To start HACMP cluster services:
1. Log in to a URL where WebSMIT is installed. The browser window displays the top-level WebSMIT screen.
2. In WebSMIT, select System Management (C-SPOC) > Manage HACMP Services > Start HACMP Services and press Continue.
For detailed instructions, see the HACMP on AIX 5L Administration Guide.
Stopping HACMP Cluster Services
To stop HACMP cluster services:
1. Log in to a URL where WebSMIT is installed. The browser window displays the top-level WebSMIT screen.
2. In WebSMIT, select System Management (C-SPOC) > Manage HACMP Services > Start HACMP Services and press Continue.
For detailed instructions, see the HACMP on AIX 5L Administration Guide.
Managing Resource Groups and Applications
To manage resource groups and applications:
1. Log in to a URL where WebSMIT is installed. The browser window displays the top-level WebSMIT screen.
2. In WebSMIT, select System Management (C-SPOC) > HACMP Resource Group and Application Management and press Continue.
For detailed instructions, see the HACMP on AIX 5L Administration Guide.
Viewing and Managing Logs
To view and manage logs:
1. Log in to a URL where WebSMIT is installed. The browser window displays the top-level WebSMIT screen.
2. In WebSMIT, select System Management (C-SPOC) > HACMP Log Viewing and Management and press Continue.
For detailed instructions, see the HACMP on AIX 5L Administration Guide.
List of Reserved Words
Do not use the following words as names in a cluster. However, you may use these words when combined with numerals or another word (for example, my_network or rs232_02).
Where You Go from Here
See the next chapter for information on additional cluster configuration tasks.
![]() ![]() ![]() |