To: | nv-l@lists.tivoli.com |
---|---|
Subject: | Re: snmpCollect |
From: | Luc BARNOUIN <luc.barnouin@thalesatm.com> |
Date: | Tue, 17 Jul 2001 10:44:43 +0200 |
Il s'agit d'un message multivolet au format MIME.reamd@nationwide.com a écrit : Hi all,Dave, We had similar problem with our configuration where snmpCollect was using from 30% to 60% of the CPU. When activating the traces, we found it was looping in querying the sysUpTime OID for one particular node. I don't know why, but each time snmpCollect queries an OID on a node, it first get the sysUpTime, and then the requested OID. On this node, we were experimenting a new SNMP agents wich had its own implementation of the sysUpTime (i.e. a different value from standard snmpd). Depending of wich agent was running at snmpCollect start (data collection initialisation) and then during data collection cycle, we get in this situation (I'm sure that Tivoli software team could explain this behavior...) - a stop/restart of snmpCollect fixed the problem until the next time.... So check snmpCollect traces to see wether your are in the same situation... Regards
luc.barnouin.vcf |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | Color not propagating to submap, Chan, Jack |
---|---|
Next by Date: | Printers within a SmartSet, moshe_asseo |
Previous by Thread: | Re: snmpCollect, Leslie Clark |
Next by Thread: | RE: snmpCollect, Scott Barr |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web