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

9. If the server does have an OS installed, immediately install the ProLiant Support Pack (see the
HP Insight Control for Linux Support Matrix for the current supported version), either manually
through the remote console or by selecting the following:
Deploy
→Deploy Drivers, Firmware, and Agents→Install ProLiant Support Pack (PSP)...
When this procedure is complete, the server is present in HP SIM and the association with the
management processor is restored.
25.20.3.4 Establishing the association with a server after a bare metal discovery.
It is possible that after, an Initiate Bare-metal discovery task completed with HP SIM acknowledging
the server, but that the server is not associated with its MP.
Perform the following actions to identify and correct the failure:
•
Examine the task results with the HP SIM Tasks & Logs
→View Task Results task to determine
why the task failed.
•
Start the remote console of the server you are trying to discover. For information on the remote
console,
“Connecting to a remote console” (page 186) .
The sequence of events should be:
1.
(For PXE boot only) A DHCP request. You should see the target server issuing a DHCP
request and receiving a response.
If the target server does not receive a response, make sure that the log file on the DHCP
server contains a DHCPDISCOVER entry with the target server’s MAC address.
If not, check your DHCP server and network configuration.
2. Insight Control for Linux boot menu.
If the boot menu does not appear, check your network configuration.
3. A ten second delay.
4. Loading of the Insight Control for Linux RAM disk.
If the server tries to boot a local disk instead of the Insight Control for Linux RAM disk, examine
the /opt/repository/boot/pxelinux.cfg file for stale MAC address files.
Delete the stale MAC address files for the server you are trying to discover.
•
Rerun the Options
→IC-Linux→Initiate Bare Metal Discovery task.
The server should run through its boot routine, bring up a network with DHCP, acquire several
packages from the CMS, and start the HP Health and HP SNMP management agents. If
successful, a message will appear asking you to press the Enter key to bring up a console
shell.
25.20.4 Establishing association between iLO and server
During an Insight Control for Linux bare metal discovery operation, the association between the
iLO and its server might not occur. If this happens, the bare metal discovery post processing task
failure during the power down server operation displays the following error message on the Tasks
& Logs
→View Task Results... page:
Checking to see if power is on.
Failed: Error retrieving BMC for server. Root cause: Could not determine the
BMC associated with the server (0000001b78be9f480000000300000016) in the database.
Probably not discovered yet.
Attempting to power down via management processor
Unable to communicate with the management processor: Unable to power off system.
Root cause:Could not
determine the BMC associated with the server (0000001b78be9f480000000300000016) in the
database.
Probably not discovered yet.
To restore the association, follow this procedure:
25.20 Troubleshooting server-to-management processor associations 239