T
toramanand
Guest
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
Ramanand
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
Ramanand
