Allow trap varbind OID's to be used as keys in SNMP eventconf.xml mask
Description
Customer question:
“I have a trap what in occasions I receive a varbind and in other occasions not…so, the param number received is different…can I configure ONMS in order to consider the varbind OID instead of the param sequence number?”
But from my understanding, OpenNMS ignores varbind OID’s which are sent with varbinds but only looks at the sequence position of the varbind in the trap. If the number of varbinds changes for the same trap, the wrong varbind index will be read.
So the customer is asking, is there a way to use the varbind oid as a key instead of the sequence number to access the varbind value . I don’t think this feature is in the code – but please show me if I am wrong.
Customer question:
“I have a trap what in occasions I receive a varbind and in other occasions not…so, the param number received is different…can I configure ONMS in order to consider the varbind OID instead of the param sequence number?”
Analysis:
The trap definition in https://datatracker.ietf.org/doc/html/rfc1157 shows that all varbind should have an ObjectName and a value
– variable bindings
VarBind ::=
SEQUENCE
{ name ObjectName,
value ObjectSyntax }
VarBindList ::=
SEQUENCE OF
VarBind
But from my understanding, OpenNMS ignores varbind OID’s which are sent with varbinds but only looks at the sequence position of the varbind in the trap. If the number of varbinds changes for the same trap, the wrong varbind index will be read.
So the customer is asking, is there a way to use the varbind oid as a key instead of the sequence number to access the varbind value . I don’t think this feature is in the code – but please show me if I am wrong.
It doesn’t show up in the varbind definition of the eventconf xsd https://github.com/OpenNMS/opennms/blob/develop/opennms-config-model/src/main/resources/xsds/eventconf.xsd