<?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[Troubleshooting Unexpected Node Statuses - A Tool]]></title><description><![CDATA[<p dir="auto">I find that we always seem to be spend so much time trying to trying troubleshooting strange Status Calculation problems with nodes, trying to find the cause of incorrect statuses.<br />
A nodes status can be influenced by children (interface etc.) and how they're setup to calculate and propagate status, status polling, Overridden Status DCI etc.</p>
<p dir="auto">We really need an additional Tool in NetXMS Console which you can select a node and it gives us a tree/list of the things taken into account, and the result of each item, when calculating the status of a node to try to determine root causes of unexpected statuses.</p>
]]></description><link>https://forum.netxms.org/topic/6701/troubleshooting-unexpected-node-statuses-a-tool</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 12:28:26 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/6701.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 30 Sep 2020 05:26:04 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Troubleshooting Unexpected Node Statuses - A Tool on Wed, 30 Sep 2020 17:59:41 GMT]]></title><description><![CDATA[<p dir="auto">Actually sounds as really good idea. Registered it in our tracker: <a href="https://track.radensolutions.com/issue/NX-1961" rel="nofollow ugc">https://track.radensolutions.com/issue/NX-1961</a></p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/28637</link><guid isPermaLink="true">https://forum.netxms.org/post/28637</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Wed, 30 Sep 2020 17:59:41 GMT</pubDate></item></channel></rss>