Bug ID 1993081: SNMP traps are not being generated for bigipExternalLinkDown (.1.3.6.1.4.1.3375.2.4.0.218) and bigipExternalLinkUp (.1.3.6.1.4.1.3375.2.4.0.219).

Last Modified: Oct 15, 2025

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

Known Affected Versions:
16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 16.1.6, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2, 17.1.3, 17.5.0, 17.5.1, 17.5.1.2, 17.5.1.3

Opened: Jul 28, 2025

Severity: 3-Major

Symptoms

Two SNMP traps bigipExternalLinkDown (.1.3.6.1.4.1.3375.2.4.0.218) and bigipExternalLinkUp (.1.3.6.1.4.1.3375.2.4.0.219) were added as part of ID807957 fix. However, currently, these two traps are not being generated. Instead of bigipExternalLinkDown or bigipExternalLinkUp trap, when alertd.nokia.linktraps db key and alertd.nokia.alarm db key is both set to disabled (default), bigipExternalLinkChange trap (.1.3.6.1.4.1.3375.2.4.0.37) is being generated upon link status change (up/down). When alertd.nokia.linktraps db key and alertd.nokia.alarm db key is both set to enable, Nokia specific snmp traps (.1.3.6.1.4.1.94.7.1.4.2.1) is generated upon link status change (down/up) and Nokia Alarm database is correctly updated with those snmp traps. Fix for ID807957 is still valid here.

Impact

BigipExternalLinkDown trap and bigipExternalLinkUp trap is not being generated.

Conditions

- Running software version that has fix for ID807957 (16.1.0 or later / 17.x). - SNMP trap destination is configured and link status change happens. - alertd.nokia.linktraps db key and alertd.nokia.alarm db key is both disabled (default value).

Workaround

None.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips