HP Insight Management Agents 9.10 Managing ProLiant Servers with Linux HOW TO Whitepaper

Table 17 Known issues with agents
DetailsIssue Number
Cannot manage server from Systems Insight Manager, grayed-out utilization button, or missing file
system space used information in the mass storage window
Issue 1
To work around this issue, complete the following steps:Workaround
1. Check if the network is reachable 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/log/hp-snmp-agents/cma.log for error
messages. You must be logged in as “root” to access this file.
Grayed-out system board, expansion boards or configuration buttonsIssue 2
Check the Standard Equipment Agent status with the Linux command “ps –ef | grep
cmastdeqd”.
If the agent is not running, start the Standard Equipment Agent manually using the
following command:
Workaround
# /opt/hp/hp-snmp-agents/server/etc/cmastdeqd start
If the agent is running but not reporting data, or if it was correctly started but is no
longer running, check the file /var/log/hp-snmp-agents/cma.log for error
messages. You must be logged in as “root” to access this file.
Missing SCSI drive information in the mass storage windowIssue 3
Check the SCSI Agent status with the command “ps –ef | grep cmascsid”.Workaround
If the agents are not running, they must be started. (See the start/stop documentation
for appropriate agent).
If the agent is running but not reporting data, or if it was correctly started but is no
longer running, check the file /var/log/hp-snmp-agents/cma.log for error
messages. You must be logged in as “root” to access this file.
Added SCSI devices do not appearIssue 4
To minimize system overhead, the cmascsid process does not search for new hardware
every poll_time. There is a delay of up to 32 times the poll interval, which is normally
Workaround
every 30 seconds, up to 16 minutes in the default case before new SCSI devices are
discovered by cmascsid and reported to the ProLiant Management Console. Once
the hardware has been discovered, its status is checked each poll_time and reported
to ProLiant Management Console when it has changed.
Missing or 0-value SCSI hard drive serial number or capacityIssue 5
Most SCSI hard drives do not make this information available to the host when the drive
media is not spinning. Hot-pluggable drives do not start spinning until the Operating
Workaround
System attempts to open them. Obtaining this information requires access to the drive.
After the drive is first opened, to minimize system overhead, there can be a delay of
up to 32 times the poll_time of the cmascsid process before updated information is
available to the ProLiant Management Console.
Grayed-out button for a SCSI controllerIssue 6
33