If you import a MIB - any MIB - then TRAPs that are defined in that MIB should be automatically interpreted by the zentrap daemon as it processes incoming TRAPs. Thus, you should see "words" in OIDs rather than dotted decimal.

If you haven't already found it, my Zenoss Event Management paper may help - https://www.skills-1st.co.uk/papers/jane/zenoss4-events/ .

Cheers,

Jane

Email: jane.curry@skills-1st.co.uk    Web: https://www.skills-1st.co.uk

Hi Jane!

Thank You for replay! I loaded the proper MIB file and the trap is interpeted good. My problem is, recieved trap doesn't contain that information what I need. I can query the neede information with that command:

snmpwalk -v2c -c 1.3.6.1.4.1.9.9.46.1.6.1.1.17

I don't know how could use this in the event transformation. I've read from netsnmp modul of python and it could be good for me:

import netsnmp

oid = netsnmp.varbind("3.6.1.4.1.9.9.46.1.6.1.1.17")

var = netsnmp.snmpwalk (oid, Version = 2c, DestHost='192.168.1.1', Community = 'readcommunity')

I don't know exactly how to install python netsnmp modul on CentOS under Zenoss 4.2.5. Can You help me

Thank You for your book it is very good and useable!

All Best

Hi!

Yes it is a Cisco device. Unfortunate when a trunk port goes down I get a trunk port dynamic status change trap. It's contained an integer 1 means UP 2 DOWN. But it isn't contained which interface. So that when I get an interface down trap, I'd like query is it tunk port or not. This information I get next command:

snmpwalk -v2c -c 1.3.6.1.4.1.9.9.46.1.6.1.1.17

It should use in the event transform section.

The netsnmp is on Zenoss server, but I need net-snmp-python modul. I think I could use netsnmp.snmpwalk python method. I don't know how!

Thanks your answer!