Nodes drop their ip adresses and take another one automaticaly

[augusteDOUAMBA]

Hello, I need help.
[pre]Some of  my nodes changes IP address automatically. How can I avoid it?
[font=Verdana, Arial, Helvetica, sans-serif]i[/font]n the image I manually changed the node's IP address to match its real address but some time later it changes address.

need your help . thanks

[/pre]

---

[Filipp Sudanov]

1. On what exactly version of NetXMS this is happening? 
2. Whare are the capabilites of such node (visible on the Overview page)
3. Do you have network discovery enabled? Can you show screenshot of network discovery configuration?
4. Does NetXMS obtain mac addresses for these nodes (visible in Interfaces tab of node)
5. Do these machines have static IP or they get IP address via dhcp?
6. In configuration->Server configuration what are the values of the following parameters:

Objects.Nodes.ResolveDNSToIPOnStatusPoll
Objects.Nodes.ResolveDNSToIPOnStatusPoll.Interval
Objects.Nodes.ResolveNames
Objects.Nodes.SyncNamesWithDNS

[Filipp Sudanov]

One more question for clarification - in node properties -> Communication in Primary host name field you have IP address or hostname?

[augusteDOUAMBA]

1. On what exactly version of NetXMS this is happening?

5.0.4

2. Whare are the capabilites of such node (visible on the Overview page)

just SNMP

3. Do you have network discovery enabled? Can you show screenshot of network discovery configuration?

network Discovery is enabled!! Screenshot below

4. Does NetXMS obtain mac addresses for these nodes (visible in Interfaces tab of node)

not an interface of the node. in fact netxms does not detect the node interfaces because it uses the generic NET-SNMP driver which is not suitable. it's the address of another node in the network. I noticed this was happening after a duplicate Mac message appeared between nodes.

5. Do these machines have static IP or they get IP address via dhcp?
   static address but assigned by a DHCP server. this is the same address that it retrieves from the server each time it starts.
   definitively static.

6. In configuration->Server configuration what are the values of the following parameters:

Objects.Nodes.ResolveDNSToIPOnStatusPoll  : never
Objects.Nodes.ResolveDNSToIPOnStatusPoll.Interval :0
Objects.Nodes.ResolveNames : true
Objects.Nodes.SyncNamesWithDNS: false

7.One more question for clarification - in node properties -> Communication in Primary host name field you have IP address or hostname?
IP address

---

[Filipp Sudanov]

By NET-SNMP you mean that these devices are computers and net-snmp package is used to provide snmp daemon? Or netxms snmp driver is GENERIC?
Can you provide screenshot of Overwiew page for such device? What are these devices, what producer, what models?

[augusteDOUAMBA]

1. By NET-SNMP you mean that these devices are computers and net-snmp package is used to provide snmp daemon? Or netxms snmp driver is GENERIC?

snmp drivers is generic

2. Can you provide screenshot of Overwiew page for such device? What are these devices, what producer, what models?

Screenshot below

it's Telrad cpe7000 .
as you see in the screenshot, the snmp generic driver is used. but in reality the snmp object oid should be .1.3.6.1.4.1.17713.20.  I use this oid as root for the dci of this equipments
it is from the cambium family but its driver is not one of the cambium drivers supported by netxms as you see

---

[augusteDOUAMBA]

Hi,
I still haven't found a solution to my problem. I just need to turn my back for the addresses of my change nodes. which distorts the supervision on these nodes. I deactivated absolutely everything (snmp, modbus, ethip, configuration...) but nothing to do. I just do pings on nodes but the addresses change constantly.
a capture of the event log

---

[uldis]

Hi there

We have been checking google resources and it would seem there are cases when static IPs jump to DHCP, though the exact scenarious and DHCP setups are unclear. As a test, we would suggest to switch off DHCP on your affected node where static IP ( and not DHCP reservation ) is present and leaving it under observation for some days. 
Please let us know your feedback on the above.

[augusteDOUAMBA]

Thanks,
I can try that but I don't think that's the problem.
There is one thing I don't understand.
All these nodes are created manually on netxms with an ip address not with a name which could be subject to dns name resolution. So why does netxms change the node address itself?
Let's assume that the node switches to dhcp, normally on netxms the ip address should remain the same and the node becomes inaccessible as it has changed address.
On physical equipments the addresses remain the same. So I think it is netxms which is not found or which is lost in the assignment of interfaces to the different nodes at each configuration poll.

[pre]In fact, I see that the nodes exchange their interfaces (their addresses). These are therefore interfaces present in the netxms database.
Is there not a problem with interface indexing? I notice that these nodes have identical mac addresses.

[/pre]

[uldis]

Coming back to this issue, would you have any more feedback for us, please? Did you try disabling DHCP? We had a look at our test setup and found similar pattern of events as you posted on 11.09.24. We checked remote node in question and could see server reboot and link fluctuations, so the events were reflecting server NOK status. We dont see any pattern that would indicate any generic issues with the product. Please also try to check remote node messages file for timeframe in question.