Hi All,
Is there any setting that I can configure on the BigFix Relay so that, if the Relay goes down, the clients do not register with another Relay or directly with the BigFix Server?
Currently, when the Relay goes down, the clients appear offline/inactive and remain that way until the original Relay comes back online and the clients can register with it again.
I have configured the same relay as both the primary and secondary relays on each client, and I have also configured it as the manual relay.
Could you please advise if there is any setting that can be configured on the Relay or the clients to achieve this behavior?
BR,
Mohamed
Hi Mohamed,
The behavior you are trying to achieve preventing clients from failing over to another relay or the Root Server is entirely controlled by Client settings, rather than Relay settings. When a Relay goes down, it cannot dictate client behavior, so the configuration must be enforced on the endpoints themselves.
Configuring relayserver1 and relayserver2 with same relay will have negative impact.
In case you do not have relayserver2 for that location, it's best to leave it blank than using same relayserver1 details
Also you may want to look for _BESClient_RelaySelect_FailoverRelay settings
Yes I agree with you all setting must done on client side and that what I done.
But what impact that may happen if for configureing primary and secondary relay with the same value, did you face issue before with?
In that case, I would suggest your first action should be to configure _BESClient_RelaySelect_ResistFailureIntervalSeconds to the maximum allowed value. This will make the client tolerate communication failure with its current Relay for longer before attempting Relay selection.
If that is still not sufficient, you could consider building a custom task to configure the local firewall and restrict outbound BigFix communication on port 52311 to only the Relay you want the client to communicate with. This would need to be designed and tested carefully.
If you need a more foolproof restriction, I would enforce it at the network/firewall level rather than relying solely on endpoint firewall rules.
However, I personally would not recommend permanently restricting clients to a single Relay. If that Relay becomes unavailable for an extended period, those clients could effectively become isolated from the BigFix infrastructure. At a larger scale, recovery could become difficult, and you may eventually need manual intervention to bring some of those clients back online.
So I would first try increasing the ResistFailure interval, while still keeping a controlled failover path available.
4 Likes