Is it possible, using the “Generic Trap Receiver” protocol, to have traps update existing rows in the “Traps” table instead of have them add a new row each time?
For example, when a trap is already added to the table, another trap from the same source and with the same OID could simply update the bindings. This would make it possible to generate an alarm on that specific OID.
I thought this would be possible by configuring the “Trap OID Update Table”, but I can’t get this to work.
Hi Joey,
I faced the same issue when using the latest version of the Generic Trap Receiver driver (1.0.0.23). However, using the previous version (1.0.0.22), I was able to update an existing trap in the Trap table with a trap from the same source and trap OID.
A task has been created to further investigate this issue [DCP134186].
We have another SNMP Trap sender that sends traps for errors on different signal paths using the same OID, but with different bindings, e.g.
CHANNEL | Binding 1 (General) | Binding 2 (Channel ID) | Binding 3 (Alarm)
Channel 11 | 1 | 11 | 0(1)
Channel 12 | 1 | 12 | 0(1)
Channel 13 | 1 | 12 | 0(1)
The alarm status is sent in binding 3 as boolean value 0 for false, or 1 for true.
We would ideally get one line per channel in the trap table, that toggles binding 3 depending on the alarm state of the channel included in the latest trap.
How can the “Update Trap” table be configured to allow
I already tried several combinations on a staging system, but couldn’t find the right setting yet.
Many thanks for any support!
Hi Dojo,
I believe my use case would be a bit different. I have a SNMP test trap sender set up with the following SNMP trap bindings:
1.3.6.1.2.1.1.4.0.1 -> “ALARM”
1.3.6.1.2.1.1.4.0.2 -> “CLEAR”
How do I have to set up the Update Trap Table to achieve, that the “CLEAR” overrides the “ALARM”? I would like to achieve automatic clearing of SNMP trap alarms in the element.
The solution above provides only a way to overwrite the binding value of a specific OID.
Hi André, in your example these are 2 different traps and there is also no additional binding to somehow link both to one another? If that is the case, I’m afraid that will not be supported today and would probably also be difficult to implement generically.
Hi Joey,
many thanks for your feedback.
There are binding 1 and 2 for each trap, but this is generic:
.
TrapIndex – Timestam – TrapOID(Lookup Value) – Binding1 – Binding2
55 – 25.10.2022 13:42 – Ref. Locked Normal – 0 – 10.110.18.92
47 – 25.10.2022 13:41 – Ref. Present Normal – 0 – 10.110.18.92
42 – 25.10.2022 13:41 – Ref. Present Fault – 0 – 10.110.18.92
43 – 25.10.2022 13:41 – Ref. Locked Fault – 0 – 10.110.18.92
So there is no information except the Trap OID to identify a trap value that shoudl be refreshed.
After some further testing and checking with the developer, I was able to get it working using the latest version.
The “Trap OID Updated” and “Trap OID Updating” both need to be set to “*” and the “Binding Alarm Index” needs to be set to “Trap OID”. When that is configured in the “Trap OID Update Table”, then rows for a specific IP and OID combination will be updated in the Traps table instead of adding a new row every time a trap is received.