SNMP Configuration and Management Manual

Troubleshooting the SNMP Agent
SNMP Configuration and Management Manual—424777-006
7-6
Diagnosing Request Errors
which the agent process was started. To override the default trace files, you must
provide DEFINE statements specifying the locations of the primary and backup trace
files. For example:
ADD DEFINE =PRIMARY-TRACE-FILE, CLASS MAP, FILE $NETMAN.SNMP.SNMPTRCP
ADD DEFINE =BACKUP-TRACE-FILE, CLASS MAP, FILE $NETMAN.SNMP.SNMPTRCB
Using DEFINE statements is described in the TACL Reference Manual.
Diagnosing Request Errors
Table 7-1 describes what the SNMP agent does when it or one of the subagents with
which it is communicating receives Get, GetNext, or Set requests that do not result in a
normal response. The SNMP agent usually increments one of the counters in its
SNMP group. In most cases, the SNMP agent also assigns a value to the Error-Status
field of a GetResponse PDU or generates a trap.
Table 7-1. Handling Requests That Cannot Be Processed (page 1 of 3)
Error Condition
SNMP Group Counter
Incremented
Error-Status
Value
Assigned Message Handling
The results of an
operation cannot
fit into a single
SNMP message.
snmpOutTooBigs tooBig SNMP agent stops
processing the
request and returns
an error.
The SNMP
version number in
the request does
not match the
version supported.
snmpInBadVersions SNMP agent
discards the
request.
The incoming
request could not
be authenticated.
snmpInBadCommunityNames SNMP agent
discards the
request and
generates an
authenticationFailur
e trap.
The SNMP agent
could not decode
the request PDU.
snmpInASNParseErrs SNMP agent
discards the
request.