Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP MA-VE
Known Affected Versions:
14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1
Fixed In:
16.1.0, 16.0.1.2, 15.1.4, 14.1.4.3
Opened: Feb 19, 2020 Severity: 3-Major
In some unsupported environments, the underlying sock driver uses only only 1 queue. You can confirm whether it does so by executing the tmctl command to check the rxq column (which shows 0): tmctl -d blade -i tmm/ndal_rx_stats' and You can verify this on the tx side as well.
When multi-q is present, the use of single queue can impact performance when using the sock driver.
This occurs in certain unsupported environments. Note: When you run 'ethtool -l', you can see: 'command not supported'.
Use other available drivers. You can check the available drivers by executing the tmctl command: tmctl -d blade -i tmm/device_probed
Fixed an issue with the sock driver.