Forum Discussion
Cory_O
Aug 25, 2015Cirrus
We have ADCs on both the upstream and downstream sides of our AirWatch SEG environment. Since all the devices are merely MS Exchange ActiveSync clients, we used the same persistence and overall settings as detailed in the F5 Exchange Deployment Guide. Simply follow the manual process in the guide for the ActiveSync service.
Health monitoring on the upstream side [SEG] required the following three monitors:
ltm monitor https /Common/ActiveSync_https_monitor {
cipherlist DEFAULT:+SHA:+3DES:+kEDH
compatibility enabled
defaults-from /Common/https
destination *:*
interval 10
ip-dscp 0
recv "HTTP/1.1 401 Unauthorized"
send "GET /Microsoft-Server-Activesync HTTP/1.1\\r\\nHost: %YOUR_FQDN_HERE%\\r\\nConnec
tion: Close\\r\\n\\r\\n"
time-until-up 0
timeout 31
}
ltm monitor https /Common/EASIntegration_https_monitor {
cipherlist DEFAULT:+SHA:+3DES:+kEDH
compatibility enabled
defaults-from /Common/https
destination *:*
interval 10
ip-dscp 0
recv "HTTP/1.1 200 OK"
send "GET /SegConsole/management.ashx\?ping HTTP/1.1\\r\\nHost: %YOUR_FQDN_HERE%\\r\\nC
onnection: Close\\r\\n\\r\\n"
time-until-up 0
timeout 31
}
ltm monitor https /Common/SEGConsole_https_monitor {
cipherlist DEFAULT:+SHA:+3DES:+kEDH
compatibility enabled
defaults-from /Common/https
destination *:*
interval 10
ip-dscp 0
recv "HTTP/1.1 200 OK"
send "GET /SegConsole/default.aspx HTTP/1.1\\r\\nHost: %YOUR_FQDN_HERE%\\r\\nConnection
: Close\\r\\n\\r\\n"
time-until-up 0
timeout 31
}
This is of course assuming you're using SEG and not another AW product!
I hope that helps!
-C