Guys, I am getting desperate here [Shocked] I did a fresh stack install of Zenoss 2.3 on a different CentOS 5 server and I am getting the same results - most of the fields in the incoming traps have trailing numbers in OIDs. Most of the times it's trailing .0 (zero), for some traps (interface related mostly) I have index numbers. Here are a few examples:
> snmp trap linkDown > community public > ifDescr.9 E1 5/4 > ifIndex.9 9 > ifType.9 18 > snmpTrapOID.0 (1, 3, 6, 1, 6, 3, 1, 1, 5, 3) > sysUpTimeInstance 71904358 > > snmp trap ciscoConfigManEvent > ccmHistoryEventCommandSource.108 2 > ccmHistoryEventConfigDestination.108 6 > ccmHistoryEventConfigSource.108 4 > community public > snmpTrapOID.0 (1, 3, 6, 1, 4, 1, 9, 9, 43, 2, 0, 1) > sysUpTimeInstance 208056579 This breaks all the event transforms associated with these traps!!! I also noticed that after upgrade to 2.3 the summary line in the event console for the traps which don't have corresponding mib loaded began to look like zenoss is doing partial mib match. Here is an example how the trap parsing changed (note - mibs DID NOT change during upgrade): Before upgrade: snmp trap 1.3.6.1.4.1.6876.4.1.0.4 After upgrade: snmp trap enterprises.6876.4.1.0.4 I would really hate to downgrade to 2.2.3 because I have to many event transforms to change [Evil or Very Mad] Zenoss gurus - PLEASE HELP! -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=29098#29098 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
