This section includes information for troubleshooting SNMP on all platforms.
Traps are sent only if the corresponding verb request is received by the server. They are not sent in any other cases. For example, ndsDeleteAttribute is sent only when the ndsRemoveEntry (trap number 108) request is sent. But an application can always read the ACLs and decide to check whether the user has sufficient rights to perform the delete operation. In this case, the ndsDeleteAttribute trap will not be generated. However, you can use iMonitor to view the verb statistics on a particular server.
To get the traps for all occurrences, set the time interval to zero.
You can enable traps to send only on failure conditions. You can enable traps to get them under all conditions.
Or
Or
An incorrect version of ucd-snmp might be present on the system, or the links to required libraries might be missing.
To resolve this, install ucd-snmp-4.2.1, ucd-snmp-4.2.2, or ucd-snmp-4.2.3 and create links to the missing ucd-snmp version libraries.
Complete one of the following workarounds to install and create links to the missing ucd-snmp version libraries:
NOTE: We recommend you to use the first workaround as uninstalling ucd-snmp may require to uninstall all the dependent rpms.
For example, if you want to install ucd-snmp-4.2.3 in /home/edir/snmp, go to cd /home/edir/snmp and run the following commands:
rpm2cpio ucd-snmp-4.2.3-109.i386.rpm | cpio -ivd
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/edir/snmp/usr/lib
To find which libraries are missing, enter the following:
ldd /usr/bin/ndssnmpsa
To create links to the missing libraries, refer the following example:
If your system had ucd version 4.2 earlier, create the following links to ucd version 4.2.1:
ln -s /usr/lib/libucdagent-0-4.2.so /usr/lib/libucdagent-0.4.2.1.so
ln -s /usr/lib/libsnmp.so-0-4.2.so /usr/lib/libsnmp-0.4.2.1.so
ln -s /usr/lib/libucdmibs-0-4.2.so /usr/lib/libucdmibs-0.4.2.1.so
NOTE: If ucd snmp is installed in custom location, you should create the link by using the custom location as a prefix.
If you get an error (for example, a timeout error) while contacting the SNMP master agent from the MIB browser, do the following:
You can check this using the ps command as follows:
ps -ef | grep snmpdm
See the net-snmp-5.0.8 master agent related error and warning messages in the /usr/adm/snmpd.log file.
NOTE: If the net-snmp master agent is down and is restarted, then ndssnmpsa should also be restarted.
See the NAA agent related error and warning messages in the /var/adm/snmpd.log file.
Ensure that you have started the NAA agent with log messages enabled. Start the naaagt as follows:
/usr/sbin/naaagt -m APALL
NOTE: By default, naaagt terminates automatically when snmpdm terminates (unless naaagt is started with the -K option). See the naaagt man page for more details.
Ensure that net-snmp-5.0.8 is configured, up, and running.
For any problem configuring the eDirectory SNMP subagent (ndssnmpsa), see the /var/nds/ndssnmpsa.log file. To get the debug messages, start ndssnmpsa in verbose mode as follows:
/usr/bin/ndssnmpsa -v 3 -l 3
Where v is verbose mode and l indicates the log mode.
Ensure that the trap destination is entered in net-snmp configuration.
For more details on how to configure see section Starting/Configuring the NET-SNMP Master Agent.