Task 5: Run the discover Command to Discover System Components

The next step in the configuration process is the discovery of all system components. In addition to configuring the system topology by discovering all hardware components, the discover command also configures the administration network and interconnect and populates the configuration and management database (CMDB).




	Important Note About HP Server Blades and Enclosures: The discovery process differs if the hardware configuration contains HP server blades and enclosures. See the HP XC Systems With HP Server Blades and Enclosures HowTo for instructions about how to run the discovery process with the --enclosurebased option for HP server blades and enclosures: http://www.docs.hp.com/en/highperfcomp.html

Begin this procedure as the root user on the head node.
Capture command output into a file; this step is optional, but HP recommends it:
# script your_filename
Change to the configuration directory:
# cd /opt/hptc/config/sbin

Start the automatic discovery of all network components in the system:

# ./discover --system [--super] [--oldmp] [--outfile file_name]  \
   [--ic=AdminNet] [--verbose]




	Notes About the discover Command Line: The --super option is required for large-scale systems (systems with up to 1024 compute nodes) with a hardware configuration that consists of a Super Root Switch into which multiple Root Administration Switches are connected. The --oldmp option is required on HP Integrity servers (such as the rx8620) if their management processors (MPs) have statically set IP addresses and are not configured to use DHCP. The --oldmp option is no longer required if the HP Integrity server has been upgraded with MP firmware Version 3.15 or newer. Do not include the --oldmp option on the command line for HP ProLiant nodes because that hardware family uses iLO and LO-100i as their console port management devices and uses DHCP to obtain their IP addresses. Use the --outfile `file_name` option to save a copy of the HP XC system information that is written to the configuration and management database. You must supply an existing file name on the head node. Saving this information optional, but it enables you to use the --infile `file_name` option if it becomes necessary to restore the HP XC system to the point in the installation just after the discover command was run but before the cluster_config utility is run. Use the --ic=AdminNet option only if you are configuring the interconnect on the administration network. When the interconnect is configured on the administration network, a single LAN is used; the administration network and the interconnect share the same ports and switches. All other interconnect types (Myrinet, InfiniBand, and QsNet^II) are discovered automatically based on the interconnect found on the head node; specific command options are not necessary for those interconnect types. HP recommends that you include the --verbose option because it provides useful feedback and enables you to follow the discovery process. Table 3-2 and discover(8) contain information about additional keywords you can add to the command line to bypass some of the questions that will be asked during the discovery process. Use of these keywords is optional. If you encounter problems during the discovery process, see “Troubleshoot the Discovery Process” for troubleshooting guidelines. The discover command does not properly discover HP ProLiant DL140 and DL145 servers until the password is set. Running the discover command now determines the IP address of the console ports so you can use the telnet command to access the console ports and set the password. This process is described in “Modify the Default Password for HP ProLiant DL140 and DL145 Hardware Models”.

Follow along with the command output. The sample output shown here was created by using the --verbose option on a small HP XC system with six HP ProLiant servers (Opteron architecture). The output you see will be different. The information you supply depends on whether or not you entered additional keywords on the command line.




	NOTE: Table 3-2 describes each prompt and provides information to help you with your answers.

Enter the actual total number of nodes in this cluster: 6
Enter the number of nodes that are workstations: 0 

Discovering Root switches...
Enter the MAC address of the admin root switch
in the format xx:xx:xx:xx:xx:xx : your_MAC_address    1
Please enter the ProCurve switch Administrator password: your_password  2
Please re-enter password: your_password
Restarting dhcpd

Enter the common user name for all console port management 
devices: your_user_name   3
Please enter the password for your_user_name: your_password
Please re-enter password: your_password

Discovering 172.20.65.2 port 39 ... Console Port OK
Restarting dhcpd
discovered_cps is 4
Checking if all console ports are reachable ...
number of cps to check, 3
pinging 172.21.0.13  no response from 172.21.0.13

pinging 172.21.0.15  no response from 172.21.0.15

pinging 172.21.0.14  no response from 172.21.0.14

Following console ports did not respond:
 172.21.0.13 172.21.0.15 172.21.0.14

number of cps to check, 3
pinging 172.21.0.13
pinging 172.21.0.15
pinging 172.21.0.14  .done
Opening /etc/hosts
Opening /etc/hosts.new.XC
Opening /etc/powerd.conf
Building /etc/powerd.conf ... Querying cp-n13
Querying cp-n14
Querying cp-n15  4
done
Attempting to start hpls power daemon ... done
Waiting for power daemon ... done

switchName necs1-1 switchIP 172.20.65.2 type 2650
switchName nems1-1 switchIP 172.20.65.1 type 2848
Attempting to power on nodes with nodestring 8n[13-15]
Powering on all known nodes ... done

Discovering Nodes...
running port_discover on 172.20.65.1
nodes Found = 1 nodes Expected = 4

running port_discover on 172.20.65.1
nodes Found = 1 nodes Expected = 4

running port_discover on 172.20.65.1
nodes Found = 1 nodes Expected = 4

running port_discover on 172.20.65.1
nodes Found = 1 nodes Expected = 4

