For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

zexiong_357458's avatar
zexiong_357458
Icon for Nimbostratus rankNimbostratus
Apr 03, 2018

gratitous arps may be sent out too quickly for network device to process, which may result in stale ARP entries on the device.

gratitous arps may be sent out too quickly for network device to process, which may result in stale ARP entries on the device. From the article,K7332: Gratuitous ARPs may be lost after a BIG-IP fail...
application delivery
BIG-IP
youssef1's avatar
youssef1
Icon for Cumulonimbus rankCumulonimbus
Apr 03, 2018

Hello Zexiong,

 

I encountered a similar problem at a customer.

 

By default, the arp.gratuitousrate database variable is set to 0, which means that there is no limit to the number of gratuitous ARPs that the BIG-IP system can send out per second. If the arp.gratuitousrate database variable is set to values in the order of several thousands, the behavior is similar to 0 (unlimited).

 

So as evoked Blakely, you have to reduce the number of ratuitous ARPs that the BIG-IP system can send out per second.

 

I managed a client that had more than 800vs. and I also noticed that the gratuitus arp were retransmitted 3 times (2400 arp). So if had to reduce the rate of arp send by second to resolve my issue.

 

https://support.f5.com/csp/article/K11985

 

Regards