Bug ID 521036: Dynamic ARP entry may replace a static entry in non-primary TMM instances.

Last Modified: Aug 19, 2026

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

Known Affected Versions:
11.5.3, 11.5.3 hf1, 11.5.3 hf2, 11.6.0, 11.6.0 hf1, 11.6.0 hf2, 11.6.0 hf3, 11.6.0 hf4, 11.6.0 hf5, 11.6.0 hf6, 11.6.0 hf7, 11.6.0 hf8, 11.6.1, 11.6.1 hf1, 11.6.1 hf2, 11.6.2, 11.6.2 hf1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3

Fixed In:
12.0.0, 11.5.4

Opened: May 01, 2015

Severity: 3-Major

Symptoms

In a very rare occasion, a dynamic ARP entry may replace a static entry in non-primary TMM instances. When the BIG-IP system attempts to send packets to an address, "tmsh show net arp" lists two entries for the address: one static and the other shows up as "incomplete" status.

Impact

The issue may impact traffic flow if traffic goes through non-primary TMM instances.

Conditions

The issue is due to a very rare race condition, and the BIG-IP system is configured with a static ARP entry.

Workaround

There is no workaround but the issue is very rare to occur.

Fix Information

Dynamic ARP entry no longer replaces a static entry in non-primary TMM instances.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips