ITM Agent Insights: Debugging problems of an SNMP Agent you created with Agent Builder
shepardd 100000QR7C Visits (7498)
This blog will help you with your SNMP agent that you built with Agent Builder when it is not being able to retrieve data and, in the TEP GUI, you see the NO_I
The first thing you should do is enable the trace level in the agent log.
For all new instances or prod
Once the traces are enable, recreate the problem. In the log file you will find some messages - generated by the snmpqueryclass module - showing the problem.
For example, you might find messages like the following:
As you can see from the messages above, the root cause of the problem is the error code 5. The status 5 error indicates that the SNMP agent on the remote system replied to our request with a "general error". Once you get a clear idea of the error code that the ITM agent received from the SNMP agent, you will need to run the snmpgetnext and snmpwalk commands for the problematic OID. In this case, if you run the snmpwalk command, then you will receive all the proper information but, at the end of the output, you might see an error like the following one:
Error in pack
This error message will reflect the error code 5 in the agent trace log. It means that the problem is not related with the ITM agent but with the SNMP agent that provided the problematic outcome.
Additional ITM Agent Insights series of IBM Tivoli Monitoring Agent blogs are indexed under IT
Subscribe and follow us for all the latest information directly on your social feeds: