Re: [nv-l] Netview Polling

[Leslie Clark <lclark@us.ibm.com>]

You cannot stop netmon from discovering
all addresses on a router, that's its job. However, in the case where you
don't have routing to those addresses, you should just tell netmon to poll
them via snmp. It will then do an snmpget of the ifOperStatus of all of
the interfaces, through the one address you do have SNMP access to, and
they will be nice and green.  You can do this either by putting one
address for each one in the seedfile with $ in front of it, or, in the
/usr/OV/conf/oid_to_type file, you can put add the S flag to the OID for
those types of routers. Stop/start netmon, and you are all set. 

Regarding Francois' advice to add name
resolution for the trap sources, I would add that when you do this, you
want to make sure that the forward resolution resolves to the address you
reach it by. If you were using just the hosts file, it would be like this:

10.10.10.5  MyRouter1  # the
address that I can talk to
10.10.10.1  My Router1  #
The loopback address of the router, where traps come from

So when Netview discovers it by 10.10.10.5,
it will name it MyRouter1. When a trap comes in from 10.10.10.1, it will
look that address up and assign it to MyRouter1 in the events display.
When you use menu functions on Netview against the node MyRouter1, it will
lookup the address and use 10.10.10.5. 

If the .5 address is already in your
DNS, and you decide to add the .1 address to the etc\hosts file on the
Windows box, you must also add the .5 address to the etc\hosts file because
the hosts file will take precidence.  

Cordially,

Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
(248) 552-4968 Voicemail, Fax, Pager

awatthey@mmm.com
Sent by: owner-nv-l@lists.us.ibm.com

01/13/2005 04:35 AM

Please respond to
nv-l

To	nv-l@lists.us.ibm.com
cc
Subject	[nv-l] Netview Polling

Hi,

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.

Regards,
Alan.