When an element fails to respond for longer than the number of seconds specified in the setting “The element goes into timeout state when it is not responding for (sec)” the DMA will put the element in a timeout state. The specified number must be between 0 and 120.
We have a DataMiner agent where some elements sporadically breach the max limit of 120 and go into a timeout state. Our users have asked us if its possible to increase this limit beyond 120, and if we cannot, what is the reasoning behind the 120 second cap?
The limit was initially lower, but has been raised to 120 seconds with RN2716 in DataMiner version 6.5.4. This was done back then because there were devices that had a delay of 90 seconds and to be able to meet this situation, the value has been raised with a margin to 120 seconds.
Hi Jeremiah,
I’m not aware of a reason why the limit is 120 seconds for this setting but I wonder why a maximum of 120 seconds is not sufficient. If your user wants to ignore such communication issue, would it be not a solution to just disable the option?
Hi Jeremiah,
Feel free to vote on the feature request via Dojo
https://community.dataminer.services/new-feature-suggestions/maximum-element-timeout-increase/