Cisco Cisco Email Security Appliance X1050 Guía Del Usuario
8-24
Cisco IronPort AsyncOS 7.6 for Email Advanced Configuration Guide
OL-25137-01
Chapter 8 Centralized Management
Leave as many settings at the cluster level as possible. If only one machine in the cluster needs a different
setting, copy that cluster setting to the machine level for that machine. Do not move that setting. If you
move a setting which has no factory default (e.g. HAT table, SMTPROUTES table, LDAP server profile,
etc.), the systems inheriting the cluster settings will have blank tables and will probably not process
email.
setting, copy that cluster setting to the machine level for that machine. Do not move that setting. If you
move a setting which has no factory default (e.g. HAT table, SMTPROUTES table, LDAP server profile,
etc.), the systems inheriting the cluster settings will have blank tables and will probably not process
email.
To have that machine re-inherit the cluster setting, manage the CM settings and delete the machine
setting. You will only know if a machine is overriding the cluster setting when you see this display:
setting. You will only know if a machine is overriding the cluster setting when you see this display:
Settings are defined:
To inherit settings from a higher level: Delete Settings for this feature at this mode.
You can also Manage Settings.
Settings for this feature are also defined at:
Cluster: xxx
Or this display:
Delete settings from:
Cluster: xxx
Machine: yyyy.domain.com
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.
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.
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:
changed the name of your Main_Group (using RENAMEGROUP) to London, it will look like this:
cluster = CompanyName