Cisco Cisco Email Security Appliance C170 Guia Do Utilizador
31-8
Cisco AsyncOS 8.5 for Email User Guide
Chapter 31 System Administration
Managing the Configuration File
•
You can download an existing configuration file, make changes to it, and upload it to the same
appliance. This, in effect, “bypasses” both the CLI and the GUI for making configuration changes.
appliance. This, in effect, “bypasses” both the CLI and the GUI for making configuration changes.
•
You can upload entire configuration file via FTP access, or you can paste portions of or an entire
configuration file directly into the CLI.
configuration file directly into the CLI.
•
Because the file is in XML format, an associated DTD (document type definition) that describes all
of the XML entities in the configuration file is also provided. You can download the DTD to validate
an XML configuration file before uploading it. (XML Validation tools are readily available on the
Internet.)
of the XML entities in the configuration file is also provided. You can download the DTD to validate
an XML configuration file before uploading it. (XML Validation tools are readily available on the
Internet.)
Managing Multiple Appliances with XML Configuration Files
•
You can download an existing configuration file from one appliance, make changes to it, and upload
it to a different appliance. This lets you manage an installation of multiple appliances more easily.
Currently you may not load configuration files from C/X-Series appliances onto an M-Series
appliance.
it to a different appliance. This lets you manage an installation of multiple appliances more easily.
Currently you may not load configuration files from C/X-Series appliances onto an M-Series
appliance.
•
You can divide an existing configuration file downloaded from one appliance into multiple
subsections. You can modify those sections that are common among all appliances (in a multiple
appliance environment) and load them onto other appliances as the subsections are updated.
subsections. You can modify those sections that are common among all appliances (in a multiple
appliance environment) and load them onto other appliances as the subsections are updated.
For example, you could use an appliance in a test environment for testing the Global Unsubscribe
command. When you feel that you have configured the Global Unsubscribe list appropriately, you
could then load the Global Unsubscribe configuration section from the test appliance to all of your
production appliances.
command. When you feel that you have configured the Global Unsubscribe list appropriately, you
could then load the Global Unsubscribe configuration section from the test appliance to all of your
production appliances.
Managing Configuration Files Using the GUI
To use the GUI to manage configuration files on your appliance, click the Configuration File link on the
System Administration tab.
System Administration tab.
The Configuration File page contains the following sections:
•
Current Configuration - used to save and export the current configuration file.
•
Load Configuration - used to load a complete or partial configuration file.
•
End-User Safelist/Blocklist Database (Spam Quarantine) - For information, see
and
•
Reset Configuration - used to reset the current configuration back to the factory defaults (you
should save your configuration prior to resetting it).
should save your configuration prior to resetting it).
Saving and Exporting the Current Configuration File
Using the Current Configuration section of the System Administration > Configuration File page, you
can save the current configuration file to your local machine, save it on the appliance (placed in the
can save the current configuration file to your local machine, save it on the appliance (placed in the
configuration
directory in the FTP/SCP root), or email it to the address specified.
You can mask the user’s passwords by clicking the checkbox. Masking a password causes the original,
encrypted password to be replaced with “*****” in the exported or saved file. Please note, however, that
configuration files with masked passwords cannot be loaded back into AsyncOS.
encrypted password to be replaced with “*****” in the exported or saved file. Please note, however, that
configuration files with masked passwords cannot be loaded back into AsyncOS.