Cisco Cisco Email Security Appliance C160 Mode D'Emploi
8-35
Cisco IronPort AsyncOS 7.5 for Email Advanced Configuration Guide
OL-25137-01
Chapter 8 Centralized Management
Copy vs. Move
When to copy: when you want the cluster to have a setting, and a group or machine
to also have no settings or to have different settings.
to also have no settings or to have different settings.
When to move: when you want the cluster to have no setting at all, and for the
group or machine to have the settings.
group or machine to have the settings.
Good CM Design Practices
When you LIST your CM machines, you want to see something like this:
cluster = CompanyName
Group Main_Group:
Machine lab1.example.com (Serial #: XXXXXXXXXXXX-XXXXXXX)
Machine lab2.example.com (Serial #: XXXXXXXXXXXX-XXXXXXX)
Group Paris:
Machine lab3.example.com (Serial #: XXXXXXXXXXXX-XXXXXXX)
Machine lab4.example.com (Serial #: XXXXXXXXXXXX-XXXXXXX)
Group Rome:
Machine lab5.example.com (Serial #: XXXXXXXXXXXX-XXXXXXX)
Machine lab6.example.com (Serial #: XXXXXXXXXXXX-XXXXXXX)
Be careful not to lose track of the level at which you are making changes. For
example, if you have changed the name of your Main_Group (using
RENAMEGROUP) to London, it will look like this:
example, if you have changed the name of your Main_Group (using
RENAMEGROUP) to London, it will look like this:
cluster = CompanyName
Group London:
Machine lab1.cable.nu (Serial #: 000F1FF7B3F0-CF2SX51)
...
However, this configuration tends to confuse many administrators, because they
begin making changes to the London systems at the group level, and they stop
using the Cluster level as the normal configuration level for basic settings.
begin making changes to the London systems at the group level, and they stop
using the Cluster level as the normal configuration level for basic settings.