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.
#!/bin/bash
# Unmanage interfaces added
to networks 172.16. and 172.17 by VPN.
Date=`date`
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 ]
then
/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
fi
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?
Cordially,
Leslie A. Clark
IT Services Specialist, Network Mgmt
Information Technology Services Americas
IBM Global Services
Detroit
Palkovics László <lpalkovics@pcs.hu>
Sent by: owner-nv-l@lists.us.ibm.com
05/31/2006 10:31 AM
Please respond to
nv-l@lists.us.ibm.com
To
<nv-l@lists.us.ibm.com>
cc
Subject
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, 10.10.0.0/16, 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 10.10.1.1, for example. Why did the seedfile entry not
work and how do I go through and globally delete this network from all
interfaces/segments/objects?
TIA
--
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