Bug ID 683246: SNMP trap suppression should be based upon OID rather than trap text

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1

Fixed In:
14.0.0

Opened: Sep 13, 2017

Severity: 3-Major

Symptoms

There are two db variables that allow trap suppression to be configured. They are snmp.bigiptraps.suppress.interval and snmp.bigiptraps.suppress.count. The suppression is cleared with each new trap issued so it does not successfully suppress traps when multiple traps are issued in the suppression interval.

Impact

It can appear that trap suppression is not working if multiple traps are being issued in the suppression interval.

Conditions

Configuring SNMP trap suppression.

Workaround

There is no workaround at this time.

Fix Information

The trap suppression processing has been improved to consider the full trap contents.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips