Cisco Cisco Email Security Appliance C160 Mode D'Emploi

Page de 1211
 
33-11
AsyncOS 9.1.2 for Cisco Email Security Appliances User Guide
 
Chapter 33      System Administration
  Managing the Configuration File
is considered ambiguous and is not allowed, even though it is “complete” syntax.
Caution
When uploading or pasting a configuration file or subsections of a configuration file, you have the 
potential to erase uncommitted changes that may be pending. 
Caution
If disk space allocations in the configuration file are smaller than the amount of data currently stored on 
the appliance, the oldest data will be deleted to meet the quota specified in the configuration file. 
Empty vs. Omitted Tags
Use caution when uploading or pasting sections of configuration files. If you do not include a tag, then 
its value in the configuration is not modified when you load a configuration file. However, if you include 
an empty tag, then its configuration setting is cleared.
For example, uploading this: 
will remove all listeners from the system!
Caution
When uploading or pasting subsections of a configuration file, you have the potential to disconnect 
yourself from the GUI or CLI and to destroy large amounts of configuration data. Do not disable services 
with this command if you are not able to reconnect to the appliance using another protocol, the Serial 
interface, or the default settings on the Management port. Also, do not use this command if you are 
unsure of the exact configuration syntax as defined by the DTD. Always back up your configuration data 
prior to loading a new configuration file. 
Note About Loading Passwords for Log Subscriptions
If you attempt to load a configuration file that contains a log subscription that requires a password (for 
example, one that will use FTP push), the 
loadconfig
 command does not warn you about the missing 
password. The FTP push will fail and alerts will be generated until you configure the correct password 
using the 
logconfig
 command. 
Note About Character Set Encoding 
The “encoding” attribute of the XML configuration file must be “
ISO-8859-1
” regardless of the 
character set you may be using to manipulate the file offline. Note that the encoding attribute is specified 
in the file whenever you issue the 
showconfig
saveconfig
, or 
mailconfig
 commands: 
Currently, only configuration files with this encoding can be loaded. 
        </rat_entry>
      </rat>
<listeners></listeners>
<?xml version="1.0" encoding="ISO-8859-1"?>