HP Insight Management Agents 9.10 Managing ProLiant Servers with Linux HOW TO Whitepaper
Table 17 Known issues with agents (continued)
DetailsIssue Number
Next, generate a trap to localhost using the Linux “snmptrap” utility. The Linux
command “snmptrapd –f –Le” should display the trap. Note that the recent
versions of snmptrapd will not accept incoming notifications by default. See
snmptrapd.conf(5) manpage for information on configuring access control
settings to enable incoming notifications.
Unable to set thresholds on MIB items or no user-defined SNMP traps are receivedIssue 11
Check the Threshold Agent status with the Linux command “ps –ef | grep
cmathreshd”. If the agent is not running, start the Threshold Agent using the following
command:
# /opt/hp/hp-snmp-agents/server/etc/cmasthreshd start
Workaround
If the agent is running but not reporting data, or if the agent 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. Verify that the server
SNMP community string defined in your snmpd.conf (using rwcommunity keyword)
matches the community string defined at the management console. If you are using
Systems Insight Manager, the community string can be set in the Device Setup window.
For more information see the section on community strings in the Systems Insight Manager
User Guide Help file.
If the “threshold sets” still do not work, perform the following procedure:
1. Stop the Threshold agent and delete previous alarm threshold files using the following
command:
# /opt/hp/hp-snmp-agents/server/etc/cmasthreshd stop
2. Start the Threshold agent using the following command:
# /opt/hp/hp-snmp-agents/server/etc/cmasthreshd start
Disabling SNMP sets for a specific agentIssue 12
Stop the agent associated with the desired MIB. Change the agent command line
argument set switch to “-s NOT_OK” in the corresponding /opt/hp/
Workaround
hp-snmp-agents/<agent>/etc/<subagent> file. This disables the SNMP sets
for this agent only. Restart the agent for the changes to take effect.
Disabling SNMP traps for a specific agentIssue 13
Stop the agent. Change the agent command line argument trap switch to “-t NOT_OK”
in the /opt/hp/hp-snmp-agents/<agent>/etc/<subagent> file. This disables
SNMP traps for this agent only. Restart the stopped agent for the changes to take effect.
Workaround
Disabling remote rebootIssue 14
Stop the server Standard Equipment Agent with the following command:
# /opt/hp/hp-snmp-agents/server/etc/cmastdeqd stop
Workaround
Edit /opt/hp/hp-snmp-agents/server/etc/cmastdeqd and change the
cmastdeqd agent command line reboot switch to “-r NOT_OK”. This disables SNMP
reboots for this device only. Restart the Standard Equipment Agent for the new changes
to take effect.
Peer Agents will not runIssue 15
Check the /var/log/hp-snmp-agents/cma.log file for messages. If it is caused
by not running snmpd, then configure snmpd to start automatically during boot. If you
Workaround
changed the snmpd.conf files, you must restart snmpd and agents with the following
commands:
# /etc/init.d/snmpd restart
# /etc/init.d/hp-snmp-agents restart
35