Bug ID 922885: BIG-IP Virtual Edition does not pass traffic on ESXi 6.5

Last Modified: May 18, 2023

Affected Product(s):
BIG-IP MA-VE(all modules)

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

Opened: Jul 01, 2020

Severity: 3-Major

Related Article: K27872027


BIG-IP Virtual Edition (VE) does not pass traffic when deployed on ESXi 6.5 hypervisors, when the VE is using VMXNET 3 network interfaces (VMXNET 3 interfaces are the default). 'tmsh show net interface' indicates that one or more interfaces are not initialized.


Traffic does not pass through non-mgmt interfaces.


-- BIG-IP VE running on VMware ESXi 6.5 hypervisor.


-- On the BIG-IP systems, you can switch to the 'sock' driver. Note: The workarounds that switch driver must be applied individually to devices, as they do not synchronize via ConfigSync. IMPORTANT: The driver must be configured the same way on all devices in a sync-failover device group. 1, At the command prompt, run the following command to enable the sock driver in tmm_init.tcl: echo "device driver vendor_dev 15ad:07b0 sock" >> tmm_init.tcl 2. Restart tmm: tmsh restart sys service tmm -- After restarting, the sock driver should be listed in the 'driver_in_use' column when running the following command. tmctl -d blade tmm/device_probed pci_bdf pseudo_name type available_drivers driver_in_use ------------ ----------- --------- --------------------- ------------- 0000:03:00.0 F5DEV_PCI xnet, vmxnet3, sock, 0000:0b:00.0 1.1 F5DEV_PCI xnet, vmxnet3, sock, sock 0000:13:00.0 1.2 F5DEV_PCI xnet, vmxnet3, sock, sock 0000:1b:00.0 1.3 F5DEV_PCI xnet, vmxnet3, sock, sock

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips