<insert sound of hand smacking forehead here>

No, I didn't add the .0 at the end of the OID..

When I do add it and try the zensnmpperf run command, I get the
following output, it seems to indicate a problem with some other OIDS
for that device (or am I not reading it correctly)?


zenoss:/usr/local/zenoss/bin # ./zenperfsnmp run -v 10 -d 2169-FGT-1
DEBUG:zen.zenperfsnmp:Gathering performance data for 2169-FGT-1
DEBUG:zen.zenperfsnmp:Configured 1 devices
DEBUG:zen.zenperfsnmp:received config for 2169-FGT-1
DEBUG:zen.zenperfsnmp:Updated configCycleInterval config to 30
DEBUG:zen.zenperfsnmp:Updated snmpCycleInterval config to 60
DEBUG:zen.zenperfsnmp:getting device ping issues
DEBUG:zen.zenperfsnmp:Unresponsive devices: [['2276', 1, 1029]]
DEBUG:zen.RRDUtil:create new rrd
/usr/local/zenoss/perf/Devices/2169-FGT-1/os/interfaces/201_BACKBONE/IfInOctets.rrd
Unhandled error in Deferred:
Traceback (most recent call last):
  File "/usr/local/zenoss/Products/ZenUtils/Chain.py", line 45, in
success
    self.next()
  File "/usr/local/zenoss/Products/ZenUtils/Chain.py", line 40, in
next
    self.defer.callback(self.results)
  File "/usr/local/zenoss/lib/python/twisted/internet/defer.py", line
229, in callback
    self._startRunCallbacks(result)
  File "/usr/local/zenoss/lib/python/twisted/internet/defer.py", line
294, in _startRunCallbacks
    self._runCallbacks()
--- <exception caught here> ---
  File "/usr/local/zenoss/lib/python/twisted/internet/defer.py", line
307, in _runCallbacks
    self.result = callback(self.result, *args, **kw)
  File "/usr/local/zenoss/Products/ZenRRD/zenperfsnmp.py", line 405, in
storeValues
    self.storeRRD(deviceName, oid, value)
  File "/usr/local/zenoss/Products/ZenRRD/zenperfsnmp.py", line 431, in
storeRRD    oidData = self.proxies[device].oidMap[oid]
exceptions.KeyError: '.1.3.6.1.2.1.2.2.1.16.44'
DEBUG:zen.zenperfsnmp:getting device ping issues
DEBUG:zen.zenperfsnmp:Unresponsive devices: [['2276', 1, 1030]]
WARNING:zen.zenperfsnmp:Devices status is not clearing.  Restarting.
Unhandled error in Deferred:
Traceback (most recent call last):
  File "/usr/local/zenoss/Products/ZenUtils/Chain.py", line 45, in
success
    self.next()
  File "/usr/local/zenoss/Products/ZenUtils/Chain.py", line 40, in
next
    self.defer.callback(self.results)
  File "/usr/local/zenoss/lib/python/twisted/internet/defer.py", line
229, in callback
    self._startRunCallbacks(result)
  File "/usr/local/zenoss/lib/python/twisted/internet/defer.py", line
294, in _startRunCallbacks
    self._runCallbacks()
--- <exception caught here> ---
  File "/usr/local/zenoss/lib/python/twisted/internet/defer.py", line
307, in _runCallbacks
    self.result = callback(self.result, *args, **kw)
  File "/usr/local/zenoss/Products/ZenRRD/zenperfsnmp.py", line 405, in
storeValues
    self.storeRRD(deviceName, oid, value)
  File "/usr/local/zenoss/Products/ZenRRD/zenperfsnmp.py", line 431, in
storeRRD    oidData = self.proxies[device].oidMap[oid]
exceptions.KeyError: '.1.3.6.1.2.1.2.2.1.16.44'
DEBUG:zen.zenperfsnmp:getting device ping issues
DEBUG:zen.zenperfsnmp:Unresponsive devices: [['2276', 1, 1031]]
WARNING:zen.zenperfsnmp:There are still 1 devices to query, waiting for
them to finish
DEBUG:zen.zenperfsnmp:getting device ping issues
DEBUG:zen.zenperfsnmp:Unresponsive devices: [['2276', 1, 1032]]
WARNING:zen.zenperfsnmp:Devices status is not clearing.  Restarting.
Unhandled error in Deferred:
Traceback (most recent call last):
  File "/usr/local/zenoss/Products/ZenUtils/Chain.py", line 45, in
success
    self.next()
  File "/usr/local/zenoss/Products/ZenUtils/Chain.py", line 40, in
