Cisco Cisco Content Security Management Appliance M1070 Mode D'Emploi

Most configuration settings for the Security Management appliance can be managed in a single 
configuration file. The file is maintained in Extensible Markup Language (XML) format. 

You can use this file in several ways: 

In case of unexpected disaster to your primary Security Management appliance, you can quickly 
configure a second Security Management appliance to restore service. 

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. 

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. 

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. 

You can upload an entire configuration file through FTP, or you can paste portions of a configuration 
file directly into the CLI. 

Because the file is in XML format, an associated document type definition (DTD) 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.) 

You can use the configuration file to speed configuration of another appliance, for example a cloned 
virtual appliance. 

Using the Current Configuration section of the Management Appliance > System Administration > 
Configuration File page, you 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. 

Optionally, mask the user’s passwords by selecting the check box. Masking a password causes the 
original, encrypted password to be replaced with “*****” in the exported or saved file.

Configuration files with masked passwords cannot be loaded back into AsyncOS.

The configuration file must have been saved from an appliance running the same AsyncOS version as 
the appliance on which you will load the configuration.