Cisco Cisco Content Security Management Appliance M160 Guía Del Usuario

Descargar
Página de 441
 
14-46
AsyncOS 8.1 for Cisco Content Security Management User Guide
Chapter 14      Common Administrative Tasks
  •
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. 
However, you cannot load configuration files from Email Security appliances onto a Security 
Management 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. 
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. 
Managing Configuration Files 
To manage configuration files on your appliance, choose Management Appliance > System 
Administration > Configuration File
.
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 (Cisco IronPort Spam Quarantine): used to manage the 
safelist/blocklist database
  •
Reset Configuration: used to reset the current configuration back to the factory defaults (you 
should save your configuration prior to resetting it) 
Related Topics 
  •
Saving and Exporting the Current Configuration File
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. 
Masking the password
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.
Note
Configuration files with masked passwords cannot be loaded back into AsyncOS.
Loading a Configuration File
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.