linkDown alarms are not generated for unknown ifIndex values
Description
Acceptance / Success Criteria
None
Lucidchart Diagrams
Activity
Show:
Christian Pape December 14, 2018 at 10:27 AM
Please review & merge:
Christian Pape December 13, 2018 at 2:58 PM
Bamboo is currently building the branch...
Christian Pape December 13, 2018 at 2:57 PM
My approach is a "default" attribute instead of "optional". This default value is used as fall-back value for the assignment. In this case you can provide something like "Unknown" for unresolvable fields. Giving no default value for an assignment will behave as before.
Jesse White December 8, 2018 at 5:08 PMEdited
One approach would be to support marking some of the assignment elements in the translator-configuration.xml as "optional" and providing default values for these.
In the default configuration we leverage the event translator to enrich the
uei.opennms.org/generic/traps/SNMP_Link_Downtraps with the ifDescr, ifName and ifAlias of the associated interface in order to generate auei.opennms.org/translator/traps/SNMP_Link_Downevent. The alarm data is associated with the translated event, which leads to alarms being created with descriptive fields.As it is currently written, the
uei.opennms.org/translator/traps/SNMP_Link_Downevents only get generated if we find a match for the corresponding ifIndex in the database. If none is found, then no alarm is generated.We should update the configuration, and enrich the event translator if necessary to support translating these events for cases in which the ifIndex is not found in the database.