Last Modified: Aug 27, 2026
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2, 17.1.3, 17.1.3.1, 17.1.3.2, 17.1.3.4, 17.5.0, 17.5.1, 17.5.1.2, 17.5.1.3, 17.5.1.4, 17.5.1.5, 17.5.1.6, 17.5.1.8, 21.1.0, 21.1.0.1
Opened: Aug 21, 2026 Severity: 2-Critical
When you update the IP geolocation database on a BIG-IP system that is processing traffic, the Traffic Management Microkernel (TMM) may produce a core file and restart. If you perform the update on more than one system in turn, each system may be affected
Traffic disrupted while TMM restarts
- A legacy version 1 IP geolocation city database file is present in /shared/GeoIP. - One or more virtual servers use a TCP Analytics profile with the City or Postcode entity enabled - Client connections are open, and the client IP addresses resolve to a city or a postcode - You update the IP geolocation database while those connections are open. Updating any single geolocation database reloads all of them
Disable the City and Postcode entities in the TCP Analytics profile Alternatively, update the IP geolocation database on a system that is not processing traffic: - Fail over so that the system you want to update is the standby system - Update the IP geolocation database on the standby system - Fail back, then repeat for the other system
None