Cisco Systems CL-28826-01 Security Camera User Manual


  Open as PDF
of 2616
 
1-23
User Guide for Cisco Security Manager 4.4
OL-28826-01
Chapter 1 Getting Started with Security Manager
Completing the Initial Security Manager Configuration
Links in the page enable you to drill down to more detailed information in the JumpStart or to
relevant information in the online help.
Completing the Initial Security Manager Configuration
After you install Security Manager, there are several configuration steps you might want to perform to
complete the installation. Although most of the features you initially configure have default settings, you
should familiarize yourself with the features and decide if the default settings are the best settings for
your organization.
The following list explains the features you might want to initially configure, with pointers to topics that
provide more detailed information where appropriate. You can configure these features in any order, or
delay configuring those that you do not yet need to use.
Configure an SMTP server and default e-mail addresses. Security Manager can send e-mail
notifications for several actions that occur in the system. For example, you can get an e-mail when
your deployment job finishes reconfiguring network devices. For e-mail notifications to work, you
must configure an SMTP server.
For information on configuring an SMTP server and setting the default e-mail addresses, see
Configuring an SMTP Server and Default Addresses for E-Mail Notifications, page 1-25
Create user accounts. Users must log into Security Manager to use the product. However, if a user
logs in with an account another user is already using, the first user is automatically disconnected.
Thus, each user should have a unique account. You can create accounts local to the Security Manager
server, or you can use your ACS system to manage user authentication. For more information, see
the Installation Guide for Cisco Security Manager
Configure default deployment settings. When users deploy configurations to devices, they can select
how the configurations should be deployed and how Security Manager should handle anomalies.
However, you can select system-default settings that make it easier for users to follow your
organization’s recommendations. To set deployment defaults, in Configuration Manager, select
Tools > Security Manager Administration, and then select Deployment from the table of contents
to open the Deployment settings page (see Deployment Page, page 11-9).
The following deployment settings are of particular interest:
Default Deployment Method—Whether configuration deployments should be written directly
to the device or to a transport server, or if configuration files should be written to a specified
directory on the Security Manager server. The default is to deploy configurations directly to the
device or transport server, if one is configured for the device. However, if you have your own
methods for deploying configuration files, you might want to select File as the default
deployment method. For more information on deployment methods, see Understanding
Deployment Methods, page 8-8
When Out-of-Band Changes Detected—How to respond when Security Manager detects that
configuration changes were made on the device through the CLI rather than through Security
Manager. The default is to issue a warning and proceed with the deployment, overwriting the
changes that were made through the CLI. However, you can change this behavior to simply skip
the check for changes (which means Security Manager overwrites the changes but does not warn
you), or to cancel the deployment, thus leaving the device in its current state. For more
information about handling out-of-bound changes, see Understanding How Out-of-Band
Changes are Handled, page 8-12.
Allow Download on Error—Whether to allow deployment to continue if minor configuration
errors are found. The default is to not allow deployment when minor errors are found.