next
    self.defer.callback(self.results)
  File "/usr/local/zenoss/lib/python/twisted/internet/defer.py", line
229, in callback
    self._startRunCallbacks(result)
  File "/usr/local/zenoss/lib/python/twisted/internet/defer.py", line
294, in _startRunCallbacks
    self._runCallbacks()
--- <exception caught here> ---
  File "/usr/local/zenoss/lib/python/twisted/internet/defer.py", line
307, in _runCallbacks
    self.result = callback(self.result, *args, **kw)
  File "/usr/local/zenoss/Products/ZenRRD/zenperfsnmp.py", line 405, in
storeValues
    self.storeRRD(deviceName, oid, value)
  File "/usr/local/zenoss/Products/ZenRRD/zenperfsnmp.py", line 431, in
storeRRD    oidData = self.proxies[device].oidMap[oid]
exceptions.KeyError: '.1.3.6.1.2.1.2.2.1.16.44'
DEBUG:zen.zenperfsnmp:getting device ping issues
DEBUG:zen.zenperfsnmp:Unresponsive devices: [['2276', 1, 1033]]
WARNING:zen.zenperfsnmp:Devices status is not clearing.  Restarting.
Unhandled error in Deferred:
Traceback (most recent call last):
  File "/usr/local/zenoss/Products/ZenUtils/Chain.py", line 45, in
success
    self.next()
  File "/usr/local/zenoss/Products/ZenUtils/Chain.py", line 40, in
next
    self.defer.callback(self.results)
  File "/usr/local/zenoss/lib/python/twisted/internet/defer.py", line
229, in callback
    self._startRunCallbacks(result)
  File "/usr/local/zenoss/lib/python/twisted/internet/defer.py", line
294, in _startRunCallbacks
    self._runCallbacks()
--- <exception caught here> ---
  File "/usr/local/zenoss/lib/python/twisted/internet/defer.py", line
307, in _runCallbacks
    self.result = callback(self.result, *args, **kw)
  File "/usr/local/zenoss/Products/ZenRRD/zenperfsnmp.py", line 405, in
storeValues
    self.storeRRD(deviceName, oid, value)
  File "/usr/local/zenoss/Products/ZenRRD/zenperfsnmp.py", line 431, in
storeRRD    oidData = self.proxies[device].oidMap[oid]
exceptions.KeyError: '.1.3.6.1.2.1.2.2.1.16.44'
DEBUG:zen.zenperfsnmp:getting device ping issues
DEBUG:zen.zenperfsnmp:Unresponsive devices: [['2276', 1, 1034]]
WARNING:zen.zenperfsnmp:Devices status is not clearing.  Restarting.
Unhandled error in Deferred:
Traceback (most recent call last):
  File "/usr/local/zenoss/Products/ZenUtils/Chain.py", line 45, in
success
    self.next()
  File "/usr/local/zenoss/Products/ZenUtils/Chain.py", line 40, in
next
    self.defer.callback(self.results)
  File "/usr/local/zenoss/lib/python/twisted/internet/defer.py", line
229, in callback
    self._startRunCallbacks(result)
  File "/usr/local/zenoss/lib/python/twisted/internet/defer.py", line
294, in _startRunCallbacks
    self._runCallbacks()
--- <exception caught here> ---
  File "/usr/local/zenoss/lib/python/twisted/internet/defer.py", line
307, in _runCallbacks
    self.result = callback(self.result, *args, **kw)
  File "/usr/local/zenoss/Products/ZenRRD/zenperfsnmp.py", line 405, in
storeValues
    self.storeRRD(deviceName, oid, value)
  File "/usr/local/zenoss/Products/ZenRRD/zenperfsnmp.py", line 431, in
storeRRD    oidData = self.proxies[device].oidMap[oid]
exceptions.KeyError: '.1.3.6.1.2.1.2.2.1.16.44'
DEBUG:zen.zenperfsnmp:getting device ping issues
DEBUG:zen.zenperfsnmp:Unresponsive devices: [['2276', 1, 1035]]
WARNING:zen.zenperfsnmp:Devices status is not clearing.  Restarting.
Unhandled error in Deferred:
Traceback (most recent call last):
  File "/usr/local/zenoss/Products/ZenUtils/Chain.py", line 45, in
success
    self.next()
  File "/usr/local/zenoss/Products/ZenUtils/Chain.py", line 40, in
next
    self.defer.callback(self.results)
  File "/usr/local/zenoss/lib/python/twisted/internet/defer.py", line
