Alfred, it does run fine for most people. That's why people are
suggesting that you are most likely suffering from poor response
from name resolution. Here are some things you should do:
1) Force netmon to start with tracing turned on, rather than trying to turn
it
on from the commandline, because by then it is too late to see why it is
hanging up. Use daemon configuration to tell netmon to trace (-1). That
will
stop and start netmon with the new parameter. Then tail -f netmon.trace.
Right at the beginning, you will see it checking on every interface in the
database doing fixups. This should scroll by so fast that you cannot read
it.
Instead, I think you will see that it is taking 3 or 4 seconds for each
object.
If that is the case, then you have a name resolution problem. When you make
a change in the snmp configuration dialog, netmon does that exact same
fixup
processing again. So I'm pretty sure that is your problem.
2) If most of the interfaces being examined are actually unresolved, there
is not much sense in going to DNS. Perhaps you should consider not going to
DNS at all. You number of interfaces is not so great that using /etc/hosts
for some
things will cause you problems, I think. If you have a few devices with a
large
number of interfaces (like 50), consider putting those interfaces in the
hosts file
and making sure that it is checked before DNS by making /etc/netsvc.conf
with 'hosts=local,bind' in it. To generate updates to /etc/hosts, here's
what I
do:
rnetstat -I ADDRESS | awk '{print $2 " " NAME}' > NAME.hosts
where ADDRESS is one of the ip addresses or the resolvable name of the
node,
and NAME is the name you want to give it. Edit the output file, move the
address
you like best to the top, and append this to the /etc/hosts file. This
gives exactly
the kind of resolution that Netview likes best: all addresses resolve to
the same
name, and a particular name always resolves to the same address.
3) To cause name resolution to timeout more quickly, add these entries
to /etc/environment:
RES_RETRY=1
RES_TIMEOUT=1
The defaults for these are 4 and 5, I believe, and can end up wasting
a lot of time. Better to have no names than to wait for names.
I think what the people have been trying to suggest is that you
should look for your problem on your DNS, not on Netview. I see
this a lot, and since I never have control over the DNS, I circumvent
the problem by the steps above.
I hope this helps.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
Sebastian.Szumczyk@natned.com.pl@tkg.com on 11/15/2000 03:51:36 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: nv-l@tkg.com
cc:
Subject: RE: [NV-L] please answer this question!
hi,
thanx for reply, but i had got based name resolution switch to a
dns-based:-)
but it doesn't work:-( is there a possibility to restart netmon without any
delay on aix 4.3.2?
bast3k
-----Original Message-----
From: REIBENSCHUH Alfred [mailto:alfred.reibenschuh@it-austria.com]
Sent: Tuesday, November 14, 2000 6:17 PM
To: 'IBM NetView Discussion'
Subject: RE: [NV-L] please answer this question!
hi!
from the symptom i judge that you use aix 4.3.2
if this is true then you have to switch from a /etc/hosts
based name resolution to a dns-based
sorry, but aix 4.3.x now uses some IPv6 resolution
and a large number of entries in the /etc/hosts file
slows netmon down to the 2 hours you stated
in our case it took 6 hours for netmon to begin polling
(30k+ object in the database)
mfG. Alfred Reibenschuh
INFORMATIONSTECHNOLOGIE AUSTRIA GMBH
TELEKOMMUNIKATION
Networkmanagement
Intranet Info-koordinator
A-1020 Wien, Lassallestrasse 5
T: ++43-1-21717-58947
F: ++43-1-21717-58979
E: alfred.reibenschuh@it-austria.com
> -----Original Message-----
> From: Sebastian.Szumczyk@natned.com.pl
> [mailto:Sebastian.Szumczyk@natned.com.pl]
> Sent: Tuesday, November 14, 2000 4:46 PM
> To: nv-l@tkg.com
> Subject: RE: [NV-L] please answer this question!
>
>
> yes, i run netmon trace (netmon -M -1) then i tail file
> netmon.trace, but i
> can't see nothing! but when netmon starts working it writes
> to netmon.trace
> many entries so it works fine :-) the problem is i have to
> wait for that
> more than 2 hours after restarting netmon. why?
>
> -----Original Message-----
> From: James_Shanks@tivoli.com [mailto:James_Shanks@tivoli.com]
> Sent: Tuesday, November 14, 2000 4:23 PM
> To: IBM NetView Discussion
> Subject: Re: [NV-L] please answer this question!
>
>
> How did you decide that netmon was hung?
>
> If it really is, then my guess is that you have severe name resolution
> problems.
>
> Are you running the netmon trace?
>
> James Shanks
> Team Leader, Level 3 Support
> Tivoli NetView for UNIX and NT
>
>
>
> Sebastian.Szumczyk@natned.com.pl on 11/14/2000 10:03:20 AM
>
> Please respond to IBM NetView Discussion <nv-l@tkg.com>
>
> To: nv-l@tkg.com
> cc: (bcc: James Shanks/Tivoli Systems)
> Subject: [NV-L] please answer this question!
>
>
>
>
> hi,
> first of all i would like to ask you for reply on this
> message as soon as
> possible cause i'm very disappointed of netmon and i'm in
> real troubles :-(
> i've got 1200 objects in database, defined location.conf and
> seed.file.
> when
> i restarted netmon it hung! so i decided to remove seed.file
> from netmon
> configuration, but still if i would like to change sth for
> instance snmp
> configuration netmon hangs for over 2 hours!!! what's going
> on? how solve
> this problem?
>
> bast3k
>
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> ^ Sebastian Szumczyk ^
> ^ WAN/UNIX/TIVOLI System Specialist ^
> ^ Nationale Nederlanden Polska S.A. ^
> ^ tel.: + 48 22 522-06-18 ^
> ^ + 48 0 604-598-600 ^
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> ______________________________________________________________
> ___________
> NV-L List information and Archives: http://www.tkg.com/nv-l
>
>
> ______________________________________________________________
> ___________
> NV-L List information and Archives: http://www.tkg.com/nv-l
> ______________________________________________________________
> ___________
> NV-L List information and Archives: http://www.tkg.com/nv-l
>
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|