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

Network Discovery cannot start on the Main Poller

All of a sudden, I am getting the error, "unable to start discovery", but I find it only happens when I use the main poller in the profile. Also, I notice that the SNMP tab is suddenly completely empty.

Any thoughts on what might be happening? Could it be the load on the main poller? The overall polling rate is currently at 75% with 11955 elements assigned.

Find more posts tagged with

Accepted answers

All comments

bobmarley

If you have additional polling engines perhaps try balancing the nodes onto the APE's. As a general rule I try to keep nodes off of the main poller to free up resources. It also serves as a 'parking lot' for nodes that were recently added or ones I am working on until they are move out to the APE's. In my instances the polling rate is generally 98 percent or higher.

marcrobinson

I agree with @bobmarley. Your polling rate should be above 75% typically. I tend to use the main polling engine just for discovery and to park nodes for later migration also. The main poller is responsible for a lot of the solarwinds platform duties - ie alerts etc. Keeping it happy is honestly a good thing. If you have capacity on your additional polling engines, then I would recommend spreading out that load. Beyond that, the snmp tab should not become suddenly empty. Check to see if maintenance is running and run and active diagnostic and see if anything comes up ugly in the recommendations. I have a feeling you may want to talk to support, but start with the above recommendations first.

bobmarley

I have had 'unable to start discovery' many times before. Never on an existing discovery that had worked in the past but on new ones that were being set up. The only pattern I noticed so far was it happens more often if I change the default timeout values for SNMP, WMI etc to make the discovery go faster. Using the defaults seemed to work after rebuilding the discovery a second time.