Hello all. We have been rolling out BES Clients (9.2) to our stores but are getting alot of “chattiness” from the clients that are excessive according to our Network department. We currently have deployed about 3000 clients but still have another 15,000 to go. Every store has a relay configured, that connects to two relays in the NOC (balanced), then two more top relays in our data center. They have been assigned in the correct relay path, but the bulk of the traffic is between the lowest relay and the relays at the NOC.
Does anyone have any suggestions on what we can do to reduce the chat?
You should increase the client minimum report interval to something like 90 seconds or more:
_BESClient_Report_MinimumInterval
You should increase the analysis report interval to something like 300 seconds or more:
_BESClient_Report_MinimumAnalysisInterval
I would suggest bumping up these numbers from the defaults slowly and measure the change.
You can also have the relays in the stores hold onto reports for longer, a larger size, and more in number so that they send the reports up the chain in larger batches. The defaults are pretty fast/small/chatty, which is fine when it isn’t going over a WAN.
Client polling is not the issue as @strawgate recommends because that should only effect traffic between the clients themselves and their direct parent relay. It should not cause much more traffic from the relay in the stores and the next level up relay in the NOC. It should mostly affect the traffic from the relay in the stores to the clients in the stores.
I’m not certain about the traffic from the client heartbeat that @strawgate mentions and how that is passed along from the relays, if at all. In either case, increasing the heartbeat to 45 minutes to an hour is not a bad idea, but I don’t think that will have nearly the impact that the minimum report interval would since that is something like 30 seconds by default, while the heartbeat is something like 20minutes by default.