What's Up .....
Here's the deal..... Having logging trigger set to "1" created a lot of unnecessary log entries and false downs when a device misses just a single poll. So to cut down on this I went through and changed everything to logging trigger "2" which is great, it really helps out with the logs, now they are nice a clean.
However, we still get Events generated when a single poll is missed, and we need to acknowledge these events, but since nothing was logged now we don't know what the problem was (i.e. was it missed icmp, or missed SNMP check, etc). I still want Events to be generated but only after 2 consecutive missed polls (to correlate with how we have logging set up). I don't see any way to change Event generation to "2".... am I missing something or is it not possible?
My suggestion to Ipswitch for future versions is to incorporate a fast poller engine to reduce the amount of false events/logs. i.e. when a node misses a poll put the node into a fast poll state so that it gets polled again, right away or before the next polling cycle, do this for a number of times before the next "official" poll and then if it misses that one too, then you can safely generate an event and log it. If the poll succeeds then great, chalk it up to just a dropped packet...
this would greatly reduce false down's generated by network congestion or just a simple missed packet.
Thanks,
Bruce
