[ Next Article | Previous Article | Book Contents | Library Home | Legal | Search ]
System Management Guide: Communications and Networks

Problem Determination for the SNMP Daemon

If the snmpd agent is not behaving as you expected, following are some hints to help you determine and correct the problem. If you are having problems, it is strongly recommended that you start up the snmpd agent with some type of logging. If you are having trouble with the invocation of the snmpd daemon, it is strongly recommended that you set up the syslogd daemon for logging at the daemon facility and DEBUG severity level. See "SNMP Daemon Logging Facility" , the snmpd command, and the snmpd.conf file for more information on snmpd logging.

Daemon Termination Problem

If the snmpd daemon terminates as soon as it is invoked, the following are possible reasons for failure and probable solutions:

Daemon Failure Problem

If the snmpd daemon fails when you issue a refresh or a kill -1 signal, the following are possible reasons for failure and probable solutions:

MIB Variable Access Problem

If Management Information Base (MIB) variables cannot be accessed from the snmpd agent; if the snmpd agent is running, but the Simple Network Management Protocol (SNMP) manager application times out waiting for a response from the snmpd agent, try the following:

MIB Variable Access in Community Entry Problem

If a community entry is specified in the configuration file with a MIB view name, but MIB variables cannot be accessed, check the following:

No Response from Agent Problem

If the IP address in the community is specified as 0.0.0.0, but there is no response from the snmpd agent, try the following:

noSuchName Problem

If in attempting to set an MIB variable that the snmpd agent is supposed to support, noSuchName error message is returned, the following may be the reason:

The set request you issued did not include a community name for a valid community with write access. The SNMP protocol dictates that a set request with a community with inappropriate access privileges be answered with the noSuchName error message.

Solution: Issue the set request with a community name for a community that has write privileges and includes the host from which the set request is issued.


[ Next Article | Previous Article | Book Contents | Library Home | Legal | Search ]