I made my Cisco device generate snmp trap authenticationFailure which is sent
to Zenoss. Here is the tcpdump decode of this real-life trap packet (SNMP part
only):
Code:
No. Time Source Destination Protocol
Info
1 17:10:23.311967 172.30.41.3 172.24.171.20 SNMP
sNMPv2-Trap
Simple Network Management Protocol
version: v2c (1)
community: public
data: sNMPv2-Trap (7)
sNMPv2-Trap
request-id: 1096
error-status: noError (0)
error-index: 0
variable-bindings: 5 items
Item
name: 1.3.6.1.2.1.1.3.0 (SNMPv2-MIB::sysUpTime.0)
valueType: value (0)
value: simple (4294967295)
value: simple (4294967295)
application-wide: timeticks-value (3)
timeticks-value: 74361756
Item
name: 1.3.6.1.6.3.1.1.4.1.0 (SNMPv2-MIB::snmpTrapOID.0)
valueType: value (0)
value: simple (4294967295)
simple: objectID-value (2)
Value: OID: SNMPv2-MIB::authenticationFailure
Item
name: 1.3.6.1.4.1.9.2.1.5.0
(SNMPv2-SMI::enterprises.9.2.1.5.0)
valueType: value (0)
value: simple (4294967295)
value: simple (4294967295)
application-wide: ipAddress-value (0)
ipAddress-value: 172.24.171.10 (172.24.171.10)
Item
name: 1.3.6.1.4.1.9.9.412.1.1.1.0
(SNMPv2-SMI::enterprises.9.9.412.1.1.1.0)
valueType: value (0)
value: simple (4294967295)
simple: integer-value (0)
Value: INTEGER: 1
Item
name: 1.3.6.1.4.1.9.9.412.1.1.2.0
(SNMPv2-SMI::enterprises.9.9.412.1.1.2.0)
valueType: value (0)
value: simple (4294967295)
simple: string-value (1)
Value: STRING: "172.24.171.10"
As you can see in the actual packet each OID has a trailing zero.
Now, here is how this CISCO-SNMP-TARGET-EXT-MIB looks like in Zenoss mib
browser:
> Name OID Type
> cExtSnmpTargetAddrEntry 1.3.6.1.4.1.9.9.412.1.2.1 row
> cExtSnmpTargetAddrIntIfIndex 1.3.6.1.4.1.9.9.412.1.2.1.1 column
> cExtSnmpTargetAddrTable 1.3.6.1.4.1.9.9.412.1.2 table
> cExtSnmpTargetAuthAddr 1.3.6.1.4.1.9.9.412.1.1 node
> cExtSnmpTargetAuthInetAddr 1.3.6.1.4.1.9.9.412.1.1.2 scalar
> cExtSnmpTargetAuthInetType 1.3.6.1.4.1.9.9.412.1.1.1 scalar
> ciscoSnmpTargetExtMIB 1.3.6.1.4.1.9.9.412 node
> ciscoSnmpTargetExtMIBCompliances 1.3.6.1.4.1.9.9.412.2.1 node
> ciscoSnmpTargetExtMIBConformance 1.3.6.1.4.1.9.9.412.2 node
> ciscoSnmpTargetExtMIBGroups 1.3.6.1.4.1.9.9.412.2.2 node
> ciscoSnmpTargetExtMIBObjects 1.3.6.1.4.1.9.9.412.1 node
So as we can see there are NO trailing zeros in Zenoss compiled mibs. So what
it looks like is that Zenoss is taking the first matching part in each OID and
appends the remaining part as digits. This could be a reasonable behavior BUT
IT DIDN'T WORK LIKE THIS PRIOR release 2.3.0. I guess it was just trimming off
the trailing unrecognized digits in previous versions.
Could someone confirm this behavior as new in version 2.3.0 or please point me
in right direction of correcting this error?
-------------------- m2f --------------------
Read this topic online here:
http://forums.zenoss.com/viewtopic.php?p=28382#28382
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
