9 years ago
Custom Ping Intervals
Currently, LM has hard-coded the Ping dataSource to use 250ms ICMP Ping intervals. We need the flexibility to adjust the Ping interval (ms) in the DataSource (Either static or system property valu...
On 2/28/2016 at 1:02 PM, Jessie Bryan said:Currently, LM has hard-coded the Ping dataSource to use 250ms ICMP Ping intervals. We need the flexibility to adjust the Ping interval (ms) in the DataSource (Either static or system property value).
Background:
We've seen at least one company "Mimosa" that has changed it's newest firmware to block ICMP messages if they are sent "too quickly". For Mimosa wireless gear, this is represented in LM as an 80% packetloss (2 pings permitted, 8 are then rejected). Mimosa does not want their hardware resources depleted by multiple, quick, Ping requests. The workaround currently is to alter the thresholds in LM to compensate for an 80% packetloss reading. By having the ability to adjust Ping Interval for these hosts in LM, we can have better visibility into network issues.
We actually ran into this exact problem to. Dell's iDRAC will drop packets after 4 pings in 1 second or less. We fixed the issue by dropping the ping count down, but it not ideal. I agree, and had requested in an email (prior to this community) to have an option to adjust the latency.