5 Discovering the Hardware Components
This chapter describes the following tasks, which you must complete in the order shown:
• “Task 1: Prepare for the System Configuration” (page 27)
• “Task 2: Change the Default IP Address Base (Optional)” (page 28)
• “Task 3: Use the cluster_prep Command to Prepare the System” (page 28)
• “Task 4: Discover Switches” (page 29)
• “Task 5: Set the Onboard Administrator Password” (page 30)
• “Task 6: Discover Enclosures and Nodes” (page 30)
5.1 Task 1: Prepare for the System Configuration
Open the HP XC System Software Installation Guide to Chapter 3, and follow the instructions in
Task 1, where you gather the information required for the system preparation and discovery
phase.
Read the information in “Node Naming Differences” in this HowTo, which describes internal
node numbering conventions for server blades that are not described in the Chapter 3 in the HP
XC System Software Installation Guide.
5.1.1 Node Naming Differences
As described in Table 3-1 in the HP XC System Software Installation Guide, internal node naming
differs when the hardware configuration contains enclosures and HP server blades.
When the hardware configuration does not contain enclosures and HP server blades, internal
node names are assigned in a dense fashion in which there are no missing numbers in the node
numbering scheme except for a possible missing number between the branch nodes and those
nodes that are connected to the root administration switch.
In an enclosure-based system, the discover command uses a sparse node numbering scheme.
This means that internal node names are assigned based on the enclosure in which the node is
located and the bay the node is plugged into.
For example, if a node is plugged into bay 10 of enclosure 1, the node is numbered
{node_prefix}10. In a configuration with two enclosures in which there might be 16 nodes
in each enclosure, the node in bay 10 in enclosure 2 is numbered {node_prefix}27.
In this release, 16 is the maximum number of server blade nodes in a real enclosure. A real
enclosure is defined as an enclosure with one of more Onboard Administrators. The maximum
number of non-blade server nodes in a virtual enclosure is 38. A virtual enclosure is defined as
a ProCurve switch that has at least one console port from a non-blade server node plugged into
it.
5.1.2 Head Node Naming
When the hardware configuration does not contain (real) enclosures and HP server blades, the
cluster_prep command determines and assigns the head node name by using the number
that represents the maximum number of nodes allowed in the hardware configuration, which
you supply. For example, if the maximum number of nodes allowed in your hardware
configuration is 128, the head node is node {node_prefix}128.
When the hardware configuration contains server blades, the head node is named for its location
in the system just like every other node, as described in “Node Naming Differences”. The only
exception is when the head node is a non-blade server node whose console port is not connected
to the administration network ProCurve switch. In this case, the head node is named
{node_prefix}0.
5.1 Task 1: Prepare for the System Configuration 27
