Cisco Cisco Email Security Appliance X1050 Guía Del Usuario
39-12
Cisco AsyncOS 9.1 for Email User Guide
Chapter 39 Centralized Management Using Clusters
Managing Clusters
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.
Leaving a Cluster Permanently (Removal)
You use the
REMOVEMACHINE
operation of
clusterconfig
to remove a machine permanently from a
cluster. When a machine is permanently removed from a cluster, its configuration is “flattened” such that
it will work the same as it did when it was part of the cluster. For example, if there is only a cluster-mode
Global Unsubscribe table, the Global Unsubscribe table data will be copied to the machine’s local
configuration when the machine is removed from the cluster.
it will work the same as it did when it was part of the cluster. For example, if there is only a cluster-mode
Global Unsubscribe table, the Global Unsubscribe table data will be copied to the machine’s local
configuration when the machine is removed from the cluster.
Upgrading Machines in a Cluster
A cluster does not allow the connected machines to have different versions of AsyncOS.
Before you install an AsyncOS upgrade, you need to disconnect each machine in the cluster via the
clusterconfig
command. After you upgrade all the machines, the cluster can be reconnected via the
clusterconfig
command. You can have two separate clusters running while you upgrade machines to
the same version. You can also upgrade clustered machines on the GUI Upgrades page.
You can download the upgrade in the background so that you do not need to disconnect the cluster
machines until you are ready to install the upgrade.
machines until you are ready to install the upgrade.