Installation guide
7 Load balancing and high availability
Sophos Mobile Control (SMC) makes it possible to set up a high-availability environment. This ensures that the SMC service remains externally accessible and tasks can be further processed even after failure of a Sophos Mobile Control node. To achieve this, load balancing, that distributes client and browser sessions by using DNS Round Robin to the available nodes, is required.
The following describes setting up clustering for Sophos Mobile Control and configuring load balancing by means of Sophos UTM.
7.1 Requirements
■
■
■
■
One separate Windows server for each Sophos Mobile Control node.
All nodes must be on the same network.
One Microsoft SQL or MySQL database server or cluster.
Sophos UTM or Apache Reverse Proxy (mod_proxy) for load balancing. Load balancer must support permanent session cookies and official SSL web server certificates.
Note: For detailed information about the installation requirements see http://downloads.sophos.com/readmes/readsmc_6_eng.html
and https://www.sophos.com/en-us/medialibrary/PDFs/documentation/smc_6_s_eng_supplement.pdf
.
Architecture
For an example of a three-node Sophos Mobile Control cluster see Architecture examples (page
7).
For multicast communication between the individual Sophos Mobile Control nodes, optionally a separate network can be used. The network interface to be used can be selected during cluster configuration, as described in
Set up the first node
(page 26). It may also be a VLAN.
Note: If you want to operate a second Sophos Mobile Control cluster for test purposes, a separate network is needed.
Ports and protocols
The following table shows the required ports and protocols for communication between the individual nodes of a Sophos Mobile Control server cluster.
Protocol
TCP
TCP
Ports
7600, 54200, 57600
7600, 57600
Destination
<Incoming>
<Outgoing>
25
