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

Does it often take that long to run an auto discovery??

I have been testing the auto discover feature as we have lots of ad hoc drives that no one tells me about. So I thought that it would be best to run a domain wide scan of any drive/node changes every night.

We have about 1,000 nodes and the plan was to stop overloading, I was going to do one domain at a time. Which is fine, but when I ran a singular scan on one node, which was added via the IP address, it took about 15 minutes to find a small 5gb drive I added this morning. I ran it twice to see if it was me, but no. The results were the same: about 15 minutes for one node. If want to run this on 1,000 modes I'm looking at bloody days doing this.

I ran the discovery and thought that it might be maybe a resource issue, but during this time, the CPU only reached 50% and the RAM only about 30% (my server has 20gb and it was using only 6gb at that time)

The only thing I could put it down to is:

- Checking all of the credentials: this might be a factor. So I have removed everything other than SNMP credentials

- maybe (because I was polling for VM ware and checking for agents on nodes.) it could have been that.

- Maybe China??!

Update - I ran it the third time on the same node and then on another, random node and it seemed to be running fine on those two separate occasions.

Find more posts tagged with

Accepted answers

All comments

shaun_9999

It takes about a minute to do now. So I'm not sure. I suppose I just need to chuck it on a domain and see what happens.

mesverrum

I've always felt like there was some overhead and concurrency going on where the time it takes to discover is not directly linear to the number of nodes, as in 10 nodes might take 5 minutes, but 100 nodes does not take anywhere near 50 minutes, more like 15. I haven't thrown wireshark on there to verify but it would seem that it tests multiple addresses and protocols at the same time, I know in NCM it connects to 10 devices at a time for example. Removing credentials and protocols that I don't expect to use does speed it up since it doesnt have to try them all and fail over and over before moving on.

gfsutherland

I have something around 250 or so nodes.... 15-20 minutes...

shaun_9999

Even thinking about it, I still cant understand why it did it. Slowly building an auto discovery up (so removing some nodes, adding WMI credentials, adding more nodes, etc.) It still runs in about a minute.

Now, the other thing: I was looking at how I can include to add nodes and do a scan for new volumes n one large, lazy scan. As lets be honest: adding nodes is just too much effort. Let the application do that while you put your feet up and watch knight rider.

Below is a shot of a standard VM that we have. As you can seem there are a lot of random network devices. I can guessing from either a windows related thing, or from the hosting environment, or other. You'd think that I could make a standard and just use the Local area connection 2 and then off I go. But no, some are called 'virtual NIC' others are VMware3 : xxx. All sorts of random rubbish.

I'm wanting to be so lazy that I don't even want to add or remove devices/volumes. So does anyone have a good idea on how would I accomplish this?

bobmarley

You would probably be better off breaking down your discoveries down into smaller chunks rather than doing a domain wide single discovery.

Mine seem to run concurrently when done in that fashion. Also If you make them too large they might not complete at all.

shaun_9999

"I was going to do one domain at a time"

That is what I am going to do. I don't want to do eight domains in one discovery. Eg

- Domain 1 at 10pm

- Domain 2 at 11pm

- Domain 3 at 12am

- ...

Until I have no more domains to scan. Even though we don't have that many nodes, we have about 20,000 users over eight domains. So yeah, I am not going to do them in one job.