The IBM eServer BladeCenter JS20 - IBM Redbooks
The IBM eServer BladeCenter JS20 - IBM Redbooks
The IBM eServer BladeCenter JS20 - IBM Redbooks
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>The</strong> csmsetupyast command uses an XML template file found in /opt/csm/install<br />
as a default template for the Autoyast configuration files that it creates for each<br />
<strong>BladeCenter</strong> <strong>JS20</strong> cluster node. Depending upon the release of SuSE that you<br />
are using at the time, the file has the format:<br />
yastcfg.InstallDistributionNameInstallDistributionVersion-Arch.xml<br />
For example, in our lab environment, the file was called<br />
yastcfg.SLES9-ppc64.xml.<br />
If you want to use a different template, first create the template and then specify it<br />
on the csmsetupyast command using the -k option. We recommend that you<br />
copy the default template when creating new templates to ensure that you<br />
include all the elements that CSM requires in the template.<br />
Review the output of the csmsetupyast command carefully and resolve any errors<br />
before you proceed further.<br />
Starting the cluster node installation<br />
Start the cluster node installation using the installnode command. We<br />
recommend that you try to install a few nodes at first and make sure it works<br />
before you try to install many the nodes concurrently. To start installation of a<br />
single node, use the command:<br />
installnode -n blade1<br />
<strong>The</strong> installnode command takes a few minutes to complete when used with<br />
<strong>BladeCenter</strong> <strong>JS20</strong> cluster nodes. This is because the installnode command<br />
must wait until the <strong>BladeCenter</strong> <strong>JS20</strong> boot process has reached the point where<br />
it can pass network installation parameters to the firmware.<br />
When the installation is underway, the installnode command exits and displays<br />
the status for each node it was asked to install. You can monitor the status of the<br />
install as it progresses using the monitorinstall command. You can also open a<br />
remote console to watch the installation progress using the rconsole command.<br />
For more information about installing CSM, see CSM for Linux: Planning and<br />
Installation Guide, SA22-7853.<br />
158 <strong>The</strong> <strong>IBM</strong> Eserver <strong>BladeCenter</strong> <strong>JS20</strong>