Bug ID 662296: Under heavy traffic load tcpdump -i 0.0 can impact the VIPRION management cluster IP address

Last Modified: Apr 19, 2021

Bug Tracker

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

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Opened: Apr 30, 2017
Severity: 2-Critical
Related AskF5 Article:
K12776

Symptoms

Management connectivity loss over the management cluster IP address. This is caused by a secondary blade temporarily taking over the cluster primary due to starvation of clusterd on the blade running tcpdump.

Impact

Loss of connectivity to the cluster floating IP address. The /var/log/ltm clusterd shows timeouts and temporary change of primaryship.

Conditions

-- A multi-bladed configuration with full traffic load. -- Run tcpdump -i 0.0.

Workaround

Mitigation: -- Judicious use of tcpdump -i 0.0. Workaround: -- Kill tcpdump from the SSH session to the slot IP address directly or using the console. -- Restart tmm to fix the issue with MPI stream connection loss.

Fix Information

None

Behavior Change