This chapter describes how to install the SGI Cluster Manager for Linux software.
This chapter discusses the following:
The following packages are required:
Required GUI infrastructure packages from the SUSE LINUX Enterprise Server 9 (SLES9) CDs (some of these may be already installed depending on the installation options selected):
control-center2-2.4.0-166.1.ia64.rpm eel-2.4.2-72.1.ia64.rpm gdk-pixbuf-0.22.0-62.1.ia64.rpm gnome-desktop-2.4.1.1-132.1.ia64.rpm gnome-panel-2.4.2-63.1.ia64.rpm libglade-0.17-230.1.ia64.rpm libgnomeprint-2.5.3-43.1.ia64.rpm libgnomeprintui-2.5.3-46.1.ia64.rpm libwnck-2.4.0.1-125.1.ia64.rpm libzvt-2.0.1-54.1.ia64.rpm metacity-2.6.3-71.1.ia64.rpm nautilus-2.4.2-50.1.ia64.rpm python-gtk-2.0.0-215.1.ia64.rpm python-xml-2.3.3-88.1.ia64.rpm pyxml-0.8.3-185.1.ia64.rpm startup-notification-0.5-319.1.ia64.rpm |
Required GUI infrastructure packages from the SGI Cluster Manager base product CD:
python-gnome-2.0.3-2.ia64.rpm python-orbit-2.0.0-177.ia64.rpm |
Required base product packages from the SGI Cluster Manager base product CD:
clumanager-2.0.0-sles9sgi400r3.ia64.rpm
sgi-cluster-manager-docs-4.0-1.noarch.rpm
sgicm-config-cluster-2.0.0-sles9sgi400r3.noarch.rpm
| Note: The sgicm-config-cluster RPM is dependent upon the clumanager RPM. You must install the clumanager-2.0.0 RPM first. |
Optional high-availability plug-ins for CXFS, DMF, TMF, and local XVM from the SGI Cluster Manager storage software plug-ins CD:
clumanager-sgi-2.0.0-sles9sgi400r3.ia64.rpm |
For additional information, see the README file.
Do the following:
If necessary, upgrade to the supported level of SGI ProPack according to the directions in SGI ProPack for Linux Start Here. See “Software Requirements” in Chapter 1.
Insert the SGI Cluster Manager 4.2 for Linux -- Base Product CD and do the following to mount the CD and see its contents:
# mount /dev/cdrom /mnt/cdrom # cd /mnt/cdrom # ls COPYING README RPM_MD5_SUMS SGI TRANS.TBL |
Read the README file to learn about any late-breaking changes in the installation procedure and exact RPM names.
Install the following additional GUI infrastructure RPMs by using the rpm(8) command:
# rpm -Uvh python-gnome-* python-orbit-* |
Install the SGI Cluster Manager software from the base CD:
# rpm -Uvh clumanager-*.rpm sgi-cluster-manager-docs-*.rpm \ sgicm-config-cluster-*.rpm |
If you have purchased the optional high-availability product for CXFS, DMF, TMF, and local XVM, insert the SGI Cluster Manager 4.2 for Linux -- Storage Software Plug-ins CD. Do the following to mount the CD and see its contents:
# mount /dev/cdrom /mnt/cdrom # cd /mnt/cdrom # ls COPYING README RPM_MD5_SUMS SGI TRANS.TBL |
Read the README file to learn about any late-breaking changes in the installation procedure and exact RPM names.
Install the software from the CD:
# rpm -Uvh clumanager-sgi-*.rpm |
If you intend to use L2 serial port connections in your cluster (see “Power Control” in Chapter 2), you must assure that the ioc4_serial module is loaded when the system boots. Edit the file /etc/sysconfig/kernel and find the line that starts with MODULES_LOADED_ON_BOOT. It may look something like this:
MODULES_LOADED_ON_BOOT="job numatools xpmem fetchop mmtimer csa mca_recovery" |
Change this line to include ioc4_kernel:
MODULES_LOADED_ON_BOOT="job numatools xpmem fetchop mmtimer csa mca_recovery ioc4_serial" |
| Note: This change will take effect at the next reboot. |
To upgrade from the previous release, do the following:
Relocate all services to one member. For example:
# clusvcadm -r service -m member |
For more information, see “Service Administration” in Chapter 5.
Stop cluster daemons on the member to be upgraded. For example:
# /etc/init.d/clumanager stop |
For more information, see “Stopping Cluster Processes” in Chapter 5.
Install the new software as described in “Installing the Software”.
Start the cluster daemons on the member. For example:
# /etc/init.d/clumanager start |
For more information, see “Starting Cluster Processes” in Chapter 5.
Relocate the services to the upgraded member if needed. For example:
# clusvcadm -r service -m member |
For more information, see “Service Administration” in Chapter 5.
If you modified /usr/lib/clumanager/create_device_links, restore your modifications by copying the backup file that is automatically made:
# cp /usr/lib/clumanager/create_device_links.rpmsave /usr/lib/clumanager/create_device_links |
| Note: When you install the SGI Cluster Manager software, a new /usr/lib/clumanager/create_device_links file is installed. If the create_device_links file was modified, the changed file will be will be saved as /usr/lib/clumanager/create_device_links.rpmsave . |
To uninstall the software, use the following command:
rpm -e rpm_name |
Uninstalling the clumanager RPM will attempt to stop cluster daemons in the local node.
For example:
# rpm -e clumanager-2.0.1-sles9sgi400r4.ia64.rpm \ clumanager-sgi-2.0.1-sles9sgi400r4.ia64.rpm \ sgi-cluster-manager-docs-4.2-1.noarch.rpm \ sgicm-config-cluster-2.0.1-sles9sgi400r4.noarch.rpm |
| Note: The above is an example. You must provide complete RPM names. Check the documentation and your system to determine the correct RPM names for your system. |
For more information, see the rpm(8) man page.