Cisco Cisco Content Security Management Appliance M160 Guia Do Utilizador
14-46
AsyncOS 9.0 for Cisco Content Security Management Appliances User Guide
Chapter 14 Common Administrative Tasks
Saving and Importing Configuration Settings
mail3.example.com> mailconfig
Please enter the email address to which you want to send
the configuration file.
[]> administrator@example.com
Do you want to include passwords? Please be aware that a configuration without passwords
will fail when reloaded with loadconfig. [N]> y
The configuration file has been sent to administrator@example.com.
The s
aveconfig
command on the Security Management appliance stores and saves all of the
configuration master files (ESA and WSA) with a unique filename to the
configuration
directory.
mail3.example.com> saveconfig
Do you want to include passwords? Please be aware that a configuration without passwords
will fail when reloaded with loadconfig. [N]> y
The file C650-00065B8FCEAB-31PM121-20030630T130433.xml has been saved in the configuration
directory.
mail3.example.com>
The loadconfig Command
Use the
loadconfig
command to load new configuration information into the appliance. You can load
information using one of two methods:
•
Placing information in the
configuration
directory and uploading it
•
Pasting configuration information directly into the CLI
See
for more information.
The rollbackconfig Command
See
The publishconfig Command
Use the
publishconfig
command to publish changes a configuration master. The syntax is as follows:
publishconfig config_master [job_name] [host_list | host_ip
where config_master is a supported Configuration Master, as listed in the Compatibility Matrix in the
Release Notes for this release at
Release Notes for this release at
. This keyword is required.
The keyword job_name is optional and will be generated if it is not specified.
The keyword host_list is a list of host names or IP addresses for WSA appliances to be published, and
will be published to all hosts assigned to the configuration master if not specified. The optional host_ip
can be multiple host IP addresses, each separated by a comma.
will be published to all hosts assigned to the configuration master if not specified. The optional host_ip
can be multiple host IP addresses, each separated by a comma.
To verify that the
publishconfig
command was successful, check the
smad_logs
file. You can also
verify that the publish history was successful from the Security Management appliance GUI by choosing
Web > Utilities > Web Appliance Status. From this page choose the web appliance that you want the
publish history details. Additionally, you can go the Publish History page: Web > Utilities > Publish >
Publish History.
Web > Utilities > Web Appliance Status. From this page choose the web appliance that you want the
publish history details. Additionally, you can go the Publish History page: Web > Utilities > Publish >
Publish History.