Bug ID 483141: mcpd might restart when creating large numbers of traffic groups and devices

Last Modified: Sep 13, 2023

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

Known Affected Versions:
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: Oct 07, 2014

Severity: 3-Major

Symptoms

mcpd might core or become unresponsive and be restarted by sod.

Impact

mcpd will restart.

Conditions

A large (greater than 64) number of traffic groups are already configured, there are many (greater than 4) devices in trust, and the user creates additional traffic groups.

Workaround

This can be mitigated by turning off mcpd heartbeat monitoring (tmsh modify sys daemon-ha mcpd heartbeat disabled) while traffic groups are being added, but it is not recommended to be left disabled.

Fix Information

The system now handles updating the traffic group state as a result of creating a traffic group while there are many existing traffic groups and devices.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips