Using the Event Monitoring Service (June 2003)

Troubleshooting
MIB Monitor Troubleshooting
Appendix B94
MIB Monitor Troubleshooting
The MIB monitors that ship with EMS rely on various SNMP MIBs and
need to have HP-UX SNMP subagents configured correctly and be
running, before they can reliably report on the status of their resources.
Other monitors that may be added might also need special SNMP
configurations.Review the following troubleshooting hints to help ensure
that your environment is set up correctly:
• Refer to the standard /var/adm/syslog/syslog.log file. It is
always useful when troubleshooting system and ServiceGuard
concerns.
• Certain log files may grow without bound. This may fill up file
systems and cause unpredictable behavior in SNMP. Check (and
possibly remove) the following files:
/var/adm/snmpd.log
$ORACLE_HOME/network/log/listener.log
$ORACLE_HOME/rdbms/audit/*.aud
$ORACLE_HOME/rdbms/log/*.trc
• If MIB resource classes under system , rdbms , cluster , and net are
unavailable, there might be a problem with the HP SNMP daemons
(snmpdm, mib2agt, and hp_unixagt). Try using the following
commands to stop and restart HP SNMP:
/sbin/init.d/SnmpMaster stop
/usr/sbin/snmpd