I have a question regarding return code checking for a serverfarm on ACE. I am looking to have the ability to monitor a client's session real-time and monitor return codes passing back from the origin servers to the client.
For example, if during a client's session there is a single HTTP 500 error code sent from server to client, the intercept that response and first retry the request on a different server in the farm. Or perhaps only if I see three 500 error codes in 30 seconds. Something like that.
From what I can tell from the docs the retcode check command for a serverfarm is maybe only for statistical purposes?
In ACE return codes checking is only used to count number of return codes from Rservers. Unlike CSMs (where return codes were used for inband health monitoring) ACE is not using them for load balancing or inband health
monitoring. Once you enable return code checking and counting you can then display the return code statistics per serverfarm
With 2.0 you will be able to do more than count the response code returns. you can take a server out of rotation (leaving the active connections intact but refusing new connections until the rserver is put back into rotation).
not exactly what you were looking for, but better than just keeping statistics.
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
Introduction Prepositioning is a powerful tools on the WAAS platform but
it is not always easy to figure out why your jobs are failing when
trying to retrieve the files.Here is a method that should help you to
figure out the reason why they are not succes...