The IBM eServer BladeCenter JS20 - IBM Redbooks

Management node selection
Each CSM cluster requires a management node, which provides the central point
of administration and control for the entire cluster. CSM has complex rules
concerning the compatibility of management nodes, non-management nodes
(cluster nodes), and the operating system they run. We attempt to simplify these
rules by focusing exclusively on the requirements for a management node that
only manages BladeCenter JS20s. If your environment is more complex, refer to
the CSM planning documents.
You can use a CSM management node to both install and manage BladeCenter
JS20s, or you can use a management node to manage BladeCenter JS20s that
were installed using other mechanisms. Most environments use CSM to both
install and manage BladeCenter JS20s, so we focus on that scenario.
If you use a management node to both install and manage BladeCenter JS20s
running Linux, you must use the same type of Linux distribution on both the
management node and the BladeCenter JS20s. However, the management node
does not need the same processor architecture that is used in the BladeCenter
JS20.
For example, if you plan to install SLES on BladeCenter JS20s, you can use the
following types of management node and operating system combinations to both
install and manage the BladeCenter JS20s:
► A supported xSeries server running SLES
► A supported pSeries server running SLES
► A IBM HS20 Blade Server running SLES
► A IBM BladeCenter JS20 running SLES
In large installations, we recommend that you use either an xSeries or pSeries
server as a management node. If your environment also contains
non-BladeCenter JS20s, such as the HS20 Blade Server, or xSeries cluster
nodes, we recommend that you use an xSeries management node such as the
xSeries 345.
We performed our testing of CSM using an xSeries management node, since
many users of the BladeCenter JS20 may have environments that includes HS20
Blade Servers.
Chapter 4. Planning considerations 65