Wrong OID mappings by SNMP Trap parser
Dear,
I am using OpManager to receive SNMP Traps from Cisco/Starent GGSNs. The problem is following. When I receive SNMP trap in OpManager then I've got wrong text which doesn't match to received OID. Here is an example:
Message: starCardUp is received from 10.253.60.69 with the following related information : sysUpTime.0: 29 days, 6 hours, 32 minutes, 56 seconds. , snmpTrapOID.0: .1.3.6.1.4.1.8164.2.52 , .1.3.6.1.4.1.8164.1.19.1.1.2: isrhoj , .1.3.6.1.4.1.8164.1.19.1.1.4: Security Admini , .1.3.6.1.4.1.8164.1.19.1.1.3: /dev/pts/7 , starTimeTicks: 1298453523
As you can see message start with starCardUp trap but that is wrong, because if you read further then you can see that OID ".1.3.6.1.4.1.8164.2.52" doesn't match to that message. You can check that from attached files. This trap should match to trap "starCLISessionStart".You can check that from trap.parsers file.
It looks that SNMP parser dosn't try to match complete OID it looks like it matches just first matching digits. And that is a resaon why you have wrong parsing. I mean starCardUp OID is .1.3.6.1.4.1.8164.2.5 and starCLISessionStart is .1.3.6.1.4.1.8164.2.52. So as you can see it doesn't look at all digits.
Please let me know how to solve this problem because my company is testing OpManager and we would like to use it for our network.
Kind Regards,
Ivo Srhoj
Packet Core Expert
New to ADSelfService Plus?