Last Modified: Oct 19, 2025
Affected Product(s):
F5OS Velos
Known Affected Versions:
F5OS-A 1.5.1, F5OS-A 1.5.2, F5OS-A 1.5.3, F5OS-A 1.5.4, F5OS-A 1.8.0, F5OS-C 1.6.0, F5OS-C 1.6.1, F5OS-C 1.6.2, F5OS-C 1.6.4, F5OS-C 1.8.0, F5OS-C 1.8.1, F5OS-C 1.8.2
Fixed In:
F5OS-A 1.8.3
Opened: Feb 05, 2025 Severity: 3-Major
If you restore a backup containing an SNMP user, but the SNMP user’s SNMP Engine ID does not match the current system, a new SNMP user will be created with the same name and the current system’s SNMP Engine ID. However, this is only seen when the database is later backed up.
Two SNMP users with the same name (but different SNMP Engine IDs) are saved to subsequent backups. SNMP will not work.
-- Restoring a database backup that contains an SNMP user. -- Doing the restore on a system with a different SNMP Engine ID.
Reconfigure the SNMP user authentication and privacy passwords after restoring the backup. SNMP will work after configuring passwords.
When backup is restored on a system with a different EngineID, SNMP might not work for SNMP users. However, it can be mitigated by reconfiguring the SNMP user authentication and privacy passwords after restoring the backup.