Bug ID 423115: mcpd cores when virtual servers in traffic groups have non-floating IP address

Last Modified: Jul 12, 2023

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

Known Affected Versions:
11.3.0, 11.4.1

Fixed In:
11.5.0, 11.4.1 HF9, 11.3.0 HF9

Opened: Jun 12, 2013

Severity: 2-Critical

Related Article: K15268

Symptoms

Changing IP addresses on traffic groups in an HTTP iApp service from floating to non-floating and then performing a full sync operation, might cause mcpd to crash and write out a core file on the peer device.

Impact

The mcpd process restarts, which also results in most other system daemons restarting as well.

Conditions

This occurs after changing the IP addresses on a traffic group in an iApp service from floating to non-floating, and then syncing.

Workaround

Ensure that iApps and the objects within them are associated with the same traffic group.

Fix Information

mcpd no longer cores when syncing virtual servers in a traffic group that have non-floating IP addresses.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips