![]() ![]() ![]() |
Chapter 5: Installing HACMP on Client Nodes
This chapter describes how to install and configure the HACMP software on client systems. It also describes how to edit files and scripts related to the Cluster Information Program (Clinfo). This chapter contains the following sections:
Prerequisites
Before you install the HACMP software on client systems:
Make sure that the system has at least 2.6 MB available for the installation. Read the chapter on Planning for HACMP Clients in the Planning Guide. Read the Release Notes for HACMP in /usr/es/sbin/cluster/release_notes for additional information on installing the HACMP software. If you are installing HACMP on Linux, read the Linux Release Notes for HACMP in /usr/es/sbin/cluster/release_notes.linux/ for issues relevant to HACMP on the Linux platform. If you are using HAView, see section HAView Requirements in Chapter 4: Installing HACMP on Server Nodes. Install HACMP on the server nodes. For more information, see Chapter 4: Installing HACMP on Server Nodes.) Overview
Installing the HACMP software on each client that runs the clinfo daemon enables the clients to receive messages about events and actions taken by the high availability software running in the cluster. The client can take predefined, automatic steps in response to some situations handled by the high availability software, and it can print messages to inform users logged in to a client of the cluster state and thus make them aware of actions required to maintain connectivity.
Installing and Configuring HACMP on Client Systems
To install and configure the HACMP software on each client, complete these steps:
Step 1: Installing the Base System Client Images
For a new installation, the /usr directory requires a minimum of 2.6 MB of available space.
To install the base high availability software on a client:
1. Place the HACMP CD into the CD-ROM drive and enter:
smit install_selectable_allSMIT displays the Install Selectable All panel.
If you are not sure of the name of the input device, select one from the picklist. Select the proper drive and press Enter. That value is entered into the INPUT device/directory field as the valid input device. 2. Press Enter. SMIT refreshes the panel.
3. In the SOFTWARE to install field, use the picklist to select the client software modules associated with the following cluster images: cluster.es, cluster.msg, and cluster.adt.es.
Note: Note that if you select at least one client module associated with an installable image, all other required client modules are installed automatically.
4. Enter values for other fields as appropriate for your site.
5. Press Enter when you are satisfied with the entries.
SMIT prompts you to confirm your selections.
6. Press Enter again.
7. Read the HACMP release_notes file in the /usr/es/sbin/cluster/ directory for further instructions.
8. Copy the /usr/es/sbin/cluster/etc/clhosts.client file from the server to each client node, renaming it as /usr/es/sbin/cluster/etc/clhosts.
9. (Optional) Edit the clinfo.rc script as described in the section Step 3: Editing the clinfo.rc Script.
10. Reboot the client.
Repeat this procedure for each client system.
Step 2: Copying the clhosts.client File onto Client Nodes
During the verification phase of running the Two-Node Cluster Configuration Assistant, HACMP creates and populates a clhosts.client file on all HACMP servers.
Copy this /usr/es/sbin/cluster/etc/clhosts.client file from a HACMP server node to all client nodes, renaming it clhosts (remove the .client extension).
Step 3: Editing the clinfo.rc Script
The /usr/es/sbin/cluster/etc/clinfo.rc script updates the ARP cache on the local node whenever an event occurs. If you are not using IPAT via IP Replacement with Alternate Hardware Addresses, a copy of the /usr/es/sbin/cluster/etc/clinfo.rc script must exist on each server node and client in the cluster in order for all ARP caches to be updated.
The HACMP software is distributed with a template version of the /usr/es/sbin/cluster/etc/clinfo.rc script. You can use the script as distributed, modify it, or replace it with a custom script.
Note: If you are not using IPAT via IP Replacement with Alternate Hardware Addresses, the ARP function must remain in the clinfo.rc script.
The format of the clinfo call to clinfo.rc:
The clinfo utility obtains information about the interfaces and their current state, and checks for changed states of interfaces:
If a new state is UP, clinfo calls clinfo.rc join interface_name. If a new state is DOWN, clinfo calls clinfo.rc fail interface_name. If clinfo receives a node_down_complete event, it calls clinfo.rc with the fail parameter for each interface currently UP. If clinfo receives a fail_network_complete event, it calls clinfo.rc with the fail parameter for all associated interfaces. If clinfo receives a swap_complete event, it calls clinfo.rc swap interface_name. For complete information about cluster events and customizing scripts, see the chapter on Planning for Cluster Events in the Planning Guide.
For a sample client application that uses the Clinfo API within the context of a customized clinfo.rc script, see Programming Client Applications.
If you have custom applications that use the Clinfo API and plan to use symmetric multi-processors, you may need to modify your application. Afterwards, recompile and link your application. For updated information about the library routines, see the Programming Client Applications.
Step 4: Updating the ARP Cache for Clients Not Using Clinfo
On clients that are not running clinfo, you will need HACMP to update the client’s ARP cache by pinging the client from a cluster node when an IP address has moved. Add the client IP label you want to notify to the PING_CLIENT_LIST variable in the clinfo.rc script on each node. Now, whenever a cluster event occurs, clinfo.rc runs the following command for each host specified in PING_CLIENT_LIST:
Step 5: Rebooting the Clients
The final step in installing the HACMP software on a client is to reboot the client.
![]() ![]() ![]() |