Bug ID 1122313: VXLAN tunnels fail to pass traffic after TMM restarts

Last Modified: Dec 07, 2023

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

Known Affected Versions:
15.1.8, 15.1.7, 15.1.6, 15.1.5.1, 15.1.5, 14.1.5.1, 14.1.5, 14.1.4.6, 14.1.4.5, 14.1.4.4, 14.1.4.3, 14.1.4.2, 14.1.4.1, 14.1.4, 14.1.3.1, 14.1.3

Fixed In:
17.1.0, 15.1.9

Opened: Jun 27, 2022

Severity: 2-Critical

Symptoms

After TMM restarts (or the tenant reboots), VXLAN tunnels will not pass traffic. The administrator may see messages such as the following in /var/log/tmm: notice MCP message handling failed in 0x9ce140 (16977920): May 26 14:07:19 on 1 - MCP Message: notice create { notice l2_forward_tunnel { notice l2_forward_tunnel_vlan_name "/Common/vxlan-tunnel"

Impact

VXLAN tunnels do not function.

Conditions

-- BIG-IP tenant running on rSeries appliance or VELOS chassis -- VXLAN tunnels

Workaround

After TMM restarts, delete and recreate the FDB entries associated with the tunnel. To do this manually, run these commands: TMPFILE=$(mktemp -p /var/tmp) tmsh list net fdb tunnel all one-line > "$TMPFILE" tmsh delete net fdb tunnel all all-records tmsh load sys config merge file "$TMPFILE" rm -f "$TMPFILE" Or a one-line command: TMPFILE=$(mktemp -p /var/tmp) && tmsh list net fdb tunnel all one-line > "$TMPFILE" && tmsh delete net fdb tunnel all all-records && tmsh load sys config merge file "$TMPFILE" && rm -f "$TMPFILE" To configure the system to automatically apply the workaround after TMM restarts, put the following content into /config/user_alert.conf: # Delete and re-add tunnel FDBs after TMM starts up to work-around ID1122313 alert tmm_vxlan_workaround "Tmm ready - links up" { exec command="TMPFILE=$(mktemp -p /var/tmp) && tmsh list net fdb tunnel all one-line > $TMPFILE && tmsh delete net fdb tunnel all all-records && tmsh load sys config merge file $TMPFILE && rm -f $TMPFILE"; }

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips