Bug ID 1715685: Protocol inspection takes up to 5 hours before starting to work after a reboot

Last Modified: Oct 15, 2025

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

Fixed In:
17.1.3

Opened: Nov 12, 2024

Severity: 3-Major

Symptoms

Long hours of CPU spike of ipsd and mcpd were observed after a sudden reboot of BIG-IP Virtual Edition. Protocol inspection stats from "tmctl protocol_inspection_stats" are not recorded for up to 5 hours after rebooting.

Impact

Ipsd and mcp high cpu utilization after reboot. This can last for several hours. During this time, protocol inspection is not ready.

Conditions

The ips profile loaded with a significant number of profiles and includes HTTP and OTHER services for all.

Workaround

Reduce the duplicated IPS Profiles

Fix Information

After the fix, IPS Profiles will take less time to reach the ready state, even if the tmm or mcpd is restarted.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips