Forum Discussion
Russell_77729
Nimbostratus
NimbostratusPersistence Profile for ActiveSync and AirWatch
Sorry if this sounds like a dumb question but I am still learning how to tame the beast that is LTM. I am using LTM to load balance ActiveSync coming in from an AirWatch server in the DMZ. the iApp...
That's a very old version of the iApp. The problem is that the default source IP persistence is overriding the command to persist on the basic auth header in the iRule.
You could disable strictness and remove the source IP persistence from the VIP, but I recommend upgrading your deployment using the new v1.4.0 template since it has many other fixes. You can get an RC version here: https://devcentral.f5.com/wiki/iApp.Microsoft-Exchange-2010-and-2013-iApp-Template.ashx
Or you can wait until October 6th, when we'll be officially releasing v1.4.0 to downloads.f5.com. If you do decide to go with the RC, you'll still want to get the official version once it's out.
Russell_77729Nimbostratus
NimbostratusYes, 2010, ActiveSynce was deployed using f5.microsoft_exchange_2010_cas.2012_06_08.
ltm virtual aa_exch2010_activesync_as_https {
app-service /Common/aa_exch2010_activesync.app/aa_exch2010_activesync
destination /Common/xx.xx.xx.xx:https
ip-protocol tcp
mask 255.255.255.255
persist {
aa_exch2010_activesync_source_address_persistence_profile {
default yes
}
}
pool aa_exch2010_activesync_as_pool
profiles {
/Common/ntlm { }
aa_exch2010_activesync_caching_profile { }
aa_exch2010_activesync_clientssl {
context clientside
}
aa_exch2010_activesync_http_profile { }
aa_exch2010_activesync_lan-optimized_tcp_profile {
context serverside
}
aa_exch2010_activesync_oneconnect { }
aa_exch2010_activesync_serverssl {
context serverside
}
aa_exch2010_activesync_wan-optimized-compression_profile { }
aa_exch2010_activesync_wan-optimized_tcp_profile {
context clientside
}
}
vlans-disabled
}