Administration Guide

Local Navigation

How the BlackBerry Enterprise Server uses health parameters

The BlackBerry® Enterprise Server uses health parameters to define the failover and promotion thresholds. The health parameters indicate if a BlackBerry Enterprise Server service or component is healthy or unhealthy. For example, the value for the Wireless network access health parameter indicates whether the BlackBerry Router can access the wireless network. The health parameters are identical for both the failover threshold and the promotion threshold. You can choose the health parameters for the services and components that are important to your organization.

After you choose the health parameters that you want the BlackBerry Enterprise Server to use to determine when an automatic failover process should occur, the failover process can occur automatically if all of the following conditions are present:
  • The values for the health parameters that you define as part of the failover threshold for the primary BlackBerry Enterprise Server indicates whether a service or component is unhealthy.
  • The values for the health parameters that you define as part of the promotion threshold for the standby BlackBerry Enterprise Server indicate whether all the required services and components are healthy.
  • If you configure a health parameter for the primary BlackBerry Enterprise Server so that it is above the failover threshold, the health parameter value must indicate that the BlackBerry Enterprise Server service or component is healthy on the standby BlackBerry Enterprise Server before the automatic failover process can occur, even if you configure the health parameter to be below the promotion threshold line.

You must configure the health parameters that you choose for the primary BlackBerry Enterprise Server so that they are above the failover threshold. You must configure the health parameters that you choose for the standby BlackBerry Enterprise Server so that they are above the promotion threshold. The BlackBerry Enterprise Server ignores the health parameters that you configure to be below the thresholds.

The BlackBerry Enterprise Server updates the values of the health parameters periodically so that the BlackBerry Enterprise Server can determine automatically when a failover process should occur.

Defining when failover occurs

How you configure the failover threshold and promotion threshold impacts when failover occurs. You can configure the thresholds in any of the following ways:

  • For failover to occur when the standby BlackBerry® Enterprise Server is in an acceptable state, you can move the promotion threshold so that it is higher than the failover threshold. An acceptable state provides only the BlackBerry services that your organization considers essential.
  • For failover to occur only when the standby BlackBerry Enterprise Server is in a healthier state than the primary BlackBerry Enterprise Server, you can move the promotion threshold so that it is lower than the failover threshold.
  • For failover to occur when the standby BlackBerry Enterprise Server can provide the same services that the primary BlackBerry Enterprise Server can provide when it is healthy, you can move the promotion threshold so that it is equal to the failover threshold.

Configuring failover to occur when the standby BlackBerry Enterprise Server is in an acceptable state

By default, the thresholds are configured so that if the primary BlackBerry® Enterprise Server loses its SRP connection or its messaging server connection, or the primary BlackBerry Enterprise Server cannot browse the Internet, the primary BlackBerry Enterprise Server must fail over. The standby BlackBerry Enterprise Server can promote itself if it can connect to the BlackBerry® Infrastructure and messaging server. This default configuration is designed to make sure that the BlackBerry Enterprise Server remains in an acceptable state.

To maintain the BlackBerry Enterprise Server in an acceptable state, you configure the standby BlackBerry Enterprise Server to promote itself when it is sufficiently healthy to provide the BlackBerry services that your organization considers essential. The primary BlackBerry Enterprise Server cannot demote itself as long as it provides the BlackBerry services that your organization uses but does not consider essential.

For example, when the BlackBerry Enterprise Server pair uses the default configuration, if the primary BlackBerry Enterprise Server cannot connect to the messaging server, and the standby BlackBerry Enterprise Server cannot browse the Internet, the primary BlackBerry Enterprise Server must demote itself because one of its health parameters indicates that it is not sufficiently healthy. The standby BlackBerry Enterprise Server, even though it is experiencing an issue, can promote itself to become the primary BlackBerry Enterprise Server because all of the required health parameters indicate that it is healthy enough to become the primary instance.

Configuring failover to occur when the standby BlackBerry Enterprise Server can provide the same services that the primary BlackBerry Enterprise Server can provide

If you move the failover threshold and promotion threshold so that the identical health parameters are above both thresholds, the primary and standby BlackBerry® Enterprise Server instances must meet the same requirements to be considered sufficiently healthy to run. You can move the promotion threshold to be the same as the failover thresholds if your organization requires that the failover process can promote a healthy standby BlackBerry Enterprise Server only.

In this scenario, you configure the standby BlackBerry Enterprise Server to promote itself when it can provide most of the BlackBerry services that your organization requires. The primary BlackBerry Enterprise Server demotes itself when it cannot provide most of the BlackBerry services that your organization considers essential.

For example, you can configure the failover threshold and the promotion threshold so that the primary and standby BlackBerry Enterprise Server instances must be able to connect to the BlackBerry® Infrastructure and messaging server and browse the Internet. If the primary BlackBerry Enterprise Server cannot connect to the messaging server and the standby BlackBerry Enterprise Server cannot browse the Internet, the standby BlackBerry Enterprise Server cannot promote itself because it is not sufficiently healthy.

Configuring failover to occur when the standby BlackBerry Enterprise Server is in a healther state than the active BlackBerry Enterprise Server

If you move the failover threshold and promotion threshold so that the promotion threshold is lower than the failover threshold, failover occurs only if the standby BlackBerry® Enterprise Server is healthier than the primary BlackBerry Enterprise Server that is sufficiently healthy to run. You can move the promotion threshold so that it is lower than the failover threshold if your organization wants to limit failover occurrences and requires that failover occurs only if the standby BlackBerry Enterprise Server meets all of your organization’s requirements.

In this scenario, you configure the standby BlackBerry Enterprise Server to promote itself when it can provide most or all of the BlackBerry services that your organization requires. The primary BlackBerry Enterprise Server does not demote itself as long as it can provide at least the BlackBerry services that your organization considers essential.

For example, you configure the failover threshold so that the primary BlackBerry Enterprise Server must be able to connect to the BlackBerry® Infrastructure and messaging server and browse the Internet. You configure the promotion threshold so that the standby BlackBerry Enterprise Server must be able to connect to the BlackBerry Infrastructure and messaging server, browse the Internet, and process attachments. If the primary BlackBerry Enterprise Server cannot connect to the messaging server and the standby BlackBerry Enterprise Server cannot process attachments, the standby BlackBerry Enterprise Server cannot promote itself because it does not meet all of its requirements.


Was this information helpful? Send us your comments.