Cisco Cisco Email Security Appliance C170 Guía Del Usuario
39-22
Cisco AsyncOS 9.0 for Email User Guide
Chapter 39 Centralized Management Using Clusters
Loading a Configuration in Clustered Appliances
Restricted commands, on the other hand, are commands that only apply to a specific mode. For example,
users cannot be configured for specific machines — there must be only one user set across the whole
cluster. (Otherwise, it would be impossible to login to remote machines with the same login.) Likewise,
since the Mail Flow Monitor data, System Overview counters, and log files are only maintained on a
per-machine basis, these commands and pages must be restricted to a machine.
users cannot be configured for specific machines — there must be only one user set across the whole
cluster. (Otherwise, it would be impossible to login to remote machines with the same login.) Likewise,
since the Mail Flow Monitor data, System Overview counters, and log files are only maintained on a
per-machine basis, these commands and pages must be restricted to a machine.
You will notice that while Scheduled Reports may be configured identically across the whole cluster, the
viewing of reports is machine-specific. Therefore, within a single Scheduled Reports page in the GUI,
configuration must be performed at the cluster mode, but viewing of reports must be done at the machine
mode.
viewing of reports is machine-specific. Therefore, within a single Scheduled Reports page in the GUI,
configuration must be performed at the cluster mode, but viewing of reports must be done at the machine
mode.
The System Time pages encompass the
settz
,
ntpconfig
, and
settime
commands, and thus represents
a mixture of restricted and non-restricted commands. In this case,
settime
must be restricted to
machine-only modes (since time settings are specific for machine), while
settz
and
ntpconfig
may be
configured at cluster or group modes.
Figure 39-8
Example of Interdependent Settings
In this representation, the listener “IncomingMail” is referencing a footer named “disclaimer” that has
been configured at the machine level only. The drop-down list of available footer resources shows that
the footer is not available on the machine “buttercup.run” which is also available in the cluster. There
are two solutions to this dilemma:
been configured at the machine level only. The drop-down list of available footer resources shows that
the footer is not available on the machine “buttercup.run” which is also available in the cluster. There
are two solutions to this dilemma:
•
promote the footer “disclaimer” from the machine level to the cluster level
•
demote the listener to the machine level to remove the interdependency
In order to fully maximize the features of a centrally managed system, the former solution is preferred.
Be aware of interdependencies among settings as you tailor the configuration of your clustered
machines.
Be aware of interdependencies among settings as you tailor the configuration of your clustered
machines.
Loading a Configuration in Clustered Appliances
AsyncOS for Email allows you to load a cluster configuration in clustered appliances. You can load the
cluster configuration in the following scenarios:
cluster configuration in the following scenarios:
•
If you are migrating from an on-premise environment to a hosted environment and you want to
migrate the on-premise cluster configuration to the hosted environment.
migrate the on-premise cluster configuration to the hosted environment.