I tried the host file but it gave me more trouble than anything else as the
name resolution is a lot heavier on the CPU if the host file is big. The
main reason is that the Netview server was also a syslog server and syslogd
not being multithreaded, it started eating 100% of one cpu and dropping
traffic. Maybe if you don't have other name resolution intensive process it
would work but it all depends on the size of the host file.
Also I wonder what others do for the name resolution of HSRP interface ?
The way I do is to resolve the ip to the name of the primary router but it
lead to frequent problems when somehow Netview elect an HSRP interface to
be the "SNMP address" for a device.
Salutations, / Regards,
Francois Le Hir
Network Projects & Consulting Services
IBM Global Services
Phone: (514) 205 6695
"Evans, Bill"
<Bill.Evans@hq.do
e.gov> To
Sent by: "'nv-l@lists.us.ibm.com'"
owner-nv-l@lists. <nv-l@lists.us.ibm.com>
us.ibm.com cc
Subject
03/08/2004 03:21 RE: [nv-l] seed file
PM
Please respond to
nv-l
Another important item is to use only one name in DNS for each router. All
the interfaces on that device should resolve to the same name. The name
should resolve to the loopback address for the router.
This gives you the best functioning of NetView although there is a
continuing argument from many who want a unique DNS name for each interface
for other reasons. I find the device name qualified by the interface name
(e.g. Router.Serial1/0) gives the uniqueness I need for interfaces. When
necessary I override the DNS with a local hosts file to achieve this. In
my present situation the DNS has only the loopback address and I use hosts
to resolve the other names.
Bill Evans
-----Original Message-----
From: Paul [mailto:pstroud@bellsouth.net]
Sent: Monday, March 08, 2004 2:05 PM
To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] seed file
Chris,
Only use one IP for each device, you are causing netmon to do a lot of
additional and unecessary cycles. Let me explain:
netmon reads the entries from the seedfile, pings the node, if it
responds, it is added to the database and an SNMP poll in scheduled.
When the device is polled via SNMP all the interfaces are discovered
and finally the full device is added to the map.
If you put multiple IPs in the seedfile for the same device it will be
added and polled mutliple times, one for each ip in the seedfile. This
is uneccesary as netmon will already discover it via SNMP. That and
you might confuse things. Ie. netmon discovers on interface and adds it
and finds another interface and adds it before the first SNMP poll
is completed. Now it must delete one of the devices(as we know they
are on the same device) and fixup the correct device. This is all
uneccesary processing.
The best practice is to add a single interface from each device.
Paul
Christopher J Petrina wrote:
>
> Greetings all,
>
> UNIX netview. Using a seefile forl imited discovery. In the seedfile
> I have multiple entries (multiple IP's) for the same device, ie(every
> ip interface of a single router) is in the seedfile. When netview
> runs through the seedfile it finds the first IP of a device when it
> comes to the second IP of that device what does netview do. Each IP
> interface also has an entryo in DNS as well. Does netview change the
> name of the device if it finds another name. Also once it has
> initially found it, and then polls the device (SNMP) what name will it
> chose for the device in netview, and why does it sometimes change the
> name of the device.
>
>
> Chris Petrina
|