What you want to do is exclude the
DHCP IP address ranges (scopes) from
netmon discovery by putting entries
in the seedfile, preceeded with a !
Notice how you can use a range of addresses.
Unfortunately once netmon has discovered them,
it's kinda hard to make them go away. I inherited
a database with thousands of them already discovered,
so when I got the seedfile right, I blew away the
database and did a fresh discovery (nv6000_smit automapgen).
Check the NetView Administrator's guide for
>From: "Mahesh Tailor" <MTailor AT carilion DOT com>
>Reply-To: IBM NetView Discussion <nv-l AT tkg DOT com>
>To: <nv-l AT tkg DOT com>
>Subject: [NV-L] Cisco VPN & NV
>Date: Thu, 12 Jul 2001 11:21:30 -0400
>We have mutiple Cisco VPN 3000 Concentrator's and NV has discovered them
>correctly. But, everytime a client makes a connection a new network is
>created for the client IP address. For example, if a client connected via
>the concentrator and is assigned an IP address (DHCP) of 220.127.116.11, then
>a 18.104.22.168 IP Network symbol is added to map and an interface is added
>to VPN concentrator. Of course, this goes down when the client
>disconnects and netmon generates an interface down trap for the
>I really do not care for these clients attaching/disconnecting. How can
>I prevent these from being discovered/monitored?
>Carilion Health System
>NV-L List information and Archives: http://www.tkg.com/nv-l