User's Guide

AirTight Management Console User Guide
108

Replication of policies from one server to another server in server cluster: Replication of most
policies from one server to another server in a server cluster is possible. This is regardless of whether
the policies are being copied from parent server to child server or child server to parent server.

Aggregation of data in dashboard widgets: The number of dashboard widgets available in AirTight
Management Console is a lot higher than those available on SpectraGuard Manager. Aggregated
data from all active servers in the server cluster is seen in most of the dashboard widgets on AirTight
Management Console.
Create and Manage Server Cluster
The creation of a server cluster and management of servers in the server cluster is done using the server
command line interface (CLI). Viewing of the aggregated server cluster data and management of policies
on the child servers from the parent server is done through AirTight Management Console of parent
server.
Following are the prerequisites to create a server cluster.

The AirTight Wi-Fi/AirTight WIPS servers that form a cluster must have the same software version
and build installed.

A valid license must have been applied to all child servers to be added to the server cluster.
 The child server must not be a part of any other server cluster.
 If a firewall is active on the network, TCP port 22 and UDP port 1194 must be open on the firewall for
cluster formation and parent-child communication. TCP port 22 is for incoming connections to child
servers and UDP port 1194 is for incoming connections to parent server.
You can perform five cluster-related operations from the server command line interface. They are as
follows.
1.
Set up a server cluster/assign parent server to a server cluster.
2. Add a child server to a server cluster.
3. Delete or remove a child server from a server cluster.
4. Delete an entire server cluster.
5. Check the status of servers in a cluster or check if a server is part of a cluster.
The servers in a server cluster are assigned IDs when they become a part of the server cluster. A parent
server is assigned 1 as ID in the cluster. As and when the child servers are added, they are assigned
sequentially incrementing IDs. The child server added first is assigned 2 as ID, the next one is assigned 3
as ID and so on.
After creating the cluster, you must mount the child servers on the parent server location tree, to be able
to view aggregated server data on the UI or push policies from parent server to child server.
The following figure illustrates the mapping of an existing location tree with child servers in a server
cluster.