This same thing was happening to me...i found this in
/opt/zenoss/Products/ZenEvents/zentrap.py:
An array of vendor OIDs that insert a "0" in the mib, so I appended this list
to include the ones that were giving me trouble (added are in bold)...it works
for me hopefully for you too.
# Some vendors form their trap MIBs to insert a 0 before the
# specific part of the v1 trap, but the device doesn't actually
# send the 0. Unfortunately we have to make explicit exceptions
# for these to get the OIDs decoded properly.
expandableV1Prefixes = (
'1.3.6.1.2.1.17', # Spanning Tree Protocol
'1.3.6.1.4.1.1916', # Extreme Networks
'1.3.6.1.4.1.6247', # Comtech
'1.3.6.1.4.1.8072', # Net-SNMP
'1.3.6.1.4.1.12394.1.2', # Rainbow
'1.3.6.1.4.1.1991', # Foundry
'1.3.6.1.4.1.6889.2.17.1', # Avaya
'1.3.6.1.4.1.476.1.42.3.3', # Liebert
'1.3.6.1.4.1.9.9.41.2', # Cisco-Syslog
)
-------------------- m2f --------------------
Read this topic online here:
http://forums.zenoss.com/viewtopic.php?p=29375#29375
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
