I would be remiss if I did not point out that clearing your database to fix 
discovery would never be a recommended process (in my opinion). If you can't 
get somethign discovered, it is my experience, that there is a very good reason 
for it. Usually, it has to do with part of the object such as an interface 
already being discovered, perhaps with a different name than you are expecting. 
Discovery can fail for other reasons as well, but the rule of thumb will be 
(and some others can back me up here) that clearing the database is swinging a 
sledgehammer at a gnat. Keep in mind, in most cases, topology rediscovery will 
an outage situation for the NetView platform. Most shops during normal 
production would not want to do that.
 
Also remember that under certain circumstances, discovery doesn't happen 
immediately. It can take a while. I know that lots of times nodes pop right 
into discovery but it's not always that fast. What I would do is do an 
ovtopodump to a file and then use your favorite editor to poke around for the 
partial object. doing your usual topology maintenance (ovtopofix -A and 
mapcount -a) might also help. But clearing the database should be viewed as a 
"last ditch" effort.

-----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 Michael Webb
Sent: Wednesday, January 28, 2004 4:38 PM
To: nv-l AT lists.us.ibm DOT com
Subject: RE: [nv-l] netmon.seed file



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
Inactive hide details for Michael Webb/Raleigh/IBM@IBMUSMichael 
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
Inactive hide details for "Kevin Campbell" ' src="cid:764174313@29012004-00e0" 
width=16>"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> 
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> 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