Hi, Arjen. I have learned some interesting things by turning on tracing in
snmpcollect, especially at startup, which you do in the daemon
configuration.
Tracing and verbose. I have seen it do this sometimes, and it usually
is as a result of not being able to ask the device the actual question you
have configured, as opposed to the test you make with snmpget or snmpwalk.
One thing I found out that way is this: sometimes you are pulling too much
data
from a device at one time, and the device refuses to answer. Netview will
try to
get it all in one trip. To solve this, on the snmpCollect daemon settings,
reduce
the maxpdu from 100 to 50. This forces snmpCollect to make two trips, and
the
device is happy. This is just a guess. But when more than a few interfaces
on
a device are involved, I drop the maxpdu.
Tracing may also show that it is having some name resolution problems.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
(248) 552-4968 Voicemail, Fax, Pager
"Hageman, Arjen (A)" <AHAGEMAN@dow.com>@tkg.com on 04/27/2001 10:08:55 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: "'nv-l@tkg.com'" <nv-l@tkg.com>
cc: "'arno.westhuis@eds.com'" <arno.westhuis@eds.com>
Subject: [NV-L] snmpCollect not working
To all.
Our situation is as follow :
* Sun/Solaris machine with O.S. 8.0
* Tivoli 3.6.2
* NetView for Tivoli 6.0.2
We try to work with the snmpCollect function to retrieve MIB-2 information
of network devices. For some reason, we are not able to get snmpCollect to
generate the files on the directory : /usr/OV/databases/snmpCollect.
NV6K can reach all devices via ping/SNMP and using the MIB browser, we are
able to extract info. The number of devices from which we try to collect
data is appr: 200 and the number of reported MIB values per device is 12.
The file systems have plenty of disk space left. snmpCollect sometime works
with irregular time intervals or doesn't do anything at all. CPU
utilization
is less then 10%. I even try to set the concurrent SNMP sessions from 5
(default) to 500 but has no effect. I cannot determine what factor or
parameter is responsible for this behavior.
Does anyone have any idea what goes wrong? Any suggestion is welcome.
Kind regards,
A. Hageman
Terneuzen.
* : 31.115.674050
* : 31.115.674327
* : ahageman@dow.com
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|