Problem: VOS is not responding to ARP requests.
VOS has default setting of only to process 300 ARP requests per second. If VOS receives more than 300 ARP requests per second when combined across all interfaces, it will drop ARP requests exceeds the limit.
Run below VOS CLI command to confirm ARP requests are received more than current ARP rate-limit configured on VOS:
CLI: unhide full
CLI: show statistics internal arp
Check for RLEXCEEDED column. If it is incrementing, ARP requests are received more than currently configured ARP rate-limit on VOS.
If RLEXCEEDED is not incrementing but still there is no response to ARP requests, Please check if ARP requests are received for correct subnet. Please also check if mbuf(packet buffers) is exhausted by looking at alarms and/or by checking 'Packet Buffer Depletion' under 'System->Appliance anomalies'.
If mbuf(packet buffers) issue is seen, please contact Versa support.
Follow below solutions if ARP limit is exceeded.
Solution-1:
If there is wider subnet like /21 or /16 configured on one or more interfaces on VOS, it is possible that too many hosts in subnet sending too many ARP requests. Change the subnet to more smaller subnet like /24.
Solution-2:
If changing subnet to smaller is not possible, increase the ARP rate-limit to higher value. Find the rate at which ARP requests are received (you can check current ARP requests per second by doing tcpdump or running above 'show statistics internal arp' every seconds and count the difference between RECEIVED packets. Once you find current ARP requests per second sent to VOS, increase ARP rate-limit accordingly on VOS:
