Bug ID 1049321: When run from tmsh, tcpdump -i a-trunk reports "ERROR:Device not found"

Last Modified: Jul 24, 2024

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

Known Affected Versions:
11.5.10, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5

Opened: Sep 24, 2021

Severity: 4-Minor

Symptoms

Unable to collect a tcpdump specifying the interface as a network trunk, when run from tmsh. This is particularly likely to occur for users who are authenticated via a remote authentication mechanism (i.e. LDAP or TACACS).

Impact

Capturing network traffic from a network trunk does not work.

Conditions

-- User with role Administrator or Resource Administrator logs in with a default shell of 'tmsh' -- User tries to collect a tcpdump specifying a network trunk as the interface.

Workaround

1. Launch bash ("run util bash") and unset the TMOS_PATH variable prior to invoking tcpdump, by doing one of the following: - unset TMOS_PATH; tcpdump ... - env -u TMOS_PATH tcpdump ... Note: this workaround will only work for users with the 'Administrator' role 2. Specify an interface in the trunk instead of the trunk itself 3. Capture on a VLAN.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips