HP XC System Software Installation Guide Version 4.0

• In an enclosure-based system with single density HP server blades, 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}26.
The c7000 enclosure has a maximum of 16 bays and the c3000 enclosure has a maximum of
8 bays.
The maximum number of single density server blade nodes in a c7000 real enclosure is 16,
and the maximum number of double density server blade nodes is 32. 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 48. 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.
The sparse numbering scheme for double density blades is not as straight forward as it is
for single density blades. For instance, if the hardware configuration has two enclosures
consisting all of double density blades, the nodes in the first enclosure are numbered from
{node_prefix}1 to {node_prefix}32. Node {node_prefix}33 in the second enclosure
is actually present in bay number 17 because bay numbers 1 to 16 are not present when only
double density blades are in an enclosure.
• Double density server blades like the HP ProLiant BL2x220c have two separate nodes for
each server blade, which means that a c7000 enclosure can have a maximum of 32 nodes
per enclosure compared to the maximum of 16 single density server blades. A c3000 enclosure
can have a maximum of 16 nodes per enclosure compared to the maximum of 8 single density
server blades.
Internal node numbers are calculated based on enclosure bay location as follows:
slot number + (blade number in the slot * maximum number of bays) = bay number
For example, when a c7000 enclosure is populated with double density server blades, node
numbers are calculated as follows:
1A (node 1, blade 1) = 1 + (1 * 16) = 17 (Node number = 1, Hostname = {prefix}1)
1B (node 2, blade 1) = 1 + (2 * 16) = 33 (Node number = 2, Hostname = {prefix}2)
2A (node 1, blade 2) = 2 + (1 * 16) = 18 (Node number = 3, Hostname = {prefix}3)
2B (node 2, blade 2) = 2 + (2 * 16) = 34 (Node number = 4, Hostname = {prefix}4)
When the hardware configuration contains double density blade servers such as the ProLiant
BL2x220c, you must include the --extended {contiguous|non-contiguous} option
on the discover command line when you are discovering nodes so that internal node
numbers are assigned correctly:
— Using the --extended contiguous option results in naming the nodes serially, for
example: 1A, 1B, 2A, 2B, 3A, 3B...16A, 16B are n1, n2, n3, n4, n5, n6...n31, n32 respectively
— Using the --extended non-contiguous option results in naming the nodes in the
order they are connected to the Interconnect switches on the enclosure backplane, for
example: 1A, 1B, 2A, 2B, 3A, 3A...16A, 16B are numbered as n1, n17, n2, n18, n3, n19...
n16, n32 respectively.
When the hardware configuration contains only single density blades, using the --extended
option results in odd numbered node names (such as 3, 5, 7, and so on); no nodes names
will have an even number (such as 2, 4, 6, and so on). In that situation, node are numbered
{node_prefix}1, {node_prefix}3, {node_prefix}5...{node_prefix}33.
52 Preparing to Configure the System