Interpret parameters sent in a trap to human readable text

Description

When traps are sent they often contain variables with specific meanings. I
would like this interpreted when the trap generates the event to show what
these mean. For example if I receive the following trap -
eid - .1.3.6.1.4.1.181.2.2
generic - 6
specific - 5002
variables -
.1.3.6.1.2.1.2.2.1.1.1=1(Counter32,text);
.1.3.6.1.2.1.2.2.1.2.1=T1 Network Interface(OctetString,text);
.1.3.6.1.2.1.10.18.6.1.10.1=4096(Counter32,text);
.1.3.6.1.2.1.10.18.7.1.2.1=15(Counter32,text);
.1.3.6.1.2.1.10.18.7.1.5.1=0(Counter32,text)

The variables are -
ifIndex, ifDescr, dsx1LineStatus, dsx1CurrentESs, dsx1CurrentUASs

The dsx1LineStatus has the following table associated with it -

The various bit positions are:
1 dsx1NoAlarm No Alarm Present
2 dsx1RcvFarEndLOF Far end LOF (a.k.a., Yellow Alarm)
4 dsx1XmtFarEndLOF Near end sending LOF Indication
8 dsx1RcvAIS Far end sending AIS
16 dsx1XmtAIS Near end sending AIS
32 dsx1LossOfFrame Near end LOF (a.k.a., Red Alarm)
64 dsx1LossOfSignal Near end Loss Of Signal
128 dsx1LoopbackState Near end is looped
256 dsx1T16AIS E1 TS16 AIS
512 dsx1RcvFarEndLOMF Far End Sending TS16 LOMF
1024 dsx1XmtFarEndLOMF Near End Sending TS16 LOMF
2048 dsx1RcvTestCode Near End detects a test code
4096 dsx1OtherFailure any line status not defined here

I would like opennms to include this table in the configuration and translate
the value 4096 sent in this event to the words "dsx1OtherFailure-any line
status not defined here"(Yea, bad example it still doesn't tell me but I might
get one that does). I don't know how you would store this in the events table,
maybe another field, one with the original and one with the human readable with
the variable seperated by a semi-colon like they are now. For now I will just
add the information to the event as it is pasted above.

Environment

Operating System: Linux Platform: PC

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Marcel Fuhrmann May 8, 2018 at 7:10 PM

As discussed with , we can close this issue.

Ronny Trommer March 23, 2016 at 7:13 PM

this one gets it's 14th birthday in a few weeks, we should think harder

Jeff Gehlbach March 20, 2016 at 1:52 PM

I do think that varbind decodes solves this one.

Ronny Trommer July 9, 2015 at 6:11 PM

Tarus Balog October 17, 2007 at 3:28 PM

Putting against 1.8 - might slip.

Fixed

Details

Assignee

Reporter

Labels

Fix versions

Affects versions

Priority

PagerDuty

Created May 29, 2002 at 2:15 PM
Updated May 8, 2018 at 7:10 PM
Resolved May 8, 2018 at 7:10 PM