Software Planning and Installation Guide
If you are currently using CSM 1.1, you will need to follow the
procedure in this section to move to the CSM 1.2 release.
- Step 1
- Mount the CSM 1.2 CD-ROM and run the
savenodedata1.1 command, as follows:
mount /dev/cdrom /mnt/cdrom
/mnt/cdrom/savenodedata1.1 > /tmp/nodedef.migrate
The savenodedata1.1 command generates the definitions for
the nodes that are currently in your cluster and redirects them to a file
called nodedef.migrate. Later in this procedure, you
will use the nodedef.migrate file to provide your current node
definitions to the new level of CSM.
- Step 2
- Remove all CSM 1.1 RPMs from the nodes as follows:
rpm -e csm.client csm.core rsct.core rsct.core.utils src
- Step 3
- Uninstall all of the CSM 1.1 and RSCT code as follows:
rpm -e csm.gui.dcem csm.dsh csm.server csm.core rsct.core rsct.core.utils src
- Note:
- cfengine was used by CSM 1.1, but its function is replaced in CSM
1.2 with rdist. Note that because you might be using cfengine
for other things, cfengine was not removed when you uninstalled CSM.
However, you can manually remove cfengine if you don't plan on using
it.
- Step 4
- Create a partition called /csminstall. See Step 2. Create the /csminstall partition for information on how to do this.
- Step 5
- Install the new version of the csm.core package from the
CSM 1.2 CD-ROM. See Step 4. Install the csm.core file set for information on how to do this.
- Step 6
- Install the remainder of CSM 1.2 and RSCT by running the
installms command. See Step 5. Install the CSM software for information on how to do this.
- Step 7
- Redefine the nodes of your cluster for CSM 1.2, using the
definenode command and the nodedef.migrate file, as
follows:
definenode -f /tmp/nodedef.migrate
Note that some of the node attributes that are used in CSM 1.2 were
not present in CSM 1.1. When you run the definenode
command, above, the missing attributes are filled in with defaults from the
management server or left blank, as needed.
- Step 8
- For CSM-only installations, upgrade to the latest level of CSM and RSCT,
using the updatenode command, as follows:
updatenode -P
Or, for a full installation, if you wish to copy the existing data
in /tftpboot to the new /csminstall directory, perform the
following steps:
- Run the csmsetupks command, using the -p flag to point to
the /tftpboot directory, as follows:
csmsetupks -p /tftpboot/rh71
Note also that if you customized the Kickstart configuration files when
you installed CSM 1.1, those configurations will be lost when you
install CSM 1.2. As a result, you will need to customize the new
configuration files. The CSM 1.1 Kickstart configuration files
were located in /tftpboot/ks71.
- If you wish to recover file system space, do the following:
rm -rf /tftpboot/rh71
- Run the installnode command:
installnode -P
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]