ITM Agent Insights: Trap information is not shown in the TEP GUI for an Agent Builder Agent

Body

This Blog will discuss if you have an Agent Builder Agent created to receive traps but you are not seeing any information in the TEP GUI.

An Agent Builder agent has been created to receive traps and an official MIB file has been imported with no errors.  Once the agent is installed, if you do not see entries in the TEP GUI for the received traps, check the following:

In the agent logs, with KBB_RAS1= ERROR (UNIT: snmp ALL) you could find the following error message:

(4F194C24.0133-2:snmpeventqueryclass.cpp,1203,"processInform") No event class matches the received trap: generic=6 specific=6 oid=1.3.6.1.4.1.1302.3.8.10.2.1

This means the Agent Builder agent is not able to find a matching OID of the received trap. The received OID is compared with all the OIDs listed in the itm_toolkit_agent.xml file.  Based on this, you need to have a look at the itm_toolkit_agent.xml and in particular you should check for all the lines like the following:

<global_snmp_event_settings_for_group oids="1.3.6.1.4.1.1302.3.8.10.2.1.0-6">

As you can see, in this case we have an extra zero. In fact, our agent will compare the received OID1.3.6.1.4.1.1302.3.8.10.2.1 with the value stored in the xml file: 1.3.6.1.4.1.1302.3.8.10.2.1.0.
The Agent Builder currently removes that last .0 to determine the Enterprise OID of the trap and this is working as expected considering the following information:

As the builder/agent supports both SNMP V2 trap to an SNMP V1, we act like V2 to V1 mapper, per the RFC mapping rules.

From RFC 2089 which tells how to map an SNMP V2 trap to an SNMP V1 trap:

- If the snmpTrapOID.0 value is not one of the standard traps, then the generic-trap field is set to 6 and the specific-trap field is set to the last subid of the snmpTrapOID.0
  value.

- If the next to last subid of snmpTrapOID.0 is zero, then the enterprise field is set to snmpTrapOID.0 value and the last 2 subids are truncated from that value.
- If the next to last subid of snmpTrapOID.0 is not zero, then the enterprise field is set to snmpTrapOID.0 value and the last 1 subid is truncated from that value.

Considering that in this case the MIB ends with a .0, you need to edit the itm_toolkit_agent.xml and find the lines that look like:                       

<global_snmp_event_settings_for_group oids="1.3.6.1.4.1.1302.3.8.10.2.1.0-6">

and delete the .0 (including the dot)

so it will now look like:
<global_snmp_event_settings_for_group oids="1.3.6.1.4.1.1302.3.8.10.2.1-6">

Then regenerate the re-install the agent.

Additional ITM Agent Insights series of IBM Tivoli Monitoring Agent blogs are indexed under ITM Agent Insights: Introduction.

Subscribe and follow us for all the latest information directly on your social feeds: