Last Modified: Dec 15, 2020
See more info
Known Affected Versions:
13.1.0, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 13.1.1, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 14.0.0, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 14.1.0, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124
15.0.0, 126.96.36.199, 188.8.131.52, 13.1.3
Opened: Apr 19, 2019
Related AskF5 Article: K74921042
BIG-IP Virtual Edition (VE) does not pass traffic when deployed on ESXi 6.7 Update 2 hypervisors, when the VE is using VMXNET 3 network interfaces (VMXNET 3 interfaces are the default).
Traffic does not pass through non-mgmt interfaces.
-- BIG-IP VE running on VMware ESXi 6.7 Update 2 (build number 13006603) hypervisor. -- VMXNET 3 NICs.
You can use the following workarounds: -- Until this issue is fixed in a Point-Release for your software branch, you can contact F5 Networks Technical Support to obtain an Engineering Hotfix to address the issue. This workaround allows TMM to continue to use the VMXNET3 driver, which is preferable. -- On BIG-IP version 14.1.0, you can switch to the 'sock' driver. -- On BIG-IP versions earlier than 14.1.0, you can switch to the 'unic' 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. To switch driver: 1. Add a line to /config/tmm_init.tcl that reads 'device driver vendor_dev 15ad:07b0 DRIVER' (replacing DRIVER with 'unic' or 'sock', as appropriate). For example: echo "device driver vendor_dev 15ad:07b0 sock" >> /config/tmm_init.tcl 2. Restart tmm for the changes to take effect (restarting tmm disrupts traffic): bigstart restart tmm 3. After tmm restarts, confirm the driver in use by examining the output of: tmctl -d blade tmm/device_probed
BIG-IP VE now passes traffic on ESXi 6.7 Update 2.