Network Discovery Problem NPM v10

Question

I am currently trialing NPM v10 and I am having problems completing a full network discovery of my switches/routers. When I include all the various subnets I want to run the discovery on although it starts it eventually is coming back with

'Discovery has been interrupted by timeout, results of discovery are not complete'

I thought there was an issue with aparticular subnet as it was the last one that was displayed so I removed this and tested it on its own and it worked fine as did the full discovery without it but I have added another subnet to the full discovery and it again fails.

Is there a log file anywhere that could perhaps give me more specific failure details, are there limitations to the number of subnets a discovery can be run on.

Any ideas as this obviously has a knock on affect on the Connect Now feature.

kreases · Answer

Sorry we never did get a resolve for this issue, at the time we were just testing NPM v10. On our live system we just don't use the auto discovery option at all because it tends to bring up device IP addresses we just don't need to monitor so it just generates work removing these.

mgibson · Answer

Yep ther must be a limitation, I have a large network and have 13 segments (on one particular scan) I am trying to discover some of which are a /22. Seems to get this error about the same place.

Were you able to find a root cause/solution?

MarieB · Answer

Hey kreases--

Go ahead and open a support ticket here.
http://www.solarwinds.com/support/ticket
Click Submit a Technical Support Ticket.
In order to receive technical support, you will need to be current on your SolarWinds maintenance. Complete the form. You will not be able to upload your diagnostics, but you will receive an email back that allows you to upload diagnostics.

M