HP XC System Software Release Notes for Version 3.2.1

5 System Discovery, Configuration, and Imaging
This chapter contains information about configuring the system. Notes that describe additional
configuration tasks are mandatory and have been organized chronologically. Perform these tasks
in the sequence presented in this chapter.
The HP XC system configuration procedure is documented in the HP XC System Software
Installation Guide.
IMPORTANT: Before you begin, depending upon the cluster platform type, see Chapter 10
(page 35), Chapter 11 (page 37), or Chapter 12 (page 39) to determine if additional
platform-specific notes apply to the system discovery, configuration, or imaging process.
5.1 Changes to Internal Node Numbering When Double Density Server
Blades are Present
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, Host name={node_prefix}1)
1B (node 2, blade 1) = 1 + (2 * 16) = 33 (Node number=2, Host name={node_prefix}2)
2A (node 1, blade 2) = 2 + (1 * 16) = 18 (Node number=3, Host name={node_prefix}3)
2B (node 2, blade 2) = 2 + (2 * 16) = 34 (Node number=4, Host name={node_prefix}4)
In addition, the sparse numbering scheme described in the HP XC System Software Installation
Guide does not mention that, for double density blades, the sparse numbering scheme 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.
5.2 Notes that Apply Before Running the cluster_prep Utility
Read the notes in this section before you invoke the cluster_prep utility.
5.2.1 Required Task for Some NIC Adapter Models: Verify Correct NIC Device Driver
Mapping
On head nodes installed with dual-fiber NIC server adapter models NC6170 or NC7170, Ethernet
ports might be reordered between the Kickstart kernel and the subsequent HP XC kernel reboot.
Use the procedure described in this section to correct the mapping if a re-ordering has occurred.
At the time of the Kickstart installation, the fiber ports are identified as eth0 and eth1, and the
onboard ports are identified as eth2 and eth3.
The /etc/modprobe.conf file is written as follows:
• alias eth0 e1000
• alias eth1 e1000
• alias eth2 tg3
• alias eth3 tg3
5.1 Changes to Internal Node Numbering When Double Density Server Blades are Present 23