Bug ID 1927521: DPDK has dependency on SSSE3

Last Modified: May 01, 2025

Affected Product(s):
BIG-IP LTM(all modules)

Known Affected Versions:
17.5.0

Opened: Apr 16, 2025

Severity: 3-Major

Symptoms

TMM goes into restart loop with following error in /var/log/tmm regarding SSSE3 not being available notice ERROR: This system does not support "SSSE3". notice Please check that RTE_MACHINE is set correctly. notice EAL: FATAL: unsupported cpu type. notice EAL: unsupported cpu type. notice dpdk: Error: rte_eal_init() failed, err=-1 notice xnet_lib [pci:0000:02:00.0]: Error: Failed to initialize driver notice xnet[02:00.0]: Error: Unable to attach to xnet dev notice xnet(1.1)[02:00.0]: Error: Unable to initialize device notice xnet(1.1)[02:00.0]: Waiting for tmm1 to reach state 4... notice ndal Error: Restarting TMM notice Initiating TMM shutdown. notice tap(tap)[00:00.0]: Waiting for tmm1 to reach state 4... notice ---------------------------------------------

Impact

Traffic disrupted while tmm restarts.

Conditions

1) xnet-DPDK is being used 2) BIG-IP running in an environment where SSSE3 is not available either because CPU is so old that it does not support SSSE3 or SSSE3 has been disabled in VM's config.

Workaround

Switch to 'sock' driver by adding the following line into /config/tmm_init.tcl, replacing <VENDOR_ID:DEVICE_ID> with the corresponding interfaces' Vendor and Device IDs shown via 'lspci -nn'. For environments in HyperV or Azure, f5f5:f550 should be used for Vendor and Device. [root@BIGIP:Active:Standalone] log # cat /config/tmm_init.tcl device driver vendor_dev <VENDOR_ID:DEVICE_ID> sock [root@BIGIP:Active:Standalone] log #

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips