Dispatcher Connections Test
The BlackBerry Dispatcher is designed to compress and encrypt all information sent to the BlackBerry UEM. The BlackBerry Dispatcher is also designed to decompress and decrypt all information that users send from the BlackBerry UEM, and to send that information to other BlackBerry services and components.
All communication between the BlackBerry components passes through this service. The BlackBerry Dispatcher provides secure connectivity using IPPP for End point devices. The USP of Blackberry services is security, so dispatcher becomes the key component which provides secure communication whcih users can trust. Any issues with dispatcher can cause a security compromise, so it becomes important to monitor dispatcher continuously and report any issues before they can cause concern.
This test periodically checks the connectivity between the Blackberry UEM and the external devices and promptly alerts administrators if devices are unable to establish a connection. In this process, the test also reports how many errors the dispatcher had encountered during the connection.
Target of the test : A BlackBerry UEM
Agent deploying the test : An external agent
Outputs of the test : One set of results for Blackberry UEM.
Parameter |
Description |
---|---|
Test Period |
How often should the test be executed. |
Host |
The IP address of the target server that is being monitored. |
SNMPPort |
The port at which the monitored target exposes its SNMP MIB; |
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. |
Timeout |
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. |
SNMPversion |
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. |
Context |
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. |
Username |
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. |
Authpass |
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. |
AuthType |
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:
|
EncryptFlag |
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. |
Encrypttype |
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:
|
Encryptpassword |
Specify the encryption password here. |
Confirm Password |
Confirm the encryption password by retyping it here. |
EngineID |
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. |
Measurement |
Description |
Measurement Unit |
Interpretation |
||||||
---|---|---|---|---|---|---|---|---|---|
Status |
Indicates whether the connection is currently established or not. |
Number |
This measure denotes whether the connection is currently established. The values reported by this measure and its numeric equivalent are mentioned in the table below:
Note: By default, this measure reports the above-mentioned States while indicating the connection status of the BlackBerry Dispatcher. However, in the graph of this measure, states will be represented using the corresponding numeric equivalents only - i.e., 0 or 1. |
||||||
Transmitted transactions |
Indicates the number of transactions transmitted to the BlackBerry Configuration Database during the last measurement period. |
Number |
If the number of transcations are decresing over last few measurements administaraots may have to investigate it further |
||||||
Transaction errors |
Indicates the number of errors encountered during the database connection. |
Number |
A high value is a cause for concern, as too many error-prone transactions can significantly damage the user experience. |