Yes, updating xnmsnmpconf requires a lot of work on the part of netmon.
If you turn on netmon tracing (netmon -M -1) you will see what all is going
on. (Turn it back off with netmon -M 0). If it is not whizzing by at
unreadable
speeds, check into your name resolution speeds, as the others have
said.
But in real life, in a good-sized network, once you are in production, you
should plan on saving those updates to snmp configurations for off-shift.
It is going to take a little while, and netmon will get a little behind.
I'm not sure what version you are on, but recent versions included
attempts to improve netmon's startup processing, which may improve
this as well, by interspersing activities in a more balanced way.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
"Brad Martin"
<bmartin@MetLife. To: nv-l@lists.tivoli.com
com> cc:
Subject: [nv-l] xnmsnmpconf
05/07/2002 08:22
PM
Everytime I make a change to the SNMP Configuration... it takes over an
hour before I start receiving netmon alerts or am able to do status /
demand polls. It appears that netmon is waiting until the SNMP database
cache has been completely rebuilt. Is there a faster way to accomplish
these changes?
We have a large database of approximately that 8,000 managed nodes and have
6.0.3 installed on an AIX 4.3 box.
Brad Martin
MetLife
---------------------------------------------------------------------
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)
|