Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
11.2.1, 11.4.1, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2
Fixed In:
12.1.0
Opened: Mar 17, 2014 Severity: 3-Major
When configuring an engine_id for a SNMPv3 trap destination, the engine_id was synchronized to all HA peers.
Received SNMPv3 traps would appear as if they originated from the same Big-IP system after failover to a backup Big-IP.
All
Workaround is to disbale configsync (change 'yes' to 'no') on engine_id in /defaults/config_base.conf. However, you must first remount the /usr partition to modify the file and then run tmsh load. For more information on remounting the /usr partition, see SOL11302: The /usr file system is mounted in read-only mode at https://support.f5.com/kb/en-us/solutions/public/11000/300/sol11302.html
When configuring a new SNMPv3 trap destination, or modifying an existing one, the engine_id applies to only the local Big-IP system. The trap destination is still synchronized to HA peers, but the engine_id on these systems must now be locally configured on each.