Network Discovery is scanning wrong devices

I've found that there are certain devices on our network that when I run a Discovery, the Discovery scans a totally diferent device.

For example, I have a Switch with Polling IP address 10.40.3.2 (sysname swt01.agg.cba01)... and then I configure a Network Discovery with only this IP specified and then set the "up interfaces" to be automatically imported to the monitor... but when I run this Discovery, all of this device's "up" interfaces are imported on a totally diferent node, in this case it's a switch which name is "swt02.agg.mza01":

As these interfaces are not really part of this switch, there's no info in the Interface Details tab

I've found out that these two switches are Huawei Quidway S9303 and the system-mac of both of them are the same... could this be related to this issue?

There are several IP address configured on both switches, but they are not duplicated, so I don't know why the Discovery is importing interfaces of a specific device into another device.

Has anyone seen or have anyidea why this may be happening?

Pd: Sorry for my bad english. If there's something that I didn't explain well, please let me know.

Find more posts tagged with

stale

discovery results

interfaces

discovery duplicates

discovery troubleshooting

Accepted answers

All comments

marlief22

Hi there,

SolarWinds isn't doing anything revolutionary when it comes to discovering devices. You can manually run each step on the SolarWinds server to get more information about where the issue is.

First, SolarWinds pings the device using ICMP, to recreate this do the following in cmd.exe on the SolarWinds Server:

ping 10.40.3.2

Then it will do a reverse DNS lookup on the IP address:

nslookup 10.40.3.2

Then it will do an SNMP walk to the device:

https://support.solarwinds.com/SuccessCenter/s/article/Run-SolarWinds-SNMPWALK?language=en_US

I would bet that the issue is related to the DNS lookup section, and that the identical MACs are causing problems with the DNS zone. If that's the case then you will have to resolve that outside of SolarWinds.

Kind regards,

Marlie Fancourt | SolarWinds Pre-Sales Manager

Prosperon Networks | SolarWinds Partner since 2006

If this helps answer your question please mark my answer as confirmed to help other users, thank you!

hsh

Hi there! Thanks for your reply.

I don't think it's related to the DNS lookup because these devices are switches and doesn't have any DNS configured.

Is there a way to get a log of what process did the Discovery do?

Regards!

marlief22

Hi there,

if you are giving SolarWinds an IP address and it is returning a hostname then there is some sort of DNS resolution happening, even if it's not on the device.

You can like use the Log Adjuster to get debug logs for the Network Discovery job: https://support.solarwinds.com/SuccessCenter/s/article/Adjust-logging-levels-with-the-Orion-Log-Adjuster?language=en_US

The log file in question is going to be: "C:\ProgramData\SolarWinds\Discovery Engine\OrionDiscoveryJob.log"

Kind regards,

Marlie Fancourt | SolarWinds Pre-Sales Manager

Prosperon Networks | SolarWinds Partner since 2006

If this helps answer your question please mark my answer as confirmed to help other users, thank you!

hsh

I've tried adjusting the log, but I couldn't get the reason... for now, I'll be ignoring the affected nodes since there are only four of them and try again when I'm able to change the mac-address of these devices.

Thanks for your help!!