Managing ProLiant servers with Linux HOWTO

Table 14. Known issues for hp-health

Issue

number

Details

Issue 1 Non-certified machines

Symptom When the hpasm RPM file is installed, the following message displays:

hpasm: This driver is not supported on this

system

The driver is not inserted into the list of modules.

Cause The Health Monitor cannot be initialized due to a conflict in ROM internal tables, or the

server is not supported. This driver is only supported on servers that have the ProLiant

Advanced Server Management (ASM) ASIC (PCI identifier 0x0e11a0f0 or the

Integrated Lights-Out Management ASIC (PCI identifier 0x0e11b203)). No other

ProLiant servers are supported.

Verify that the appropriate ASM ASIC is present. Use the following commands to

perform the check:

cat /proc/bus/pci/devices | grep –I 0e11a0f0

cat /proc/bus/pci/devices | grep –I 0e11b203

One of these commands should succeed and return information. Also, check to see if a

later ROM version is available for this server.

Issue 2 The hp-snmp-agents custom build does not work

Symptom The hpasm_rebuild script logs messages to the console and exits.

Cause You must execute the custom build script as user name “root.” The RPM must be

available to you and you should start the script with the version of the package that you

installed (for example 6.30.0).

Workaround Install RPM and make sure it is available from your PATH variable.

Issue 3 No console messages

Symptom No console messages appear on the text screens (for instance, Ctrl+Alt+F1), but the

error messages get logged properly in /var/log/messages.

If you run KDE or Gnome, xterms does not show the console messages originating from

the Health Monitor.

Cause The syslogd daemon is configured somewhat differently than other distributions; the

system messages do not appear on the lower digit terminals (tty1-9).

Workaround If you do not want the message to be logged on the system, configure it differently by

modifying /etc/syslog.conf in the following way:

# Log all kernel messages to the console.

# Logging much else clutters up the screen.

kern.* /dev/console

# Log anything (except mail) of level info or

higher.

# Don’t log private authentication messages!

*.info;mail.none;news.none;authpriv.none

/var/log/messages

After sending a HUP signal to syslogd process ID, you should see your kernel messages

appearing on all consoles.

“kill –1 <pid of syslogd>”

Issue 4 Superuser only