Cisco Cisco Security Manager 4.7 Guía De Instalación
26
Deployment Planning Guide for Cisco Security Manager 4.7
OL-32163-01
Security Manager Server Tuning
•
Common Services 4.2.2 (installed by default when you select Security Manager 4.7 or AUS 4.7 for
installation)
installation)
•
Security Manager 4.7 Server (required)
•
AUS 4.7 (optional)
•
Security Manager 4.7 Client (optional if the client will be installed on a dedicated client machine)
The Security Manager client can be installed by using a standalone installer. The most common way to
access this installer is to log in to the server using a web browser (https://server_hostname_or_ip) and
click on the client installer.
access this installer is to log in to the server using a web browser (https://server_hostname_or_ip) and
click on the client installer.
Detailed use of the Security Manager installer and the Security Manager client installer are described in
the
the
IP address, Hostname and DNS name
Cisco Security Manager requires a static IP address instead of a DHCP address. The IP address of a
Security Manager server can be changed, after which a system reboot is required. If a DNS server is
configured in Security Manager’s TCP/IP settings, make sure that the hostname and DNS name of the
Security Manager server are identical and are resolvable by configured DNS servers. Before installing
Security Manager, you should choose a permanent DNS and computer hostname for the server, because
the hostname and DNS name should not be modified after the installation. Changing the hostname of a
Security Manager server after the installation might require re-installing Security Manager.
Security Manager server can be changed, after which a system reboot is required. If a DNS server is
configured in Security Manager’s TCP/IP settings, make sure that the hostname and DNS name of the
Security Manager server are identical and are resolvable by configured DNS servers. Before installing
Security Manager, you should choose a permanent DNS and computer hostname for the server, because
the hostname and DNS name should not be modified after the installation. Changing the hostname of a
Security Manager server after the installation might require re-installing Security Manager.
Client Deployment
The normal and recommended practice is to install and run the Security Manager client on a separate
client machine. Security Manager only supports installing a single version of the client on a given
machine, so you cannot, for example, have the client for both Security Manager 4.6 and 4.7 on the same
machine. You can install and use the client on the server; however, this practice is suitable only for a
small size network and is not recommended for the larger enterprise networks.
client machine. Security Manager only supports installing a single version of the client on a given
machine, so you cannot, for example, have the client for both Security Manager 4.6 and 4.7 on the same
machine. You can install and use the client on the server; however, this practice is suitable only for a
small size network and is not recommended for the larger enterprise networks.
As mentioned in the
section, it may be necessary to deploy
the client on a terminal server located near the server to maintain acceptable performance, in the event
that end users are located a large distance from the server which introduces significant latency (for
example, intercontinental distances).
that end users are located a large distance from the server which introduces significant latency (for
example, intercontinental distances).
Security Manager Server Tuning
Security Manager includes several advanced parameters that you can modify to tune the application
performance. For medium and large deployments managing 50 devices or more, you can modify the
following parameters in Security Manager for optimal performance:
performance. For medium and large deployments managing 50 devices or more, you can modify the
following parameters in Security Manager for optimal performance:
•
•
•