Cisco Systems CL-28826-01 Security Camera User Manual


  Open as PDF
of 2616
 
8-2
User Guide for Cisco Security Manager 4.4
OL-28826-01
Chapter 8 Managing Deployment
Understanding Deployment
Table 8-1 Overview of the Deployment Process
Steps Deployment Steps
Step 1 Security Manager obtains the current configuration for the device and compares it to
the latest saved policies for the device in Security Manager. What Security Manager
considers to be the current configuration depends on the type of device, the deployment
method, and the settings for deployment preferences. These are the possible sources
and the conditions under which they are used:
Obtain the running configuration from the device.
The running configuration is used when deploying to the device unless the
deployment method is AUS, TMS, or CNS. You can force Security Manager to use
Configuration Archive by selecting When Deploying to Device Get Reference
Config from: Config Archive as the deployment preference (select Tools >
Security Manager Administration, then select Deployment).
Obtain the last full configuration from the Security Manager Configuration
Archive. The Configuration Archive is used when:
Deploying to file, unless you select When Deploying to File Get Reference
Config from: Device as the deployment preference.
The deployment method is TMS or CNS.
The device is not managed by Security Manager.
Deploying to a device if uploading the configuration from the device failed.
Configuration Archive is used as a backup to obtaining the configuration from
the live device.
You preview configurations.
Use the factory default configuration.
The factory default configuration is used with PIX or ASA devices if you use the
AUS deployment method. It is used for deployment and for configuration preview.
Step 2 Security Manager builds a delta configuration that contains the commands needed to
update the device configuration to make it consistent with the assigned policies. It also
builds a full device configuration.
Step 3 If you are deploying to the device, Security Manager deploys either the delta
configuration or the full configuration, depending on which deployment method you
use. If you are deploying to file, Security Manager creates two files:
device_name_delta.cfg for the delta configuration, and device_name_full.cfg for the
full configuration. In both cases, the configurations are also added to Configuration
Archive. These are the actions based on deployment method:
SSL (HTTPS), SSH, or Telnet—Security Manager contacts the device directly and
sends the delta configuration to it.
Auto Update Server (standalone or running on Configuration Engine) for PIX and
ASA devices—Security Manager sends the full configuration to Auto Update
Server, where the device retrieves it. The delta configuration is not sent.
Configuration Engine for IOS devices—Security Manager sends the delta
configuration to Configuration Engine, where the device retrieves it.
TMS—Security Manager sends the delta configuration to the TMS server, from
which it can be downloaded to an eToken to be loaded onto the device.