NimbostratusExchange 2013 - looking for guidance with owa issues
Hello,
I need some assistance/guidance with deploying Exchange 2013. I have lots of experience deploying 2010 but not 2013. We have two configs in place right now and they require persistence to work (?). The MS documentation and the F5 Deployment guide state that persistence is not needed due to the change in functionality with the CAS servers.
We have a FastL4 config with source_addr persistence and snat. It is working fine as long persistence is enabled.
We have another config created with the iApp. We chose SSL Bridging (no APM), using SNAT pool and answered "Yes" to all the services. This configuration does not work. I do not see any persistence applied anywhere which is expected. We just used the self-signed cert for a quick test. Once we say continue past the certificate warning, the browser fails to load the page. Using a quick tcpdump, I do see the initial requests make it to the pool member but then it breaks immediately. Before I add persistence to the iApp created configuration, I wanted to get a sanity check and education on this topic.
1) Are they are any situations using SSL Bridging that would need persistence? Is anyone else using persistence?
2) Please educate me as needed on my potential misunderstanding of persistence with Exchange 2013 as well as any ideas that would assist me with resolving this issue. I need to understand what is going on.
Thank you,
Thank you,
