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

Last Modified: Dec 18, 2024

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

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, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 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, 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, 15.1.10.5, 15.1.10.6, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2, 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, 16.1.5.1

Opened: Jul 01, 2020

Severity: 3-Major

Related Article: K27872027

Symptoms

BIG-IP VE does not transmit traffic when deployed on ESXi 6.5 hypervisors using VMXNET 3 network interfaces, which are the default. TMSH displays a network interface, indicating that one or more interfaces are not initialized.

Impact

Traffic does not pass through non-mgmt interfaces.

Conditions

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

Workaround

This does not occur on ESXi version 7.0. It is recommended to update the ESXi host to the version of 7.0 or above. If you cannot upgrade ESXi, you can use the following workaround. - On the BIG-IP systems, you can switch to the ‘sock’ driver. Note: The workarounds for switching drivers 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. - 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 - 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

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips