Common issues with the SNMP event adapter

The following topics list some common issues with the SNMP event adapter and gives steps on how to resolve them.

Missing events

If SNMP traps are sent to the SNMP adapter at a very high rate, some traps may not be received.
To address this behavior, edit mcxa.conf with the following settings in your SNMP adapter instance section.

PollInterval = 1

ReadsPerEngine = 200

SnmpRcvbuf = 262144

No events received in the cell

Adapters use msend which utilizes the mposter buffer. If the buffer becomes corrupt, msend fails and no events are sent from the adapter.

To address this issue, perform the following steps.

1. Stop the adapter.
2. Remove the following files from %installationDirectory/pw/server%/log/adapters/
   • mposterbuf.buf
   • mposterbuf.pos
   • mposterbuf.lck
3. Restart the adapter.

Trap matching to the wrong event class

If the incoming SNMP trap appears in the cell with the wrong class, examine the installationDirectory/pw/server/etc/mcsnmptrapd.map file. The adapter matches the incoming trap to the first definition in the map file that matches.

There might not be an exact match for the trap if the:

• MIB file has not being published
• Definitions must be reordered in the map file to ensure the best match appears first

For any queries, contact BMC Customer Support.

Changing the encoding scheme

Based on the server locale, change the SNMP configuration parameters, save the file and restart the Infrastructure Management server for the changes to reflect.

In the <installation directory>\pw\pronto\conf\pronet.conf file, modify the following properties:

# If you want to enable SNMPv1 version, uncomment the following line, and set the property value to 1 as shown in the example:
#pronet.alarms.actions.snmptrap.version=1


# If you want to enable SNMPv2 version, uncomment the following line, and set the property value to v2c as shown in the example:
#pronet.alarms.actions.snmptrap.version=v2c

Non en_us locales:

In the <installation directory>\pw\pronto\conf\i18nConf.conf file, add or modify the encoding scheme through the pronet.alarms.actions.snmptrap.encoding.<server locale> property.

#Encoding styles for different server locale
#Uncomment the following property to set the required locale as shown in the examples:


# For Chinese locale 
#pronet.alarms.actions.snmptrap.encoding.zh_CN=GBK


#For Japanese (Japan) locale
#pronet.alarms.actions.snmptrap.encoding.ja_JP=UTF-8