BlackBerry Server Routing Protocol Test

Server Routing Protocol (SRP) is a unique identifier used to communicate and authenticate the BlackBerry Enterprise Server with the BlackBerry relay. The BlackBerry relay is a key component of the BlackBerry system. It receives messages from within a corporate network, translates the messages, and routes them to the wireless network for delivery to the handheld device. 

In order to facilitate this transaction, the BlackBerry Enterprise Server maintains a constant connection with the SRP host, so that it knows where the handheld devices are located.

This test monitors the SRP host and reports the status of the BES server’s connections with the SRP host.

Target of the test : A BlackBerry Enterprise Server

Agent deploying the test : An internal/remote agent

Outputs of the test : One set of results for every server being monitored.

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed


The IP address of the host for which this test is to be configured.


The port at which the monitored target exposes its SNMP MIB; The default value is 161.


By default, the eG agent supports SNMP version 1. Accordingly, the default selection in the SNMPversion list is v1. However, if a different SNMP framework is in use in your environment, say SNMP v2 or v3, then select the corresponding option from this list.


The SNMP community name that the test uses to communicate with the firewall. This parameter is specific to SNMP v1 and v2 only. Therefore, if the SNMPVersion chosen is v3, then this parameter will not appear.


This parameter appears only when v3 is selected as the SNMPversion. SNMP version 3 (SNMPv3) is an extensible SNMP Framework which supplements the SNMPv2 Framework, by additionally supporting message security, access control, and remote SNMP configuration capabilities. To extract performance statistics from the MIB using the highly secure SNMP v3 protocol, the eG agent has to be configured with the required access privileges – in other words, the eG agent should connect to the MIB using the credentials of a user with access permissions to be MIB. Therefore, specify the name of such a user against this parameter. 


This parameter appears only when v3 is selected as the SNMPVersion. An SNMP context is a collection of management information accessible by an SNMP entity. An item of management information may exist in more than one context and an SNMP entity potentially has access to many contexts. A context is identified by the SNMPEngineID value of the entity hosting the management information (also called a contextEngineID) and a context name that identifies the specific context (also called a contextName). If the Username provided is associated with a context name, then the eG agent will be able to poll the MIB and collect metrics only if it is configured with the context name as well. In such cases therefore, specify the context name of the Username in the Context text box.  By default, this parameter is set to none.


Specify the password that corresponds to the above-mentioned Username. This parameter once again appears only if the SNMPversion selected is v3.

Confirm Password

Confirm the AuthPass by retyping it here.


This parameter too appears only if v3 is selected as the SNMPversion. From the AuthType list box, choose the authentication algorithm using which SNMP v3 converts the specified username and password into a 32-bit format to ensure security of SNMP transactions. You can choose between the following options:

  • MD5 - Message Digest Algorithm
  • SHA - Secure Hash Algorithm
  • SHA224 - Secure Hash Algorithm 224 bit
  • SHA256 - Secure Hash Algorithm 256 bit
  • SHA384 - Secure Hash Algorithm 384 bit
  • SHA512 - Secure Hash Algorithm 512 bit


This flag appears only when v3 is selected as the SNMPversion. By default, the eG agent does not encrypt SNMP requests. Accordingly, the this flag is set to No by default. To ensure that SNMP requests sent by the eG agent are encrypted, select the Yes option. 


If the EncryptFlag is set to Yes, then you will have to mention the encryption type by selecting an option from the EncryptType list. SNMP v3 supports the following encryption types:

  • DES - Data Encryption Standard
  • 3DES - Triple Data Encryption Standard
  • AES - Advanced Encryption Standard
  • AES128 - Advanced Encryption Standard 128 bit
  • AES192 - Advanced Encryption Standard 192 bit
  • AES256 - Advanced Encryption Standard 256 bit


Specify the encryption password here.

Confirm Password

Confirm the encryption password by retyping it here.


Specify the duration (in seconds) within which the SNMP query executed by this test should time out in this text box. The default is 10 seconds.

Data Over TCP

By default, in an IT environment, all data transmission occurs over UDP. Some environments however, may be specifically configured to offload a fraction of the data traffic – for instance, certain types of data traffic or traffic pertaining to specific components – to other protocols like TCP, so as to prevent UDP overloads. In such environments, you can instruct the eG agent to conduct the SNMP data traffic related to the monitored target over TCP (and not UDP). For this, set this flag to Yes. By default, this flag is set to No.


This parameter appears only when v3 is selected as the SNMPVersion. Sometimes, the test may not report metrics when AES192 or AES256 is chosen as the Encryption type. To ensure that the test report metrics consistently, administrators need to set this flag to Yes. By default, this parameter is set to No.

Measurements made by the test
Measurement Description Measurement Unit Interpretation

BlackBerry server is not connected to SRP host

Indicates whether BES is currently connected to the SRP host or not


The value 1 indicates that BES is connected to the SRP host. The value 0 indicates that BES is not connected to the SRP host. If the BES-SRP host connection fails, it would result in crucial lapses in delivery of messages to handheld devices. Therefore, if the value of this measure is 0, you are advised to perform additional prognosis to identify the cause of the connection failure, and attend to the cause quickly.

Many successful reconnection to SRP host

Indicates the number of times the blackberry server has successfully reconnected to the SRP host during the last measurement period.


The BlackBerry Enterprise Server may disconnect the Server Routing Protocol (SRP) connection to the BlackBerry Infrastructure. This disconnection may be due to the following network conditions:

  • Packet loss
  • Latency
  • Other symptoms of poor network conditions

Immediately following the SRP disconnection, the BlackBerry Enterprise Server attempts to reconnect to the BlackBerry Infrastructure. However, if poor network conditions persist during this time, the SRP connection may be repeatedly disconnected and reconnected by the BlackBerry Enterprise Server. This is what a high value of the Failed reconnections to SRP host measure would typically imply.

Few failed reconnections to SRP host

Indicates the number of times the blackberry server has failed to reconnect to the SRP host during the last measurement period.


Time connection to SRP host has been lost

Indicates the number of seconds for which BES has not been connected to the SRP host during the last measurement period.


If the BES remains disconnected from the SRP host for too long a time, it would disrupt the interaction between BES and the BlackBerry handheld devices within a wireless network. Such disconnections could be caused due to any of the following practical reasons:

  • Pathetic network conditions causing reconnections to SRP hosts to fail repeatedly
  • The BlackBerry Infrastructure is configured to disable SRP identification (IDs) that establish and exceed five connections within one minute. This configuration can be changed.
  • If the BlackBerry Enterprise Server is connected to the BlackBerry Infrastructure and another client attempts to connect using the same SRP ID and Authentication Key, the BlackBerry Infrastructure drops the connection to the BlackBerry Enterprise Server.

Improper configuration of BES can also affect the BES-SRP host connectivity. Such configuration issues include:

  • Firewall configurations disallowing BES - SRP host connections
  • The Network Access Node key is set to an IP address or NetBIOS name other than localhost.
  • The Server Routing Protocol (SRP) Address is blank or set to local host.
  • The SRP identifier or SRP authentication key are specified incorrectly.
  • On the Server tab of BlackBerry Server Configuration, the router host is not set to localhost.
  • The BlackBerry Router service cannot start.