HP XC System Software Release Notes for Version 4.0

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 9
(page 33), Chapter 10 (page 35), or Chapter 11 (page 37) to determine if additional
platform-specific notes apply to the system discovery, configuration, or imaging process.
5.1 Notes that Apply before Running the cluster_prep Utility
Read the notes in this section before you invoke the cluster_prep utility.
5.1.1 Caevat on Customizing the base_addrV2.ini File
Many users prefer to use their own IP addresses for the administration, interconnect and console
networks instead of the 172.x.x.x range of IP addresses that HP XC uses by default. You can
customize the address ranges by modifying the /opt/hptc/config/base_addrV2.ini file.
The /opt/hptc/config/base_addrV2.ini file also provides a range of dynamic IP addresses
(through the dyStart and dyEnd attributes) that are used for various XC functions.
One of them provisions IP addresses for the dbserver, imageserver, and lsf aliases. For HP
XC to provision these IP address in a proper fashion, ensure that the dyStart and the dyEnd
range of IP address is different from the base IP addresses (nodeBase, cpBase, swBase, icBase).
5.1.2 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 reordering 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
You must correct this mapping if you find that upon the HP XC kernel reboot, eth0 and eth1 are
the tg3 devices, and eth2 and eth3 are the e1000 devices.
To get the external network connection working, perform this procedure from a locally-connected
terminal before invoking the cluster_prep utility:
1. Unload the tg3 and e1000 drivers:
# rmmod e1000
# rmmod tg3
2. Use the text editor of your choice to edit the /etc/modprobe.conf file to correct the
mapping of drivers to devices. The section of this file should look like this when you are
finished:
5.1 Notes that Apply before Running the cluster_prep Utility 19