Thanks for the suggestion. This one I can answer more quickly. We do use a
full list for initial discovery, and then pare it back as you outlined. Our
seedfile contains a list of 15 names to SNMP poll, 2 names designated at HSRP,
and a handful of network ranges to include and exclude.
Karin
-----Original Message-----
From: Leslie Clark [mailto:lclark@us.ibm.com]
Sent: Friday, June 28, 2002 4:21 PM
To: nv-l@lists.tivoli.com
Subject: Re: [nv-l] Netmon initialization - how to speed it up?
Beyond Stephen's comprehensive answer I can only add this:
Are you by any chance using an explicit seedfile? Is there a long list of
nodes in
it, I mean? I've seen a big difference in performance if I take that list
out and
just run with the rules. One things are discovered, they don't need to be
in the seedfile (unless you need to rediscover them and the rules don't
cover them.)
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Dtetroit
"Binder, Karin"
<karin.binder@nwa To: "Nv-L (E-mail)"
<nv-l@lists.tivoli.com>
.com> cc:
Subject: [nv-l] Netmon
initialization - how to speed it up?
06/28/2002 04:31
PM
Hello all,
Netmon initialization takes a long time on our production system (i.e. 1
hour 42 minutes). I'd like to shorten this if possible. I suspect there
is some sort of problem contributing to the delay, but cannot pinpoint it,
and was hoping you would have some suggestions to try.
Pertinents: Netview 6.03, AIX 4.3.3 on SP2 node with 1G memory.
The process is exponentially faster on our test system. The production and
test system are like in setup, software, configuration and parameters used
in daemon startup (i.e. number pingers, tracing on/off, DNS server, etc.).
The differences are in number of devices discovered and hardware platforms.
Differences noted:
Stat Test
Production
Hardware F40
SP2
Objects in DB 16,371
49,570 Ratio 1:3
Duration of netmon fixups 7 minutes 202
minutes Ratio 1:29 **
So far I have tried:
1) Turning off tracing
2) Increasing the number of pingers to 32 (-q and -Q)
3) RES_RETRY and RES_TIMEOUT are both set to 1, and DNS works well
4) The box has been rebooted (for other reasons)
It still takes 1 hour 42 minutes +/- 1 minutes every time. I have been
working with L2 on this and we've run out of things to try. Any ideas on
what could contribute to the delay? Any other parameters to tweak? Any
debugging options?
All suggestions appreciated,
Karin Binder
---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com
*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)
---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com
*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)
|