Unknown MIBs in traps from 2510-24

[NdK]

Hello all.

I'm having troubles trying to setup a trap monitor since I get a couple of unknown MIBs. From snmpttunknown.log:

Wed Jul 18 12:56:10 2012: Unknown trap (.1.3.6.1.4.1.11.2.14.12.1.0.5) received from 10.1.86.2 at:
Value 0: 10.1.86.2
Value 1: 10.1.86.2
Value 2: 14:0:04:28.50
Value 3: .1.3.6.1.4.1.11.2.14.12.1.0.5
Value 4: 10.1.86.2
Value 5: mycomm
Value 6: .1.3.6.1.4.1.11.2.14.12.1
Value 7:
Value 8:
Value 9:
Value 10:
Ent Value 0: .1.3.6.1.4.1.11.2.14.11.1.7.2.1.4.17=12
Ent Value 1: .1.3.6.1.4.1.11.2.14.11.1.7.2.1.5.17=2
Ent Value 2: .1.3.6.1.4.1.11.2.14.11.1.7.2.1.6.17=2
Ent Value 3: .1.3.6.1.4.1.11.2.14.11.1.7.3.0.17=http://10.1.86.2/cgi/fDetail?index=17


Wed Jul 18 12:56:11 2012: Unknown trap (.1.3.6.1.4.1.11.2.14.12.4.0.1) received from 10.1.86.2 at:
Value 0: 10.1.86.2
Value 1: 10.1.86.2
Value 2: 14:0:04:28.50
Value 3: .1.3.6.1.4.1.11.2.14.12.4.0.1
Value 4: 10.1.86.2
Value 5: mycomm
Value 6: .1.3.6.1.4.1.11.2.14.12.4
Value 7:
Value 8:
Value 9:
Value 10:
Ent Value 0: .1.3.6.1.4.1.11.2.14.2.10.2.1.2.1.1=1
Ent Value 1: .1.3.6.1.4.1.11.2.14.2.10.2.1.3.1.1=1
Ent Value 2: .1.3.6.1.4.1.11.2.14.2.10.2.1.4.1.1=00 40 8B 79 A6 63
Ent Value 3: .1.3.6.1.4.1.11.2.14.2.10.2.1.6.1.1=1
Ent Value 4: .1.3.6.1.4.1.11.2.14.2.10.2.1.7.1.1=1

Those gets generated every time I connect a device with the "wrong MAC" to a port configured to accept only one (fixed and different) MAC address.

I can recognize the community (mycomm), the IP of the switch (10.1.86.2), the detail URL and the "offending" MAC address (00 40 8B 79 A6 63). No clue about the meaning of other values, nor how to add 'em to snmptt conf file.

No reference to those MIBs in mibs_oct2011.tar downloaded from support&drivers.

Can someone help me, please?

[Richard Brodie_1]

Google is great for looking up MIB values:

http://www.oidview.com/mibs/11/HP-ICF-FAULT-FINDER-MIB.html

[NdK]

Tks, I already found it, but I couldn't find what I needed.

Just after sending, I found that hpicfFf.mib contains the definition I needed, just no reference to the full OID.

That "S" in SNMP is really misleading!