Hi Dojo,
In this staging environment I get the following BPA warning for SLNET connections,
yet the RTT value is expected, as this communication involves international WAN link:
is there a way to redefine the assigned thresholds of the BPA for this specific check?
Additional info: 57ms is actually pretty good in terms of WAN link performance for these 2 endpoints - custom NATS topology was implemented in the cluster - and the host with 57ms is a leaf node in terms of NATs config, while the other belongs to the "Core".
Thanks
EDIT: adding DM version info --> DataMiner (10.5.0.0-15943-CU4)
Hello Alberto,
In the current implementation of the “Check Cluster SLNet Connections” BPA, the maximum round-trip time is defined as a constant with a fixed value of 50 ms, and therefore cannot be changed.
We will evaluate whether this limit can be made configurable in a future version of the BPA.
Until then, I’m afraid you will need to ignore the warning message being generated.
Cheers,
Paulo
Hi Alberto,
Thanks for adding the feature request, you already have my vote 🙂
The 50ms is hardcoded as a constant inside the DLL which makes it very difficult to override. The only way would be to manipulate the binary dll directly, which we definitely shouldn’t do.
To give you a more precise idea, below is a snippet from the existing code:
const int MAX_ROUNDTRIP_TIME_MS = 50;
…
CheckPingReplies(agentResult, MAX_ROUNDTRIP_TIME_MS);
…
Thanks for your feedback Paulo – feature suggestion added:
https://community.dataminer.services/new-feature-suggestions/configure-or-increase-the-round-trip-time-in-check-cluster-slnet-connections-bpa/
Ad interim, is the rule available on the DMA to tweak that value to 80ms for example?
That would give us a better perception of unexpected delays in our environment.