Managing An Established Cluster - Symantec 10521146 - Network Security 7120 Administration Manual

278 Advanced configuration
Managing node clusters

Managing an established cluster

If you want to re-add a node to the topology database after deleting it, you must
do one of the following:
For a software node: Reinstall it.
■
See the Symantec Network Security Installation Guide for reinstalling a
software node.
For an appliance node: Unconfigure and then rerun the initial configuration.
■
See the Symantec Network Security 7100 Series Implementation Guide for
unconfiguring an appliance node.
Note: SuperUsers can delete software and appliance nodes from the cluster.
Administrators, StandardUsers, and RestrictedUsers can view them, but cannot
delete them. See "User groups reference"
permissions.
This section describes the following day-to-day tasks of managing an
established cluster:
Licensing nodes in a cluster
■
Synchronizing clustered nodes
■
Changing node numbers
■
Changing node passphrases
■
Restarting sensors in a cluster
■
Licensing nodes in a cluster
The Network Security console provides an efficient way to license nodes in a
cluster.
See "Checking and applying licenses"
Synchronizing clustered nodes
Symantec Network Security automatically synchronizes between the master
node across all nodes in the cluster. Master nodes accept changes from other
master nodes, never from slave nodes. Slave nodes accept changes from any
node with a newer database.
The master node propagates information across clusters, including the global
configuration, topology database, response rule database, usernames and
passwords, user-defined signatures, and flow alert rules. Symantec Network
on page 319 for more about
on page 49.