Bug ID 558976: Improvement to cause tmm to core when mcpd exits

Last Modified: Dec 13, 2019

Bug Tracker

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

Known Affected Versions:
11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 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, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4

Fixed In:
15.1.0

Opened: Nov 18, 2015
Severity: 3-Major

Symptoms

When troubleshooting the tmm state when mcpd exits, it is not possible to generate a tmm core

Impact

Unable to force a tmm core when mcpd exits. There is no functional impact to this but it can make diagnosing issues more difficult.

Conditions

Troubleshooting mcpd and tmm state at the same time

Workaround

None

Fix Information

A new sys db variable has been added called tmm.mcp.disconnect.core to cause tmm to core when mcpd disconnects.

Behavior Change

A new sys db variable has been added called tmm.mcp.disconnect.core. The default value is disabled. When enabled, tmm will core if mcpd exists. This can be useful for troubleshooting purposes.