Bug ID 2441981: BIG-IP GUI does not expose supported SNMPv3 SHA-2 and extended AES protocol options

Last Modified: Sep 18, 2026

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

Known Affected Versions:
17.1.3.5, 17.5.1.8, 17.5.1.9, 21.0.0.2, 21.0.0.3, 21.1.0.1, 21.1.0.2

Opened: Jul 27, 2026

Severity: 3-Major

Symptoms

When configuring SNMPv3 users or trap destinations through the BIG-IP Configuration utility, the authentication and privacy protocol lists do not expose all supported options. The GUI provides only MD5/SHA for authentication and AES/DES for privacy The following options are unavailable for selection in the GUI: Authentication: SHA-256 and SHA-512 Privacy: AES-192, AES-192-C, AES-256, and AES-256-C

Impact

Cannot configure SNMPv3 users or trap destinations with the required SHA-2 authentication or extended AES privacy protocols through the GUI

Conditions

This issue occurs when all of the following apply: - BIG-IP is using a Net-SNMP version that supports the extended SNMPv3 algorithms - An administrator creates or modifies an SNMPv3 user or trap destination through the Configuration utility - The administrator needs to select SHA-256, SHA-512, AES-192, AES-192-C, AES-256, or AES-256-C - BIG-IP software using Net-SNMP 5.8 supports SHA-2 and extended AES key lengths, as documented in K82498430: SNMPv3 support for SHA2 and AES256

Workaround

- Use tmsh to configure. - Specify the auth-protocol and privacy-protocol values using tmsh; the following is an example: modify /sys snmp users add { <user> { access rw security-level auth-privacy auth-protocol sha256 auth-password defaultPassword privacy-protocol aes-192 privacy-password defaultPassword username <user> } }

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips