Relay Affiliation selection issue

Usage and Config Platform
1

Hello guys,

Im attempting to setup relay affiliation in our environment as we are looking to take advantage of the DMZ stuff.

Ive followed the articles related to this on HCL website and from what I can tell it all looks ok to me but when I do a Relay Select command on my test device it always goes to the Failover relay. Ive tried a couple of endpoints and they all go to the failover instead of doing their SeekList. Or perhaps they are doing their seeklist but not finding the Relay group.

On my relay i have this setting

image
image704×76 23.7 KB

On my client I have this client setting

image
image1013×110 41.4 KB

Ive reboot and done everything to both relay and client that i know of. It still seems to go to the failover relay.

The log from the client when the relay select action starts.

At 21:53:30 -0400 - 
   Beginning Relay Select
At 21:53:36 -0400 - 
   RegisterOnce: Attempting secure registration with 'https://vma<failoverRelayNameHere>z01:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=11.0.1.104&Body=1077650005&SequenceNumber=9760&MinRelayVersion=7.1.1.0&CanHandleMVPings=1&MinHops=5&MaxHops=6&Root=http://root.rootservername.com%3a52311&AdapterInfo=a4-bb-6d-da-63-3c_10.200.21.0%2f24_10.200.21.91_0&AdapterIpv6=a4-bb-6d-da-63-3c%5efe80%3a%3a8299%3a7292%3ac44b%3ae020%2f64_0'
   Unrestricted mode
   Configuring listener without wake-on-lan
   Registered with url 'https://vma<FailOver>mz01:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=11.0.1.104&Body=1077650005&SequenceNumber=9760&MinRelayVersion=7.1.1.0&CanHandleMVPings=1&MinHops=5&MaxHops=6&Root=http://root.rootservername.com%3a52311&AdapterInfo=a4-bb-6d-da-63-3c_10.200.21.0%2f24_10.200.21.91_0&AdapterIpv6=a4-bb-6d-da-63-3c%5efe80%3a%3a8299%3a7292%3ac44b%3ae020%2f64_0'
   Registration Server version 11.0.1.104 , Relay version 11.0.1.104
   Relay does not require authentication.
   Client has an AuthenticationCertificate
   Relay selected: vm<FailOVerRelayNameHere>z01. at: 10.10.10.4:52311 on: IPV4 (Using setting IPV4ThenIPV6)
At 21:53:37 -0400 - 
   [ThreadTime:21:53:37] ShutdownListener
   [ThreadTime:21:53:37] SetupListener success: IPV4/6
At 22:15:19 -0400 - 
   Report posted successfully

The instructions seemed pretty straight forward. Where else could I troubleshoot this issue from?

If i let the clients select Automatically Before setting up the affiliation group the clients chose the closest relay correctly from hops. But after trying to set up the Affiliation group on a test group they all point to the failover relay.

2

Automatic Relay Selection (and with that also Affiliation) requires that the client is able to resolve and PING the Relays that are listed on the Relays.dat file.

Are you able to PING the Relays from the Client?

2 Likes
3

There are a number of things to check (such as DNS resolution and open connectivity), but one way to troubleshoot is to use the Client Diagnostics tool with the Relay Selection test. There’s a Task in BES Support that can help with this (ID 353 - TROUBLESHOOTING: Run BES Client Diagnostics):

image
image1049×704 62.2 KB

1 Like
4

Agreed! ICMP traffic is required for auto relay selection: Setting up internet relays

1 Like
5

Thats a good question, but yes they are able to ping the relay. Before i setup the Affiliation on the relay it was the same relay the client was talking to already from automatic selection. All I did was set the affiliation setting to the same relay it was already communicating with.

Actually…egg on my face. Maybe they cant… Now im even more confused. How did it have the relay with automatic from hops but i cant ping it. They are on a different subnet than I thought they where. My apologies. I will return with an update when i figure this out lol.

6

Awesome. Thank you, ill give this a try!