running port_discover on 172.20.65.1
nodes Found = 3 nodes Expected = 4

running port_discover on 172.20.65.1
nodes Found = 3 nodes Expected = 4

running port_discover on 172.20.65.1
nodes Found = 3 nodes Expected = 4

running port_discover on 172.20.65.1
nodes Found = 3 nodes Expected = 4

running port_discover on 172.20.65.1
nodes Found = 3 nodes Expected = 4

running port_discover on 172.20.65.1
nodes Found = 4 nodes Expected = 4

All nodes initialized.
Powering off all nodes but head node ... done
Switch 172.20.65.1 port 42 ... Node Found
Switch 172.20.65.1 port 41 ... Node Found
Switch 172.20.65.1 port 40 ... Node Found
Switch 172.20.65.1 port 39 ... Node Found
Switch 172.20.65.1 port 38 ... NO Node Found  5
Restarting dhcpd
node n14 set to model ProLiant DL145 G1
node n13 set to model ProLiant DL145 G2
node n15 set to model ProLiant DL145 G1
node n16 set to model ProLiant DL585 G1
Opening /etc/hosts
Opening /etc/hosts.new.XC
Head Node CP device type set to iLO
Waiting for power daemon to restart... done

1	Enter the MAC address of the switch that is connected to the administration ports. Do not enter the MAC address of the switch connected to the console ports.
2	Enter the password for the Root Administration Switch that you previously defined when you prepared the hardware. If you did not preset a password, press the Enter key.
3	Enter the common user name and password that you previously defined for the console port management devices (the iLO, LO-100i, or MP devices) when you prepared the hardware. If you did not predefine these items, press the Enter key.
4	If the discover process hangs while trying to discover console ports, see Appendix N.
5	This is expected behavior. Because this is a cluster discovery process, the command output `No Switch Found` or `No Node Found` is expected. This message does not indicate a failure unless a network component is plugged into that port on the switch. If necessary, see Appendix N for information about troubleshooting problems you might encounter during the discovery process.

The following prompts are displayed for large-scale systems:

The discover process has detected 2 regions. Is this correct? [y/n] y
switchName nems0-1-0 switchIP 172.20.65.1 type 2848 
Enter the actual total number of nodes in region 1: 526
Enter the number of nodes that are workstations: 0
Enter the actual total number of nodes in region 2: 504
Enter the number of nodes that are workstations: 0
discoverSystem called with switch nems1-1-1 and Region Number 1

If you captured the output of the discover command in a file (described in step 2), press Ctrl+d to end the script session now.
This file is for your information only. Store this file in a directory where you keep administrative data.
If the hardware configuration contains HP ProLiant DL140 and DL145 hardware models, perform the procedure described in “Modify the Default Password for HP ProLiant DL140 and DL145 Hardware Models”. Otherwise, proceed to “Task 6: Set Up the System Environment”.

Modify the Default Password for HP ProLiant DL140 and DL145 Hardware Models

Perform this task only if the hardware configuration contains HP ProLiant DL140 and DL145 hardware models to modify the default console management device password. Changing the default password is not required, but HP recommends changing the factory default value for security purposes. Bypass this step for all other server models.

Use the method of your choice to view the /etc/dhcpd.conf file and look for the characters cp- in host names to determine console port names.
Use the telnet command and the internal name of the console port to log in to each node's console management device and change the default password. Supply the factory default user name admin and the default password admin to log in:
# telnet cp-node_name login: admin password: admin

The interface you use to change the password differs depending upon the BMC firmware version. Thus, do one of the following:

For BMC Firmware Version 1.03:

Press Esc and Shift+9 to enter the command-line mode.

Use the C[hange Password] option to change the console port password. The factory default password is admin; change it to the password of your choice. This password must be the same on every node in your system.

Lights-Out> C 
Type the current password> admin 
Type the new password (max 16 characters)> your_password 
Retype the new password (max 16 characters)> your_password 
New password confirmed.
Lights-Out> exit

For BMC Firmware Version 1.24 or higher:
1. Change to the following directory:
  /directory_name/-> cd map1/accounts
2. List the pre-defined users (by default, 16 users have been pre-defined):
  /directory_name/-> show
3. One user at a time, use the show command until you find the first instance of the user name admin . Start with user1 and continue executing the show command for each user in sequential order:
  /directory_name/-> show user1 /directory_name/-> show user2 {...userN}
  For the purposes of this example, assume that user3 is the first instance of the user name admin .
4. Change directory to the user directory obtained in the previous step:
  /directory_name/-> cd user3
5. Set the password. Be very careful with your key strokes; there is no password verification step:
  /directory_name/-> set password=your_password
6. Exit from the interface:
  /directory_name/-> exit

Repeat this procedure to change the console management device password on every HP ProLiant DL140 and DL145 node in the system.
Rerun the discover command with the same options.

Task 5: Run the discover Command to Discover System Components

Technical documentation

» Table of Contents

» Glossary

» Index

Modify the Default Password for HP ProLiant DL140 and DL145 Hardware Models