Bug ID 666888: tcpdump may take several seconds to start capturing packets on vCMP guests

Last Modified: Jul 12, 2023

Affected Product(s):
BIG-IP vCMP(all modules)

Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1

Fixed In:
14.0.0

Opened: May 26, 2017

Severity: 3-Major

Related Article: K16101312

Symptoms

Running a tcpdump may take 3 or more seconds to start capturing packets.

Impact

tcpdump takes a slightly longer-than-expected time to start capturing traffic.

Conditions

This issue occurs when all of these conditions are met: - tcpdump is being run within a vCMP guest on a VIPRION platform. - The guest has more than one blade in-use.

Workaround

Wait several additional seconds to ensure that the tcpdump operation has a sufficient interval to start capturing packets.

Fix Information

tcpdump now starts capturing packets sooner.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips