Relay selection based on subnet

(imported topic written by Harald.Zarakowitis)

Hi,

we have problems with the automatic relay selection. We have our local and 15 remote locations. At one location more than 50% of all clients do not connect to the local relay, although the relay is in the same subnet. Different relays are chosen which are approximately 4-5 hops away.

This is way we want to implement relay selection based on subnet (at least for remote offices, which have small lines). Is there any convenient way to do such a thing? Can the Location Property Wizard help me with this?

Best regards,

Harald

(imported comment written by Aram_Eblighatian)

Harald,

There are anumber of things that can be done given the situation:

  1. If the clients are in fact on the same subnet as the relay, and the chosen relays are 4-5 hops away, then something strange is occurring, and we should diagnose and address the issue. I’d recommend opening up a support ticket as this is not the expected behavior.

  2. Outside of diagnosing the issue, there are several configuration settings that can typically be leveraged to prevent ‘local’ clients from selecting ‘remote’ relays. Below are several useful relay control settings given the scenario you describe:

_Enterprise Server_ClientRegister_MinHopEstimateLimit - the relay will reject clients that try to register with their conservative hop count estimate greater than this number.

_Enterprise Server_ClientRegister_MaxHopEstimateLimit - same as MinHopEstimateLimit, but based on the client’s liberal hop count estimate

_BESRelay_Selection_AutoSelectableRelay - A value of “0” makes the BES Relay unavailable for auto seletion after the next actionsite propagation. A value of “1” allows the BES Relay to be used by BES Clients for auto selection. This can be useful when a relay is in a sensitive network, and you want to completely control which clients connect to it.

_Enterprise Server_ClientRegister_MaxChildCount - Maximum number of clients the BES relay will allow to register. Once this limit is reached, connections will be rejected.

_Enterprise Server_ClientRegister_MaxChildRelayCount - Maximum allowed number of BES Clients that are BES Relays. This limit is calculated independently of the MaxChildCount – it can be used to keep a BES Relay from indirectly acquiring a lot of BES Clients by picking up too many children that are BES relays.

_BESRelay_Selection_RelayPriority - all relays of priority 0 are selected before all relays of priority 1, etc.

_BESRelay_Selection_RelayWeight - The likelihood of a relay being selected is equal to its weight divided by the cumulative weight of all the relays that are the

same distance

from the selecting client (NOTE: a relay with a weight of a million will still be selected after a relay with a weight of two, if the client thinks the latter relay is a hop closer).