We host for our customer LFG - Luxembourg Financial Group, his BlackBerry Enterprise Server infrastructure. This installation contains 3 servers: 2 BES sharing a common license + 1 BES Router, all of them installed by your Netcore engineer (lu-bb1 and lu-bb2 (BES) and lu-bbsg1 (router)).
We cannot use both BES servers in the same time because we own only one server license, that is why the engineer who installed the second BES server provided us a Disaster Recovery Procedure and scripts:
- export of lu-bb1 database
- stop services of lu-bb1
- import database on lu-bb2
- update database on lu-bb2
- start services on lu-bb2

Recently we had an Operating system issue on lu-bb1, that is why we decided to active lu-bb2 and deactive lu-bb1. We applied the DR procedure which succeeded, all devices were running and email synced.

There is a wireless network in the customer environment. The WLAN profile is delivered to the BB devices through the BES and worked fine when the active BB server was lu-bb1. The BB devices reached lu-bb1 internally through the WLAN without going through GPRS when users were in the office.

But, now we have a problem concerning this internal WLAN connection.
Since we activated the second server lu-bb2, it appears the BB are not able to connect to the BES when they are in the office using WLAN connection.

Please find below the output of the devices:
-----

Wi-Fi

Current Profile: LFG_BBY

SSID: LFG_BBY

AP MAC Address: 00:1E:4A:32:10:ED

Security Type: Pre-Shared Key (PSK)

Association: Successful

Authentication: Successful

Local IP Address: 10.1.203.56

Signal Level: 0 dBm

Connection Data Rate: 54 Mbps

Status: Network acquired

Authentication Failure Reason:

Network Type: 802.11a

Network Channel: 60

Pairwise Cipher: CCMP

Group Cipher: TKIP

Gateway Address: 10.1.203.1

DHCP: Successful

Primary DNS: 10.1.100.50

Secondary DNS: 0.0.0.0

DNS suffix: lfg.local

Subnet Mask: 255.255.255.0

Server Domain Suffix:

Certificate:

Software Token:



BlackBerry Infrastructure

Address Used: //rcp.eu.blackberry.com:443

IP Used:

Connecting: Error

Authenticating router: N/A

Authenticating server: N/A

Last Contact At:



Enterprise

UIDs:

Address Used: //lu-bb2.lfg.local:4101

IP Used:

Connecting: Error

Authenticating router: N/A

Authenticating server: N/A

Last Contact At:


The device tries to reach directly lu-bb2 but fails. The server is in the same IP subnet than lu-bb1, routed the same way from WLAN, no firewall rules.

Then, we fixed our OS issue on lu-bb1 so we decided to fallback to it. We stopped all services of lu-bb2, and started them on lu-bb1. BB devices registered correctly in lu-bb1 and are all "running" now. But, the customer says the BB are not able to reach the BES internally when they use WLAN.

So, the questions are:
- Is it possible to set manually somewhere in the BES Manager which value is sent as:
Enterprise


Address Used: //lu-bb2.lfg.local:4101


- Is it possible to set a list of servers to try to connect to? In case of failover, if the BB got a list of BES, it can try to reach the first one lu-bb1, then the second one lu-bb2...

- Or, if it is not possible, how to force the update of this value?
Because after fallback to lu-bb1, the devices still try to reach lu-bb2...

Found the solution

I had to push the service books again on the Blackberry