Bug ID 922153: Tcpdump is failing on tmm 0.x interfaces

Last Modified: Apr 21, 2022

Bug Tracker

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

Known Affected Versions:
14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 16.0.0,, 16.0.1,,, 16.1.0, 16.1.1, 16.1.2,,

Opened: Jun 30, 2020
Severity: 3-Major


The tcpdump command exits immediately with an error: errbuf ERROR:TMM side closing: Aborted tcpdump: pcap_loop: TMM side closing: Aborted


Unable to capture the packets on specific tmm interfaces.


Capturing the packets on tmm interfaces.


There are two possible workarounds: -- Start tcpdump on the tmm that actually owns the interface using the TCPDUMP_ADDR command; for example, using blade1 for 1/0.16, run the command: TCPDUMP_ADDR= tcpdump -w testcap.pcap -s 0 -i 1/0.16 -- Send the TCPDUMP_ADDR command to a specific tmm, which could work from any blade (127.20.<slot>.<tmmnumber+1> (e.g. == slot1/tmm0, == slot2/tmm15): TCPDUMP_ADDR= tcpdump -w testcap.pcap -s 0 -i 1/0.16

Fix Information


Behavior Change