Forum Discussion

Tom_130951's avatar
Tom_130951
Icon for Nimbostratus rankNimbostratus
Jan 26, 2015

F5 Iapps deployment for Microsoft Exchange 2010.

Hi, I am currently deploying the F5 Iapps f5.microsoft_exchange_2010_2013_cas.v1.4.0

 

for my exchange 2010 enviroment.

 

I have a few questions regarding : 1. SNAT Pool Idle timeout: The qkview warned of the indefinite Timeout on SNAP Pool which may cause memory exhaustion. What value is recommended for exchanged? 2. HA Pair settings: F5 strongly recommend auto last hop for F5 LTM . How ever, in a 6509 HSRP environment , this may cause disruption of traffic for long live connection. thus, F5 recommends to use Last Hop Pool for HSRP /VRRP environment. Have any one has the need to use this for Exchange VS?

 

3. Any mirroring required/recommended for exchange ( connection / persistence etc. mirroring) or the application is roburst enough to recover itself.

 

I have tried open support cases but have been given text book answers mostly.

 

Any information would be greatly appreciated. Thanks, Tom

 

1 Reply

  • Hi Tom,

     

    regarding your questions:

     

    1. "SNAT Idle Timeout" should be equivalent to idle timeout settings in the related tcp profiles of your virtual server.

     

    2. AutoLastHop is faster than looking up routing tables when forwarding responses back to a client. But I guess this will have a significant impact on highly utilized systems only. Make sure to have proper routes configured to handle responses in case you want to turn off AutoLastHop. Turning it off will help to maintain connections if there is a failover on the nexthop firewall / routing gear.

     

    3. I don´t see a problem with turning on mirroring for virtual server and persistence profile. But it will double the traffic (as all traffic is replicated to peer unit) and you will observe increased CPU load on both units in your sync-failover device group.

     

    Thanks, Stephan

     

    PS: In case you are using the iApp to create the configuration items it will be necessary to disable "Strict Updates" (WebUI: iApps >> Application Services >> [Advanced Properties]).

     

    If you run the iApp again, all changes will be overwritten!