<![CDATA[Too many alerts]]>Greetings,

Just upgraded to v1.2.3.1 - so far, so good! My question: When the gateway router goes down for any given subnet on our WAN, I receive "node down" alerts for each device within that subnet (servers, printers, etc.).  Of course, those nodes are not really down, just temporarily unreachable. In this situation, all I really need (and want) to know is that the gateway router is down, and that is all.  And then of course, a second alert when the router comes back up.

What is the easiest way to accomplish this?

Thanks,

-Kevin

]]>https://forum.netxms.org/topic/1978/too-many-alertsRSS for NodeFri, 13 Nov 2026 14:42:21 GMTFri, 12 Oct 2012 15:46:02 GMT60<![CDATA[Reply to Too many alerts on Mon, 12 Nov 2012 19:53:02 GMT]]>OK great, thanks Victor!

I am now monitoring 50 remote networks, and so far I am happy with NetXMS (and I have yet to upgrade to the latest 1.2.4 version)!

-Kevin

]]>https://forum.netxms.org/post/8928https://forum.netxms.org/post/8928Mon, 12 Nov 2012 19:53:02 GMT<![CDATA[Reply to Too many alerts on Mon, 12 Nov 2012 09:57:27 GMT]]>Hi!

I've created an issue in the bug tracker: https://www.radensolutions.com/chiliproject/issues/180.

Best regards,
Victor

]]>https://forum.netxms.org/post/8921https://forum.netxms.org/post/8921Mon, 12 Nov 2012 09:57:27 GMT<![CDATA[Reply to Too many alerts on Wed, 07 Nov 2012 21:13:52 GMT]]>Hi Victor,

Has this issue been fixed with v1.2.4?  If not, could you provide me with the bug #, so I can track it.

Thanks!

-Kevin

]]>https://forum.netxms.org/post/8879https://forum.netxms.org/post/8879Wed, 07 Nov 2012 21:13:52 GMT<![CDATA[Reply to Too many alerts on Mon, 29 Oct 2012 21:36:01 GMT]]>Hi!

Yes, it is known bug.

Best regards,
Victor

]]>https://forum.netxms.org/post/8816https://forum.netxms.org/post/8816Mon, 29 Oct 2012 21:36:01 GMT<![CDATA[Reply to Too many alerts on Mon, 29 Oct 2012 18:23:19 GMT]]>Hi Victor,

I spoke with our network provider; they do not believe that the remote router being "hidden" from a traceroute would have any impact on the NetXMS server knowing the route to the remote devices.

You mentioned that it it often does not work as expected - is this a known bug?

-Kevin

]]>https://forum.netxms.org/post/8812https://forum.netxms.org/post/8812Mon, 29 Oct 2012 18:23:19 GMT<![CDATA[Reply to Too many alerts on Wed, 24 Oct 2012 19:34:31 GMT]]>Greetings,

I believe I see the problem: Our NetXMS server does not see the remote router on our MPLS network when doing a traceroute to a node behind that remote router.  I will inquire with our network provider about this, as I would much rather have the server do this, rather than having to configure a situation for each remote subnet.

-Kevin

]]>https://forum.netxms.org/post/8783https://forum.netxms.org/post/8783Wed, 24 Oct 2012 19:34:31 GMT<![CDATA[Reply to Too many alerts on Sun, 14 Oct 2012 02:54:58 GMT]]>Theoretically, server should do that automatically if it knows route from itself to nodes behind router. However, it often not working as expected. You can also do manual correlation using situations.

Best regards,
Victor

]]>https://forum.netxms.org/post/8744https://forum.netxms.org/post/8744Sun, 14 Oct 2012 02:54:58 GMT