Last Modified: Mar 28, 2025
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2, 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, 16.1.5, 16.1.5.1, 16.1.5.2, 17.0.0, 17.0.0.1, 17.0.0.2, 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, 17.1.1.4, 17.1.2, 17.1.2.1, 17.5.0
Opened: Oct 15, 2024 Severity: 3-Major
In very rare circumstances, tmm may fail to start and log a message similar to the following: /var/log/tmm: notice vmxnet3(1.3)[1b:00.0]: Waiting for tmm1 to reach state 1... /var/log/tmm1: notice Failed to connect to TMROUTED: ERR_INPROGRESS. Try again in 10 seconds. notice MCP connection expired early in startup; retrying While the issue is occurring, there will be incomplete ARP entries for tmm. # arp -an | grep 127.1.1. ? (127.1.1.2) at <incomplete> on tmm ? (127.1.1.3) at <incomplete> on tmm ? (127.1.1.4) at <incomplete> on tmm ? (127.1.1.6) at <incomplete> on tmm ? (127.1.1.7) at <incomplete> on tmm ? (127.1.1.8) at <incomplete> on tmm
Tmm is unable to start
-- BIG-IP VE -- Hypervisor under high load
Restart tmm manually with bigstart restart tmm Alternatively, set up a static arp mapping on the linux host: arp -s 127.1.1.2 00:01:23:45:67:01 arp -s 127.1.1.3 00:01:23:45:67:02 arp -s 127.1.1.4 00:01:23:45:67:03 arp -s 127.1.1.5 00:01:23:45:67:04 arp -s 127.1.1.6 00:01:23:45:67:05 arp -s 127.1.1.7 00:01:23:45:67:06 arp -s 127.1.1.8 00:01:23:45:67:07 If there are more than 8 tmms, the following script can be used: for y in $(seq $(/usr/bin/getdb Provision.tmmCountActual)); do arp -s 127.1.1.$(($y+1)) 00:01:23:45:67:$(printf "%02g" $y); done
None