Re: Cisco VPN & NV

2001-07-12 14:53:17
Subject: Re: Cisco VPN & NV
From: "Leslie Clark" <lclark AT us.ibm DOT com>
To: nv-l AT lists.tivoli DOT com
Date: Thu, 12 Jul 2001 14:53:17 -0400
I would exclude that address range from discovery in the
seedfile.  That will keep the PCs out. And I would unmanage those
interfaces on the 3000 that have already shown up, and I would define a
smartset of interfaces in that address range, identifying them as things
ought  always to be unmanaged, to flag them when new ones show up.
Eventually they will all show up, and then they will be static.  Would
that do it?


Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking

"Mahesh Tailor" <MTailor AT carilion DOT com>@tkg.com on 07/12/2001 11:21:30 AM

Please respond to IBM NetView Discussion <nv-l AT tkg DOT com>

Sent by:  owner-nv-l AT tkg DOT com

To:   <nv-l AT tkg DOT com>
Subject:  [NV-L] Cisco VPN & NV

Hello, all!

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, then
a 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?

NV: 6.0.2
AIX: 4.3.x


Mahesh Tailor
WAN Administrator
Carilion Health System
Voice: 540-224-3929
Fax: 540-224-3954
NV-L List information and Archives: http://www.tkg.com/nv-l

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