Report received from SNMP agent

With SNMPv3, certain error conditions detected on a request are sent back from the SNMP agent to the SNMP manager as a report. Some reports are expected as part of normal processing, but most often they indicate an error condition.

For the snmp command, some reports occur during normal processing, such as the usmStatsUnknownEngineIDs condition, which occurs as the snmp command performs discovery processing to learn the SNMP stackID of the agent with which it is communicating. Normal processing reports are not displayed by snmp unless debug tracing is active. Reports that indicate error conditions are typically displayed using the EZZ33431 message. For example, when an attempt is made to use a USM user with an authentication key that does not match the key that is configured at the SNMP agent, the usmStatsWrongDigests report is received.

Figure 3 shows the output received by an SNMP manager when the authentication key sent by an snmp command did not match the key defined at the agent. The command issued in the z/OS UNIX shell was:

$ snmp -h v374 -v walk usmUserStatus
 
EZZ33431 Report received : usmStatsWrongDigests
EZZ33011 Error return from SnmpRecvMsg()

Following are other common reports:

usmStatsUnknownUserNames: Indicates a request was received for a user that is not defined at the SNMP agent.
usmStatsUnsupportedSecLevels: Indicates a request was received for a defined user, but the user was not configured at the SNMP agent to use the security level specified in the request.
usmStatsDecryptionErrors: Indicates an encrypted request was received at the SNMP agent, but the request could not be decrypted. This can be the result of an invalid privacy key.