Bug ID 502928: TMM core in AWS and Azure Enviroments

Last Modified: May 14, 2019

Bug Tracker

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

Known Affected Versions:
12.0.0

Fixed In:
12.1.0, 12.0.0 HF1

Opened: Jan 26, 2015
Severity: 2-Critical

Symptoms

TMM may core when under memory pressure on Virtual Edition (VE) instances running in AWS and Azure

Impact

Traffic disrupted while tmm restarts.

Conditions

Big-IP VE version 12.0 running in AWS and Azure environments. 12.0 VE images in AWS and Azure have been modified to use the 'sockets' data plane interface. The core may be observed when the sweeper is in aggressive mode, indicating that TMM is under memory pressure.

Workaround

to switch from the 'sockets' dataplane interface to the 'unic' dataplane interface uncomment the 'modprobe unic' line in /etc/sysconfig/modules/unic.modules. The following command enables the VE 'unic' TMM dataplane interface. You must reboot to make this change take effect. ~$ sed -i 's/^#modprobe unic/modprobe unic/' /etc/sysconfig/modules/unic.modules ~$ reboot

Fix Information

This release properly handles memory allocation failures on Virtual Edition (VE) instances running in AWS and Azure, so no TMM cores occur.

Behavior Change