Symantec 10521146 Administration Guide - Page 292
Removing nodes from a failover group, Viewing incidents during failover, Edit Software Node
UPC - 037648268134
View all Symantec 10521146 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 292 highlights
292 Advanced configuration Establishing high availability failover Removing nodes from a failover group Symantec Network Security provides an efficient way to remove nodes from a failover group. To remove a node from a failover group 1 In the Network Security console, edit the active or standby objects to the network topology tree. 2 In Edit Software Node or Edit 7100 Series Node, under Failover Group Information, deselect Failover Group Member. 3 Click OK to save the changes to the topology tree. 4 Reset the Enable Watchdog Process parameter for this node to false. See "Setting Enable Watchdog Process" on page 294. Note: SuperUsers can remove nodes from a failover group; Administrators, StandardUsers, and RestrictedUsers cannot. See "User groups reference" on page 319 for more about permissions. Viewing incidents during failover Symantec Network Security provides the ability to view incidents from standby nodes during a failover. Enabling this feature causes incidents to load from all nodes in the cluster, including any standby nodes, and thus avoids dropping incidents. When a failover occurs, the incident table remains unchanged. However, this does not extend to the reporting feature, because reports are generated from active nodes only. In addition to viewing incidents from standby nodes during failover, the following includes characteristics of failover behavior: ■ Symantec Network Security maintains multiple nodes, each with its own unique ID number. One node in each failover group is recognized as active, the others as standby. Each node uses its own detection interface connections. ■ Each node stores duplicate data that the Network Security console handles according to the precedence order. For exclusive actions, all nodes within the group communicate to determine the active node. Both the primary node and the standby node detect and report on incidents and events. ■ The standby node processes the same data, performs the same analysis, and evaluates the same response rules as the active software or appliance node, but does not execute duplicate responses.