Forum Discussion
Kalpesh_48932
Nimbostratus
NimbostratusFree busy issue for exchange 2010
I am new in F5 and exchange setup and would like to understand, how we can do troubleshooting in case of exchange 2010 Free busy issue,
we had Nexus upgrade this weekend and during that, we had done failover of F5 to secure exchange traffic.
however after upgarde done, we again did failover to make initial F5 as Active.
later that day, user facing issue of Free Busy.
can you please let me know how to troubleshoot this issue on F5?
what things needs to be checked onn F5? what cause this Free busy issue?
Thanks,
5 Replies
- Hi Kalpesh, we will need more information about your deployment. Can you tell us:
- Which version of BIG-IP are you running?
- Did you use the iApp and if so, which version?
- Have you followed the post-configuration steps in the Exchange CAS deployment guide?
- Are you connecting MAPI or RPC-over-HTTP with your Outlook clients?
- Have you captured the EWS free/busy traffic using tcpdump while the problem is occurring?
thanks 
Kalpesh_48932Hi Mike,
to answer your questions,
- we are running BigIP 6900 v10
-No iApp
-This is very OLD configuration on exchange side, but yes all is based on deployment guide
- connecting using RPC over HTTP
- how to capture this output, issue is still persist.- More questions.
- Are you deployed with a single HTTP virtual server, or separate virtual servers?
- If a single virtual server, how does your combined persistence iRule account for EWS traffic? Is the pool where you are forwarding EWS traffic up?
- If a separate virtual server for EWS, is the pool up?
You will want to capture traffic using tcpdump: http://support.f5.com/kb/en-us/solutions/public/0000/400/sol411.html
You will need ssldump to decrypt the client side traffic: http://support.f5.com/kb/en-us/solutions/public/10000/200/sol10209.html
You need to look for requests for /EWS in those captures and the associated responses from the CAS. - Kalpesh_48932Hi,
Its Single HTTP server on different ports.
Yes, Irule is there and EWS pool is UP.
seems we have issue with persistance.
issue is like, user located on X site can not see F/B info of user located on Y site.
but user on Y site can see both Y and X side user F/B info - It sounds like the CAS on the X site can't contact the Availability service on the Y site. Is that service running? Can you cURL /EWS/Exchange.asmx on the CAS in site X from the CAS in site Y, and vice-versa?
