User's Guide

AirTight Management Console Configuration
107
Set up and Manage Server Cluster
A server cluster consists of 2 or more AirTight servers grouped together. One of these servers is the
managing server and it manages one or more AirTight servers. Thus, multiple servers can be managed
from a single server console in a server cluster.
The managing server is called the parent server and the servers that are managed from the parent
server are called the child servers. The parent server retrieves aggregated data from multiple child
servers in the cluster and displays it on AirTight Management Console along with the parent server data.
Benefits of Server Cluster
Following are the benefits of server cluster vis-à-vis SpectraGuard Manager.
 Eliminates the need for a separate product to manage multiple servers: SpectraGuard Manager
is a separate product used to manage multiple servers. With the incorporation of the server cluster
functionality in AirTight server, it is a lot easier to manage multiple servers using a single console
without the need for a separate product. The server cluster is accessible through AirTight
Management Console. Various templates and policies can be pushed to child server from the parent
server location tree.

HTML 5 based product: AirTight Management Console is a HTML5 based console. Hence, it is
possible to access it from any device that has an HTML5 compatible browser.

Connects with AirTight devices: AirTight Devices can connect to the AirTight Wi-Fi/AirTight WIPS
server that acts as the parent server in the server cluster.

Ready availability of all AirTight Wi-Fi/AirTight WIPS features: All the AirTight Wi-Fi/AirTight
WIPS features are available even when a server is a part of a server cluster.

Eliminates the need for certificate-based communication: There is no need to download a
certificate for SGM and AMC communication as the functionality to manage multiple servers in a
server cluster is provided in the same product.

Automatic synchronization of policies: There is no need to manually synchronize policies on child
server if the child server is not available when the policies are being synchronized from a parent
server. This is done automatically when the child server comes up the next time.