Bad OIDS added to zenperfsnmp list

[Doug Szarmach]

Doug Szarmach [http://community.zenoss.org/people/dszarmach] created the discussion

"Bad OIDS added to zenperfsnmp list"

To view the discussion, visit: http://community.zenoss.org/message/70677#70677

--------------------------------------------------------------
The following is in debug output from "zenperfsnmp run" with -v10, including the first line which is a bad OID (missing .x suffix)

'1.3.6.1.2.1.2.2.1.14': [('ifInErrors', *(BAD via SNMP GET)*
                                    'Devices/ccswi01/ifInErrors_ifInErrors',
                                    'DERIVE',
                                    '',
                                    '0',
                                    None)],
          '1.3.6.1.2.1.2.2.1.14.10101': [('GigabitEthernet0/1', *(GOOD via SNMP GET)*
                                          'Devices/ccswi01/os/interfaces/GigabitEthernet0_1/ifInErrors_ifInErrors',
                                          'DERIVE',
                                          '',
                                          '0',
                                          None)],
          '1.3.6.1.2.1.2.2.1.14.10102': [('GigabitEthernet0/2', *(GOOD via SNMP GET)*
                                          'Devices/ccswi01/os/interfaces/GigabitEthernet0_2/ifInErrors_ifInErrors',
                                          'DERIVE',
                                          '',
                                          '0',
                                          None)],
          '1.3.6.1.2.1.2.2.1.14.10103': [('GigabitEthernet0/3', *(GOOD via SNMP GET)*
                                          'Devices/ccswi01/os/interfaces/GigabitEthernet0_3/ifInErrors_ifInErrors',
                                          'DERIVE',
                                          '',
                                          '0',
                                          None)],

This leads to constant errors in log:

2012-12-21 13:42:21,579 ERROR zen.zenperfsnmp: SNMP get returned empty value: ccswi01 1.3.6.1.2.1.2.2.1.14
2012-12-21 13:42:21,579 WARNING zen.zenperfsnmp: Error reading value for ['ifInErrors'] (1.3.6.1.2.1.2.2.1.14) on ccswi01

Is happening for the following and appears to be tied to the default "zenoss.snmp.InterfaceMap":

1.3.6.1.2.1.2.2.1.8
1.3.6.1.2.1.2.2.1.20
1.3.6.1.2.1.2.2.1.14
1.3.6.1.2.1.31.1.1.1.6
1.3.6.1.2.1.31.1.1.1.7
1.3.6.1.2.1.31.1.1.1.10
1.3.6.1.2.1.31.1.1.1.11

Any idea on how to prevent all of these base OIDs from populating a device's OID list if they lack the proper .X suffix?
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/70677#70677]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[nilie]

nilie [http://community.zenoss.org/people/nilie] created the discussion

"Re: Bad OIDS added to zenperfsnmp list"

To view the discussion, visit: http://community.zenoss.org/message/70849#70849

--------------------------------------------------------------
First we have to clear some misunderstandings. You can't use snmpget on 1.3.6.1.2.1.2.2.1.14 because it is not a leaf OID, it is a subtree and an snmpwalk will show you what this subtree contains. OID 1.3.6.1.2.1.2.2.1.14.10101 works with snmpget because it is a leaf OID returning ifInErrors for the interface with index 10101.
From what I can see, it seems there are some interfaces which do not support these leaf OIDs. The last four for example means that Zenoss belives they are 64bit counters but your device has only 32bit counters.
To answer your question, if you want to remove the base OID you can do it in the template definition. If you want to remove just for some interface, disable monitoring of that interface.
In order for me to be more helpful, can you please provide this information :
* what is the manufacturer and model of the device you're monitoring
* what is the result of snmpwalk for 1.3.6.1.2.1.2.2.1.14
* what snmp version are you using for that device
* check event console for any debug event related to your device (by default the debug events are not being displayed) and post here the content of one of these messages

Hoping this will help
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/70849#70849]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[nilie]

nilie [http://community.zenoss.org/people/nilie] created the discussion

"Re: Bad OIDS added to zenperfsnmp list"

To view the discussion, visit: http://community.zenoss.org/message/70850#70850

--------------------------------------------------------------
Warning! Since we're talking about component templates, be very, very careful before modifying them.
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/70850#70850]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[Doug Szarmach]

Doug Szarmach [http://community.zenoss.org/people/dszarmach] created the discussion

"Re: Bad OIDS added to zenperfsnmp list"

To view the discussion, visit: http://community.zenoss.org/message/70853#70853

--------------------------------------------------------------
Invalid SNMP GET on the subtree is via Zenoss itself is and thus the root of my problem:

2012-12-21 13:42:21,579 ERROR zen.zenperfsnmp: SNMP get returned empty value: ccswi01 1.3.6.1.2.1.2.2.1.14

After modeling the device the error above repeats every time data is collected.  You may be on to something though - see the snmp walk below - output is counter32 and device shows applied template ethernetCsmacd_64




1.

cisco WS-C3560G-48TS (PowerPC405) processor (revision D0) with 131072K bytes of memory.
Switch Ports Model              SW Version            SW Image
------ ----- -----              ----------            ----------
*    1 52    WS-C3560G-48TS     15.0(2)SE             C3560-IPSERVICESK9-M


2.

snmpwalk -v2c -c XXXXXXX ccswi01 1.3.6.1.2.1.2.2.1.14
IF-MIB::ifInErrors.1 = Counter32: 0
IF-MIB::ifInErrors.200 = Counter32: 0
IF-MIB::ifInErrors.5002 = Counter32: 0
IF-MIB::ifInErrors.10101 = Counter32: 0
IF-MIB::ifInErrors.10102 = Counter32: 0
IF-MIB::ifInErrors.10103 = Counter32: 0
IF-MIB::ifInErrors.10104 = Counter32: 0
IF-MIB::ifInErrors.10105 = Counter32: 0
IF-MIB::ifInErrors.10106 = Counter32: 0
IF-MIB::ifInErrors.10107 = Counter32: 0
IF-MIB::ifInErrors.10108 = Counter32: 0
IF-MIB::ifInErrors.10109 = Counter32: 0
IF-MIB::ifInErrors.10110 = Counter32: 0
IF-MIB::ifInErrors.10111 = Counter32: 0
IF-MIB::ifInErrors.10112 = Counter32: 0
IF-MIB::ifInErrors.10113 = Counter32: 0
IF-MIB::ifInErrors.10114 = Counter32: 0
IF-MIB::ifInErrors.10115 = Counter32: 0
IF-MIB::ifInErrors.10116 = Counter32: 0
IF-MIB::ifInErrors.10117 = Counter32: 0
IF-MIB::ifInErrors.10118 = Counter32: 0
IF-MIB::ifInErrors.10119 = Counter32: 0
IF-MIB::ifInErrors.10120 = Counter32: 0
IF-MIB::ifInErrors.10121 = Counter32: 0
IF-MIB::ifInErrors.10122 = Counter32: 0
IF-MIB::ifInErrors.10123 = Counter32: 0
IF-MIB::ifInErrors.10124 = Counter32: 0
IF-MIB::ifInErrors.10125 = Counter32: 0
IF-MIB::ifInErrors.10126 = Counter32: 0
IF-MIB::ifInErrors.10127 = Counter32: 0
IF-MIB::ifInErrors.10128 = Counter32: 0
IF-MIB::ifInErrors.10129 = Counter32: 0
IF-MIB::ifInErrors.10130 = Counter32: 0
IF-MIB::ifInErrors.10131 = Counter32: 0
IF-MIB::ifInErrors.10132 = Counter32: 0
IF-MIB::ifInErrors.10133 = Counter32: 0
IF-MIB::ifInErrors.10134 = Counter32: 0
IF-MIB::ifInErrors.10135 = Counter32: 0
IF-MIB::ifInErrors.10136 = Counter32: 0
IF-MIB::ifInErrors.10137 = Counter32: 0
IF-MIB::ifInErrors.10138 = Counter32: 0
IF-MIB::ifInErrors.10139 = Counter32: 0
IF-MIB::ifInErrors.10140 = Counter32: 0
IF-MIB::ifInErrors.10141 = Counter32: 0
IF-MIB::ifInErrors.10142 = Counter32: 0
IF-MIB::ifInErrors.10143 = Counter32: 0
IF-MIB::ifInErrors.10144 = Counter32: 0
IF-MIB::ifInErrors.10145 = Counter32: 0
IF-MIB::ifInErrors.10146 = Counter32: 0
IF-MIB::ifInErrors.10147 = Counter32: 0
IF-MIB::ifInErrors.10148 = Counter32: 0
IF-MIB::ifInErrors.10149 = Counter32: 0
IF-MIB::ifInErrors.10150 = Counter32: 0
IF-MIB::ifInErrors.10151 = Counter32: 0
IF-MIB::ifInErrors.10152 = Counter32: 0
IF-MIB::ifInErrors.10501 = Counter32: 0

3.

zSnmpVer - v2c

4.

no severity "debug" events for device
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/70853#70853]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[Doug Szarmach]

Doug Szarmach [http://community.zenoss.org/people/dszarmach] created the discussion

"Re: Bad OIDS added to zenperfsnmp list"

To view the discussion, visit: http://community.zenoss.org/message/70854#70854

--------------------------------------------------------------
Device had 64 bit counters working:

IF-MIB::ifHCInOctets.1 = Counter64: 15261
IF-MIB::ifHCInOctets.200 = Counter64: 5291268276
IF-MIB::ifHCInOctets.5002 = Counter64: 554803913257
IF-MIB::ifHCInOctets.10101 = Counter64: 28921118
IF-MIB::ifHCInOctets.10102 = Counter64: 29061432
IF-MIB::ifHCInOctets.10103 = Counter64: 0
IF-MIB::ifHCInOctets.10104 = Counter64: 0


However, as no ifHCInErrors exists, only 32 bit counters avilable on these:

snmpwalk -v2c -c XXXXXXX ccswi01 ifInErrors
IF-MIB::ifInErrors.1 = Counter32: 0
IF-MIB::ifInErrors.200 = Counter32: 0
IF-MIB::ifInErrors.5002 = Counter32: 0
IF-MIB::ifInErrors.10101 = Counter32: 0
IF-MIB::ifInErrors.10102 = Counter32: 0

snmpwalk -v2c -c XXXXXX ccswi01 ifHCInErrors
ifHCInErrors: Unknown Object Identifier (Sub-id not found: (top) -> ifHCInErrors)

I guess it makes sense - errors should never be increasing fast enough to roll a 32 bit counter too quickly.

Back to the beginning again then - why would Zenoss want to snmp get on the ifInErrors subtree instead of the individual leaf components?
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/70854#70854]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[nilie]

nilie [http://community.zenoss.org/people/nilie] created the discussion

"Re: Bad OIDS added to zenperfsnmp list"

To view the discussion, visit: http://community.zenoss.org/message/70862#70862

--------------------------------------------------------------
First of all, my experience taught me to look at error messages for clues but not to blindly trust them as 100% true. Zenoss is using the same template for all interfaces having the same ifType because it is a component template, so if it works for at least one interface, then we must look at something else here. Can you please do a snmpwalk for 1.3.6.1.2.1.2.2.1.3 (ifType) and 1.3.6.1.2.1.2.2.1.2 (ifDescr) and post the results here ?
Second, I'm a little bit puzzled that you don't see any debug event. Usually this type of scenario results in debug events with message like "*Error reading value for "Ethernet1/7" on TRTMXBC1S2 (oid .1.3.6.1.2.1.2.2.1.14.436232192 is bad)*" every 5 minutes (the snmp perf polling interval) in the event console. This kind of event is extremely useful because it points you exactly to the OID that is not working.
Finally to answer your question, although I might be wrong here,  I believe for component templates Zenoss is getting those values  by doing a snmpwalk for the base OIDs (as opposed to doing multiple snmpget on each interface OID) and retaining only the values for the interfaces that are being monitored. It is much more efficient than building snmp queries for each OID like other network monitoring systems (MRTG - I'm looking at you) are doing.
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/70862#70862]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[Doug Szarmach]

Doug Szarmach [http://community.zenoss.org/people/dszarmach] created the discussion

"Re: Bad OIDS added to zenperfsnmp list"

To view the discussion, visit: http://community.zenoss.org/message/70863#70863

--------------------------------------------------------------
IF-MIB::ifType.1 = INTEGER: propVirtual(53)
IF-MIB::ifType.200 = INTEGER: propVirtual(53)
IF-MIB::ifType.5002 = INTEGER: propVirtual(53)
IF-MIB::ifType.10101 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10102 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10103 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10104 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10105 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10106 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10107 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10108 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10109 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10110 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10111 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10112 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10113 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10114 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10115 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10116 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10117 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10118 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10119 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10120 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10121 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10122 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10123 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10124 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10125 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10126 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10127 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10128 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10129 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10130 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10131 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10132 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10133 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10134 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10135 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10136 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10137 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10138 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10139 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10140 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10141 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10142 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10143 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10144 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10145 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10146 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10147 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10148 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10149 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10150 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10151 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10152 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.10501 = INTEGER: other(1)


IF-MIB::ifDescr.1 = STRING: Vlan1
IF-MIB::ifDescr.200 = STRING: Vlan200
IF-MIB::ifDescr.5002 = STRING: Port-channel2
IF-MIB::ifDescr.10101 = STRING: GigabitEthernet0/1
IF-MIB::ifDescr.10102 = STRING: GigabitEthernet0/2
IF-MIB::ifDescr.10103 = STRING: GigabitEthernet0/3
IF-MIB::ifDescr.10104 = STRING: GigabitEthernet0/4
IF-MIB::ifDescr.10105 = STRING: GigabitEthernet0/5
IF-MIB::ifDescr.10106 = STRING: GigabitEthernet0/6
IF-MIB::ifDescr.10107 = STRING: GigabitEthernet0/7
IF-MIB::ifDescr.10108 = STRING: GigabitEthernet0/8
IF-MIB::ifDescr.10109 = STRING: GigabitEthernet0/9
IF-MIB::ifDescr.10110 = STRING: GigabitEthernet0/10
IF-MIB::ifDescr.10111 = STRING: GigabitEthernet0/11
IF-MIB::ifDescr.10112 = STRING: GigabitEthernet0/12
IF-MIB::ifDescr.10113 = STRING: GigabitEthernet0/13
IF-MIB::ifDescr.10114 = STRING: GigabitEthernet0/14
IF-MIB::ifDescr.10115 = STRING: GigabitEthernet0/15
IF-MIB::ifDescr.10116 = STRING: GigabitEthernet0/16
IF-MIB::ifDescr.10117 = STRING: GigabitEthernet0/17
IF-MIB::ifDescr.10118 = STRING: GigabitEthernet0/18
IF-MIB::ifDescr.10119 = STRING: GigabitEthernet0/19
IF-MIB::ifDescr.10120 = STRING: GigabitEthernet0/20
IF-MIB::ifDescr.10121 = STRING: GigabitEthernet0/21
IF-MIB::ifDescr.10122 = STRING: GigabitEthernet0/22
IF-MIB::ifDescr.10123 = STRING: GigabitEthernet0/23
IF-MIB::ifDescr.10124 = STRING: GigabitEthernet0/24
IF-MIB::ifDescr.10125 = STRING: GigabitEthernet0/25
IF-MIB::ifDescr.10126 = STRING: GigabitEthernet0/26
IF-MIB::ifDescr.10127 = STRING: GigabitEthernet0/27
IF-MIB::ifDescr.10128 = STRING: GigabitEthernet0/28
IF-MIB::ifDescr.10129 = STRING: GigabitEthernet0/29
IF-MIB::ifDescr.10130 = STRING: GigabitEthernet0/30
IF-MIB::ifDescr.10131 = STRING: GigabitEthernet0/31
IF-MIB::ifDescr.10132 = STRING: GigabitEthernet0/32
IF-MIB::ifDescr.10133 = STRING: GigabitEthernet0/33
IF-MIB::ifDescr.10134 = STRING: GigabitEthernet0/34
IF-MIB::ifDescr.10135 = STRING: GigabitEthernet0/35
IF-MIB::ifDescr.10136 = STRING: GigabitEthernet0/36
IF-MIB::ifDescr.10137 = STRING: GigabitEthernet0/37
IF-MIB::ifDescr.10138 = STRING: GigabitEthernet0/38
IF-MIB::ifDescr.10139 = STRING: GigabitEthernet0/39
IF-MIB::ifDescr.10140 = STRING: GigabitEthernet0/40
IF-MIB::ifDescr.10141 = STRING: GigabitEthernet0/41
IF-MIB::ifDescr.10142 = STRING: GigabitEthernet0/42
IF-MIB::ifDescr.10143 = STRING: GigabitEthernet0/43
IF-MIB::ifDescr.10144 = STRING: GigabitEthernet0/44
IF-MIB::ifDescr.10145 = STRING: GigabitEthernet0/45
IF-MIB::ifDescr.10146 = STRING: GigabitEthernet0/46
IF-MIB::ifDescr.10147 = STRING: GigabitEthernet0/47
IF-MIB::ifDescr.10148 = STRING: GigabitEthernet0/48
IF-MIB::ifDescr.10149 = STRING: GigabitEthernet0/49
IF-MIB::ifDescr.10150 = STRING: GigabitEthernet0/50
IF-MIB::ifDescr.10151 = STRING: GigabitEthernet0/51
IF-MIB::ifDescr.10152 = STRING: GigabitEthernet0/52
IF-MIB::ifDescr.10501 = STRING: Null0
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/70863#70863]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[nilie]

nilie [http://community.zenoss.org/people/nilie] created the discussion

"Re: Bad OIDS added to zenperfsnmp list"

To view the discussion, visit: http://community.zenoss.org/message/70870#70870

--------------------------------------------------------------
I did some research for the error message you receive in the log and I found a document on this forum (see http://community.zenoss.org/thread/18556 http://community.zenoss.org/thread/18556 ) but I don't know if it applies to you. It is the same type of error message but it is related to regular templates and not to component templates.
Normally the standard ethernetCsmacd_64 template that comes by default in Zenoss should be working fine. Did you make any change to the standard templates, did you move them or is this a template you created ?
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/70870#70870]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[Doug Szarmach]

Doug Szarmach [http://community.zenoss.org/people/dszarmach] created the discussion

"Re: Bad OIDS added to zenperfsnmp list"

To view the discussion, visit: http://community.zenoss.org/message/70836#70836

--------------------------------------------------------------
Adding .0 as per that URL caused 60+ errors on the OID instead of the single error for the top level subtree entry.

Template is unmodified standard.

Every 5 minutes I get 7 errors and 7 warnings per device:

2013-01-08 13:57:57,152 ERROR zen.zenperfsnmp: SNMP get returned empty value: ccswi01 1.3.6.1.2.1.31.1.1.1.6
2013-01-08 13:57:57,474 WARNING zen.zenperfsnmp: Error reading value for ['ifHCInOctets'] (1.3.6.1.2.1.31.1.1.1.6) on ccswi01
2013-01-08 13:57:57,477 ERROR zen.zenperfsnmp: SNMP get returned empty value: ccswi01 1.3.6.1.2.1.31.1.1.1.7
2013-01-08 13:57:57,477 WARNING zen.zenperfsnmp: Error reading value for ['ifHCInUcastPkts'] (1.3.6.1.2.1.31.1.1.1.7) on ccswi01
2013-01-08 13:57:57,480 ERROR zen.zenperfsnmp: SNMP get returned empty value: ccswi01 1.3.6.1.2.1.31.1.1.1.10
2013-01-08 13:57:57,481 WARNING zen.zenperfsnmp: Error reading value for ['ifHCOutOctets'] (1.3.6.1.2.1.31.1.1.1.10) on ccswi01
2013-01-08 13:57:57,484 ERROR zen.zenperfsnmp: SNMP get returned empty value: ccswi01 1.3.6.1.2.1.31.1.1.1.11
2013-01-08 13:57:57,484 WARNING zen.zenperfsnmp: Error reading value for ['ifHCOutUcastPkts'] (1.3.6.1.2.1.31.1.1.1.11) on ccswi01
2013-01-08 13:57:57,562 ERROR zen.zenperfsnmp: SNMP get returned empty value: ccswi01 1.3.6.1.2.1.2.2.1.14
2013-01-08 13:57:57,563 WARNING zen.zenperfsnmp: Error reading value for ['ifInErrors'] (1.3.6.1.2.1.2.2.1.14) on ccswi01
2013-01-08 13:57:57,566 ERROR zen.zenperfsnmp: SNMP get returned empty value: ccswi01 1.3.6.1.2.1.2.2.1.20
2013-01-08 13:57:57,567 WARNING zen.zenperfsnmp: Error reading value for ['ifOutErrors'] (1.3.6.1.2.1.2.2.1.20) on ccswi01
2013-01-08 13:57:57,571 ERROR zen.zenperfsnmp: SNMP get returned empty value: ccswi01 1.3.6.1.2.1.2.2.1.8
2013-01-08 13:57:57,571 WARNING zen.zenperfsnmp: Error reading value for ['ifOperStatus'] (1.3.6.1.2.1.2.2.1.8) on ccswi01

These directly match to the 7 data sources in the ethernetCsmacd_64 template:


Loading Image... Loading Image...
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/70836#70836]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[Doug Szarmach]

Doug Szarmach [http://community.zenoss.org/people/dszarmach] created the discussion

"Re: Bad OIDS added to zenperfsnmp list"

To view the discussion, visit: http://community.zenoss.org/message/70872#70872

--------------------------------------------------------------
I guess I should add that graphs are working fine so I know the collection of the leaf data is fine - the only indication of trouble is the constant error spam in /opt/zenoss/log/zenperfsnmp.log.

I will try to grab a tcpdump level capture to determine if zenoss really is attempting to snmpget on the top OID.
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/70872#70872]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[Doug Szarmach]

Doug Szarmach [http://community.zenoss.org/people/dszarmach] created the discussion

"Re: Bad OIDS added to zenperfsnmp list"

To view the discussion, visit: http://community.zenoss.org/message/70873#70873

--------------------------------------------------------------
Confirmed - zenoss process really is sending a snmpget on the subtree OID

(odd this happens after all the good collection at top - packets are listed in order of capture)

So Zenoss collects all data good on leafs, then doubles back and sends invalid gets on the subtree OIDs....but why?

Loading Image... Loading Image...
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/70873#70873]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[nilie]

nilie [http://community.zenoss.org/people/nilie] created the discussion

"Re: Bad OIDS added to zenperfsnmp list"

To view the discussion, visit: http://community.zenoss.org/message/70876#70876

--------------------------------------------------------------
I guess it is because you did bound the component template once again at the device level which is incorrect. The system polls it once correctly using the component template in /Devices and then tries again with the same template bound at the device level in /Network/Switch or where ever your device is but here it is not working since you have to specifi the ifIndex. Go at the device level and unbound ethernetCsmacd template if thre is one.
I would suggest you to read the documentation section pertaining to differences between regular and component templates since Zenoss treats them differently.
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/70876#70876]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[Doug Szarmach]

Doug Szarmach [http://community.zenoss.org/people/dszarmach] created the discussion

"Re: Bad OIDS added to zenperfsnmp list"

To view the discussion, visit: http://community.zenoss.org/message/70877#70877

--------------------------------------------------------------
Looks clean now after modify of zDeviceTemplates on /Devices to be only "Device" and not "Device ethernetCsmacd_64".

Still not sure how this got here but I suspect it was related to a zenpack of some sort.

Marked as correct answer - thanks!
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/70877#70877]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[nilie]

nilie [http://community.zenoss.org/people/nilie] created the discussion

"Re: Bad OIDS added to zenperfsnmp list"

To view the discussion, visit: http://community.zenoss.org/message/70874#70874

--------------------------------------------------------------
Looking at the image you attached I found something that seems strange to me. On both my Zenoss core v3.1 and v4.2 instances, ethernetCsmacd_64 template is not bound at device level. How did yours get in there ? Loading Image... Loading Image...
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/70874#70874]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[Doug Szarmach]

Doug Szarmach [http://community.zenoss.org/people/dszarmach] created the discussion

"Re: Bad OIDS added to zenperfsnmp list"

To view the discussion, visit: http://community.zenoss.org/message/70875#70875

--------------------------------------------------------------
What is your zDeviceTemplates setting under "Config Properties" for /Device?

Mine is set to "Device ethernetCsmacd_64" but I did not set this.  Could a zenpack have done this?
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/70875#70875]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]