From: Charles G. <Cha...@co...> - 2004-08-03 20:31:07
|
*** Authentication Certificate *** Edward, I have about the same size network as you do, about 1850 now, and I've found that checking your logs and watching for errors/timeouts and resolving those increases the time dramatically. I've read that 1900's are slow with netdisco, but fortunately, I have only a couple of these on the network. My arpnip takes 110 minutes, discover takes 615 minutes and macsuck takes 300 minutes as a comparison. Charles Goldsmith Sr. Network Engineer CompUSA Corporate Team 972.528.4926 Office 972.982.4086 Cell 972.839.4458 "FreeBSD: the best things in life are free." "Vopata, Edward" <vo...@ti...> To: <net...@li...> Sent by: cc: net...@li...ur Subject: [Netdisco] Parallel Polling ceforge.net 08/03/2004 03:13 PM Hi, I have a large network with about 1700 entries in the device table (using netdisco 0.93). It is taking about 9 hours to perform an arpnip (-a), 9 hours to perform a refresh (-R), and about 12 hours to perform a macsuck (-m). Is here something I can do to reduce these times? I was wondering if netdisco could be made to poll several devices in parallel. I would think that this would help with the arpnip, macsuck, and refresh/discover processes. Also, with so many devices, the network map is a virtual blob. Is there someway that the map could be made into layers or sections to make it more readable? ---------------- Edward Vopata Texas Instruments, Inc. ------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ Netdisco mailing list net...@li... https://lists.sourceforge.net/lists/listinfo/netdisco-users |