Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 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.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 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, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1
Fixed In:
14.1.0
Opened: Apr 25, 2018 Severity: 3-Major
TMSH commands allow you to enter parameters that are put into the snmpd.conf file for configuring the SNMP agent. If you specify an engineID, then it will be part of the system configuration that may synchronize as part of a failover group. That behavior may be undesirable, so instead, you can specify an engineIDType. Then each BIG-IP system makes its own engineID based upon type. Supported types are: -- IPv4 (1) -- IPv6 (2) -- MAC address (3) -- Text (4) Here is a sample tmsh command: tmsh modify sys snmp include "engineIDType 3" When the engineIDType is 1 or 2 (IPv4 address or IPv6 address), the BIG-IP system selects the localhost address which gives a non-unique engineID.
The engineID is not unique. This is especially a problem on vCMP.
Using engineIDType 1 or engineIDType 2 uses localhost address of 127.0.0.1 or ::
Use engineIDType 3. Then the engineID is based on the MAC address, which is reliably unique.
In this release, the system determines the engineID in the following ways: -- The cluster IP address, if it is available, is used for a chassis. -- If there is no cluster address, then for IPv4, the eth0 or mgmt address is used. For IPv6 the first NIC's MAC address is used with fe80 in the first two bytes (this is the same logic that generates link-local addresses use). -- If you specify an engineIDNic as a variable in the snmpd.conf file, then that is the MAC address used.