Amer Networks E5Web GUI - Manual (Page 710)

Note: IP addresses could be public IPv4 addresses
The term "private IPv4 address" is not strictly correct when used here. Either
address used in an IP4 HA Address object may be public if management access
across the public Internet is required.
9. Save and activate the new configuration.
10. Repeat the above steps for the other Clavister Security Gateway but this time select the
node type to be Slave.
Making Cluster Configuration Changes
The configuration on both Clavister Security Gateways needs to be the same. The configurations
of the two units will be automatically synchronized. To change something in a cluster
configuration, log on to either the master or the slave, make the change, then save and activate.
The change is automatically made to both units.
11.3.4. Verifying that the Cluster Functions Correctly
Important: Perform shutdown on both master and slave
After the cluster has been configured, it is highly recommended to perform a shutdown
operation on both cluster units so they restart at approximately the same time. This is
done separately for each unit through the Web Interface or using the CLI command:
Device:/> shutdown
This will ensure both units will try to correctly synchronize with each other.
This step can be skipped but may be necessary later if synchronization does not succeed
or other problems occur.
To verify that the cluster is performing correctly, first use the ha command on each unit. The
output will look similar to the following for the master:
Device:/> ha
This device is an HA MASTER
This device is currently ACTIVE (will forward traffic)
HA cluster peer is ALIVE
Then use the stat command to verify that both the master and slave have about the same
number of connections. The output from the command should contain a line similar to the
following:
Connections 2726 out of 128000
The lower number on the left in this output is the current number of connections and the higher
number on the right is the maximum number of connections allowed by the license.
The following points are also relevant to cluster setup:
• If this is not the first cluster in a network then the Cluster ID must be changed for the cluster
Chapter 11: High Availability
710