[Top] [All Lists]

[nv-l] Netview Polling

To: nv-l@lists.us.ibm.com
Subject: [nv-l] Netview Polling
From: awatthey@mmm.com
Date: Thu, 13 Jan 2005 09:35:55 +0000
Delivery-date: Thu, 13 Jan 2005 09:39:23 +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


I'm on Windows 2000 with Netview 7.1.4 FP2.

I've been doing some traces of what Netview is doing and I've seen quite a
lot of activity.  I was wondering how I could stop it.  I have 'discover
all networks' with @limit_discovery in my netmon.seed along with a list of
the ranges it should work with.

Basically we have various parts of the network outsourced.  I have
negotiated SNMP read access to all these routers.  Netview discovers these
routers quite happily but also discovers that they have lots of other
interfaces with strange IP addresses.  There is no routing in our network
to these addresses.  Even though I have limited the range of IP addresses
that Netview should discover via the NETMON.SEED file, it still insists on
PINGing and doing NBNS name lookups on these addresses.  Of course these
packets flow out of our default route and try to get to the Internet.  This
not only wastes bandwidth but gets our IDS people after me as they think a
box has a virus trying to get to all sorts of strange addresses which have
nothing to do with our organisation.

Is there an automatic method (forget manually unmanaging things) of
stopping netview from refering to anything not specified in the seed file.


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

Archive operated by Skills 1st Ltd

See also: The NetView Web