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

Corrective actions Cause/Symptom
Rerun Options
→Identify systems... to fully discover the
iLO.
Intermittent power on, power off, and reset server errors
Intermittent power on, power off, or reset server errors
might occur during an Insight Control for Linux operation
(for example, during an OS installation, image capture,
or image deployment).
Checking to see if power is on.
Failed: Error retrieving BMC for server.
Root cause:PANIC: BMC Manager
not configured for device of this type.
IP address of server causing this problem
is venus.example.com.
Attempting to power down via management
processor Unable to
communicate with the management processor:
Unable to power off system.
Root cause:PANIC: BMC Manager not
configured for device of this type.
IP address of server causing this problem
is venus.example.com.
This situation typically presents itself when the iLO is not
completely discovered. When this occurs, the HP SIM
presentation of the iLO has a missing IP address or the
subtype of the iLO is not shown.
Perform the following operations: Power On Server operation fails during OS installation with
the message “???Checking to see if the power is on???”
This is often caused by a hung iLO.
1. Locate the hung iLO and reset it.
2. Rerun the failed operation.
25.20 Troubleshooting server-to-management processor associations
This section describes how to resolve issues with server-to-management processor associations.
25.20.1 Maintaining server-to-management processor associations
A properly discovered managed system in HP SIM consists of entries for the managed system and
its integrated management processor. HP SIM uses the agents installed on a managed system to
maintain the association between a managed system and its management processor.
Under some circumstances, this association is lost, which results in reduced functionality and
manageability with Insight Control for Linux. Any operation that requires certain types of data
collection or power control (such as rebooting) requires that association to exist.
HP SIM periodically performs data collection tasks where it connects to the managed system and
its management processor to gather configuration and usage information. If the managed system
is accessible to HP SIM through SNMP, but it does not have the agents loaded, HP SIM immediately
breaks the association.
25.20.2 Identifying a lost server-to-management processor association
To identify a managed system with a broken association with its management processor, open HP
SIM and select All Systems in the left pane.
Look under the MP column for the management processor status. A properly associated managed
system has a green check mark in this column. A broken association does not have an entry in this
column.
25.20.3 Rebuilding a server-to-management processor association
It might be necessary to rebuild an association between a previously discovered managed system
and its management processor. There are several ways to do this depending on what the problem
is and what state the managed system is in.
25.20 Troubleshooting server-to-management processor associations 237