|
Measures reported by BBerryMdsStsTest
The BlackBerry MDS receives push requests from applications; these requests typically contain the data to be delivered. The MDS then pushes the data to the BlackBerry devices. Using this test, you can monitor the data received by the MDS (from applications) and the connections established by the MDS with BlackBerry devices for transmitting data to them. With the help of the metrics reported by this test, you can ascertain the following:
- Whether any data packets were refused or declared invalid by the MDS;
- Whether any connectivity issues exist between the MDS and the devices; if so, you can also figure out whether it is owing to failed SRP (Server Routing Protocol) connections
The BlackBerry MDS may reject a data packet if it does not recognize the format of a data packet or does not recognize the device transport key that protects the data packet.
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| Refused_packets |
Indicates the number of data packets that were refused by this BlackBerry MDS Connection Service during the last measurement period.
|
Number |
The BlackBerry MDS may reject a data packet if it does not recognize the format of a data packet or does not recognize the device transport key that protects the data packet. |
| Invalid_packets |
Indicates the total number of invalid data packets that were received by this BlackBerry MDS Connection service during the last meaurement period. |
Number |
One of the reasons why a push request may have been declared invalid by the MDS is if the request contains a reliability specification, but does not include a notification URL.
In your push request, you can specify that you want the BlackBerry® device to return a result notification when the pushed data is successfully delivered. The BlackBerry® MDS Connection Service receives notifications from each destination BlackBerry device that successfully receives the pushed data and forwards those notifications to the push originator. Similarly, the BlackBerry MDS Connection Service sends a notification to the push originator if a push request is not successfully delivered to one or more destination BlackBerry devices within the allotted time. If you do not specify a reliability level for your push method, the BlackBerry MDS Connection Service does not provide the push originator with any notification regarding the outcome of the push request. You must also specify a notification URL to which the BlackBerry MDS Connection Service will send result notifications, with every push request that specifies a reliability option. A push request that requests some level of reliability but does not provide a notification URL is considered invalid and is rejected by the BlackBerry MDS Connection Service.
|
| Truncated_conns |
Indicates the number of truncated connections that were encountered by this BlackBerry MDS Connection service during the last measurement period. |
Number |
Ideally the value of this measure should be low. |
| Invalid_conns |
Indicates the number of invalid connections encountered by this Blackberry MDS Connection Service during the last measurement period. |
Number |
|
| Success_srp_conns |
Indicates the number of SRP connections that were successfully initialized between the BlackBerry Enterprise Server and the BlackBerry Infrastructure. |
Number |
The BlackBerry Dispatcher handles traffic to the BlackBerry Infrastructure. It compresses/decompresses and encrypts/decrypts wireless data. The BlackBerry Dispatcher handles all Server Routing Protocol (SRP) connections from the BlackBerry MDS Connection Service and many other components of the BlackBerry Infrastructure. The MDS Connection Service (on the BlackBerry Enterprise Server) connects to the BlackBerry Dispatcher through specific ports and communicates with the BlackBerry Infrastructure through the BlackBerry Router using a unique SRP identifier that the BlackBerry Dispatcher establishes.
Once the SRP identifier is established, the BlackBerry MDS sends a basic information packet to the BlackBerry Infrastructure via the BlackBerry Router; this packet includes version information, the SRP identifier established by the BlackBerry dispatcher, and other information that is required to open an SRP connection. If the packets so received are valid, then the BlackBerry infrastructure will send basic information packets to the BlackBerry MDS, therey successfully opening the SRP connection.
On the other hand, if the BlackBerry Infrastructure receives unrecognized packets from the BlackBerry MDS, then the SRP is connection is closed. Also, if a BlackBerry MDS uses the same SRP authentication key and SRP identifier to connect to (and then disconnect from) the BlackBerry Infrastructure 5 times in 1 minute, the BlackBerry Infrastructure deactivates the SRP identifier to help prevent a potentially malicious user from using the SRP identifier to create conditions for a DoS attack. |
| Failed_srp_conns |
Indicates the number of SRP connections that failed to materialize between the BlackBerry Enterprise Server and the BlackBerry Infrastructure. |
Number |
|