Hi Todd,
Can you pull down the last change I made to zentrap.py and see if that
doesn't fix the problem for you?
http://dev.zenoss.org/trac/changeset/5627
Thanks!
-Eric
Todd Davis wrote:
> Something strange has started happening with SNMP trap handling in the 2.0
> beta versions. I first noticed this when upgrading to 1.9.6. I have
> upgraded now to 1.9.7 and am still having this problem.
>
> Here's the situation. I have a trap I'm getting that should report as:
> rPDUNearOverload. The OID is .1.3.6.1.4.1.318.0.274. The problem is Zenoss
> is reporting it as trap: apc, which I'm guessing it is matching as
> .1.3.6.1.4.1.318. The MIBS are correctly loaded. I even tried deleting and
> re-adding all of my MIBS. Incidentally, this was all working under 1.1.2.
>
> In order to get Zenoss to show me the full OID, I removed the powernet MIB
> (APC's MIB) and waited for another trap. Now it shows that it received a
> trap: enterprises (which would match .1.3.6.1.4.1).
>
> Has anyone else been seeing problems with Zenoss mapping MIBS/traps in the
> 1.9.x series?
>
>
>
>
> _______________________________________________
> zenoss-users mailing list
> [email protected]
> http://lists.zenoss.org/mailman/listinfo/zenoss-users
>
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
