Cisco Cisco Email Security Appliance C170 Guia Do Utilizador

Now you can edit the Paris group-level DNS settings, and other machines in the Paris group will inherit 
them. Non-Paris machines will inherit the cluster settings, unless they have machine-specific settings. 
Besides DNS settings, it is common to create group level settings for SMTPROUTES.

Tip: when using the CLI CLUSTERSET function in various menus, you can use a special option to copy 
settings to All Groups, which is not available through the GUI.

Tip: complete listeners will be automatically inherited from the group or cluster, and you normally only 
create these on the first system in the cluster. This reduces administration considerably.  However, for 
this to work you must name the Interfaces identically throughout your group or cluster.

Once the settings are defined correctly at the group level, you can join machines to the cluster and make 
them part of this group. This requires two steps:

First, to join our remaining 4 systems to the cluster, we run 

clusterconfig

 on each. The larger and more 

complex the cluster, the longer it takes to join, and this can take several minutes. You can monitor the 
joining progress with the LIST and CONNSTATUS sub-commands. After the joins are complete you can 
use SETGROUP to move the machines from the Main_Group into Paris and Rome. There is no way to 
avoid the fact that initially, all machines added to the cluster inherit the Main_Group settings, not the 
Paris and Rome settings. This could affect mail flow traffic if the new systems are already in production.

Tip: do not make your lab machines part of the same cluster as your production machines.  Use a new 
cluster name for lab systems. This provides an added layer of protection against unexpected changes 
(someone changing a lab system and accidently losing production mail, for example).

Override settings, and start with default settings. For example, the default settings for the 
SMTPROUTES configuration is a blank table, which you can then build from scratch.

Override settings, but start with a copy of the settings currently inherited from Cluster xxx, or group yyy.  
For example, you may want to a new copy of the SMTPROUTES table at the group level which is 
initially identical to the cluster table. All Cisco appliances that are contained in that same group 
(SETGROUP) will get this table. Machines not in the group will still use the cluster level settings. 
Changing the SMTPROUTES on this independent copy of the table will not affect other groups, 
machines inheriting the cluster settings, or machines where the setting is defined at the individual 
machine level. This is the most common selection.

Manage settings, a sub-menu of Centralized Management Options.  From this menu you can copy as 
above, but you can also move or delete settings. If you move the SMTPROUTES to a group or machine 
level, then the routes table will be blank at the cluster level but will exist at the more specific level.

Manage settings. Continuing our SMTPROUTES example, using the delete option will also result in a 
blank SMTPROUTES table for the cluster. This is fine if you previously configured definitions for 
SMTPROUTES at the group level or machine levels.  It is not a best practice to delete the cluster level 
settings and rely only on group or machine settings.  The cluster-wide settings are useful as defaults on 
newly added machines, and keeping them reduces the number or group or site settings you have to 
maintain by one.

Q. I have a previously configured standalone machine and I join an existing cluster. What happens to my 
settings?