[SOLVED] How to configure time for NH (nexthop) delete from FAILED state
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
How to configure time for NH (nexthop) delete from FAILED state
Hi,
I have observed that NH (nexthop) entry deletion (in linux stack) from FAILED state is 9-10 min. Can anybody let me know what is default value for this and how to change this. I can reproduce this scenario by sending the traffic to host which is not available. For the unavailable host stack try to resolve the ARP(NH) and move the entry into FAILED state. Now I check the time stack is taking to delete this NH entry. I am putting some of the /proc parameters value from my system.
/proc/sys/net/ipv4/neigh/default/gc_stale_time = 60
/proc/sys/net/ipv4/neigh/default/gc_interval = 30
/proc/sys/net/ipv4/neigh/testDev/gc_stale_time = 120 >> testDev is the L3 interface (netdevice) on which I am testing the case
/proc/sys/net/ipv4/neigh/testDev/base_reachable_time = 175
/proc/sys/net/ipv4/neigh/testDev/base_reachable_time_ms = 17500
The time to remove stale ARP entry is complicated. It is relative to /proc/sys/net/ipv4/route/gc_timeout, base_reachable_time, gc_stale_time and gc_interval. The big one could gc_timeout, normal is 5 minutes.
The time to remove stale ARP entry is complicated. It is relative to /proc/sys/net/ipv4/route/gc_timeout, base_reachable_time, gc_stale_time and gc_interval. The big one could gc_timeout, normal is 5 minutes.
Thanks. I want to get the FAILED to Delete time around 1 sec. Can you suggest some values for these parameters to achieve this value.
If hardware configuration is changed and it trigger ARP flush, ARP API should be called to flush these ARP entry and shouldn't use timeout mechanics to clean up.
Requirement is not ARP flush. Scenario is slightly different. Its a complex application, where I need to trigger some operations in application and hardware when ARP is FAILED to resolved.
Ok, Well meanwhile I changed my application now. So whatever processing I was doing earlier on NH Delete notification, started doing that on FAILED notification also.
Thanks for your support.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.