Bug ID 747131: ARP table may not be updated properly by some TMMs

Last Modified: Jul 19, 2019

Bug Tracker

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

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3,,,,,,,, 12.1.4, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,,, 14.1.0,,,,,,, 15.0.0

Fixed In:

Opened: Oct 18, 2018
Severity: 3-Major


When receiving ARP request coming from the client, some TMMs may not update the ARP table properly, leading to connectivity failures.


This will have no impact in most of configurations, since BIG-IP will perform it's own resolution for client's MAC addresses. In a case where client is not responding to ARP probes sent by Big-IP, the problem may lead to connectivity failures for particular clients.


- BIG-IP with autolasthop disabled. - Client blocking ARP responses. - BIG-IP relies only on ARP requests coming from the client for sending the traffic back.


Configure static ARP entries OR enable autolasthop.

Fix Information


Behavior Change