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

Node Discovery -Scheduled Discovery Results - Why doesn't it see that the node exists on another poller already?

So when you do network discovery and you have selected to use "Poller B" as your primary polling server for this discovery and you search a whole subnet only to find that a node exists but is being managed by "Poller A" already... This node shows up in the list and you can't import it because it is already being managed by another poller.

WHY wouldn't SolarWinds be smart enough to recognize that this node already exists in the database and shouldn't be listed as a new found node?

Please SolarWinds work on your node discovery options...

Find more posts tagged with

Status: None

Comments

rschroeder

I don't know the answer to your question, but I'll hazard a guess: SW pollers know about the managed IP address of a node. If one poller happens to be managing one IP address on a node that has two or more addresses, and you inadvertently Discover the network and happen to select one of the unmanaged addresses on a node to be managed by a different poller, it will do exactly that.

I leverage this feature to help me get around problems where a remote APE tells me a site's nodes are up, but the site can't get to my main data centers due to a WAN provider problem. I manage one or more of those nodes from my main data centers using a different IP address.

It's not ideal, and I've found a superior solution is to manage the router and access switches at that remote site via a local APE, but manage the Distribution Switch at that remote site via my main polling instance. That way I know if the main data center is available to the remote users, who may have local access to a remote data center but NO ACCESS to the main data centers.