It's a 'custom' trap that we are sending which has alert information about our system. The MIB is fairly long to paste, but since we have control of how to construct it maybe I can pose the question in another way with a snippet.
It sounds like I am approaching this wrong. So how would I resolve this issue?
alertingVars OBJECT IDENTIFIER
-- 1.3.6.1.4.1.1530.1.1.1.1
::= { alertingMib 1 }
-- the associated data that contains the details needed to define the trap
alertPayload OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An alert data value in string format."
-- 1.3.6.1.4.1.1530.1.1.1.1.6
::= { alertingVars 6 }
The alertPayload currently is an OctetString containing a variable length delimited key value pair which is placed into the Variable list (and to the SendTrapV2) of which is not going to be useful to the customer. The associated portion of the trap looks like this currently from the receiver:Ent Value 3: .1.3.6.1.4.1.1530.1.1.1.1.6=Key1^Value1,Key2^Value2
The solution was to somehow represent the key value pair in a SEQUENCE type in the MIB and then modify the trap sending code to include a Sequence type within the variable list of the SendTrapV2. I've seen how SEQUENCES are defined in MIB's but I'm confused on how to approach it from the code sending side.It sounds like I am approaching this wrong. So how would I resolve this issue?