Bug ID 751292: mcpd core after changing parent netflow to use version9

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP All(all modules)

Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4

Fixed In:
15.0.0, 14.1.2.5

Opened: Nov 28, 2018
Severity: 2-Critical

Symptoms

When making changes to netflow profile (changing between v9 and v5), mcpd CPU usage on one core goes high, and a core file is written. The problem occurs only when modifying root netflow profile that is referenced by a child netflow. Modifying the root netflow profile works as expected when it is not being referred to by any child netflow. When the issue occurs, mcpd gets into a loop and hangs there for a long time.

Impact

The config changes appear to have been made. However, mcpd processes the config and stops responding. While mcpd restarts, there is no traffic management functionality (e.g., cannot retrieve or update system status, cannot reconfigure system, other daemons are not functional).

Conditions

The problem occurs only when modifying root netflow profile that is referenced by a child netflow.

Workaround

No workaround.

Fix Information

None

Behavior Change