Trace examples and explanations

The following examples are shown in this topic:
  • Agent trace
  • TCP/IP subagent traces
  • TRAPFWD trace
  • NetView® SNMP Query Engine trace
  • NetView SNMP Query Engine IUCV Communication trace
Figure 1 was produced by using snmp get sysUpTime.0. When the SNMP agent is tracing responses, it makes the following entry in the syslogd output file:
Figure 1. SNMP agent response trace
Dec 19 15:55:38  snmpagent.9.: SNMP logging data follows ==============
 
Dec 19 15:55:39  snmpagent.9.: Log_type:        snmpLOGresponse_out
Dec 19 15:55:39  snmpagent.9.:    send rc:      0
Dec 19 15:55:39  snmpagent.9.:    destination:  UDP 127.0.0.1 port 5000
Dec 19 15:55:39  snmpagent.9.: version:         SNMPv1
Dec 19 15:55:39  snmpagent.9.: community:       public
Dec 19 15:55:39  snmpagent.9.:  ('70 75 62 6c 69 63'h)
Dec 19 15:55:39  snmpagent.9.: addressInfo:     UDP 127.0.0.1 port 5000
Dec 19 15:55:39  snmpagent.9.: PDUtype:         GetResponse ('a2'h)
Dec 19 15:55:39  snmpagent.9.: request:         1
Dec 19 15:55:39  snmpagent.9.: error-status:    noError (0)
Dec 19 15:55:39  snmpagent.9.: error-index:     0
Dec 19 15:55:39  snmpagent.9.: varBind oid:
Dec 19 15:55:39  snmpagent.9.: OBJECT_IDENTIFIER
Dec 19 15:55:39  snmpagent.9.: 1.3.6.1.2.1.1.3.0
Dec 19 15:55:39  snmpagent.9.:         name:    sysUpTime.0
Dec 19 15:55:39  snmpagent.9.:         value:
Dec 19 15:55:39  snmpagent.9.: TimeTicks
Dec 19 15:55:39  snmpagent.9.: 5900 - 59.00 seconds
Dec 19 15:55:39  snmpagent.9.: End of SNMP logging data:
In the following scenario, the SNMP agent attempted to initialize, but it was not successful. The port it was using was already in use. The trace shown in Figure 2 was obtained with SNMP agent tracing set to 7.
Figure 2. SNMP agent trace of unsuccessful initialization
Dec 19 11:57:52  snmpagent.16777227.: EZZ6235I socket function failed for
SNMP inet udp socket; EDC5112I Resource temporarily unavailable.
Dec 19 11:57:52  snmpagent.16777227.:  ... errno = 112, errno2 =12fc0296
Note: Errno 112 translates to Resource temporarily unavailable. The errno is used primarily by IBM® service in diagnosing the error. In this case, issue the Netstat CONN/-c command to determine whether TCP/IP is running and, if so, which ports are in use.

Figure 3 shows the trace produced for the agent when the authentication key sent by a manager does not match the key defined at the agent. The command receives a report indicating usmStatsWrongDigests.

Figure 3. SNMP messages and agent trace for nonmatching key
IDSTMVS.S@AU1104.SOURCE.S@AGV123(1624): rc=-65 (SNMP_RC_USM_WRONG_DIGEST)
   from snmp_process_message()
Figure 4 shows the output received by an SNMP manager and the trace produced for the agent when the operator attempted to retrieve data not within the defined view. The command issued in the z/OS UNIX shell was: 
snmp -h v374a -v get usmUserStatus.12.0.0.0.2.0.0.0.0.9.67.35.37.2.117.49
Figure 4. SNMP messages and agent trace when data not in defined view
OUTPUT RECEIVED BY THE MANAGER
usmUserStatus.12.0.0.0.2.0.0.0.0.9.67.35.37.2.117.49 = noSuchObject
 
AGENT TRACE
IDSTMVS.S@AU1104.SOURCE.S@AGV123(1624): RC=-30 (SNMP_RC_NOT_IN_VIEW) 
from snmp_process_message()
The following return codes in SNMP agent traces typically indicate configuration errors:
  • SNMP_RC_NOT_AUTHENTICATED - indicates the SNMP agent received an SNMPv1 or SNMPv2c request with a community name that was not valid for use by the IP address making the request.
  • SNMP_RC_NOT_IN_VIEW - indicates the SNMP agent received an SNMPv3 request for a MIB object that is not defined to be accessible by the community name or user name making the request.
  • SNMP_RC_USM_UNKNOWN_USERNAME - indicates the SNMP agent received an SNMPv3 request for a username not configured at the SNMP agent.
  • SNMP_RC_USM_WRONG_DIGEST - indicates the SNMP agent received an SNMPv3 request for which the authentication key for the user making the request was not valid.
  • SNMP_RC_USM_DECRYPTION_ERROR - indicates the SNMP agent received an encrypted request, but the request could not be decrypted because the encryption key for the user making the request was not valid.
  • SNMP_RC_USM_UNSUPPORTED_SECLEVEL - indicates the SNMP agent received a request for a defined user, but the user was not configured to use the security level specified in the request.
Parent topic: SNMP traces