Internal node naming is affected 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 slot the node is plugged into.
For example, if a node is plugged into slot 10
of enclosure 1, the node is numbered n10. In a
configuration with two enclosures in which there might be 16 nodes
in each enclosure, the node in slot 10 in enclosure 2 is numbered n27.
Head Node Naming
The cluster_prep command prompts you to supply the maximum number of nodes in the
hardware configuration. When the hardware configuration does not contain
(real) enclosures and HP server blades, the cluster_prep command forms the head node name using the number you specify. For
example, if the maximum number of nodes allowed in your hardware configuration
is 128, the head node is node n128.
When the hardware configuration contains enclosures
and HP server blades, you are not prompted to enter the maximum number
of nodes. This means that when the head node is an HP server blade,
the head node naming scheme is based on the node naming scheme described
at the beginning of this section.
If a non-server blade is the head node and the
console port of the head node is not connected to the Administration
Network, the head node is numbered n0.
Printable version
