<?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[netxms polling fails, no error/notification]]></title><description><![CDATA[<p dir="auto">Hi</p>
<p dir="auto">I'm having mixed feelings when using netxms as I have several times thought that everything was working , and when I view the data from one node it can be marked as red for whatever reason (one example is that the poll is not supported on that node, or the netxms agent is not functioning properly). I suspect that it might be a user error on my part, but has anyone else experienced this and know how to avoid it? I really need to know if a poll has failed. It should trigger a notification.</p>
]]></description><link>https://forum.netxms.org/topic/2836/netxms-polling-fails-no-error-notification</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 20:07:01 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/2836.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 07 Jan 2014 19:21:24 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to netxms polling fails, no error/notification on Fri, 10 Jan 2014 20:54:12 GMT]]></title><description><![CDATA[<p dir="auto">Hi Victor, and thanks for your answer.</p>
<p dir="auto">So one or more of these are not enabled in terms of showing a notification when something goes wrong?</p>
<p dir="auto">I have used netxms for a while and it performs as expected as long as the poll values don't go red and show error. I only discover that something's wrong when I actually view the values manually.</p>
<p dir="auto">Raymond</p>
<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/victor" aria-label="Profile: victor">@<bdi>victor</bdi></a> said in <a href="/post/12412">netxms polling fails, no error/notification</a>:</p>
<blockquote>
<p dir="auto">Hi!</p>
<p dir="auto">System will generate events in case anything goes wrong with the node - you can handle these events and create alarms, send notifications, etc. Most important events are following:</p>
<p dir="auto">SYS_NODE_DOWN - entire node is down (NetXMS server cannot communicate using any allowed means)<br />
SYS_NODE_UNREACHABLE - NetXMS server cannot communicate with the node because of intermediate router failure<br />
SYS_NODE_UNMANAGED - someone put node into unmanaged state<br />
SYS_NODE_UNKNOWN - status of the node is unknown<br />
SYS_IF_DOWN - network interface is down<br />
SYS_IF_UNKNOWN - status if network interface is unknown (usually because of disconnected agent)<br />
SYS_IF_DISABLED - network interface was disabled<br />
SYS_SERVICE_DOWN - network service is down<br />
SYS_SERVICE_UNKNOWN - network service state cannot be determined (usually because of agent failure)<br />
SYS_AGENT_UNREACHABLE - NetXMS agent is unreachable<br />
SYS_SNMP_UNREACHABLE - SNMP agent is unreachable<br />
SYS_DCI_UNSUPPORTED - DCI goes to "unsupported" state<br />
SYS_SCRIPT_ERROR - NXSL script execution error<br />
SYS_SMTP_FAILURE - server was unable to sent e-mail notification<br />
SYS_SMS_FAILURE - server was unable to sent SMS notification</p>
<p dir="auto">Best regards,<br />
Victor</p>
</blockquote>
]]></description><link>https://forum.netxms.org/post/12444</link><guid isPermaLink="true">https://forum.netxms.org/post/12444</guid><dc:creator><![CDATA[raypetter]]></dc:creator><pubDate>Fri, 10 Jan 2014 20:54:12 GMT</pubDate></item><item><title><![CDATA[Reply to netxms polling fails, no error/notification on Wed, 08 Jan 2014 07:05:39 GMT]]></title><description><![CDATA[<p dir="auto">Hi!</p>
<p dir="auto">System will generate events in case anything goes wrong with the node - you can handle these events and create alarms, send notifications, etc. Most important events are following:</p>
<p dir="auto">SYS_NODE_DOWN - entire node is down (NetXMS server cannot communicate using any allowed means)<br />
SYS_NODE_UNREACHABLE - NetXMS server cannot communicate with the node because of intermediate router failure<br />
SYS_NODE_UNMANAGED - someone put node into unmanaged state<br />
SYS_NODE_UNKNOWN - status of the node is unknown<br />
SYS_IF_DOWN - network interface is down<br />
SYS_IF_UNKNOWN - status if network interface is unknown (usually because of disconnected agent)<br />
SYS_IF_DISABLED - network interface was disabled<br />
SYS_SERVICE_DOWN - network service is down<br />
SYS_SERVICE_UNKNOWN - network service state cannot be determined (usually because of agent failure)<br />
SYS_AGENT_UNREACHABLE - NetXMS agent is unreachable<br />
SYS_SNMP_UNREACHABLE - SNMP agent is unreachable<br />
SYS_DCI_UNSUPPORTED - DCI goes to "unsupported" state<br />
SYS_SCRIPT_ERROR - NXSL script execution error<br />
SYS_SMTP_FAILURE - server was unable to sent e-mail notification<br />
SYS_SMS_FAILURE - server was unable to sent SMS notification</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/12412</link><guid isPermaLink="true">https://forum.netxms.org/post/12412</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Wed, 08 Jan 2014 07:05:39 GMT</pubDate></item></channel></rss>