Bug ID 600970: IPsec racoon daemon 100% cpu busy

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6

Fixed In:
13.0.0

Opened: Jun 22, 2016

Severity: 3-Major

Symptoms

-- Racoon daemon runs at 100% according to top and will not start or handle any IPsec tunnels. -- No logs, no ISAKMP initiation. -- Racoonctl will hang when executed.

Impact

IPsec tunnels cannot not be established or maintained.

Conditions

-- IKEv1 -- racoon daemon caught in a busy loop Note: IKEv2 is not affected by this problem.

Workaround

bigstart restart racoon. bigstart restart tmispecd. You cannot use bigstart to restart racoon on BIG-IP version 12 software.

Fix Information

Additional loop detection has been added to the racoon process, which will cause racoond to restart. A crit level log may be written along with a racoon corefile. tmipsecd will restart racoon and the problem will be resolved. Any racoon corefile along with a qkview should be presented to F5 Support for analysis.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips