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

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 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

Fixed In:
12.0.0, 11.6.1 HF1, 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