HP Insight Management Agents 8.70 Managing ProLiant Servers with Linux HOW TO

Table 17 Known issues with agents (continued)
DetailsIssue Number
Information about the configuration of the device indicates that a SCSI controller is
installed, but no further information is available. Several conditions result in a grayed-out
button:
The SCSI agent process cmascsid might not be running
The SCSI controller might have been disabled by the System Configuration Utility
This might be an unsupported controller
Workaround
Missing or grayed-out storage controllers in the mass storage windowIssue 7
Check the Mass Storage Agent status with the Linux command ps ef | grep
cma. See the entries for cmaidad, cmafcad, cmascsid, cmasasd and cmaided.
If the agent is not running, it must be started. (See the start/stop documentation for
the 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.
Workaround
Grayed-out Recovery button in the Device View window, grayed-out Auto Recovery button in the
Recovery window or grayed-out Environment button in the Recovery window
Issue 8
To work around this issue, complete the following steps:
1. Be sure your system supports the System Health Agent features. These features are
supported only on HP ProLiant servers
2. Check the System Health Agent status with the Linux command ps ef | grep
cmahealthd. If the agent is not running, it must be started. (See the start/stop
documentation for the appropriate agent).
Workaround
Grayed-out Remote Insight button in the Recovery windowIssue 9
A grayed-out Remote Insight button can be caused by one of the following:
The Remote Insight Controller might not be configured properly
The Remote Insight driver might not be installed
The Remote Insight Agent cmasm2d might not be running
Workaround
Unable to change any values on the managed server or no SNMP traps/alarms are receivedIssue 10
34 Troubleshooting