Bug ID 1132449: Incomplete or missing IPv6 IPI database results to connection reset and/or high TMM CPU usage

Last Modified: Apr 29, 2023

Affected Product(s):
BIG-IP AFM(all modules)

Known Affected Versions:
15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6,, 15.1.7, 15.1.8,,, 16.1.0, 16.1.1, 16.1.2,,, 16.1.3,,,,, 17.0.0,,, 17.1.0,

Opened: Jul 27, 2022

Severity: 3-Major


Following IPv4 database load message is present in /var/log/ltm: 015c0010:5: Initial load of IPv4 Reputation database has been completed Note the absence of: 015c0010:5: Initial load of IPv6 Reputation database has been completed Some scenarios would result in elevated TMM CPU utilization, for example, when using IPI in global policy.


Any of the following: - TCL error results when IPI is used in an iRule resulting in connection being reset. - When using IPI in global policy, increased TMM CPU utilization may occur which leads to idle enforcer being triggered, TMM clock advanced messages appearing in LTM logs, or TMM restarting without core when MCPD is unable to communicate with TMM.


Failure to download IPv6 database from localdb-ipv6-daily.brightcloud.com.


Ensure that BIG-IP is able to communicate with BrightCloud servers, including localdb-ipv6-daily.brightcloud.com. See K03011490.

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips