Bug ID 1492337: TMM fails to start up using Xnet-DPDK-virtio due to out of bounds MTU

Last Modified: Jun 11, 2024

Affected Product(s):
BIG-IP LTM(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, 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.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 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, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3

Opened: Jan 18, 2024

Severity: 3-Major

Symptoms

TMM goes into a restart loop and fails to start with an error message that the MTU is out of bounds Log message: notice virtio_mtu_set(): MTU should be between 68 and 1500

Impact

TMM goes into a restart loop and fails to start

Conditions

- Using Xnet-DPDK-virtio driver - NIC is configured to have an MTU less than NDAL's configured MTU. By default, this is an MTU < 9198

Workaround

Create /config/tmm_init.tcl with the following entry ndal mtu <value> 1af4:1041 Replacing <value> with the corresponding value in the following log line in /var/log/tmm notice virtio_mtu_set(): MTU should be between 68 and <value>

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips