03-06-2013 05:43 AM
Hello all,
I am having a weird problem. I have an HTTPS probe that sometime fail, sometimes does not fail.
probe tcp TCP_443
port 443
interval 20
passdetect interval 20
probe https TEST-HTTPS
interval 20
passdetect interval 20
request method head url https://10.31.1.210/default.htm
expect status 200 200
The probe that sometimes fails is the TEST-HTTPS. The TCP_443 probe works perfectly well.
The ACE is configured in bridge mode.
Is it possible to capture the PROBE traffic on the ACE side?
thanks in advance,
Fernando
Solved! Go to Solution.
03-06-2013 09:12 AM
Fernando,
It sounds good then.
Mark it if it was helpful.
Good luck!
Jorge
03-07-2013 09:52 AM
Hi Fernando,
Just one observation, the probe should look like this:
probe https TEST-HTTPS
interval 20
passdetect interval 20
request method head url /default.htm
expect status 200 200
---------------------
Cesar R
ANS Team
03-06-2013 08:52 AM
Fernando,
This type of traffic is not captured by using the ACE's capture.
I would recommend to run a Wireshark capture on the servers themselves directly.
Thank you, hope this helps!
Jorge
03-06-2013 09:09 AM
I was hoping that there was a way to capture the probe traffic within the ACE.
Thanks anyway for your help, I will do the capture on the servers with wireshark.
Thanks!
Fernando
03-06-2013 09:12 AM
Fernando,
It sounds good then.
Mark it if it was helpful.
Good luck!
Jorge
03-06-2013 09:19 AM
Jorge,
How can I verify in the capture if the HTTP server is giving the correct answer
to the ACE? (or the answer the ACE expects to mark the probe as SUCCESS)
thanks,
Fernando
03-06-2013 09:21 AM
ACE is going to try to access: https://10.31.1.210/default.htm and wait for a 200 OK.
Jorge
03-07-2013 09:52 AM
Hi Fernando,
Just one observation, the probe should look like this:
probe https TEST-HTTPS
interval 20
passdetect interval 20
request method head url /default.htm
expect status 200 200
---------------------
Cesar R
ANS Team
03-08-2013 01:25 AM
Hi,
If it is not in production or if you dont have much load.
You can try playing with few of the debug option:
debug hm errors
debug hm events
debug hm info
The above will help you to identify the errors.
Also refer:
regards,
Ajay Kumar
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