Hack 74. Test Your SRP Connection


Use this utility to verify your BES's connection to RIM's network.

The SRP connection between the BlackBerry Enterprise Server and Research In Motion's network is critical. If this connection goes down for any reason, all BlackBerry devices homed on that BES will not be able to send or receive emails. This makes the SRP connection vitally important to the service.

How do you know if the SRP connection is down? RIM provides a convenient utility to run from the BlackBerry Enterprise Server to allow you to test the SRP connection at any time from a command prompt. It makes a connection with the SRP node on RIM's network that you have configured for each BES on your server machine.

7.4.1. Run bbsrptest.exe

You'll find the bbsrptest.exe utility in the following directory within the BlackBerry Enterprise Server installation:

C:\Program Files\Research In Motion\BlackBerry Enterprise Server\Utility

To run the tool, bring up a command prompt and cd to the directory. Run the utility by typing bbsrptest from the command prompt without any options. If your SRP connection test is successful, you'll receive output similar to the following:

 NetworkAccessNode is srp.na.blackberry.net. Attempting to connect to srp.na.blackberry.net (206.51.26.33), port 3101 Sending test packet Waiting for response Receiving response Checking response Successful 

Because you can configure more than one BES per server and each BES can be configured to point to a different SRP node on RIM's network, you'll get the previous output for each BES you've set up on your machine.

If the test fails, you will receive output similar to the following:

 NetworkAccessNode is srp.na.blackberry.net. Attempting to connect to srp.na.blackberry.net (192.168.0.222), port 3101 connect() failed: Connection timed out (10060) 

Notice the IP address of srp.na.blackberry.net in the previous output. I used the local HOST file to point srp.na.blackberry.net to a nonexistent address on my local network so I could generate this error for you to see.

7.4.2. Run bbsrptest.exe from Your Workstation

When you run the bbsrptest.exe utility from a computer without the BlackBerry Enterprise Server installed, you'll get the following output:

 Registry key HKEY_LOCAL_MACHINE\Software\Research In Motion\BlackBerryRouter is missing, trying HKEY_LOCAL_MACHINE\Software\Research In Motion\BlackBerry Enterprise Server\Dispatcher Registry key HKEY_LOCAL_MACHINE\Software\Research In Motion\BlackBerry Enterprise Server\Dispatcher is missing 

This is because the tool needs to determine which SRP node your BES instances are configured to connect to. If the BES software is not installed, there is no way for the tool to know how to connect to RIM's network to verify connectivity.

It turns out that the registry key and its contents are all the tool needs. You can export the registry key from the server and import it on your workstation, and you can run the utility from there.

Export the registry key using regedit. Go to the following key:

 HKEY_LOCALMACHINE\Software\Research In Motion\BlackBerry Enterprise Server 

Right-click on the previous key and choose Export from the menu, as shown in Figure 7-7.

Save the exported key to a file and then copy it to the computer from which you'd like to be able to run bbsrptest.exe. Import it into the local registry by double-clicking on the .reg file. Then simply copy the bbsrptest.exe file to a local directory and you'll be able to run the utility from the computer without BES software installed.

Figure 7-7. Exporting the registry key


A successful run of bbsrptest.exe from your local workstation tells you that your machine was able to connect through port 3101 to RIM's network. This doesn't necessarily mean your server computer will be able to do the same for a true test, run this from your BES server.




BlackBerry Hacks
Blackberry Hacks: Tips & Tools for Your Mobile Office
ISBN: 0596101155
EAN: 2147483647
Year: 2006
Pages: 164
Authors: Dave Mabe

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net