Cisco Cisco Email Security Appliance C160 Mode D'Emploi

Page de 548
Chapter 7      Centralized Management
7-470
Cisco IronPort AsyncOS 7.1 for Email Advanced Configuration Guide
OL-22164-02
Copying and Moving Settings
All non-restricted (see 
) commands have new 
operations: 
CLUSTERSHOW
 and 
CLUSTERSET
CLUSTERSHOW
 is used to show in which 
modes a command is configured (see 
). The 
CLUSTERSET
 operation allows you to move or copy the current settings 
(configurable with the current command) from one mode to another or between 
levels (e.g. from a machine to a group).
copy retains the settings for the current mode. A move resets (clears) the 
configuration of the current mode; i.e., following a move, no settings will be 
configured for the current mode.
For example, if you have configured Good Neighbor Table settings (the 
destconfig
 command) for group 
northamerica
, and you decide that you want the 
entire cluster to have these settings, you can use the 
clusterset
 operation from 
within the 
destconfig
 command to copy (or move) the current settings to the 
cluster mode. (See 
.) 
Warning
Exercise caution when moving or copying configuration settings to avoid 
inconsistent dependencies. For example, if you move or copy listeners with 
disclaimer stamping configured to another machine, and that new machine 
does not have the same disclaimers configured, disclaimer stamping will not be 
enabled on the new machine. 
Experimenting with New Configurations
One of the most advantageous ways to use clusters is to experiment with new 
configuration settings. First you make changes at the machine mode, in an isolated 
environment. Then, when you are satisfied with your configuration, you move 
those configuration changes up to the cluster mode to make them available on all 
machines.
The following example shows the steps to change a listener setting on one 
machine and then publish the setting to the rest of the cluster when ready. Because 
listeners are normally configured at the cluster level, the example starts by pulling 
the configuration down to machine mode on one machine before making and 
testing the changes. You should test experimental changes of this type on one 
machine before making the change to the other machines in the cluster.