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

Import Status: skipped, already monitored with different engine.

erik.boyer

Any ideas why I cannot re-discover nodes? They result in this error after going through the whole discovery phase.

Their assigned poller is the same server as what is doing the discovery. They are all the same poll method (SNMP).

Find more posts tagged with

Accepted answers

All comments

cvachovecj

I have moved your question to the NPM forum where you get an answer more likely.

In the meantime, could you perhaps add more background? Screenshots?

Thanks,

Jiri

mharvey

If the node is already in NPM then the import is going to skip over them as they already exist. If you are looking to update the information on the nodes via a discovery, a rediscovery is run on all monitored devices every 30 minutes by default. The node discovery is for adding new devices to be monitored, or new interfaces to existing devices, but the node itself will be skipped over should it exist.