Load Balancing AirWatch Secure Email Gateway

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

 

1   Introduction

AirWatch is a mobile security and smartphone device management software solution created by VMware. It acts as a proxy between mobile devices and an organization's email infrastructure.

 

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 enable your AirWatch Secure Email Gateway (SEG) and Mobile Access Gateway (MAG) to be Load Balanced.

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

 

2  Configuration Required

 

2.1  Global Configuration

     >No Changes Required

 

2.2  Virtual Service Configuration: 

       4 Separate Virtual Services will be required, 1 for SEG, 3 for MAG

 

2.3  SEG  Virtual Service

      > New Virtual Service

      > Enter IP Address

      > Port = 443 

      > Name = AirWatch SEG

      > Add New Virtual Service





2.4    Standard Options   

      > Disable Transparency

      >  Persistence = Source IP

      >  Persistence Time = 30 Mins 

      > Scheduling Method = Round Robin

      >  Idle Connection Timeout = 3600 seconds

 

2.5   Real Servers

      > Checker Parameter Type = HTTPS 

      > Check Port = 443  

      > Add New 

      > Enter Real Server IP Address

     > Forwarding Method = NAT

      > Port = 443  

 

3.0   MAG 443 Virtual Service

      > New Virtual Service

      > Enter IP Address of SEG Servers

      > Port = 443 

      > Name = Mobile MAG

      > Add New Virtual Service

 

3.1    Standard Options   

      > Disable Transparency

      >  Persistence = Source IP

      >  Persistence Time = 30 Mins 

      > Scheduling Method = Round Robin

      >  Idle Connection Timeout = 3600 seconds




3.2     Real Servers

      > Checker Parameter Type = HTTPS 

      > Check Port = 443  

      > Add New 

      > Enter IP Addresses of MAG servers

      > Forwarding Method = NAT

      > Port = 443  

 

 

4.0   MAG 2010 Virtual Service

      > New Virtual Service

      > Enter IP Address of SEG Servers

      > Port = 2010 

      > Name = Mobile MAG

      > Add New Virtual Service

 

4.1    Standard Options   

      > Disable Transparency

      >  Persistence = Source IP

      >  Persistence Time = 30 Mins 

      > Scheduling Method = Round Robin

      >  Idle Connection Timeout = 3600 seconds




4.2     Real Servers

      > Checker Parameter Type =TCP

      > Check Port = 2010

      > Add New 

      > Enter IP Addresses of MAG servers

      > Forwarding Method = NAT

      > Port = 2010 

 

5.0   MAG 2020 Virtual Service

      > New Virtual Service

      > Enter IP Address of SEG Servers

      > Port = 2020 

      > Name = Mobile MAG

      > Add New Virtual Service

 

5.1    Standard Options   

      > Disable Transparency

      >  Persistence = Source IP

      >  Persistence Time = 30 Mins 

      > Scheduling Method = Round Robin

      >  Idle Connection Timeout = 3600 seconds




5.2     Real Servers

      > Checker Parameter Type =ICMP

      > Check Port = 2010

      > Add New 

      > Enter IP Addresses of MAG servers

      > Forwarding Method = NAT

      > Port = 2020

 

If you have successfully Load Balanced your AirWatch 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

 

2

0 comments

Please to leave a comment.

Didn't find what you were looking for?