KB16208 - Both primary and standby BES instances are running in Standby mode

hdawg · #1 (**permalink**) 07-15-2009, 02:16 PM

KB16208 - Both primary and standby BES instances are running in Standby mode

Environment

BlackBerry® Enterprise Server version 5.0 for Microsoft® Exchange

Overview

When viewing the High Availability summary section within the BlackBerry Administration Console, the Failover status displays as Running - Standby for both the primary and standby BlackBerry® Enterprise Server instances.

Cause

This issue occurs when the SRP Identifier and Authentication key for the primary and standby BlackBerry Enterprise Server instances is also being used on a separate BlackBerry Enterprise Server instance that is connected to a separate BlackBerry Configuration Database.
Both the primary and standby BlackBerry Enterprise Server instances and the second BlackBerry Enterprise Server instance that is connected to a separate BlackBerry Configuration Database try to connect to the BlackBerry® Infrastructure at the same time. The BlackBerry Infrastructure sends a packet that contains the string NewConnectionReceivedLastConnectionWins back to the BlackBerry Dispatcher. This packet tells the BlackBerry Dispatcher to switch the primary BlackBerry Enterprise Server instance to become a standby BlackBerry Enterprise Server instance.
Here is an example of the BlackBerry Dispatcher log file when this issue occurs:

[40000] (09/29 06:45:42.284):{0x1724} [SRP] EVENT=Receive_DISCONNECT, VERSION=3, REASON=3, STRING=NewConnectionReceivedLastConnectionWins

[30000] (09/29 06:45:42.284):{0x1724} [SRP] Received SRP Disconnect command reason=3 NewConnectionReceivedLastConnectionWins

[40000] (09/29 06:45:42.284):{0xF2C} [SRP] SRPClientReceiver thread stopped

[30000] (09/29 06:45:42.284):{0xF2C} [DIAG] EVENT=Unregister_thread, THREADID=0xF2C, THREADNAME="SRPClientReceiver"

[40109] (09/29 06:45:42.284):{0x1728} [SRP] Tentative connection lost, setting failover to STANDBY

[30000] (09/29 06:45:42.284):{0x1728} [SRP] Connection lost

[50113] (09/29 06:45:42.284):{0x17CC} BES switching to failover mode STANDBY

[40000] (09/29 06:45:42.284):{0x1724} [SRP] SRPClientSessionReceiver thread stopped

[30000] (09/29 06:45:42.284):{0x1724} [DIAG] EVENT=Unregister_thread, THREADID=0x1724, THREADNAME="SRPClientSessionReceiver"

[40000] (09/29 06:45:42.284):{0x1728} [SRP] SRPClientSession thread stopped

[30000] (09/29 06:45:42.284):{0x1728} [DIAG] EVENT=Unregister_thread, THREADID=0x1728, THREADNAME="SRPClientSession"

[30488] (09/29 06:45:42.284):{0x17CC} Sending SET_FAILOVER_MODE command to BES Agent, mode STANDBY, ActiveHost=, ActiveService=, SessionId=ALL

[30309] (09/29 06:45:42.284):{0x17CC} [BIPPa] {SCS} Sending BIPP data to BES Agent (unknown), size=31, Tag=32821

[30516] (09/29 06:45:42.284):{0x17CC} Sending SET_FAILOVER_MODE command to ext service, mode STANDBY, SessionId=Sxxxxxxxx:C3:ID10,IPPP, ActiveConnectionId=0

Here is an example of the BlackBerry Controller log file when this issue occurs:

[30000] (09/29 06:45:42.738):{0x10C8} Switching to STANDBY mode

[30000] (09/29 06:45:42.738):{0x10C8} BES is in not active stopping SyncServer

[30000] (09/29 06:45:42.738):{0x10C8} BES is in not active stopping MailStore Service

[30000] (09/29 06:45:42.738):{0x10C8} BES is in not active stopping Policy Service

Resolution

Complete the following steps to switch the standby BlackBerry Enterprise Server instance back to the primary BlackBerry Enterprise Server instance:

Stop the BlackBerry Enterprise Server services on the secondary BlackBerry Enterprise Server instance (that is connected to a separate BlackBerry Configuration Database) with the same SRP Identifier as the primary and standby BlackBerry Enterprise Server instances.
Restart both the BlackBerry Router and Dispatcher service for the primary and standby BlackBerry Enterprise Server instances.

Follow Us On

Forum Sponsors

Google Advertisements