Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2, 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, 17.0.0, 17.0.0.1, 17.0.0.2
Opened: Nov 02, 2021 Severity: 3-Major Related Article:
K48785510
No response to SNMP GET request with an error message 'Timeout: No Response from <ip_address>.' after UCS restore, even though running the TMSH command 'tmsh list sys snmp' reports the correct configuration.
Any snmpget/snmpwalk operations time out. This occurs because snmpd does not load a new config during UCS restore, so if the previous sys snmp configuration differs from the one applied during UCS restore, the discrepancy causes snmpget/snmpwalk operations to time out,
-- The BIG-IP configuration has been restored from UCS. -- There is a difference between the sys snmp configuration before the UCS restore operation and after the UCS restore operation. -- The command 'tmsh list sys snmp' reports the correct configuration.
Add a short description to let snmpd reload its config: # tmsh modify sys snmp description test # bigstart restart snmpd
None