<?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[Get Status of node but disable alarms]]></title><description><![CDATA[<p dir="auto">Hi,<br />
I'm trying to get all devices of my network classfied (switches, servers, but also phones, tablets, laptops, etc..), and I'd like to separate in two main categories, or profiles: The "critical" ones, which I want to be notified for any change, and the only "observed", which I only want to keep track of ip, mac address, dns name, but don't need to be notified at all.</p>
<p dir="auto">The "crititcal" ones, have a fixed ip address, and the oberved have a dynamic ip assignment by dhcp. The dhcp is configured to keep dns name consistent.</p>
<p dir="auto">I'd like to get advice about how to accomplish this with netxms. What options do I have?</p>
<p dir="auto">If I'm not wrong, if I set a node in Unmanaged mode, it does not keep track of the ip changes, isn't it?</p>
<p dir="auto">I'll manually classifiy the nodes into containers, and the critical and oberved are the 2 main containers inside "Infrastructure Services".</p>
<p dir="auto">Thanks.</p>
]]></description><link>https://forum.netxms.org/topic/7317/get-status-of-node-but-disable-alarms</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 12:49:54 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/7317.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 01 Mar 2022 17:10:41 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Get Status of node but disable alarms on Wed, 02 Mar 2022 09:52:27 GMT]]></title><description><![CDATA[<p dir="auto">Thanks Victor,<br />
I've seen and applied new policies.<br />
Netxms can be difficult at first, but i'ts worth to give it a chance.!!</p>
]]></description><link>https://forum.netxms.org/post/31096</link><guid isPermaLink="true">https://forum.netxms.org/post/31096</guid><dc:creator><![CDATA[davidfs]]></dc:creator><pubDate>Wed, 02 Mar 2022 09:52:27 GMT</pubDate></item><item><title><![CDATA[Reply to Get Status of node but disable alarms on Wed, 02 Mar 2022 07:03:20 GMT]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">if nodes already classified into one of two containers, all you need to do is to change relevant rules in event processing policy to only trigger for nodes in "critical" container (just add that container as source filter in the rule).</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/31091</link><guid isPermaLink="true">https://forum.netxms.org/post/31091</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Wed, 02 Mar 2022 07:03:20 GMT</pubDate></item></channel></rss>