nv-l
[Top] [All Lists]

Auto. Unmanaging IP addresses

To: nv-l@lists.tivoli.com
Subject: Auto. Unmanaging IP addresses
From: "Prokott, Joe" <Joe.Prokott@WESTGROUP.COM>
Date: Tue, 15 Jun 1999 16:51:03 -0500
Reply-to: Discussion of IBM NetView and POLYCENTER Manager on NetView <NV-L@UCSBVM.UCSB.EDU>
Sender: Discussion of IBM NetView and POLYCENTER Manager on NetView <NV-L@UCSBVM.UCSB.EDU>
Has anyone found a good (or a) solution to wanting to discover some IP
addresses on a node in a managed state and either (1) not discovering other
IP addresses on the same node, or (2) having the IP addresses discovered in
an unmanaged state?

In order to address this issue in the past, we have had to discover and
manage the entire node and then manually unmanage the particular interfaces
we do not want managed.  In normal situations, this is a one-time event done
upon initial discovery of the node.  However, when dealing with NAT
addresses, this becomes a recurring process and a real pain because (1) the
NAT addresses go up/down and we do not care about their status (i.e., want
them discovered unmanaged or not at all), AND (2) the NAT addresses age out
and are removed from the SNMP ip table if not used for a period of time.
This second condition causes NetView to delete and then later rediscover
these NAT IP addresses at some arbitrary time.  Eventually, the NAT IP
addresses later become unreachable, showing down in NetView and crying wolf
that there is something down on the node.  This process cycles over and over
again.  We want to be able to manage 2 of the IP interfaces on the node, but
not the other NAT addresses.  Is there a way to deal with this problem?

Joe Prokott - West Group
Network Architect
610 Opperman Drive
St. Paul, MN  55123
Phone: 651-687-4536
Fax: 651-687-6946
E-mail: joe.prokott@westgroup.com

<Prev in Thread] Current Thread [Next in Thread>
  • Auto. Unmanaging IP addresses, Prokott, Joe <=

Archive operated by Skills 1st Ltd

See also: The NetView Web