Bug ID 491478: EAM is a CMP plugin and spins up one thread per TMM.

Last Modified: Oct 06, 2020

Bug Tracker

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

Known Affected Versions:
11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3

Fixed In:
12.0.0, 11.6.0 HF4, 11.5.2

Opened: Nov 18, 2014
Severity: 3-Major

Symptoms

When OAM is enabled on a virtual, an 'eam' v1 plugin profile is added to the virtual. Due to ht-split performance changes (specifically addition of "plugin_threads" field in BZ439449the eam plugin profile claims to be a CMP-enabled plugin but forces the thread count to 1. This causes the number of MPI devices to be 0, thus no channel is spun up - all connections through the virtual result in "No plugin configuration found" error in /var/log/ltm and the connection is reset. SYMPTOM: Virtuals with OAM enabled do not pass traffic - "No plugin configuration found" errors in /var/log/ltm

Impact

Traffic outage on OAM-enabled virtuals

Conditions

HTTP virtual with OAM enabled

Workaround

hand-edit of /defaults/config_base.conf plugin_threads { class-name profile_eam container none instance-name eam value "1" <-- change this to "tmms" }

Fix Information

EAM is a CMP plugin and spins up one thread per TMM.

Behavior Change