[Top] [All Lists]

RE: [nv-l] Removing a network

To: nv-l@lists.us.ibm.com
Subject: RE: [nv-l] Removing a network
From: "Davis, Donald" <donald.davis@firstcitizens.com>
Date: Thu, 1 Jun 2006 11:23:47 -0400
Delivery-date: Thu, 01 Jun 2006 16:24:42 +0100
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
Thread-index: AcaE1rBG2xpsg4EsTYmltHSAm540igABa3lgACwe0oA=
Thread-topic: [nv-l] Removing a network
I do something very similar with my VPN interfaces, except I use the acknowledgeUtil instead of the nvmaputil.sh --unmanage utility.
The reason is because of read-only map status propagation. Unmanaging a critical interface is not a "status change" and the interface will remain red on my Command Center's read-only maps (so does a delete). It sounds like a great idea to marry the two methods. Automatically acknowledge it first so that it turns green on the read-only maps, then automatically unmanage it.   LOL - Great minds think alike, and so do ours.
Don Davis
First Citizens Bank
Raleigh, NC

From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com] On Behalf Of Evans, Bill
Sent: Wednesday, May 31, 2006 2:09 PM
To: nv-l@lists.us.ibm.com
Subject: RE: [nv-l] Removing a network

I've done something similar in unmanaging interfaces.  Our situation is a VPN which dynamically adds interfaces as users connect across the network then the interfaces go critical when they close the session.  To counter this I unmanage any interface which is on the selected networks. 


The procedure could easily be adapted to handle the situation under discussion. I think you would only need to change the network addresses.  It is driven from the EXEC statement on the TRAPD.CONF for the NetView Interface Added trap on a Linux system.    



# Unmanage interfaces added to networks 172.16. and 172.17 by VPN. 


let Result=${RANDOM}%20

# DEBUG echo "${Date} Variables: $* "   >>/opt/webmon/IFAdd.log


IPAddress=`echo ${*} | sed -e 's/\\\\//g'`

echo "${Date} Variable IPAddress: ${IPAddress} "   >>/opt/webmon/IFAdd.log


Filter=`echo ${IPAddress} | egrep '(172.16.|172.17.)' | wc -l`

if [ ${Filter} -gt 0 ]


      /bin/sleep ${Result}  # Delay for some number of seconds between zero and 20 to prevent races.

      /usr/OV/bin/nvmaputil.sh --unmanage-interface ${IPAddress} &

      echo "${Date} Interface unmanage requested: ${IPAddress}. "   >>/opt/webmon/IFAdd.log


exit 0


Bill Evans

Home: 570-639-5691

Cell:    570-852-9549


-----Original Message-----
From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com] On Behalf Of Leslie Clark
Sent: Wednesday, May 31, 2006 11:15 AM
To: nv-l@lists.us.ibm.com
Subject: RE: [nv-l] Removing a network


That would work if you wanted to exclude the discovery of nodes that only

have interfaces with those addresses, But if you have snmp-enabled devices

with multiple interfaces, and if one or more of those interfaces meets the

criteria of the seedfile, then the node will be discovered, And once the

node is discovered, then all ip-addressable interfaces on that node will

be discovered.


One way to handle these interfaces is to unmanage them. If they get

deleted and rediscovered on a regular basis, however, they may need to be

unmanaged repeatedly. This can occur with things like VPN routers, or

things with intentional duplicate IP addresses.


Has anyone taken any other approaches to selectively unmanaging groups of

interfaces on routers?




Leslie A. Clark

IT Services Specialist, Network Mgmt

Information Technology Services Americas

IBM Global Services






Palkovics László <lpalkovics@pcs.hu>

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

05/31/2006 10:31 AM

Please respond to









RE: [nv-l] Removing a network







Put "@limit_discovery" in your netmon.seed file.

Delete the 10.10.* objects with the Object menu Delete.. command.

Restart Netmon daemon.





Feladó: owner-nv-l@lists.us.ibm.com meghatalmazó: Kain, Becki (B.)

Küldve: 2006. 05. 31., Sze 15:15

Címzett: nv-l@lists.us.ibm.com

Tárgy: [nv-l] Removing a network




I'd like to have a certain network,, never show up in my

netview map, even if a device has an ip from that network defined.


We have this now, in the seedfile


!10.10.*.*   # un reachable subnets must ignore


But, I have a device that has, as unmanaged interfaces, a ton of

interfaces with, for example.  Why did the seedfile entry not

work and how do I go through and globally delete this network from all








No virus found in this incoming message.

Checked by AVG Free Edition.

Version: 7.1.394 / Virus Database: 268.8.0/352 - Release Date: 5/30/2006



No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.8.0/352 - Release Date: 5/30/2006

Call 1.888.FC DIRECT (1.888.323.4732) or visit us on the
web at firstcitizens.com today to take advantage of our 
great products and services. 

This electronic mail and any files transmitted with it are 
confidential and are intended solely for the use of 
individual or entity to whom they are addressed. If you are 
not the intended recipient or the person responsible for 
delivering the electronic mail to the intended recipient, 
be advised that you have received this electronic mail in 
error and that any use, dissemination, forwarding, 
printing, or copying of this electronic mail is strictly 
prohibited. If you have received this electronic mail in 
error, please immediately notify the sender by return mail.
First Citizens Bank - Helping our customers achieve a
lifetime of success.  Visit us on the web at firstcitizens.com - Member FDIC

<Prev in Thread] Current Thread [Next in Thread>
  • RE: [nv-l] Removing a network, Davis, Donald <=

Archive operated by Skills 1st Ltd

See also: The NetView Web