I have a few questions for all of you that have done this before, but especially for Doug Schulze and Aleck Lin.
1. According to the wiki, network discovery will scan the MID server's gateway router for its routing table and then use that table to identify other routers. After that, the process repeats across the network until all network devices and networks have been identified. The network discovery will not scan every IP address across the network to identify network devices. Is this correct?
2. I was asked if there was a way to throttle the network discovery to limit the bandwidth needs. I haven't found a way, except to limit the number of threads the MID server can use. Is there another way? Is it even necessary to throttle the network discovery?
3. My network team is concerned about taking down remote sites with network discovery and normal discovery scans due to the remote sites having limited bandwidth. We have multiple MID servers located around the country in areas that reduce the distance between the server and that scan's target device. The team has read both of the following articles and still has concerns. We're planning a test scan of a network device at a remote site to evaluate the bandwidth usage. Do you have any other ideas or information that will help put their concerns to rest?
http://wiki.servicenow.com/index.php?title=Deploying_Multiple_MID_Servers#gsc.tab=0
http://wiki.servicenow.com/index.php?title=Discovery_Resource_Utilization#gsc.tab=0
John Edwards
Kansas City Southern
