You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All alerts should generate an SNMP trap regularly e.g. every check interval.
Usual SNMP management counts with such behavior and moreover expects that. The main reason is that for SNMP traps a UDP is used, where the reasons for UDP usage are: because it's very quick and cost almost nothing. We could use SNMP informs instead of traps, but using them we lost those advantages. SNMP inform delivery is acknowledged by recipient, it's part of SNMPv2c.
We could use inform for sending clear alerts though as those will not be repeated and the speed and cost (there shouldn't be much of them) of delivery is not so important.
All alerts should generate an SNMP trap regularly e.g. every check interval.
Usual SNMP management counts with such behavior and moreover expects that. The main reason is that for SNMP traps a UDP is used, where the reasons for UDP usage are: because it's very quick and cost almost nothing. We could use SNMP informs instead of traps, but using them we lost those advantages. SNMP inform delivery is acknowledged by recipient, it's part of SNMPv2c.
We could use inform for sending clear alerts though as those will not be repeated and the speed and cost (there shouldn't be much of them) of delivery is not so important.
There's already a BZ for this:
https://bugzilla.redhat.com/show_bug.cgi?id=1516643
The text was updated successfully, but these errors were encountered: