01-19-2006 07:54 AM
Hello all,
When you configure "hash address" as your load-balancing alorithm in your serverfarm, it seems that the CSM does not age out the hash vlaue based on the source and destination IP unless you reboot the CSM.
Would be great if somebody could anwer one of the following questions?
1)Is it possible to configure a timeout for the hash vlaue in this case?
2)Is there a default timeout?
3)Do you kow of any other way of removing the cached hashed value without rebooting the CSM?
Many thanks,
Ramin
Solved! Go to Solution.
01-19-2006 07:30 PM
Ramin,
As the hashing is a calculation, it will always return the same result regardless of whether an existing entry is found, unless a real server was to fail or a failed server recovered. You can control sticky "time to live" or aging if you use a sticky config, using the "sticky # timeout" command.
01-19-2006 07:30 PM
Ramin,
As the hashing is a calculation, it will always return the same result regardless of whether an existing entry is found, unless a real server was to fail or a failed server recovered. You can control sticky "time to live" or aging if you use a sticky config, using the "sticky # timeout" command.
01-20-2006 05:01 AM
Hi Peter,
thanks for your relpy. Makes sense to me. I will go with sticky config.
Regrads,
Ramin
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide