Bug ID 1289269: TMM fails to startup on SPK release v1.7

Last Modified: Oct 19, 2025

Affected Product(s):
BIG_IP_NEXT(SPK) SPK(all modules)

Known Affected Versions:
1.7, 1.7.1

Fixed In:
1.9.2, 1.7.2

Opened: Apr 14, 2023

Severity: 2-Critical

Symptoms

TMM fails to startup with logs, as shown below: <run_commands> WARNING: command failed in set_xnet_symlink line 1 /usr/bin/set_xnet_symlink -s nodpdk === STDOUT === Usage: set_xnet_symlink -h -m Check available libxnet variants in '/usr/lib64' directory for CPU architecture compatibility and set '/usr/lib64/libxnet.so' symlink. -h Show help. -m Run in mock mode. Report compatibility without resetting '/usr/lib64/libxnet.so' symlink. === STDERR === /usr/bin/set_xnet_symlink: illegal option -- s <main> WARNING: '/usr/bin/set_xnet_symlink' failed to set libxnet.so correctly as it detected unsupported cpu architecture.

Impact

TMM container will be in a crash loop.

Conditions

SPK deployment uses v1.7

Workaround

None

Fix Information

TMM v1.9.6 includes the fix to the crash seen in v1.9.5.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips