Dave, that snmpstatus.sh is not a Netview command, it is one I gave you.
I bet your object count has gotten over the cache setting. Check with
'ps -ef | grep ovwdb' and see what the parameter is. If it is not higher
120000, it needs to be increased just on general principals. To do that
(with serversetup) you will first want to close all maps. Note that most of
your objects are just stubs, but increase it anyway if necessary. This will
affect overall responsiveness of the system.
That should not, however, cause snmpCollect to be so busy. What are
you collecting on? See Tools...Data Collection & Thresholding.
See /usr/OV/conf/snmpCol.conf. Also look for messages in
/usr/OV/log/snmpCol.trace. You can turn on tracing from the commandline
with snmpCollect -T, and make it verbose with snmpCollect -V. Those
commands toggle the settings, so use them again to turn them off.
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
reamd AT nationwide DOT [email protected] on 07/12/2001 09:53:25 AM
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
Subject: [NV-L] snmpCollect
I am running AIX 4.3.3 with 6.02.. My snmpCollect is constantly
using 60% of my CPU. I do a snmpstatus.sh and it shows 0 behind in polling.
I currently have 106000 objects in the database maintained by ovwdb....
NV-L List information and Archives: http://www.tkg.com/nv-l