229, in callback
    self._startRunCallbacks(result)
  File "/usr/local/zenoss/lib/python/twisted/internet/defer.py", line
294, in _startRunCallbacks
    self._runCallbacks()
--- <exception caught here> ---
  File "/usr/local/zenoss/lib/python/twisted/internet/defer.py", line
307, in _runCallbacks
    self.result = callback(self.result, *args, **kw)
  File "/usr/local/zenoss/Products/ZenRRD/zenperfsnmp.py", line 405, in
storeValues
    self.storeRRD(deviceName, oid, value)
  File "/usr/local/zenoss/Products/ZenRRD/zenperfsnmp.py", line 431, in
storeRRD    oidData = self.proxies[device].oidMap[oid]
exceptions.KeyError: '.1.3.6.1.2.1.2.2.1.16.44'


 

>>> On Wed, Sep 13, 2006 at  8:25 AM, in message
<[EMAIL PROTECTED]>,
[EMAIL PROTECTED] wrote: 
> Hey Dave,
> 
> Here's a simple thing to check: are you ending your OIDs in your
config 
> with .0?
> That's what's coming back from the walk.
> 
> If you get really stuck, do this:
> 
>     $ strace - s 10000 zenperfsnmp run - v 10 - d my- router
2>/tmp/trace
>     $ gzip /tmp/trace
> 
> And then send /tmp/trace to me (off list).  That will tell me what's

> going on from a config and packet level.  It will also contain 
> passwords, community strings and the like, so make all those
generic.
> 
> Things I will be looking for:
> 
>     Is the device being scanned?
>     Are the custom OIDs being passed to zenperfsnmp?
>     Are packets coming back when those OIDs are requested?
> 
> - Eric
> 
> DAVE CUSHING wrote:
>> I've tried that a number of times and haven't had any success.  I
am
>> going to bring up another instance of ZenOSS, because I have 90
switches
>> and 40 servers in this one and trying to find stuff in the logs is
>> getting a little onerous.  It will also give me a staging area for
>> testing some changes before implementing them.
>>
>> If you would have any ideas, I would appreciate it because I am
trying
>> to justify sticking with ZenOSS over a competitor (commercial
software)
>> and if we can get the oids working it would be a huge bonus.
>>
>>   
>>>>> [EMAIL PROTECTED]  >>>
>>>>>         
>> Hi Dave,
>>
>> By default, zenperfsnmp reloads its configuration every half hour. 
So, 
>> it can take as long as 30 minutes for your configuration changes to
get 
>> loaded by zenperfsnmp and for collection to begin.
>>
>> Try restarting zenperfsnmp and check that the graphs exist.  You can

>> also run zenperfsnmp once against a single device which is useful
for 
>> debugging:
>>
>>     $ zenperfsnmp run - v 10 - d myrouter
>>
>> Once zenperfsnmp begins collection, it will take a few cycles for
the 
>> graphs to have enough data to show any values.
>>   
>> - Eric
>>
>> DAVE CUSHING wrote:
>>   
>>> I have added a perfconf oid for tracking the current number of
>>>     
>> sessions
>>   
>>> on my Fortinet Fortigate Firewall.
>>>
>>> Here is an output from snmpwalk:
>>>
>>> zenoss:/usr/local/zenoss/log # snmpwalk - v2c - cpublic
xx.xx.xx.xx
>>> 1.3.6.1.4.1.12356.1.10
>>> SNMPv2- SMI::enterprises.12356.1.10.0 = Gauge32: 2062
>>>
>>> zenoss:/usr/local/zenoss/log # snmpwalk - v1 - cpublic xx.xx.xx.xx
>>> 1.3.6.1.4.1.12356.1.10
>>> SNMPv2- SMI::enterprises.12356.1.10.0 = Gauge32: 1949
>>>
>>> So I know the firewall is answering v1 and v2c SNMP queries
correctly.
>>>
>>> I set the perfconf counter up as type gauge, with the OID as above
and
>>>     
>> a
>>   
>>> format string of %1.0lf
>>> I have the graph set up as well, but I still get no graph output
at
>>>     
>> all.
>>   
>>>  Where should I be checking to see if it is gathering the data or
>>> getting an error?  Or does someone have a pointer as to something
else
>>>     
>> I
>>   
>>> could be doing wrong?
>>>     
> 
> _______________________________________________
> zenoss- users mailing list
> zenoss- [EMAIL PROTECTED]
> http://lists.zenoss.org/mailman/listinfo/zenoss- users

_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to