Forum Discussion
AltostratusExchange_active_sync_issue
Hello ,
we have an issue with active sync. we are using f5 for load balancing for CAS.But real ip is being published to wan through our proxy and firewall is doing source nat to proxy as part of security and proxy is seeing single ip as source ip and proxy is sending single ip to f5. But f5 cannot load balance probably and so f5 is sending packets to single member due to persistence. is there a way to solve the issue with any i rule or Do we need to remove source nat config from proxy? if we remove nat from proxy, we need to accept any wan ip for load balancing. Could i please get your explanation. Can we do destination nat on the topology.
Clients --->firewall---> proxy---->f5----> cas nodes
Thanks,
3 Replies
Did you deploy the application with the latest iApp? It sounds like you are useing source persist and do not have oneconnect enabled. With the iApp I believe it using a iRule to and doing universal persist based on the Auth cookie.
persist uie [HTTP::cookie "OutlookSession"] 3600
waterfall_10467yes i have deployed it with latest iapp template" f5.microsoft_exchange_2010_2013_cas.tmpl " and i did not change anything on the configuration. in any case ,i checked config again but i think everything is ok for the deployment.
A__Gotink_33511Nimbostratus
The iApp template uses an iRule to determine persistence. For Active Sync it is "persist uie [HTTP::header "Authorization"] 7200" You can check this usage by looking at statistics for the persistence records.
But we also face a problem that active sync connections are not evenly balanced...
