F5 is upgrading its customer support chat feature on My.F5.com. Chat support will be unavailable from 6am-10am PST on 1/20/26. Refer to K000159584 for details.

Forum Discussion

Kalpesh_48932's avatar
Kalpesh_48932
Icon for Nimbostratus rankNimbostratus
Jul 16, 2013

VIP for exchange 2010 ActiveSync

hello All,

 

 

we need is the following

 

· one VIP ActiveSync

 

· Clients connects through reverseProxy et IP affinity is to exclude (3 proxy servers)

 

· No SSL Offloading if possible - SSL bridging

 

· 18000 connections concurrentes

 

· Respect the F5 configuration best practices as described in the attached document. (3 SNAT pools for examples ???? etc…)

 

 

I would like to confirm on, persistence profile can be used in such scenario (use of proxy between client and F5). we are planning to use universal persistence profile for irule of Authorisation.

 

iRule name : ActiveSync Persist

 

when HTTP_REQUEST {

 

if { [HTTP::header exists "Authorization"] } {

 

persist uie [HTTP::header "Authorization"] 7200

 

} else {

 

persist source_addr

 

}

 

}

 

 

can you please confirm the settings, which will be more appropriate and recommended? I have gone through f5-exchange-2010-dg-pdf.zip

 

 

 

 

2 Replies

  • If you got the config from the deployment guide then is likely to be OK. Since load balancing EAS may be little difficult if you're not familiar with Exchange per i'd suggest to first test with only one server in the ActiveSync pool. if that works the first then your proxy, the certificate installed on it (way to important), and the config of the F5 is correct. After confirming that you may want to tray using several pool members and the proper persistence irule

     

     

     

    regards,
  • Hello All,

     

    I created VIP based on deployment guide, however it is not working.

     

    below is the configuration from F5.

     

    virtual vs_Adex_ActiveSync { translate service disable snatpool snat_r_vs_casarray_activesync pool Pool_Adex_ActiveSync destination 10.1.1.10:https ip protocol tcp persist source_addr profiles { Clientssl_Adex_ActiveSync { clientside } serverssl { serverside } tcp {} } vlans INTERCO enable }