All work
- clog messages not generating alarms (uei.opennms.org/vendor/Cisco/traps/clogMessageGenerated)NMS-12936
- impossible to catch BSM events based on severity for notificationsNMS-12405
- Be able to expand parameters without include the original valueNMS-11814
- Mikrotik RouterOS trap definitionsNMS-7237Resolved issue: NMS-7237Marcel Fuhrmann
- New Liebert/Emerson event definitionsNMS-7167Resolved issue: NMS-7167Marcel Fuhrmann
- Backup Exec UEI contain "http://" in ueiNMS-7166Resolved issue: NMS-7166Marcel Fuhrmann
- Siemens HiPath 4000 event filesNMS-7027Resolved issue: NMS-7027Marcel Fuhrmann
- Wildcards no longer evaluated in "id" mevalue of eventconfNMS-6592Resolved issue: NMS-6592Matt Brozowski
- SNMP support for Clavister security devicesNMS-6107Resolved issue: NMS-6107Jeff Gehlbach
- Bits of event-acknowledgement UI still showingNMS-5733Resolved issue: NMS-5733Jeff Gehlbach
- Varbind generator for existing XML event files.NMS-5554
- Add logmsg support to send-event.plNMS-5373Resolved issue: NMS-5373Jeff Gehlbach
- Multiple parmid's not supported in event descriptionsNMS-5132Jeff Gehlbach
- OpenNMS-defined node event: nodeDown -> filter is not appliedNMS-4460Resolved issue: NMS-4460Jeff Gehlbach
clog messages not generating alarms (uei.opennms.org/vendor/Cisco/traps/clogMessageGenerated)
Description
Acceptance / Success Criteria
is caused by
Lucidchart Diagrams
Activity
David HustaceOctober 13, 2020 at 7:03 PM
This is not a bug. This can be handled in configuration. I would check the videos and documentation around event configuration. Feel free to reach out to the OpenNMS group if you need assistance with this configuration.
Héctor SánchezSeptember 30, 2020 at 11:49 AM
I pasted the wrong line on my previous comment: "uei 'uei.opennms.org/vendor/Cisco/traps/tcpConnectionClose' marked as 'donotpersist'; not processing"
2020-09-30 11:17:13,296 DEBUG [AggregatorFlush-Trap] o.o.n.e.p.HibernateEventWriter: HibernateEventWriter: uei 'uei.opennms.org/vendor/Cisco/traps/clogMessageDiscarded' marked as 'donotpersist'; not processi
ng event.
Héctor SánchezSeptember 30, 2020 at 11:45 AM
Removing "maskelement" on clogMessageDiscarded event at events/Cisco.events.xml ( ) makes all syslog traps being matched as clogMessageDiscarded, instead of clogMessageGenerated*, thus making them ignored: "uei 'uei.opennms.org/vendor/Cisco/traps/tcpConnectionClose' marked as 'donotpersist'; not processing"
Looks like clogMessageDiscarded is a clon of clogMessageGenerated, probably added to filter out some log messages and added upstream by mistake, the label is also wrong as is a duplicate of clogMessageGenerated.
Adding a varbind to clogMessageDiscarded or removing that event makes it work; I was unable to do so via gui (Cant save the changes: Commit failed" error )so I updated the event file and triggered a config reload.
Héctor SánchezSeptember 30, 2020 at 11:38 AM
eventd debug logs:
Hi,
snmp traps configured on cisco devices like this:
Do not trigger alarms, nor events.