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 help?

Hi guys,

I'm in the process of a network discovery for our entire network which contains a lot of IP address ranges.

Due to the size of the network we have used a lot of ranges but unsure of what exactly from the 10. network so I would like to do a network sonar of the whole 10 range. Obviously this will take a long time, and I have used the core router as the seed. As this has so many subnets attached to it the network discovery scan take a very long time and the discovery times out due to the 300minute restriction.

Does anybody have any advice on how we can perform the scan faster as currently it only scans from 10.1.0.0 to 10.9.0.0 in the allotted time, i know for definite that we have networks up to the 10.31 range.

We also have smaller subnets using 172.16 to 172.32, and wireless devices using the 192.168 ranges.

Any help would be welcome on processes previous user have used.

Thanks,

Ian

Find more posts tagged with

network_discovery

network_sonar

Accepted answers

All comments

unityictcomms

We've had some success entering the addresses of just two core nodes as the IP address "range" and not using seeds.

If you've a fast M.A. Network, try turning all the default discovery options down to minimum too.

FormerMember

Another possible solution would be to create multiple scheduled discovery jobs that can run at different times. Each job limited to only a few subnets each. The initial setup I am sure would be time consuming, but with the multiple jobs you can kick off each "area" at different times to also not tax the network resources too much. I would set HOPs to 0(zero) as well otherwise you might start finding those subnets that you have never seen before that are configured on the switches. These might be the generic 192.168 networks that are defaults sometimes.

Just a suggestion on how it might be easier to manage a few jobs then taxing the network too hard with SNMP retrying and requests all at once.

I have had the same issue in that I discover all the devices on a fairly small network, but looking at all the interfaces takes a long long time. These are fully populated 6509 and 6513 switches that have 48port ether cards in most of the slots. My discovery will hang/time out eventually trying to read "STRAY PORTS" have to almost limit my jobs to a single device. My Discovery time out is 400 minutes