Installation guide

Release Notes
7. If the cluster uses Panasas storage, then you should have already downloaded the Panasas rpm that matches the Scyld
ClusterWare 4.9.0 kernel you have just installed. Now install the Panasas rpm using rpm -i.
8. Configure the network for Scyld ClusterWare: run /usr/sbin/beonetconf to specify the cluster interface, the maximum
number of compute nodes, and the beginning IP address of the first compute node. See the Installation Guide for more
details.
9. If the private cluster network switch uses Spanning Tree Protocol (STP), then either reconfigure the switch to disable
STP, or if that is not feasible because of network topology, then enable Rapid STP or portfast on the compute node and
edge ports. See the Section called Issues with Spanning Tree Protocol and portfast for details.
10. Examine /etc/grub.conf to confirm that the new 2.6.9-100.490g0000.ELsmp kernel is the default, then reboot your
master node.
11. The first time Beowulf services start, e.g., when doing /sbin/service beowulf start or /etc/init.d/beowulf start, you will
be prompted to accept a Scyld ClusterWare End User License Agreement (EULA). If you answer with an affirmative
yes, then Beowulf services start and Scyld ClusterWare functionality is available, and you will not be prompted again
regarding the EULA.
However, if you do not answer with yes, then Beowulf services will not start, although the master node will continue
to support all non-Scyld ClusterWare functionality available from the base distribution. Any subsequent attempt to start
Beowulf services will again result in a prompt for you to accept the EULA.
Note: if Beowulf is configured to automatically start when the master node boots (i.e., /sbin/chkconfig --list beowulf
shows Beowulf on for levels 3, 4, and 5), then the first reboot after installing Scyld ClusterWare will fail to start Beowulf
because /etc/init.d/beowulf is not executed interactively and no human sees the prompt for EULA acceptance. In
this event, you may start Beowulf manually, e.g., using /sbin/service beowulf start, and respond to the EULA prompt.
Post-Installation Configuration Issues
Following a successful update or install of Scyld ClusterWare, you may need to make one or more configuration changes,
depending upon the local requirements of your cluster. Larger cluster configurations have additional issues to consider; see
the Section called Post-Installation Configuration Issues For Large Clusters.
Resolve *.rpmnew and *.rpmsave configuration file differences
As with every Scyld ClusterWare upgrade, after the upgrade you should locate any Scyld ClusterWare *.rpmsave and
*.rpmnew files and perform merges, as appropriate, to carry forward the local changes. Sometimes an upgrade will save the
locally modified version as *.rpmsave and overwrite the basic file with a new version. Other times the upgrade will keep
the locally modified version untouched, installing the new version as *.rpmnew.
For example,
cd /etc/beowulf
find . -name \*rpmnew
find . -name \*rpmsave
and examine each such file to understand how it differs from the configuration file that existed prior to the update. You may
need to merge new lines from the newer *.rpmnew file into the existing file, or perhaps replace existing lines with new
modifications. For instance, this is commonly done with /etc/beowulf/config and config.rpmnew. Or you may need
to merge older local modifications in *.rpmsave into the newly installed pristine version of the file. For instance, this is
occasionally done with /etc/beowulf/fstab.rpmsave.
5