WARNING: BES Client has incorrectly chosen a BES Relay

Usage and Config Platform
1

(imported topic written by AviE91)

Hey Experts,

Hoping i will find the answer here, my issue is that i have a relay in each remote office LAN (40 remote offices) that is suppose to serve the clients in it’s LAN,

In head office there’s the TEM Main Server which is also the top level relay for all other relays

In head office DMZ there’s a relay with a public IP

All of these relay are installed and report successfully (i checked the “Relay Status” analysis under “BigFix Management”)

The issue happens through out the remote office, the clients choose DMZ Relay even tho hop count to LAN Relay is smaller.

from a client in one of the remote office i ran BESDiagnostics -r (relay selection test) and after viewing the entire output,

I filtered all the relays the client reached and the summary (i changed the IP to represent role of relay and location):

"

DNS name IP Address Num Hops RelayVersion

DMZASIA DMZHKG 9 8.1.617.0

DMZEMEA DMZEMEA 12 8.1.617.0

LocalLANRelay LocalLANRelay 1 8.1.617.0

Based on these results, BES Client should have chosen (hopcount 1):

LocalLANRelay

BES Client last chose: DMZEMEA

  • WARNING: BES Client has incorrectly chosen a BES Relay."

Okay, question is really simple, why is the client choosing an incorrect relay in the first place?!

2

(imported comment written by Paul K)

Hi,

I would recommend opening a PMR with Technical Support on this issue so that we can help try to debug this issue.

The following link is to the world wide Support directory. http://www.ibm.com/planetwide/region.html

Please be sure to have your IBM Customer Number ready when you call.

3

(imported comment written by AviE91)

Hey,

just want to update that the problem was that the TEM server was not available (we keep it blocked on FW schedule from remote relays BUT not from DMZ relays) and the relays were all underneath it in the hierarchy, so whenever a client wanted to register on the LAN relay it failed because the relay didn’t have open communication to forward the registration request to TEM server.

Registration is done only on TEM server, relays only forward the registration request up the chain to TEM Server.