 |
» |
|
|
|
The first step in the configuration process is to prepare
the system by running the cluster_prep command.
This process sets up the node naming prefix, the number of nodes in
the system, the configuration and management database administrator's
password, the external Ethernet connection on the head node, starts
the MySQL service, and initializes the configuration and management
database. Begin this procedure as the
root user on the head node. Change to the following directory: # cd /opt/hptc/config/sbin |
Start
the system preparation process by invoking the cluster_prep command. An additional command line option is required if the hardware
configuration contains HP server blades and enclosures. Command output is similar to the following. Table 3-1 describes
each prompt and provides information to help you with your answers. |
The cluster_prep utility prepares the head node for the
automated discovery process. This utility is run during the initial
cluster configuration or any time your cluster is reconfigured.
If you reconfigure your cluster, you must run the discover
command after running the cluster_prep utility.
Do you want to continue? (yes/no) [n] y
Enter the prefix to assign to internal node names. The prefix
can contain up to 6 alphanumeric characters, and the last
character must be alphabetic. The default node prefix
is the letter "n":
Enter node naming prefix [n]: your_prefix 1
Enter the maximum number of nodes in this cluster [ ]: 16 2
Setting system name to n16 ... done 3
Please enter the Database Admin Password : your_password
Please re-enter password: your_password
Do you want to configure the external connection on the
head node? [y] Enter
External Ethernet device on the head node [eth1] Enter
IP address []: your_IPaddress
Netmask []: your_netmask
You have the option to provide an IPv6 address for the external
Ethernet connection.
You can enter an IPv6 address, press the [ ] keys to delete the
value shown, or press the Enter key to accept the value shown.
IPv6 address (optional) []: Enter
Gateway IP address []: your_IPaddress
You have the option to override the system default MTU value.
You can enter 9000 to enable jumbo frames,
press the [ ] keys to delete the value shown and use the system default,
or press the Enter key to accept the value shown.
MTU value (optional) []: Enter
IP address for DNS name server [ ]: your_IPaddress
Provide one or more DNS domains to use for search paths or press the
Enter key to accept the default response.
Enter one domain name on a line, and after the last domain name, enter
a period (.) on a line by itself and press the Enter key.
Search path: [ ]southpole.com
. 4
[P]roceed, [R]etry: p 5
Restarting network ... done |
|
| 1 | Node prefix conventions
are described in Table 3-1. The internal node naming scheme is described
in “Internal Node Naming”. The default node prefix is the letter n. | | 2 | In this example, the maximum number of nodes supported
by the interconnect switch is 16. Enter the maximum number of nodes
allowed by your interconnect switch. If the system is configured with
HP server blades, you are not prompted for the maximum number of nodes. | | 3 | The internal host name of the head node is based
on the node naming prefix and the maximum number of nodes in the system.
Therefore, as shown in this example, the head node host name is set
to n16. However, if the head node is an HP server blade, the head node
is named based on the node naming prefix and its physical location
in the hardware configuration. For example, if the head node is located
in enclosure 1, bay 1, the head node is node 1. | | 4 | Be sure to include a period (.) after the last
domain name. | | 5 | Enter the letter r to change
a response. Otherwise, enter the letter p to
continue. |
Press Ctrl-Alt-Backspace to restart
the X server to accommodate the head node host name change. Log back in to the system
as the root user. Click on the Linux
for High Performance Computing splash screen to close it. Complete this step only if you are
using the virtual console and media on an HP server blade head node. You must reset the temporary
cabling and settings you made to the Onboard Administrator. Do one
of the following, depending upon how you accessed the Onboard Administrator: If you accessed the Onboard Administrator through
a connection to a public network, return all cabling to its original
configuration and press the reset button on the Onboard Administrator. If you assigned a temporary static IP address to access
the Onboard Administrator, do the following: Clear all enclosure bay IP addressing settings. Use the Insight Display panel on the enclosure to
set the Onboard Administrator for DHCP. Return all cabling to its original configuration. Press the reset button on the Onboard Administrator.
Click Applications System ToolsTerminal to open a terminal window.
|
Printable version
