Cisco Cisco Email Security Appliance C170 사용자 가이드

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.

Consider the following example:

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: 

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.

When you create the cluster, the machine you happen to be logged into is automatically added to the 
cluster as the first machine, and also added to the Main_Group. Its machine level settings effectively get 
moved to the cluster level as much as possible. There are no settings at the group level, and the only 
settings left at the machine level are those which do not make sense at the cluster level, and cannot be 
clustered. Examples are IP addresses, featurekeys, etc.