CHAPTE R
17-1
User Guide for Cisco Secure Access Control System 5.4
OL-26225-01
17
Configuring System Operations
You can configure and deploy ACS instances so that one ACS instance becomes the primary instance
and the other ACS instances can be registered to the primary as secondary instances. An ACS instance
represents ACS software that runs on a network.
An ACS deployment may consist of a single instance, or multiple instances deployed in a distributed
manner, where all instances in a system are managed centrally. All instances in a system will have an
identical configuration.
Use the Distributed System Management page (System Administration > Operations > Distributed
System Management) to manage all the instances in a deployment. You can only manage instances from
the primary instance. You can invoke the Deployment Operations page from any instance in the
deployment, but it only controls the operations on the local server.
Note You can register any primary instance or any secondary instance to another primary instance; however,
the primary instance you wish to register cannot have any secondary instance s registered to it.
The primary instance, created as part of the installa tion process, centralizes the configuration of the
registered secondary instances. Configuration changes made in the primary instance are automatically
replicated to the secondary instance. You can force a full replication to the secondary instance if
configuration changes do not replicate to the secondary instance.
This chapter contains:
•Understanding Distributed Deployment, page 17-2
•Scheduled Backups, page 17-6
•Synchronizing Primary and Secondary Instances After Backup and Re store, page 17-9
•Editing Instances, page 17-9
•Activating a Secondary Instance, page 17-14
•Registering a Secondary Instance to a Primary Instance, page17-14
•Deregistering Secondary Instances from the Distributed System Management Page, page 17-17
•Deregistering a Secondary Instance from the Deployment Operations Page, page 17-17
•Changing the IP address of a Primary Instance from the Primary Server, page 17-21
•Failover, page17-22
•Promoting a Secondary Instance from the Distributed System Management Page, page 17-18
•Replicating a Secondary Instance from a Primary Instance, page 17-19