Cisco Cisco Email Security Appliance X1050 Guía Del Usuario
38-21
Cisco AsyncOS 8.5.6 for Email User Guide
Chapter 38 Centralized Management Using Clusters
Cluster Communication
If you choose not to discard your changes, they are still intact (but uncommitted). You can review your
changes against the current settings and decide how to proceed.
changes against the current settings and decide how to proceed.
You can also use the
clustercheck
command at any time to verify that the cluster is operating correctly.
Interdependent Settings
In a centrally managed environment, some interdependent settings are configured in different modes.
The flexibility of the configuration model allows you to configure settings at multiple modes, and the
laws of inheritance govern which settings will be used on a per-machine basis. However, some settings
have dependencies on other settings, and the availability of the dependent settings’ configuration is not
limited to settings at the same mode. Thus, it is possible to configure a setting for one level that
references a setting that is configured for a specific machine at a different level.
The flexibility of the configuration model allows you to configure settings at multiple modes, and the
laws of inheritance govern which settings will be used on a per-machine basis. However, some settings
have dependencies on other settings, and the availability of the dependent settings’ configuration is not
limited to settings at the same mode. Thus, it is possible to configure a setting for one level that
references a setting that is configured for a specific machine at a different level.
The most common example of an interdependent setting involves a select field on a page that pulls data
from a different cluster section. For example, the following features can be configured in different
modes:
from a different cluster section. For example, the following features can be configured in different
modes:
•
using LDAP queries
•
using dictionaries or text resources
•
using bounce or SMTP authentication profiles.
Within centralized management, there are restricted and non-restricted commands. (See
.) Non-restricted commands are generally configuration commands that can be
shared across the cluster.
The
listenerconfig
command is an example of a command that can be configured for all machines in
a cluster. Non-restricted commands represent commands that can be mirrored on all machines in a
cluster, and do not require machine-specific data to be modified.
cluster, and do not require machine-specific data to be modified.
1. Force entire cluster to use test.example.com version.
2. Force entire cluster to use mail3.example.com version.
3. Ignore.
[1]>
losangeles> clustercheck
Do you want to check the config consistency across all machines in the cluster? [Y]> y
Checking losangeles...
Checking newyork...
No inconsistencies found.