Forum Discussion
mikeshimkus_111
Sep 06, 2013Historic F5 Account
Sounds good. BTW, if you used the iApp, EWS is persisted on source IP, ActiveSync uses the Basic auth header value, and Outlook Anywhere uses auth header or source IP. All of the other HTTP services do use cookie.
- Rabbit23_116296Sep 06, 2013NimbostratusOK I haven't phased in Outlook anywhere and ActiveSync yet because of architectural dependencies. You raise an interesting point though because I just went through the template and it presents me with the question - 'Are you deploying Outlook Anywhere? (includes EWS and OAB)' Then it only presents a single FQDN to use. I have not gone down this route yet as all traffic served through the F5 at the moment is RPC (internal), EWS (internal and external), OWA (internal and external) and Autodiscover, leaving ActiveSync and external Outlook Anywhere still going through multiple AD site NLBS that I'm in the process of decommissioning. These are the interfaces and what they are used for: Web App -- 10.187.62.21 ActiveSync -- 10.187.62.22 Autodiscover -- 10.187.62.23 RPC (ports 59523, 59524) -- 10.187.62.24 IMAP4S -- 10.187.62.25 So I could have multiple virtual servers per IP/port combos that would respect virtual server persistence profiles etc? This is something I never considered :) I did find this and not sure if it would affect our deployment as it is a simple LTM, no GTM - http://support.f5.com/kb/en-us/solutions/public/9000/800/sol9890.html Thanks for the reply.
- mikeshimkus_111Sep 06, 2013Historic F5 AccountYou can either have one virtual server that accepts traffic for all services and assigns persistence and pools using a single iRule, or separate virtual servers for each service. Persistence profiles can be set to match across virtual servers, so if I understand the question, the answer is yes, you could set up multiple virtuals maintain persistence across them as long as they share a common persistence profile where "match across" is set.