Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Discovering a Device by Two IPs

Guys I am running into an issue and I am having a hard time believing nobody else has run into this (according to support). We are just starting to turn on auto discovery and I have one discovery profile setup with all our subnets that we use for loopbacks on routers, so I can easily discover all our routers (which I have already done and it worked great). However now I am trying to discover the LAN switches and devices at our sites, so I have setup another discovery profile for one site to test and added its LAN subnets. When that discovery finished it found the router there that was already discovered by the loopback profile but it sees it with the LAN IP address. So essentially I can have the same device in the DB twice (or more) with different IP addresses.

I want to discover the routers by there loopback because some of our sites have a backup vpn tunnel so there could be another ways to still get to it. If I am polling it via a LAN interface and that interface goes down it will mark the device as down completely. Talking to support they said they have not run into this before and I cant believe nobody else has run into this. I will have to submit for a feature request.

So from the sounds of it when a device is discovered it will poll it to see how many interfaces is has but it does not record or save the IPs of those interfaces with the main device (this is the way Openview NNM does it).

Has anyone else run into this or do I have something setup wrong? As a work around I am just clicking the ignore option for my routers when it is found on the LAN profile.

Thanks

Mike P

BTW I am running NPM 10.2.1

Find more posts tagged with

Accepted answers

mdriskell

First of all NO SW doesn't support multiple IPs on the same device. Many people have complained and it's on their radar but (I personally have been waiting since 2006 when I first installed).

There are multiple feature requests for it so feel free to add your comments there (and like to show support)

I did the same thing you mentioned to ignore the extra device IPs from future discoveries. It is a very frustrating to even have to do this but that's the case.

Number 3 on this thread.

http://thwack.solarwinds.com/message/161227#161227

All comments

mdriskell

First of all NO SW doesn't support multiple IPs on the same device. Many people have complained and it's on their radar but (I personally have been waiting since 2006 when I first installed).

There are multiple feature requests for it so feel free to add your comments there (and like to show support)

I did the same thing you mentioned to ignore the extra device IPs from future discoveries. It is a very frustrating to even have to do this but that's the case.

Number 3 on this thread.

http://thwack.solarwinds.com/message/161227#161227

mdriskell

Oh and whomever said from support that no one has ever ran into this should go to thwack and run a search for Multiple IPs on a node and see the dozens (if not hundreds) of posts complaining about this.

I'm often quick to promote solarwinds for many of my previous customers but this "limitation" has haunted me for years. That being said I still choose it over anything else.

Michael_P

Yeah I did a bunch of searching on here after I posted above. I could not believe that nobody had ever seen this issue and I had to vent by asking. I swear sometimes I think we are the only people doing stuff like this, I hear that a lot from other vendors. I should have searched first. LOL

So your work around is to ignore the dups? I am looking for an automate way to do it, I see a table called discoverednodes. I hate having to do stuff like this manually.

I will definitely post on the other thread, this has to be added.

mdriskell

What I did was to create a discovery using a list of all of my ancillary IP addresses. I let it discover all of them...then I added them to the ignore list. Bad news is you have to have a listing of all IPs on your routers in order to do so but if you have it handy try that.

Network_Guru

+1 on prioritizing the fix for this multiple IP discovery issue.

I've seen this issue for years on our DR's with 300 Vlan interfaces, but never reported it, since it seemed like such a major bug, that I assumed many others had already reported this issue, and SW would see the value in resolving this ASAP.

The auto-discovery tool is just OK for one time, initial discovery of devices, but running this discovery on a schedule is not saving any time over a manual discovery process.

-=Cheers=-

chris.lapoint

Thanks Mike for closing the loop with the workaround. As you noted, this is a known issue and at the top of our list to fix as described in our what we're working on post.

Michael_P

Mike that might work for us. We do have a CMDB that has all our IP addresses added. So I can easily add those to a 'ignore' discovery profile and then when they are discovered just ignore them all.....

This definitely needs to get fixed, otherwise in my mind auto-discovery is totally useless.

thamizh85

Perhaps, you could use SQL to identify all the duplicate nodes and manually delete them. See this post:

FormerMember

I am starting to think that this is an issue of they cant/dont want to fix this enough to compete with IPAM which is the product they want you to buy sepatatly to get all these nice bells and whisles.