<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Alarms based on Topology]]></title><description><![CDATA[<p dir="auto">Hello all,</p>
<p dir="auto">I am attempting to limit alarms for nodes based on topology so I only receive alerts for the first node down in a chain. Would someone be able to point me in the right direction for this?</p>
<p dir="auto">Thanks!</p>
]]></description><link>https://forum.netxms.org/topic/7681/alarms-based-on-topology</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 20:11:19 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/7681.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 22 May 2023 20:40:25 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Alarms based on Topology on Mon, 29 May 2023 11:46:35 GMT]]></title><description><![CDATA[<p dir="auto">Normally it should happen automatically for events SYS_NODE_DOWN if topology is known to the server. If server is able to determine route from itself to unreachable node, it will check all intermediate nodes, and generate SYS_NODE_DOWN only for router closest to the server, and SYS_NODE_UNREACHABLE for nodes down the line.<br />
For more complex logic you can use script filters - all kind of topology information is available in scripts, so you can filter events based on peer nodes, routing information, etc.</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/32483</link><guid isPermaLink="true">https://forum.netxms.org/post/32483</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Mon, 29 May 2023 11:46:35 GMT</pubDate></item></channel></rss>