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




	NOTE: On HP-UX version 10.20, if `trapdestagt` was running, it might need to be restarted manually with the command /usr/sbin/trapdestagt. NNM or OV depends on `trapdestagt` to set up SNMP trap notification on managed systems.

If changes are needed to dictionary files, stop any MIB monitors that are already running.
If changes are needed to snmpd.conf, stop and restart HP SNMP, following the procedure above.
NOTE: The -c option is not required if public is one of the get-community or set-community names.

MIB Monitor Troubleshooting

Technical documentation

» Table of Contents

» Glossary

» Index