Ok, so the problem with modeling the device was that zenoss apparently forgot
the custom snmp community after adding the device, and set it back to public,
so all SNMP was failing. Fixed that and now I'm modeled fine.
The event came pre-configured with Zenoss with the following transform:
Code:
index = None
for key, value in evt.__dict__.items():
if key.find('1.3.6.1.2.1.2.2.1.1') >= 0:
index = value
break
if index is not None:
for obj in device.os.interfaces.objectItems():
if obj[1].ifindex == index:
evt.component = obj[1].id
break
And I had to change the key.find to look for ifIndex, since that OID was being
translated, so the transform didn't find it.
Now my SNMP linkUp/Down traps are getting the component set properly. I'm
having trouble getting the event correlation work, so a linkUp clears the
associated linkDown event, but if I can't figure that out, I'll start a new
thread.
Thanks all!
-------------------- m2f --------------------
Read this topic online here:
http://forums.zenoss.com/viewtopic.php?p=36627#36627
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
