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

Last Modified: Apr 17, 2024

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

Known Affected Versions:
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, 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, 17.0.0, 17.0.0.1, 17.0.0.2, 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

Opened: Jul 27, 2022

Severity: 1-Blocking

Symptoms

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.

Impact

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.

Conditions

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

Workaround

Ensure that BIG-IP is able to communicate using https with BrightCloud servers, including localdb-ipv6-daily.brightcloud.com. For more detailed troubleshooting steps, see K03011490.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips