One of the reasons for the BlackBerry SNMP service to fail is an invalid trap destination in the SNMP settings on the BES server. This prevents the BES MIB from being initialized.
In this article, we will check the Trap destinations from the SNMP service properties, and make sure they are all valid.
- SNMP End of MIB View.
- Empty MIB.
- No OID for this Version.
How to Troubleshoot the Issue
We are going to check that there are no old hostnames or IP addresses in the SNMP trap destination of the BES SNMP service, because they all must be valid for the SNMP service to work properly. When a host is decommissioned and does not resolve at the DNS level anymore, it will prevent the SNMP service from initializing the BlackBerry MIB as expected if still listed as an SNMP service trap destination.
- Remote connect to the BlackBerry server you are investigating.
- Log in as Administrator.
- Run services.msc
- Right-click the SNMP service ans select Properties.
- Go to the Traps tab:
- Note the IP addresses and hostnames listed in the Trap destinations field. We will use this to determine the root cause of the problem if there is an actual issue. If the list of Trap destinations is empty, you can directly skip to checking the registry of the BES server.
- Open a Command Prompt and enter nslookup followed by a trap destination name to make sure we get an answer from the hostname or IP address.
If the host-name or IP address specified as a destination in the BES SNMP Trap settings is invalid, the nslookup command will fail as shown in the example below:
Invalid SNMP Trap destinations entries must be removed and the BES server rebooted at the OS level to rebuild the MIB.
RIM Related Technote
- BlackBerry Enterprise Server services fail to initialize SNMP when an invalid trap destination is specified.