Managing ProLiant servers with Linux HOWTO

Issue

number

Details

Symptom You experience the following problems:

• Commands like insmod, modprobe, rmmod, or rpm are not available.

• The RPM install fails because file permissions are being denied (see below).

"Failed to open //var/lib/rpm/packages.rpm

error: cannot open //var/lib/rpm/packages.rpm"

Cause Preparing a driver install necessitates access to system administrator rights.

Workaround Be sure to log in as "root" before you attempt the driver install.

Issue 5 The agents do not seem to expose their data through SNMP; my management console does not see any

status.

Symptom Through SNMP browsers or other management software, the servers appear dead. No

SNMP traffic is available through them.

Cause This can be caused by many things. Here is a checklist of the most common problems:

• SNMP is not running.

• The agents and/or drivers have not started properly (see Issue 7).

• The snmpd.conf file is misconfigured.

– rwcommunity is undefined for either localhost or the management console.

– -community string mismatches the one from the management console.

– trapsink or trapcommunity is undefined. Trapcommunity may be undefined for

localhost.

• Firewalling software is enabled on the system and set up to block SNMP traffic.

• The cmaX extension is absent from the snmp stack.

Table 15 describes common problems that might occur during installation and operation of the Host

OS Agent, the Standard Equipment Agent, the SCSI Agent, the System Health Agent, the Threshold

Agent, and the Peer Agents. In most cases, a workaround is available.

Table 15. Known issues for agents

Issue

number

Details

Issue 1 Cannot manage server from Systems Insight Manager, grayed-out utilization button, or missing file system

space used information in the mass storage window

Workaround To work around this issue, complete the following steps:

1. Check if the network is working by pinging the server from the system running

Systems Insight Manager.

2. Be sure that Systems Insight Manager is using the correct community string, which is

defined in the server’s snmpd.conf file.

3. Be sure that post-installation configurations have been performed properly, if needed.

4. Check the Host OS Agent status with the Linux command ps –ef | grep cmahostd.

If the agent is not running, start the Host OS Agent manually using the following

command:

#/opt/hp/hp-snmp-agents/server/etc/cmahostd start

If the Host OS Agent is running but not reporting data, or if it was correctly started but

is no longer running, check the file /var/spool/compaq/cma.log for error messages.

You must be logged in as “root” to access this file.

Issue 2 Grayed-out system board, expansion boards, or configuration buttons