beautypg.com

HP Insight Control Software for Linux User Manual

Page 247

background image

Corrective actions

Cause/Symptom

Retry after waiting a short period of time, that is a minute
or two.

If this is unsuccessful, reset the management processor
by one of the following methods:

Upgrade the firmware on the server and management
processor to the most recent version.

Power cycle the server.

Log into the iLO's web interface and reset it by
selecting Diagnostics under the System Status tab,
then selecting Reset.

Use ssh or telnet to log into the iLO and perform a
reset map1

to reset the iLO.

Problem manipulating EV

This is usually caused when a server is booting and a
power control command is sent to its management
processor. Most commonly the system is in a BIOS boot
and the management processor cannot determine the
power status.

Select Configure

Management

Processor

Credentials to modify the credentials for

this managed system.

Unable to power off server: Error retrieving BMC for
server. Root cause: Error status "User login name was
not found"

This is most commonly caused by incorrect credentials
for the management processor.

For the corrective action, see

Section 23.19 (page 247)

.

Server Control tool fails

The managed system fails to be powered down, powered
up, or rebooted because the target server lost association
with its management processor.

Test the communication with the server’s management
processor with the ping command. If the

MP

does not

respond, reset it. If the server is a c-Class BladeServer, log
into the

OA

to reset it. For non-blade servers, unplug the

MP.

Unable to communicate with management processor:
Error retrieving BMC for server. Root cause:PANIC:Error
instantiating BMCManager for BMC of server IP
address

.

This can occur during an installation of an OS.

23.19 Troubleshooting server-to-management processor associations

This section describes how to resolve issues with server-to-management processor associations.

23.19.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 HP 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 a number of 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.

23.19.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.

23.19 Troubleshooting server-to-management processor associations

247