I think this is a fairly common issue, the trade-off between control
and the adminstrative burden it entails.
If I were letting routers be discovered by whatever interface is
found, I would just add matching names to the hosts file for those
interfaces,
without bothering with the delete/rediscover. I would override the DNS
with /etc/hosts entries for those interfaces (on AIX this is done in
/etc/netsvc.conf with hosts=local,bind, Solaris does it differently).
I might set up a collection (smartset) that contains things without name
resolution, and, if needed, things that have goofy interface-oriented
names that need changing. Treat that as an after-discovery to-do list.
I have found it to be very useful to have consistent name resolution
not only on the loopback, but also on the nearest interface, since
that is usually the one that the traps come in from. It allows me to
correlate events with objects on the map, among other things.
Anybody else?
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
---------------------- Forwarded by Leslie Clark/Southfield/IBM on
03/29/2000 08:30 PM ---------------------------
"Jewan, P. (Pritesh)" <PriteshJ AT nedcor DOT com>@tkg.com on 03/29/2000
06:59:50
PM
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'" <nv-l AT tkg DOT com>
cc:
Subject: [NV-L] Netview Seed File with oid's
Hello People,
We currently have a network with about 550 Cisco routers and 250 Cisco
switches as well a large number of other servers(NT,AIX,SUN etc). The way
we have been doing the discovery in the past was to put the IP addresses of
the device into the seed file and let netmon discover the nodes. This
method was important to us because we wanted to discover the routers using
their loopback addresses as the loopback addresses are tied to names in the
DNS server. However our environment is growing at a rapid pace and as a
result new routers go out in the network and their addresses are sometimes
not reported and as a result are never put into the seedfile.
We are currently investigating other methods of creating a seedfile to
alleviate this problem. The only suitable method I could think of was to
use Cisco OID's for the Cisco devices but then this leaves us with the
problem of the routers been discovered with the first address that netmon
finds. The only thing this helps us with is that we now know that there is
a router out there and can then put it's loopback address into the
seedfile, delete the object and let netmon rediscover it bye the loopback
address.
Has anyone encountered a similar situation? Any ideas/suggestion would be
greatly appreciated.
Regards
Pritesh Jewan
ESM - Technology & Operations Division
Nedcor Bank Limited (South Africa)
Tel : +27 - 011 - 320 5417
Cell: +27 - 82 570 5046
Fax : +27 - 011 - 8814743
e-mail : priteshj AT nedcor DOT com
|
