 | Level: Introductory Harish Chauhan (hchauhan@in.ibm.com), Linux Architect, IBM
20 May 2005 As you all know, managing a large set of machines in an IT industry, for various activities, is very difficult. The IBM® Cluster Systems Management (CSM) tool simplifies this process. Follow along as IBM Linux™ Architect Harish Chauhan provides step-by-step instructions on how to install the CSM tool.
Introduction
A system administrator can easily manage a large cluster of machines with ease and comfort. Beginners who have very little knowledge about setting up a CSM environment can use this article as a guide. The main example considers a homogeneous environment, which means that all the machines in a cluster have the same operating system installed.
Hardware, software, and setup
Use the following hardware and software for your setup:
- xSeries® server model: x345 (8670-IQS) with dual processors
- IBM CSM Version 1.4.0.13
- Red Hat Enterprise Linux (RHEL) Advanced Server Version 3.0 with update 3 or 4 / SUSE Linux Enterprise Server for POWER (SLES) 9.1
- i386 architecture
Figure 1. Setup diagram
Follow these steps to properly install the CMS tool:
- Follow the installation and configuration information for your hardware and software.
- Set up the network connectivity among the machines, as shown in Figure 1.
- Set up the CSM master:
- Identify and designate the CSM master machine. In your setup, choose master.my.com as your CSM master.
- Update the
/etc/hosts file for the hostname/IP details.
10.10.10.100 master.my.com my # IP master
10.10.10.1 node1.my.com node1 # IP of 1st node
10.10.10.2 node2.my.com node2 # IP of 2nd node
|
- Insert the CSM CD in the DVD/CDROM drive.
- Extract the CSM code into the /dump/csm_dump directory.
#tar xvf /dump/csm_dump/csm-linux-1.4.0.13.i386.tar.gz
|
- Copy the Red Hat CDs into the /dump/rereqs directory, as some Red Hat RPMs are required prerequisites for the CSM master.
- Download autoupdate rpms from http://freshmeat.net/projects/autoupdate.
- Install the CSM core file.
#rpm -ivh /dump/csm_dump/csm.core-1.4.0.13-105.i386 |
This copies the necessary installation scripts in the /opt/csm/bin folder.
- Run
installms, where /dump/prereqs/RedHat/RPMS contains Red Hat RPMS and
/dump/csm_dump contains CSM code.
#cd /opt/csm/bin
#./installms -p /dump/csm_dump:/dump/prereqs/RedHat/RPMS
|
The above image doesn't show the complete output.
- Before you can use this master, you have to activate the "Try and Buy" or the "Permanent license" option, enter:
Note : "MaxNumNodesInDomain = 0" and "ExpDate = ".
- To activate the Try and Buy license option, enter:
#/opt/csm/bin/csmconfig -L
|
When you accept the license message, you are free to test the master for next 90 days.
- For activating the Permanent license option, enter:
#/opt/csm/bin/csmconfig -L /dump/csm_dump/csmlum.full
|
The csmlum.full license file is available on your purchased CD.
- To check the status of the license, enter:
- Now CSM master is ready and you're all set to define the nodes. The nodes that are managed by this master are known as
ManagedNodes.
- To set the PATH variable, enter:
#export PATH=/opt/csm/bin:$PATH
|
- You can define the nodes in two ways:
-
#definenode -n node1
#definenode -n node2 |
-
#definenode -f node_def_file |
The node_def_file contains stanzas for each node as follows:
node1.my.com:
ManagementServer=master.my.com
InstallOSName=Linux
InstallCSMVersion=1.4.0
InstallDistributionName=RedHatEL-AS
InstallDistributionVersion=3
node2.my.com:
ManagementServer=master.my.com
InstallOSName=Linux
InstallCSMVersion=1.4.0
InstallDistributionName=RedHatEL-AS
InstallDistributionVersion=3
|
- After you add the node definition on the master, you can see the defined nodes by executing:
- Now its time to register the nodes.
Make sure the /etc/hosts file is up to date on all the nodes before executing the next command.
#updatenode -n node1
#updatenode -n node2
|
Or, try the following:
#updatenode -a [All the nodes]
|
- The
Monitorinstall command shows you the status of all the nodes.
#monitorinstall
Node Mode Status
------------------------------------------
node1 Managed Installed
node2 PreManaged Not Installed
|
- Make sure your CSM master and nodes are successfully installed and configured.
- To test, enter:
#export DSH_LIST=/etc/node_list |
The node_list contains a shortname of your nodes, one hostname per line.
- To display the date output from both nodes, enter:
- To show the status of all the nodes, whether they are "alive" or not, enter:
node1: 1 (Alive)
node2: 1 (Alive) |
-
The Distributed Command Execution Manager (DCEM) GUI is included in the CSM for management of nodes.
-
You need to make a back up of the CSM and ERRM after every major change in the setup.
- Use the
backup command to perform the backup:
This command will back up the CSM master in the /var/opt/csm/csmdata directory.
- To back up other files where <my_files> are
/etc/dhcpd.conf, /etc/hosts, and so forth, enter:
- To back up the node data, enter:
#lsnode -F > /csmbackup/node.data
#nodegrp -L > /csmbackup/nodegrp.data
|
- To backup ERRM data, enter:
#lsrsrc -i IBM.Condition > / csmbackup/errmconditions.data
#lsrsrc -i IBM.Response > / csmbackup/errmresponses.data
#lscondresp -lx > /csmbackup/errmcondresp.data
|
You should always back up the following directories:
- /csminstall
- /etc/opt/csm
- /var/opt/csm
- Perform the following steps to restore.
- To restore, enter:
The hostname and operating system on the master shouldn't change while performing the backup.
- To restore node data, enter:
#definenode -f /csmbackup/node.data
#nodegrp -f /csmbackup/nodegrp.data
|
IBM.ConditionI and IBM.Response should be deleted before restoring the ERRM data.
- To restore ERRM data, enter:
#mkrsrc -f /csmbackup/errmconditions.data IBM.Condition
#mkrsrc -f /csmbackup/errmresponses.data IBM.Response
|
Resources
About the author | 
| | Harish has been with IBM since 1998 and has 14 years of experience. During his last eight years with IBM, he has spent five years at the India Research Lab and one year at the IBM T.J.Watson Research Center. Harish has been leading the Linux Center of Competency in Bangalore, India for the past year and a half. You can contact him at hchauhan@in.ibm.com. |
Rate this page
| |
