HP Insight Control Software for Linux - Manual (Page 213)

Corrective actions Cause/Symptom
more than 80% of the time; budget approximately 20%
additional IP addresses.
Verify that your DHCP service configuration is properly
configured to provide a Boot Server Hostname or Managed Servers will not PXE Boot
When a console is connected to a managed system, either
directly or through the managed system's iLO remote
next-server value, instructing the PXE boot process to
load a network boot loader. The value of this field should
console, the boot process reaches the PXE boot stage, but
proceeds directly to the local boot.
be the management IP address of the CMS. For DHCP
configuration examples, see the HP Insight Control for Linux
Installation Guide.
Verify that your DHCP service configuration is properly
configured to provide an Option 140 value, and that Insight Control for Linux RAM disk boots, but reports rsync
errors
The managed server PXE boots into the Insight Control for
Linux RAM disk, either for discovery or to capture or deploy
value is set to be the management IP address of the CMS.
For DHCP configuration examples, see the HP Insight
Control for Linux Installation Guide.
a Linux image, but it does not complete its operation. The
last messages report that the rsync command was unable
to download files.
25.8 Troubleshooting discovery problems
The following table describes possible causes of problems that may occur during the device
discovery process and provides actions to correct them.
Corrective actions Cause/Symptom
Perform the following actions to identify and correct the
cause of the bare-metal discovery failure: Initiate Bare-metal discovery fails; HP SIM does not
acknowledge the server.
•
Ensure that the user name and password of the MP are
set to the Insight Control for Linux global user name and
password.
•
Ensure that the MP is functioning correctly and is
communicative; it might need to be reset.
• Determine if a network issue is preventing
communication with the MP.
See “Establishing the association with a server after a bare
metal discovery.” (page 240)
Initiate Bare-metal discovery completes; HP SIM
acknowledges the server but it is not associated with its
MP.
See the entry for After an Initiate Bare-metal discovery
completes; HP SIM acknowledges the server but it cannot Initiate Bare-metal discovery completes; HP SIM
acknowledges the server but it cannot be used for
installation, capture, or deployment operations.
be used for installation, capture, or deployment operations
in
“Deploying Linux images” (page 232) .
Perform these actions: Bare metal discovery returns "There are no MAC addresses
registered for this system."
• Run the Tasks & Logs →View Task Results... menu option.
Examine the output of the HP SIM Initial Data
Collection
task for the server or servers with the
missing MAC addresses. This task collects the MAC
addresses from the Insight Control for Linux agents
running in RAM disk on the target server.
If the Initial Data Collection post-processing
task failed, review the failure and the HP SIM logs in
/var/opt/mx/logs
for the cause.
•
Manually run the HP SIM Data Collection task on
the server or servers that failed, if the servers remained
in the Insight Control for Linux RAM disk environment.
If the task works, the failure is likely caused by network
or database contention.
25.8 Troubleshooting discovery problems 213