Verifying That The Cluster Functions Correctly - D-Link NetDefendOS User Manual

Also select the Advanced tab for each interface and set the High Availability, Private IP
Address field to be the name of the IP4 HA Address object created previously for the
interface (NetDefendOS will automatically select the appropriate address from the master
and slave addresses defined in the object).
10. Save and activate the new configuration.
11. Repeat the above steps for the other NetDefend Firewall but this time select the node type
to be Slave.
Making Cluster Configuration Changes
The configuration on both NetDefend Firewalls needs to be the same. When using the Web
Interface or CLI for management the configurations of the two units will be automatically
synchronized, provided automatic synchronization is enabled. To change something in a cluster
configuration, log on to either the master or the slave unit as an administrator, make the change,
then save and activate. The change is automatically made to both units. Automatic
synchronization is discussed in more depth in Section 11.1, "Overview".

11.3.4. Verifying that the Cluster Functions Correctly

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:
gw-world:/> 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
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.
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:
gw-world:/> 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.
832
Chapter 11: High Availability