Forum Discussion
Brian_Mayer_841
Jan 20, 2012Nimbostratus
I should also note that I'm only using the basic HTTPS monitor now, which only confirms that SSL traffic is reaching ISA. I conducted a failure test (took down the backend Exchange Client Access systems) to simulate a failure and the LTM did not know that the backend was in a bad state. As I feared, a simple HTTPS monitor only confirmed that the SSL port is up on the frontend NIC of the ISA hosts.
So as I mentioned I'm now trying to configure a more intelligent monitor - one in which the LTM calls the OWA application and passes login credentials, then pattern matches something off of the resulting page. Here's what I've been testing with, to no avail:
SEND: GET /owa HTTP/1.1\r\nHost: dev.mail.company.com\r\nConnection: Close\r\n\r\n
RECV: Set-Cookie: cada (I chose this because I found that I have a cookie, which starts with this string, set upon successful login to OWA)
I also did some TCPDUMPs as well to dig into the failing HTTPS monitor traffic and for some reason the SSL cert key was not able to decrypt the capture traffic so I couldn't really tell where or why the probe was failing. So, still flying blind here!
Any help is much appreciated. Thank you all in advance.
Regards,
Brian