nv-l
[Top] [All Lists]

RE: [nv-l] netmon.seed file

To: <nv-l@lists.us.ibm.com>
Subject: RE: [nv-l] netmon.seed file
From: "Barr, Scott" <Scott_Barr@csgsystems.com>
Date: Wed, 28 Jan 2004 15:47:39 -0600
Delivery-date: Wed, 28 Jan 2004 21:53:55 +0000
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com
Thread-index: AcPl5Y7Bu0pRJnVSTHumXt69xu1+WQAArf6A
Thread-topic: netmon.seed file
Have you tried pinging a router within one of those subnets while discovery is running?
-----Original Message-----
From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com]On Behalf Of Kevin Campbell
Sent: Wednesday, January 28, 2004 3:31 PM
To: nv-l@lists.us.ibm.com
Subject: [nv-l] netmon.seed file

I have tried a number of configurations but can not get it to discover devices the way I want them to. I have a number of subnets that I manage, lets say (10.60.180.*-10.60.190.* and 10.60.120.*-10.60.132.*). I would lick to have netmon auto discover anything on these subnets. The only way I can get the devices to show up is to add each device into the seed file. How can I get the devices to be auto discovered. I have tried what the config docs say making my netmon.seed file look this:

 

10.60.180-190.*

10.60.120-132.*

 

But the only thing that gets discovered is the Netview server and the default route. I have tried a number of others for example:

 

10.60.180.*

10.60.181.*

10.60.182.*

 

…and so on

 

But nothing other than specific IPs seem to be working

 

Any advice would be great

Thanks

KevinC

 

<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web