Bug ID 811701: AWS instance using xnet driver not receiving packets on an interface.

Last Modified: Jul 07, 2020

Bug Tracker

Affected Product:  See more info
BIG-IP LTM, VE(all modules)

Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 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, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.1.0, 15.1.0.1

Fixed In:
15.1.0.2

Opened: Aug 01, 2019
Severity: 2-Critical

Symptoms

Packets are being sent to the AWS instance but no packets are seen on interface.

Impact

Loss of packets in the interface, in turn, causing data loss.

Conditions

-- AWS instance using xnet driver. -- Occurs when the instances are idle and then suddenly passes traffic again. -- Other, more specific conditions are unknown at this time.

Workaround

A temporary way to avoid the problem is to configure BIG-IP Virtual Edition (VE) to use an alternative network driver in place of the default 'xnet' driver. In releases 14.1.0 and later, this would be the 'sock' driver. Use The following command sequences from the BIG-IP instance's 'bash' prompt to configure the alternative driver. (Note the use of the 'greater-than' symbol.) # echo "device driver vendor_dev 1d0f:ec20 sock" > /config/tmm_init.tcl [check that the file's contents are correct] # cat /config/tmm_init.tcl [restart the BIG-IP's TMM processes] # bigstart restart tmm [make certain that the 'driver_in_use' is 'sock'] # tmctl -dblade -i tmm/device_probed

Fix Information

None

Behavior Change