Руководство Пользователя для Cisco Cisco Email Security Appliance C380
34-6
User Guide for AsyncOS 9.8 for Cisco Email Security Appliances
Chapter 34 System Administration
Managing the Configuration File
Alerts will be sent 180 days, 150 days, 120 days, 90 days, 60 days, 30 days, 15 days, 5 days, 1 day and
0 seconds before the license expires, and at the same intervals before the grace period ends. These alerts
will be of type “System” at severity level “Critical.” To ensure that you receive these alerts, see
0 seconds before the license expires, and at the same intervals before the grace period ends. These alerts
will be of type “System” at severity level “Critical.” To ensure that you receive these alerts, see
These alerts are also logged in the system log.
Individual feature keys may expire earlier than the virtual appliance license. You will also receive alerts
when these approach their expiration dates.
when these approach their expiration dates.
Related Topics
•
Managing the Configuration File
All configuration settings within the appliance can be managed via a single configuration file. The file
is maintained in XML (Extensible Markup Language) format.
is maintained in XML (Extensible Markup Language) format.
You can use this file in several ways:
•
You can save the configuration file to a different system to back up and preserve crucial
configuration data. If you make a mistake while configuring your appliance, you can “roll back” to
the most recently saved configuration file.
configuration data. If you make a mistake while configuring your appliance, you can “roll back” to
the most recently saved configuration file.
•
You can download the existing configuration file to view the entire configuration for an appliance
quickly. (Many newer browsers include the ability to render XML files directly.) This may help you
troubleshoot minor errors (like typographic errors) that may exist in the current configuration.
quickly. (Many newer browsers include the ability to render XML files directly.) This may help you
troubleshoot minor errors (like typographic errors) that may exist in the current configuration.
•
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 web interface for making configuration
changes.
appliance. This, in effect, “bypasses” both the CLI and the web interface 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.