Cisco Cisco Email Security Appliance C170 Guia Do Utilizador
35-12
Cisco AsyncOS 8.0.1 for Email User Guide
Chapter 35 Centralized Management Using Clusters
Managing Clusters
A 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.
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.
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.
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.
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.
Procedure
Step 1
Use the
clustermode cluster
command to change to the cluster mode.
Remember: the
clustermode
command is the CLI command you use to change modes to the cluster,
group, and machine levels.
Step 2
Type
listenerconfig
to see the listener settings configured for the cluster.
Step 3
Choose the machine you want to experiment with, then use the
clusterset
command to copy settings
from the cluster “down” to machine mode.
Step 4
Use the
clustermode
command to navigate to machine mode for the experimental machine, e.g.:
clustermode machine newyork.example.com
Step 5
In machine mode, on the experimental machine, issue the
listenerconfig
command to make changes
specifically for the experimental machine.
Step 6
Commit the changes.
Step 7
Continue to experiment with the configuration changes on the experimental machine, remembering to
commit the changes.
commit the changes.
Step 8
When you are ready to apply your new settings to all the other machines, use the
clusterset
command
to move the settings up to the cluster mode.
Step 9
Commit the changes.