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

Last Modified: Jan 22, 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.4, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 15.0.0, 15.0.1, 15.0.1.1, 15.1.0

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; in releases 13.1.0 through 14.0.x, the 'unic' driver is the alternative. Use one of 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.) -- Commands for Releases 14.1.0 and later: # 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 -- Commands for releases 13.1.0 through 14.0.0: # echo "device driver vendor_dev 1af4:1000 unic" > /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 'unic'] # tmctl -dblade -i tmm/device_probed

Fix Information

None

Behavior Change