What would cause node names to randomly change from a friendly (and sometimes manually set) name to the polling IP? Happens across 3 separate NPM environments. Persists through multiple versions of the product. Only happens to Windows nodes.
How are you polling the nodes ? (snmp/wmi)
Could be there is no hostname that is visable via SNMP and DNS no longer has an entry for that IP.
They're monitored via WMI. I'm working a ticket now, but waiting for the issue to happen again to provide logs. DNS still resolves the IP to a name in the cases I've tested.
Where is this info being populated - System Info Area ?
Confirmed bug since NPM 10.7. Ticket#747415. No update regarding if and when it will be addressed.
what about reverse lookup by IP ?
If it can't resolve the IP to a host name it tends to use the IP address.
This is not an uncommon problem for NMS tools.
I don't have any issue performing an nslookup for any of the affected IPs. It would be nice to have an option to freeze fields.
The issue is now more concerning than just names randomly changing to IPs. Sometimes I have to manually rename nodes multiple times before the change sticks. Sometimes the name change never sticks and I give up. Sometimes renaming node A actually renames node X (this is my favorite). Fun times, especially when the vast majority of your alert rules are based upon server names.
I am hitting this same issue in 11.5. Can anyone confirm whether this is still an open issue?
We are on NPM 11.5.2 and this is still an issue for us as well. It only does this it seems on Windows nodes (being polled with WMI). They are all SQL Servers, and have AppInsight for SQL added to their resource polling via SAM 6.2.1. Came in this morning and it had changed three database servers from their proper names to their IPs overnight.
We are in NPM 11.0.1, SAM 6.1.1 and are seeing this also.
Only started seeing this issue recently when we switched Windows servers from SNMP polling to WMI polling (and added AppInsight for SQL to same servers).
Current Windows server that it occurred for - I checked the Windows logs for anything at the time that SolarWinds "decided" to change the Node Name but came up blank.
I do see event msgs in SW for the some of the AppInsight components going into an "unknown" state a couple of minutes prior.
This all occurred at 2.02am - possibly DB backups or something occurring that is triggering - no idea really.
Annoying and problematical - have users looking for Nodes in SW and complaining they cannot find what was previously there (yes - they can find by IP Address but users do not think like that).
I'm running into the same issue with Windows boxes. I'm running SAM 6.2.1 and NPM 11.5.2 . I do have a few that are doing this that are being monitored through SNMP. I'm still researching and trouble shooting them, but it seems like it is newly added servers atm. I'm currently suspecting it is when some of the other techs are adding them through the Virtualization Discovery. I add them manually in settings and add a node. The ones I have added don't seem to do the name change. There could be no link, but it is really hard to pin point what the ones doing it have in common.
Also to add, there seems to be no rhyme or reason to it swapping between what we set in Orion to the DNS name, or the System name.
We can't be the only folks seeing this issue. Anyone had further communication with support about it?
Are they being added by hostname or ip address ?
If they are being added by ip address I would suspect DNS reverse lookup may be wonky.
As stated above, there was no rhyme or reason to the name changes. It didn't matter if it was Windows, Linux, VM, Physical, WMI or SNMP monitoring. I had another issue happen, contacted tech support and they re-installed the services on my Orion box. As an unintended result this also fixed servers changing names.
Unfortunately this didn't allow me to continue troubleshooting the issue to figure out the cause, but this did fix it.
This issue was addressed in a hotfix for 11.5.2 - if you're still experiencing this, I suggest installing the latest hotfix for Orion Platform (currently v6).
I will have to look it up and see what was causing it. Upgraded to NPM 11.5.2 and SAM 6.2.1 in August and I think hotfix 4. I was worried I fubar'd something.
I have SAM 6.2.2 and NPM 11.5.2 and have never seen this issue in any previous versions or the current with the latest hotfix. (and the Windows team does a terrible job of keeping DNS up to date.) Running on Windows Server 2012 R2 with a 2012 SQL DB. Odd this problem isn't universal.
This is still an issue in 12.0.1 for Windows WMI hosts.
I now see it happening on my systems.
