Has anyone had issues with the MIB provided for SNMP trap handling. It doesn't seem to match up to the traps we actually recieve. They seem to have the OIDs wrong. The file we have says:



DESCRIPTION "The MIB module for entities implementing the SNMP protocol for BlackBerry server."
REVISION "200506201630Z" --June 20, 2005 11:30 E

After taking another look at the "BlackBerry Enterprise Server for Microsoft Exchange Version 4.0 Maintenance Guide Appendix C: SNMP Values" I noticed that for the BlackBerry Enterprise Server events section the traps are defined as ".1.3.6.4.1.3530.9". The MIB loads up the traps as ".1.3.6.4.1.3530.5.9". So the documentation is closer to some of the traps we are seeing in our production environment.

The problem in the MIB file is they have coded:

-- RIM
-- FROM RIM-MIB;

rim OBJECT IDENTIFIER ::= { enterprises 3530}
blackBerryServer OBJECT IDENTIFIER ::= {rim 5}
besTrapVariables OBJECT IDENTIFIER ::= {blackBerryServer 9}

The besTrapVariables line should be instead

besTrapVariables OBJECT IDENTIFIER ::= {rim 9}

In order to make it dependent on the "3530" tree. I can't believe we are the first ones to stumble across this. Was this correct in previous BES versions?

Use the MIB from the latest Service Pack

That is where we got the MIB. Does your MIB have the same identfication within the file of:
REVISION "200506201630Z" --June 20, 2005 11:30 E

Thank you!

From RIM support:

Further to our discussion today regarding BlackBerry Enterprise Server SNMP Traps OIDs defined in the MIB file does not matching the actual Traps OIDs generated by the BlackBerry Enterprise Server SNMP agent. For example in the MIB file besTrapVariables OBJECT IDENTIFIER ::= {blackBerryServer 9} Which means that traps should be generated under 1.3.6.1.4.1.3530.5.9 but traps are generated under 1.3.6.1.4.1.3530.9.

We have created SDR 90238 for above said issue and will be fixed in future releases of Service Pack.