For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Kashif_Rana_493's avatar
Kashif_Rana_493
Icon for Nimbostratus rankNimbostratus
Apr 10, 2013

Load Balance Exchange 2010 Server

Hi All

 

I have three CAS servers. I want to load balance these three servers. I have only one virtual IP. Should I need to create three VS as below:

 

1- One VS for Outlook any where

 

2- One VS for Address Book

 

3- One VS for RPC

 

Please also advise the recommended load balancing and monitor method?

 

Looking for the reply

 

Thanks

 

 

3 Replies

  • AndOs's avatar
    AndOs
    Icon for Cirrostratus rankCirrostratus

    Hi!

     

     

    We recently deployed Exchange 2010 in our organization together with Big-IP LTM and APM.

     

    I found some useful information in the exchange iapp deployment guide regarding setup of VIPs and what protocols are involved in the different exchange services.

     

    http://www.f5.com/pdf/deployment-gu...app-dg.pdf

     

     

    Which loadbalancing method to choose depends on how you would like to distribute clients depending on server load; Doing simple round robin, or one of the more intelligent methods.

     

     

    For RPC we use a simple tcp monitor on port 135. The HTTP based services can be monitored by a simple http monitor, or by something more specific for each service. Again, it depends on your needs.

     

     

    We used the iApp template for exchange 2010 to get a basic config and then made customizations to that.

     

    That got us up and running pretty fast with monitors and loadbalancing methods for the services we had chosen.

     

     

    /Andreas

     

  • Deployment guide are very usefuel, you can almost totally based you configuration on those documents.

     

    I'm deploying a two-CAS scenario right now and using only one IP address for using in 4 different VS:

     

     

    1.- VS::80 only to redirecto to VS:443

     

    2.- VS::443 for all HTTPs based Services

     

    3.- VS::135 for non-http traffic (outlook client)

     

    4.- VS::* for outlook client when using no-rpc ports in the same session.

     

     

    Using this ONE-IP scenario makes use an iRule to define persistence based on the service accessed by the client but it's clearly deifined on the deployment guide.

     

     

    Good luck with that!

     

     

    HH