Forum Discussion
Ken_107043
Nimbostratus
NimbostratusExchange 2010 Monitors for LTM
I'm still pretty green when it comes to what can be done with the LTM, but I haven't had much luck getting it to perform how I would like.
The deployment guides for Exchange 2010 are far fro...
What I meant by that statement is that you can't use a local hostname, but have to use the external FQDN, for the monitor string.
Let's say you have 3 CA servers: ca0.domain.com (10.0.0.10), ca1.domain.com (10.0.0.11) and ca2.domain.com 10.0.0.12). You correctly configure the external URL for OWA to be something like https://owa.domain.com/owa, and correctly set up SSL offloading: removing the requirement for SSL on the appropriate IIS directories and creating the correct Registry entry on each server. You leave the internal URL untouched on each (so https://ca0.domain.com/owa, https://ca1.domain.com/owa, and https://ca2.domain.com/owa, respectively).
If you ssh to the BIG-IP, you can start to test connect strings. Pick host ca0 and do the following (where represents hitting Enter, and for everything after the first telnet, will translate to \r\n in the monitor string).
telnet 10.0.0.10 80
GET /owa/auth/logon.aspx?url=http://ca0.domain.com/owa/&reason=0 HTTP/1.1
User-Agent: Mozilla/4.0
Host: ca0.domain.com
That will work just fine for ca0, but will fail for ca1 and ca2, so it's the wrong way to go. You must use the external FQDN (owa.domain.com in this case) in place of any of the local FQDNs (ca0.domain.com, etc.), like so:
telnet 10.0.0.10 80
GET /owa/auth/logon.aspx?url=http://owa.domain.com/owa/&reason=0 HTTP/1.1
User-Agent: Mozilla/4.0
Host: owa.domain.com
Which when translated to the BIG-IP monitor GUI input field would be:
GET /owa/auth/logon.aspx?url=http://host.domain.com/owa/&reason=0 HTTP/1.1\r\nUser-Agent: Mozilla/4.0\r\nHost: owa.domain.com\r\n\r\n
