<?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[Nodes automatically change their primary hostname after upgrade to v3.7]]></title><description><![CDATA[<p dir="auto">Hello,<br />
we recently upgraded to v3.7, but noticed very wierd and unfortunately very destructive behavior.</p>
<p dir="auto">The nodes keep changing their primary hostname without human intervention. The new address is some of the addresses of the nodes, but that completely breaks our monitoring.</p>
<p dir="auto">Is that expected behaviour and how can we disable it? It is completely ruining our monitoring and other support processes.</p>
<p dir="auto">Obviously we have set "Prevent automatic SNMP configuration changes", but that does not help.</p>
<hr />
<p dir="auto"><img src="/assets/uploads/files/smf/0000000005443-changeip1.png" alt="changeip1.png" class="img-markdown  img-fluid" width="1166" height="727" /></p>
<p dir="auto"><img src="/assets/uploads/files/smf/0000000005444-changeip2.png" alt="changeip2.png" class="img-markdown  img-fluid" width="624" height="547" /></p>
<p dir="auto"><img src="/assets/uploads/files/smf/0000000005445-changeip3.png" alt="changeip3.png" class="img-markdown  img-fluid" width="622" height="657" /></p>
]]></description><link>https://forum.netxms.org/topic/6970/nodes-automatically-change-their-primary-hostname-after-upgrade-to-v3.7</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 16:07:09 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/6970.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 02 Mar 2021 15:49:13 GMT</pubDate><ttl>60</ttl></channel></rss>