03-13-2014 06:41 AM
Hello mates,
At two of our clients we have problems with https probes since upgrade to Exchange SP1. The probe fails with %ACE-3-251010: Health probe failed for server XXXXXXX on port 443, unrecognized or invalid response in the log.
ACE_1/VC_MAIL# show probe probe-ssl detail
probe : probe-ssl
type : HTTPS
state : ACTIVE
description : OWA HTTPS Monitoring
----------------------------------------------
port : 443 address : 0.0.0.0 addr type : -
interval : 5 pass intvl : 10 pass count : 3
fail count: 2 recv timeout: 5
http method : GET
http url : /owa/auth/logon.aspx
conn termination : GRACEFUL
expect offset : 0 , open timeout : 10
regex cache-len : 0
expect regex : -
send data : -
--------------------- probe results --------------------
probe association probed-address probes failed passed health
------------------- ---------------+----------+----------+----------+-------
serverfarm : MailFarm-HTTPS
real : sof-mail-01[443]
1.2.3.4 163 150 13 FAILED
Socket state : CLOSED
No. Passed states : 0 No. Failed states : 1
No. Probes skipped : 0 Last status code : 0
No. Out of Sockets : 0 No. Internal error: 0
Last disconnect err : Unrecognized or invalid response
Last probe time : Thu Mar 13 15:37:37 2014
Last fail time : Thu Mar 13 15:10:42 2014
Last active time : Never
real : sof-mail-02[443]
1.2.3.5 163 152 11 FAILED
Socket state : CLOSED
No. Passed states : 0 No. Failed states : 1
No. Probes skipped : 0 Last status code : 0
No. Out of Sockets : 0 No. Internal error: 0
Last disconnect err : Unrecognized or invalid response
Last probe time : Thu Mar 13 15:37:39 2014
Last fail time : Thu Mar 13 15:10:44 2014
Last active time : Never
Configuration:
probe https probe-ssl
description OWA HTTPS Monitoring
interval 5
faildetect 2
passdetect interval 10
receive 5
request method get url /owa/auth/logon.aspx
expect status 200 409
I tried to get only / not /owa/auth/logon.aspx, but the result is the same.
Do you have such issues? Some advices?
EDIT: Forgot to mention that the server is in perfect health, and when monitoring with tcp probe on 443 port everything is ok.
The URL when I try to access via browser is https://mail.xxx.bg/owa/auth/logon.aspx?replaceCurrent=1&url=https%3a%2f%2fmail.xxx.bg%2fowa
Best regards!
04-30-2014 06:04 AM
Hi There,
Did you get anywhere with this?
We have something similar.
Thanks.
05-07-2014 11:41 AM
Unfortunately no, I used plain tcp probe on 443.
I had this issue on two different networks - one was with ACE modules in 6500 switches, and the other was with 4710 appliances.
05-08-2014 06:46 AM
Thanks for the information. It appears to be a problem for quite a few, but I can't find any information with regard to a resolution.
06-30-2014 11:37 AM
We are having this exact same issue after upgrading Exchange 2013 to SP1 except with ACE-30's! We have had to reduce our "health check" to a TCP check only.
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