|
Re: [nv-l] Netmon on NT
2003-12-05 01:42:32
I have found that some devices just don't make any noise on the network that would get them discovered. For instance we used to see this with hubs all the time. You just about had to ping them, or put them in the seedfile and let netmon ping them, or use the ping spray to get them discovered. But if they are in the arp cache of a device in the seedfile, and if your ranges don't exclude them, then you should not have to enter them in the seedfile.
Remember that once things are discovered, you don't need to leave them in the seedfile. I will often use big chunks of seedfile to get things discovered, and then take them out leaving only the rules. Save the big seedfiles for rediscovery purposes just in case. At certain release levels I saw netmon startup delays with really big seedfiles, so I just don't use them beyond the initial discovery.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
|
| "Christopher J Petrina" <cjp8 AT meadwestvaco DOT com>
Sent by: owner-nv-l AT lists.us.ibm DOT com
12/04/2003 09:34 AM
Please respond to nv-l
|
To: nv-l AT lists.us.ibm DOT com
cc:
Subject: Re: [nv-l] Netmon on NT
|
I figured that ping spray was used only during discovery. We do have some very distant offices with response times in the 500 - 2000ms response range. The seed file is fully populated, however that has always been a issue I think. It was my understanding that the seed file should not have to contain every device yoiu want discovered, but rather some of the more core deivces that have access to the entire network. LAN and WAN both. Provided I chose like a major Core Switch or Router and place those int he seedfile that Is hould not have to enter every subnet into the seedfile. Unless of course I want to limit discovery or exclude some particular devices.
I do beleive that the answer to discovery you have given me better helps me to understand. THANK YOU
|
|
|
