Thanks for your quick reply Leslie.
I followed your advice, so far so good !
After deletion, nv6k rediscovered ~200 nodes, but none of them are win95
which is far better than yesterday.
I went from approx 13000 objects down to 7000 in the DB.
Thanks again !
> -----Original Message-----
> From: Leslie Clark [SMTP:lclark@US.IBM.COM]
> Sent: Thursday, February 03, 2000 5:21 PM
> Subject: Re: Seedfile not working ?
> As long as netview has heard about them, they will come back.
> Here's what to do:
> ovstop netmon.
> Select and delete the things you don't want (from ALL submaps)
> Wait for the deletion events to show up in the events display.
> Repeat on maps other than default (make sure netmon is not restarted
> when you bring up the other maps)
> ovtopofix -a (to get rid of all traces of them)
> ovstart netmon
> Now they should not show up.
> You will, however, get stub objects in the database, with just two
> fields, as reminders to not discover them. And they will be checked
> via snmp once a day (by default) to see if they have turned onto
> something that is permitted.
> Leslie A. Clark
> IBM Global Services - Systems Mgmt & Networking
> Dear List,
> I've activated a seed file today, the goal is to suppress discovery of
> Windows95 workstations and HP Printers.
> Until now, I've never used a seed file, but these 'unwanted' devices were
> unmanaged at discovery time (by using specific entries in the oid_to_type
> Now, this doesn't seem to work. After the seedfile activation (and restart
> of netmon),
> I've deleted a few win95 devices, and they reappeared after a while.
> Here is the seedfile I'm using (really simple) :
> !@oid 18.104.22.168.22.214.171.124.12.2.1 # Novell NIOS Windows 95 SNMP Agent
> !@oid 126.96.36.199.188.8.131.52.3.9.1 # HP Network Printer
> The OID I'm using is correct (we're using Novell's SNMP Agent on our
> Any idea what's happening here ?
> Thanks for your input !