Load Balancing your Zimbra Environment

Configuration has yet to be fully verified, Kemp Support will gladly assist if your Zimbra traffic is not flowing as expected.

 

1   Introduction

Zimbra, also known as Zimbra Collaboration Suite or ZCS, is a group collaboration software suite developed by Zimbra, Inc. It is available for free as an open source package, or as a commercial "Network Edition".

 

1.1  Document Purpose

This section details a configuration for a specific application that has been provided by a customer but has yet to be fully tested.

This specific configuration will ensure that your Zimbra servers are highly-available, scalable, and secure.

Configuration has yet to be fully verified, Kemp Support will gladly assist if your Zimbra traffic is not flowing as expected.

 

2. Configuration Required

Two Virtual Services will be required, one for Web Access, and one for Admin Access,  both Listening on port 443 with SSL-Acceleration (Offloading) required for Admin Access VS.

 Depending on your environment A content rule will also be required for Admin Access VS, which will be a response rule to overcome a HTTP 302 port 9071 redirect sent from the server to the client, this will change the redirect to port 443. If you believe this 302 is not taking place, you can skip sections 2.2 and 3.6.

 

2.1  Global Configuration

 

2.2   Create Content Rule

     > Rules & Checking

     > Content Rules

     >  New Rule

 

3.0    Virtual Service Configuration: 

 

 3.1   Web Access Virtual Service

      > New Virtual Service

      > Enter IP Address

      > Port = 443

      > Name = Zimbra Proxy Web Access

      > Add New Virtual Service


 

3.1     Standard Options   

      > Disable Transparency

      >  Persistence = Source IP

      >  Persistence Time = 1 Hour 

      > Scheduling Method = Round Robin

 

3.2    Real Servers

      > Checker Parameter Type = HTTPS 

      > Check Port =  443

      > Add New 

      > Enter Real Server IP Address

      > Port = 443

      > Forwarding Method = NAT

      

 

3.3     Admin Access Virtual Service 

      > New Virtual Service

      > Enter IP Address

      > Port = 443

      > Name = Zimbra Admin Access

      > Add New Virtual Service


 

3.4     Standard Options   

      > Disable Transparency

      >  Persistence = Source IP

      >  Persistence Time = 1 Hour 

      > Scheduling Method = Round Robin

 

 

3.5     Enable SSL Acceleration  (Enable Re-encryption if Server Requires)

      >  Re-Encrypt if server requires secure connection

      >  Assign Certificate

    

 

3.6   Add Response Rule To VS

       > Advanced Options

       >  HTTP Header Modifications -

       

     >  Add Rule 

     

 

3.7    Real Servers

      > Checker Parameter Type = HTTPS 

      > Check Port =  443

      > Add New 

      > Enter Real Server IP Address

      > Port = 443

      > Forwarding Method = NAT

      

 

If you have successfully Load Balanced your Zimbra environment by implementing this specific configuration, please give a thumbs up or please leave a comment on a possible alteration that was required to make it function. Thank you

 

1

0 comments

Please to leave a comment.

Didn't find what you were looking for?