Cisco Cisco Content Security Management Appliance M390 Guía Del Usuario
9-16
AsyncOS 8.1 for Cisco Content Security Management User Guide
Chapter 9 Managing Web Security Appliances
Publishing a Configuration Master Using the Command Line Interface
Note
See important requirements and information in
The Security Management appliance provides you with the ability to publish changes through a
Configuration Master using the following CLI command:
Configuration Master using the following CLI command:
publishconfig config_master [--job_name] [--host_list | host_ip]
where config_master is either 7.1, 7.5, or 7.7. This keyword is required. The option job_name is
optional and will be generated if it is not specified.
optional and will be generated if it is not specified.
The option host_list is a list of host names or IP addresses for Web Security appliances to be published,
and will be published to all hosts assigned to the Configuration Master if not specified. The option
host_ip can be multiple host IP addresses, each separated by a comma.
and will be published to all hosts assigned to the Configuration Master if not specified. The option
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.
> 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.
Publishing Configurations Using Advanced File Publishing
Use advanced file publish to push a compatible XML configuration file from your local file system to
managed Web Security appliances.
managed Web Security appliances.
For information about which settings you can configure using Advanced File Publishing, see
Note
Any change that would cause a Web proxy restart when committed on the Web Security appliance will
also cause a proxy restart when you publish it from the Security Management appliance. You will receive
a warning about proxy restarts when you use Advanced File Publishing.
also cause a proxy restart when you publish it from the Security Management appliance. You will receive
a warning about proxy restarts when you use Advanced File Publishing.
Web Proxy restarts temporarily interrupt web security services. For more information about the effects
of restarting the web proxy, see the “Checking for Web Proxy Restart on Commit” section in the Cisco
IronPort for Web Security User Guide.
of restarting the web proxy, see the “Checking for Web Proxy Restart on Commit” section in the Cisco
IronPort for Web Security User Guide.
To perform an advanced file publish, you can choose one of the following:
•
•
Advanced File Publish: Publish Configuration Now
Procedure
Step 1
From the source Web Security appliance, save a Configuration File.
For configuration file compatibility information, see the