<![CDATA[Missed pooling]]>I apologize if I missed this somewhere, but is there an easy way to get NetXMS to wait until two missed pooling cycles pass before considering a node "down".  I have one location that has squirly internet and I get about 30 notifications a day.  I just want to know if the event lasts more than one pass.  This would be the built-in up/down status.  Not on a specific service or rule I have built.  As far as I can tell, it looks like I would need to disable the pooling and look for my own data.

]]>https://forum.netxms.org/topic/2098/missed-poolingRSS for NodeFri, 13 Nov 2026 12:15:38 GMTThu, 03 Jan 2013 02:06:22 GMT60<![CDATA[Reply to Missed pooling on Wed, 30 Jan 2013 05:19:38 GMT]]>Thanks Victor... I looked everywhere... so I thought.  Sorry for the delayed reply... forgot I posted this to be perfectly honest.

]]>https://forum.netxms.org/post/9467https://forum.netxms.org/post/9467Wed, 30 Jan 2013 05:19:38 GMT<![CDATA[Reply to Missed pooling on Thu, 03 Jan 2013 10:20:28 GMT]]>Hi!

You can set number of polls required to change status of node's interface(s) (in interface object's properties on "Polling" page). Server will consider interface down only if it is not responding for n polls, and therefore entire node will be considered down only after n polls.

Best regards,
Victor

]]>https://forum.netxms.org/post/9235https://forum.netxms.org/post/9235Thu, 03 Jan 2013 10:20:28 GMT