We would like to see the hash value calculated by the ACE when the HTTP probe hash command configured.
This is possible on CSS via the "sh service" command. We have tried to get it from sh rserver , sh probe XXX detail sh serverfarm XXX det but we do not get it.
Is this possible to get it on the ACE as we do on the CSS?
We need this to manually configure it via the hash <value> command because if the ACE probe is reseted for any reason, the probe http hash will be re-calculated based on the first http response of the server and we can not predict that the server will give the expected web page at this time.
A // question is: on what the md5 value is calculated? HTTP header + payload or only http object payload? We have calculated the md5 hash value by ourselves but the probe is still failing whatever the http portion used for the calculation is.
We would like to set it because the server application generates a OK web pages when it has checked all the internal processes and a NOK web page when at leats one process is failing.
If we use just the hash command (without the value) and if the probe is reseted for any reason, it will request the web page and make the hash based on the server response and will compare the next http page it gets from the server with this hash.
If the server sends back the NOK page during the probe first attempt, the hash will be based on this web page and not on the OK web page. This will make the probe state to be success and then failed if the web sends back the OK web page.
We needs the hash value of the OK web page to ensure the probe state is success when OK web page is sent back by the server to the ACE probe.
We tested to calculate the md5 hash value of a HTTP data (data length = Content-length parameter in http header) and put is as the value of the hash command. but the probe was still failing.
Is there any special calculation method used by the ace: i mean not only http data.
I'm doing something similar to what you're doing where I check a bunch of processes and return "SUCCESS" when all processes I'm concerned about are running correctly and I return "FAILED" when some of my processes do not pass testing. In either case the page returned is error code 200 (valid page). So in my case I check for a string value of SUCCESS and anything else is considered a failure. So I suppose in your case you would have to change the string value since OK is a substring of NOK.
One thing I haven't tested is a scripted probe. If you take a look at the example HTTP probe (you can download from Cisco) you can see where they use regular expressions to parse server responses. You can easily modify the probe to ensure that you have OK and not NOK as a pass criteria.
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...