This article helps determining the root cause of BES12 Server Routing Protocol (SRP) connection alert messages sent by GSX Monitor, while the BES Administration Console shows the SRP as being connected. This is usually related to an issue with the BES Core processes not properly populating the Windows Simple Network Management Protocol (SNMP) information.
Here we check the related SNMP Management Information Base (MIB) maintained by the BES Core Services to locate the source of the SRP error message received by GSX Monitor.
Symptoms
- SRP connection is Down.
How to Troubleshoot the Issue
The SRP is the external connection the BES server is using to communicate with the BlackBerry infrastructure, by default over TCP port 3101. The SRP can connect directly to the Internet or indirectly using a BlackBerry Router or TCP Proxy server. 
The BES Core Service is responsible for maintaining SNMP Object Identifiers (OID) that GSX Monitor uses to determine the status of the SRP connection. In rare cases the information in the BES MIB is not correctly reported, this will cause GSX Monitor to incorrectly flag the SRP connection as being down.
The BlackBerry Server may need to be restarted to resolve this issue.
Here we determine if the SRP connection status information is available in the MIB using a generic SNMP Browsing and Querying tool to connect to the monitored BlackBerry server. In our example, we use the iReasoning MIB Browser:
- Create a new Agent in the MIB browsing tool from Tools > Options.
- In the Options window, select the Agents tab:
- Add a new agent.
- Enter the SRP Host IP Address and Community string.
- Select SNMP version 1 and Port 161.
- Select OK to save the agent.
- Close the options and return to the main screen.
Now that we have created an agent to use a specific community string and host, we can select it in the main screen for our tests:
Checking the OID used by GSX Monitor on the SRP host:
- Select the Agent created above from the Address drop down.
- In the OID field, paste .1.3.6.1.4.1.3530.8.7.15.120.15.1.2 as shown below:
- Press Go to execute the request:
This will return the value of 1 for an UP status or 0 for DOWN. If the above OID returns nothing at all, then the MIB data may not be being maintained.
Optional: Check the description field matches the message displayed in GSX Monitor to confirm there is a connection to the MIB.
- In the OID field, paste .1.3.6.1.4.1.3530.8.7.15.120.15.1.6
- This will return the text description of the error if there is one:
- The value returned is blank if there is no SRP connection error:
- If the OID .1.3.6.1.4.1.3530.8.7.15.120.15.1.2 returns nothing and the BES Administration Console reports the SRP as being connected, then the root cause of the problem is the BlackBerry SNMP data is not being maintained correctly.
- If "Snmp End Of MIB View" is returned, then the MIB has not been properly created.
- Having an incomplete or missing MIB has absolutely no impact on the BES server's performance. It may well go unnoticed until the MIB is attempted to be read for monitoring purposes.
If you see any other SRP connection error message, it is possible the Windows SNMP service has stopped communicating with the BES MIB and the data is not refreshed properly. A complete OS reboot is required, see the Possible Workaround section below for more details.
Possible Workaround
The only way to have any effect on the BlackBerry MIB is to restart the BlackBerry server operating system as MIBs are only built by the Windows SNMP service during an OS start up. Just restarting the BlackBerry services will not reconstruct the MIB.
If there is still an issue with the BES MIB not being properly populated after a complete reboot of the machine, then there may be something in the Windows SNMP service configuration that is preventing it from working as expected. Please see our article on removing non-resolvable hosts from the SNMP Configuration for more information. If the SNMP OID information is still not available, you should contact BlackBerry technical support to resolve the issue.