Symantec™ Security Gateways Reference Guide - Sawmill

132 Ensuring availabilityCluster administrationThe new node is only aware of the reference node at this point because the small record passed by thereference node contained only the IP address of the reference node. The new node does not have a clusterconfiguration yet, so the new node listens to messages from the reference system. Once the new nodedetermines that the reference system has the most current configuration, synchawk on the new noderetrieves the configuration from the reference node. The new node now has the complete clusterconfiguration record, including information on any other nodes in the cluster. An activate changes is doneon the new node automatically as part of the retrieval process, and the new node is now in sync with thecluster.Configuration information for creating a cluster and adding nodes to a cluster is found in your product’sadministrator’s guide.Deleting nodes from a clusterThe node being deleted is left in one of two possible states after being removed from the cluster. The nodeeither maintains the current configuration, minus the cluster attributes, or reverts back to its original statebefore joining the cluster. If you elect to keep the current configuration, the cluster configurationinformation is deleted, but the location and policy information is preserved and used as the activeconfiguration. Choosing to revert back to the original configuration removes all configuration changes thattook place after joining the cluster.Warning: You cannot delete a cluster node from the node to be deleted; you must be on another node.Configuration information for deleting nodes from a cluster is found in your product’s administrator’sguide.