<?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[Bug: Port number reverting to default/161 after failed poll attempt]]></title><description><![CDATA[<p dir="auto">This is a big problem for us at the moment. I've noticed a bunch of devices that I setup for monitoring have changed from port i've manually set (1616) to the default (161) and this changes the device that NetXMS actually monitors</p>
<p dir="auto">The setup is there's a bunch of small MikroTik routers and DSLAM's behind those routers. The routers have a forwarding rule, anything UDP 1616 forward to the DSLAM on port 161<br />
Both the router and DSLAM therefore share an IP address, but both can be polled via SNMP on different port numbers. The default of 161 for the Router, and 1616 for the DSLAM</p>
<p dir="auto">This works fine initially but it seems that if a device stops responding for whatever reason, then NetXMS tries the default port number of 161, this then succeeds and it uses that information, screwing up the monitoring as now its polling the router, not the DSLAM</p>
]]></description><link>https://forum.netxms.org/topic/6198/bug-port-number-reverting-to-default-161-after-failed-poll-attempt</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 21:05:29 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/6198.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 30 Sep 2019 01:16:56 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Bug: Port number reverting to default/161 after failed poll attempt on Mon, 14 Oct 2019 10:17:43 GMT]]></title><description><![CDATA[<p dir="auto">We've created a feature request for this, you can follow the progress here: <a href="https://track.radensolutions.com/issue/NX-1699" rel="nofollow ugc">https://track.radensolutions.com/issue/NX-1699</a></p>
]]></description><link>https://forum.netxms.org/post/26730</link><guid isPermaLink="true">https://forum.netxms.org/post/26730</guid><dc:creator><![CDATA[Filipp Sudanov]]></dc:creator><pubDate>Mon, 14 Oct 2019 10:17:43 GMT</pubDate></item><item><title><![CDATA[Reply to Bug: Port number reverting to default/161 after failed poll attempt on Thu, 10 Oct 2019 06:18:16 GMT]]></title><description><![CDATA[<p dir="auto">3.0<br />
I saw this checkbox, but is there a way to make this the default behavior? I'm happy to have that checkbox ticked for everything in NetXMS<br />
Problem is when i'm going through adding 20 DSLAM's, if 1 of them doesn't add successfully the first time I won't be able to go in and change that option before it reverts to the default port number anyway<br />
Plus adding devices then having to go in and make fiddly manual changes afterwards is always a pain</p>
]]></description><link>https://forum.netxms.org/post/26715</link><guid isPermaLink="true">https://forum.netxms.org/post/26715</guid><dc:creator><![CDATA[Millenium7]]></dc:creator><pubDate>Thu, 10 Oct 2019 06:18:16 GMT</pubDate></item><item><title><![CDATA[Reply to Bug: Port number reverting to default/161 after failed poll attempt on Mon, 30 Sep 2019 09:22:39 GMT]]></title><description><![CDATA[<p dir="auto">What NetXMS version are you using?<br />
In 3.0 there is <em>Prevent automatic SNMP configuration changes</em> checkbox in SNMP communication properties that should prevent NetXMS from trying the default port.</p>
]]></description><link>https://forum.netxms.org/post/26646</link><guid isPermaLink="true">https://forum.netxms.org/post/26646</guid><dc:creator><![CDATA[Filipp Sudanov]]></dc:creator><pubDate>Mon, 30 Sep 2019 09:22:39 GMT</pubDate></item></channel></rss>