Ping Failing from collector to device and back?

On 12/12/2022 at 12:23 PM, mnagel said:

I would not hold my breath.  I pushed my CSM at the time on this issue back in 2018 and they refused to consider it a bug, but a feature request.  I also brought that up recently with my current CSM and I got crickets.  I dutifully followed through, but since the feature request "system" is nearly worthless, nothing has been done.  I cannot begin to enumerate the number of embarrassing conversations with clients that start like "Why is LogicMonitor alarming about SNMP being down or a host being down when we can get to those devices just fine?"  The workaround is time-intensive (manual collector restarts) and the repeated data loss is unforgivable.  I don't know what possessed the developers to generate a fixed SNMP session ID or ICMP ID once when the collector starts rather than at each new get/walk or ping.  It is the ultimate in false optimization and causes unending problems for any but the smallest simplest network.  LM should be ashamed of letting this continuing to happen.

I've pushed our CSM a good deal on infrequent SNMP failures, and I was able to hop on a Zoom call with their Devs and walk them through the exact behavior we were seeing (I keyed on this by virtue of alerts for SNMP host down, despite 'Poll Now' clearly showing a response), and I recently received some tacit confirmation that this 'bug' was, indeed, acknowledged. I wasn't aware of the exact cause of the problem, but was able to clearly demonstrate to them that this presents as a bug, clearly not a 'feature' request.

Obviously, no indication of timeline for fix, but this seemed like something that finally landed -- Hopefully this will lead to a fundamental fix. I'll be sure to highlight this thread to our CSM as well, in case that might help at all.