Also, you will probably have to clear your DB and rediscover. I have noticed once in a while that after initial discovery has taken place with limited discovery (like a seed file with ranges in them), simply updating the seed file may not always kick-start the discovery engine to pick up a new subnet.

Regards,

Michael Webb, IBM Tivoli
Q1CA Distributed NetView / ITSA SVT
Email: mlwebb AT us.ibm DOT com
Ext: (919) 224-1410, T/L: 687-1410
Michael Webb/Raleigh/IBM@IBMUS

Michael Webb/Raleigh/IBM@IBMUS Sent by: owner-nv-l AT lists.us.ibm DOT com 01/28/2004 05:32 PM Please respond to nv-l

To: nv-l AT lists.us.ibm DOT com cc: Subject: RE: [nv-l] netmon.seed file

Try adding one specific IP address per subnet as an initial seed entry such as:

10.60.180.x

where x is a valid IP address (like a router)

If that does not help to get that subnet discovered, then try a different syntax for your range, like

10.60.180.1-255

instead of 10.60.180.*.

Regards,

Michael Webb, IBM Tivoli
Q1CA Distributed NetView / ITSA SVT
Email: mlwebb AT us.ibm DOT com
Ext: (919) 224-1410, T/L: 687-1410
"Kevin Campbell" <kcampbell AT tgen DOT org>

"Kevin Campbell" <kcampbell AT tgen DOT org> Sent by: owner-nv-l AT lists.us.ibm DOT com 01/28/2004 05:24 PM Please respond to nv-l

To: <nv-l AT lists.us.ibm DOT com> cc: Subject: RE: [nv-l] netmon.seed file

Yes. I have also added one and more of the routers into the seed file as well. Still no luck
AIX 5.1
Netview 7.1.3 (fixpack 1 and 2)

-----Original Message-----
From: Barr, Scott [mailto:Scott_Barr AT csgsystems DOT com]
Sent: Wednesday, January 28, 2004 2:48 PM
To: nv-l AT lists.us.ibm DOT com
Subject: RE: [nv-l] netmon.seed file

Have you tried pinging a router within one of those subnets while discovery is running?
-----Original Message-----
From: owner-nv-l AT lists.us.ibm DOT com [mailto:owner-nv-l AT lists.us.ibm DOT com]On Behalf Of Kevin Campbell
Sent: Wednesday, January 28, 2004 3:31 PM
To: nv-l AT lists.us.ibm DOT 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