Forum Discussion
ScottB_85935
Nimbostratus
Jan 23, 2012Outlook WEB APP Sessions timing out
Hello,
We have recently migrated to Exchange 2010, and leverage F5 devices in a single virtual Server setup to load balance between our Exchange 2010 CAS front-end servers.
What we are experiencing are that Outlook Web App sessions (Web based mail for Ex2010) are timing out randonly early disconnecting clients. When using OWA one has the option to choose 'public' (15 minute timeout) or 'private' (8 hour timeout), but sometimes randomly users will select 'Private' option and still will be timed out/disconnected in 5 minutes.
Does anyone have any ideas on what might remedy this?
Also, F5 support directed me to the following technote.
http://support.f5.com/kb/en-us/solu...r=18886310
Could this idle timeout setting of 5 minutes be stepping on the 15 minute public, and 8 hour private setting? How do F5 settings work with Exchange Services like OWA that have custom timeout settings?
This is the portion of the irule in which we account for OWA connections that defaulted from the F5/Exchange 2010 single virtual server deployment template.
}
default {
This final section takes all traffic that has not
otherwise been accounted for and sends it to the
pool for Outlook Web App
persist cookie
pool Ex2010_single_owa_pool
If using the Web Accelerator module, uncomment the
following line and change the name to that of
your WA class.
HTTP::class select Ex2010_single_wa_http_class
}
}
}
Thanks in Advance. This has been very frustrating to resolve.
Scott B.
11 Replies
- J_Ford_41146
Nimbostratus
I'm seeing the same issue when moving to the latest version of the Exchange iApp. The newest version fixed an issue I was having with getting Outlook Anywhere to work with Exchange 2010, but inadvertently caused this OWA timeout bug. I ended up rolling back to the previous version of the iApp until this gets sorted out.
Does anyone have any idea if changing the idle timeout as noted in SOL7166 resolves this issue?
Thanks,
J - mikeshimkus_111Historic F5 Accounthi Scott/J,
After a bit of work today, we think we've come up with an iRule to honor OWA connection timeouts. Can you apply this rule to your OWA virtual server and let us know how it works for you? We have this on a list of fixes for the next version of the iApp.
thanks
Mike
when HTTP_REQUEST {
if { ([HTTP::method] eq "POST") && ([HTTP::path] contains "/owa/auth.owa") } {
set content_length [HTTP::header "Content-Length"]
HTTP::collect $content_length
if { ([HTTP::payload $content_length] contains "flags=4") || ([HTTP::payload $content_length] contains "flags=5") } {
IP::idle_timeout 28800
} elseif { ([HTTP::payload $content_length] contains "flags=0") || ([HTTP::payload $content_length] contains "flags=1") }{
IP::idle_timeout 900
} else {
return
}
}
} - mikeshimkus_111Historic F5 AccountFYI, you will need to disable strictness on your Exchange iApp before attaching this rule to the virtual server. Once you have disabled strictness, you will need to run this command from the BIG-IP command line:
bigstart restart bigd
This is a known bug with iApp strictness that will be addressed in a future release.
thanks - J_Ford_41146
Nimbostratus
Mike,
Thanks for passing this along. I'm going to implement this and will get back to you with the results. Really appreciate the help on this one!
Cheers,
J - mikeshimkus_111Historic F5 AccountNo problem. Here's an alternate way to do it if that one ends up giving you issues:
when HTTP_REQUEST {
if {[HTTP::method] eq "POST" && [string tolower [HTTP::path]] contains "/owa/auth.owa"}{
Trigger collection for up to 1MB of data
if {[HTTP::header "Content-Length"] ne "" && [HTTP::header "Content-Length"] <= 1048576}{
set content_length [HTTP::header "Content-Length"]
} else {
set content_length 1048576
}
Check if $content_length is not set to 0
if { $content_length > 0} {
HTTP::collect $content_length
}
}
}
when HTTP_REQUEST_DATA {
Check the flags parameter value
switch [URI::query "?[HTTP::payload]" flags] {
0 -
1 {
IP::idle_timeout 900
}
4 -
5 {
IP::idle_timeout 28800
}
}
} - blaksplash_1044
Nimbostratus
Hey mikeshimkus,
we are having an issue that seems exatly like this. We updated the iApps to version iapps-1.0.0.4.0, but OWA is still randomly kicking people out after 3-5 minutes. I tried both iRules you listed, but the problem is still there. BTW, I put your iRules at the top of the list when I tested. But, I have found that if I disable all servers in the pool except for 1, the issue is not there. So this may be related to server persistence.
Any ideas?
thanks - mikeshimkus_111Historic F5 AccountI think this is related to a separate issue with the persistence profile not treating the cookie as a session cookie, although that option is checked in the profile settings.
The workaround, which will be included in the next update to the iApp, involves setting the timeout to zero on the cookie persistence profile. You will need to disable strictness on the iApp before running this command.
Here is the command:
tmsh (enters tm shell)
modify ltm persistence cookie timeout 0 (sets timeout to zero)
quit (exits tm shell)
If you are running version 11.0 or 11.1, you will then need to restart the bigd process from the BIG-IP command line (not tmsh):
bigstart restart bigd
Please let me know if that fixes the issue. - mikeshimkus_111Historic F5 AccountSorry, the formatting left out some of that command; it should be:
modify ltm persistence cookie (application name)_cookie_persistence_profile timeout 0 - FernL_29896
Nimbostratus
I had the same issue on our end, OWA disconnects after 5 minutes, when using template f5.microsoft_exchange_2010_cas.2012_04_06 . F5 support recommended downloading and using the latest version of the exchange CAS template, f5.microsoft_exchange_2010_cas.2012_06_08. This template is only available for LTM v12, but F5 support said it's ok to use on v11, which we did.
We applied the template to the existing OWA applicaiton and this immediately fixed the OWA disconnect issue, and possibly another issue with ActiveSync activation intermitently failing. We're in the process of testing but all looks good so far. - Bjarne_10209
Nimbostratus
Had the same problem. A OWA session timed out after 180 sec. Doing as described in SOL11679 solved my timeout problem.
http://support.f5.com/kb/en-us/solu...11679.html
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects