Cisco Acs 57 User Guide

							11   
Configuring System Operations
Editing Instances
Replication Time  Time stamp of the last replication. The time stamp is in the form hh:mm dd:mm:yyyy.
Version Current version of the ACS software running on the secondary ACS instance. Valid values can be 
the version string or, if a software upgrade is initiated, Upgrade in progress.
Description Description of the secondary instance.
Edit Select the secondary instance that you want to edit and click this button to edit it.
Delete Select the secondary instance that you want to delete and click this button to delete it.
Activate If the option to auto-activate the newly registered secondary instance is disabled, the secondary is 
initially placed in the inactive state. Click Activate to activate these inactive secondary instances.
Deregister
1Disconnects the secondary instance from the primary instance. Stops the secondary instance from 
receiving configuration updates from the primary instance. Deregistration restarts the deregistered 
node.
When full replication is in progress on an instance, do not attempt to deregister that instance. Wait 
until the full replication is complete and the secondary instance is restarted before you deregister 
the secondary instance. 
Promote Requests to promote a secondary instance to the primary instance. All updates to the current 
primary instance are stopped so that all replication updates can complete. The secondary instance 
gets primary control of the configuration when the replication updates complete.
The secondary instance must be active before you can promote it to the primary instance.
Full Replication Replicates the primary instance’s database configuration for the secondary instance. ACS is 
restarted.
When full replication is in progress on an instance, do not attempt to deregister that instance. Wait 
until the full replication is complete and the secondary instance is restarted before you deregister 
the secondary instance.
Backup Select the secondary instance that you want to back up and click this button to take a backup. See 
Backing Up Primary and Secondary Instances, page 7 for more information.
Refresh Click to refresh the Distributed System Management page manually.
Refresh Interval Select the time interval in seconds for the Distributed System Management page to be refreshed 
automatically. The default value is 30 seconds. The available options are No Refresh, 15 seconds, 
30 seconds, and 60 seconds. 
If you select:
No Refresh—ACS does not refresh the Distributed System Management page automatically. 
You must click Refresh to refresh the page manually. 
15 seconds—ACS refreshes the Distributed System Management page for every 15 seconds. 
30 seconds—ACS refreshes the Distributed System Management page every for 30 seconds. 
60 seconds—ACS refreshes the Distributed System Management page every for 60 seconds. 
The selected interval works only when you are in the Distributed System Management page. If you 
navigate to any other page, ACS resets the refresh interval to its default value. 
Note: The refresh interval does not work when you delete a deregistered secondary instance or 
instances from the Distributed System Management page.
1. Deregistration restarts the deregistered node, but does not restart ACS. Registration and Full Replication restart ACS because the database is replaced.
Table 4 Distributed System Management Page  (continued)
Option Description 
						

							12
Configuring System Operations
 
Editing Instances
Note: ACS displays two asterisks “**” in a column when that particular ACS instance information is unavailable. The 
two asterisks indicate that the communication is not available and you need to log in to that particular ACS instance 
to view the required information. 
Note: You will not have session time-outs if you are on the Distributed System Management Page as the page is refreshed 
automatically at regular intervals.
2.From the Primary Instance table, click the primary instance that you want to modify, or check the Name check box 
and click Edit.
3.Complete the fields in the Distributed System Management Properties page as described inTable 5 on page 12:
Table 5 Distributed System Management Properties Page 
Option Description
Instance Data
Hostname  Name of the ACS host machine.
Launch Session for Local 
GUI Click this button to launch a new instance of the selected ACS machine. You are required to log 
in to the primary or secondary instance.
This option appears only when you view or edit another instance.
Role Specifies a primary or secondary instance or Local.
IP Address IP address of the primary or secondary instance.
Port Port for Management service.
MAC Address MAC address for the instance.
Description Description of the primary or secondary instance.
Check Secondary Every 
(only applies for primary 
instance)Rate at which the primary instance sends a heartbeat status request to the secondary instance. 
The default value is 60 seconds. The minimum value is 30 seconds and the maximum value is 30 
minutes.
Statistics Polling Period 
(only applies for primary 
instance)Rate at which the primary instance polls the secondary instance for statistical and logging 
information. During each polling period, the primary server does not send any query to all the 
secondary servers, but, all ACS servers send their health information to the log collector server. 
The minimum value is 60 seconds and the maximum value is 30 minutes. However, you can 
specify a value of 0 which indicates to turn off polling and logging. As a result, the log collector 
server does not show any health status. The default value is 60 seconds. 
Enable Auto Activation 
for Newly Registered 
Instances (only applies 
for primary instance)Check this check box to automatically activate the registered secondary instance.
Instance Status
Status Indicates if the primary instance or secondary instance is online or offline.
Version The current version of the ACS software.
Replication Status (only 
applies for secondary 
instances)Replication status values are: 
UPDATED—Replication is complete on ACS instance. Both management and runtime services 
are current with configuration changes from the primary instance.
PENDING—Request for full replication has been initiated. 
REPLICATING—Replication from the primary to the secondary is processing.
DEREGISTERED—Deregistered the secondary instance from the primary.
N/A—No replication on primary instance. 
						

							13   
Configuring System Operations
Editing Instances
4.Click Submit.
The Primary Instance table on the Distributed System Management page appears with the edited primary instance.
Related Topics
Replicating a Secondary Instance from a Primary Instance, page 20
Viewing and Editing a Secondary Instance, page 13
Viewing and Editing a Secondary Instance
To edit a secondary instance:
1.Choose System Administration > Operations > Distributed System Management.
The Distributed System Management page appears with two tables:
Primary Instance table—Shows the primary instance.
Secondary Instances table—Shows a listing and the status of the secondary instances registered to the primary 
instance. 
See Table 4 on page 10 to view column definitions. 
2.From the Secondary Instances table, click the secondary instances that you want to modify, or check the check box 
near the secondary instances and click Edit.
3.Complete the fields in the Distributed System Management Properties page as described inTable 5 on page 12. 
4.Click Submit.
The Secondary Instances table on the Distributed System Management page appears with the edited secondary 
instance.
Related Topics
Editing Instances, page 9 Last Update Time (only 
applies for primary 
instance)Time stamp of the last database configuration change. The time stamp is in the form hh:mm 
dd:mm:yyyy.
Last Replication Time 
(only applies for 
secondary instances)Time stamp of the last replication. The time stamp is in the form hh:mm dd:mm:yyyy.
Last Replication ID (only 
applies for primary 
instance)Transaction ID that identifies the last configuration change on the secondary instances. This value 
increases by 1 for every configuration change. Valid values are 1 to infinity.
Primary Replication ID 
(only applies for 
secondary instances)Transaction ID that identifies the last configuration change on the primary instance. This value 
increases by 1 for every configuration change. Valid values are 1 to infinity.
Table 5 Distributed System Management Properties Page   (continued)
Option Description 
						

							14
Configuring System Operations
 
Activating a Secondary Instance
Viewing and Editing a Primary Instance, page 9
Deleting a Secondary Instance
To delete a secondary instance:
1.Choose System Administration > Operations > Distributed System Management.
The Secondary Instances table on the Distributed System Management page appears with a list of secondary 
instances. 
2.Deregister the secondary instance you wish to delete. Refer to Deregistering Secondary Instances from the 
Distributed System Management Page, page 17.
3.Check one or more check boxes near the secondary instances that you want to delete.
4.Click Delete.
The following warning message appears:
Are you sure you want to continue deleting the selected instance(s)?
Please note that auto Refresh will be disabled during this operation.
5.Click OK.
The Secondary Instances table on the Distributed System Management page appears without the deleted secondary 
instances.
Activating a Secondary Instance
To activate a secondary instance:
1.Choose System Administration > Operations > Distributed System Management.
The Distributed System Management page appears with two tables:
Primary Instance table—Shows the primary instance.
Secondary Instances table—Shows a listing and the status of the secondary instances registered to the primary 
instance. 
See the Table 4 on page 10 to view column descriptions. 
2.From the Secondary Instances table, check the check box near the secondary instances that you want to activate.
3.Click Activate.
4.The Secondary Instances table on the Distributed System Management page appears with the activated secondary 
instance. See the Table 5 on page 12 for valid field options. 
Related Topics
Viewing and Editing a Secondary Instance, page 13
Deleting a Secondary Instance, page 14
Replicating a Secondary Instance from a Primary Instance, page 20
Registering a Secondary Instance to a Primary Instance, page 15 
						

							15   
Configuring System Operations
Registering a Secondary Instance to a Primary Instance
Deregistering a Secondary Instance from the Deployment Operations Page, page 18
Promoting a Secondary Instance from the Distributed System Management Page, page 19
Using the Deployment Operations Page to Create a Local Mode Instance, page 22
Registering a Secondary Instance to a Primary Instance
To register a secondary instance to a primary instance:
1.Log into the machine that will be used as a secondary Instance for another ACS server. 
2.Choose System Administration > Operations > Local Operations > Deployment Operations.
The Deployment Operations page appears, displaying the information described in Table 6 on page 15: 
.
Table 6 System Operations: Deployment Operations Page 
Option Description
Instance Status
Current Status  Identifies the instance of the node you log into as primary or secondary, and identifies whether 
you are running in local mode.
Primary Instance Hostname of the primary instance.
Primary IP IP address of the primary instance.
Registration (only active for an instance not running in Local Mode)
Primary Instance Hostname of the primary server that you wish to register with the secondary instance.
Admin Username Username of an administrator account.
Admin Password  Password for the administrator’s account.
Hardware  Replacement Check to enable a new or existing ACS instance hardware to re-register to a primary instance and 
acquire the existing configuration already present in the primary instance. This is useful when an 
instance fails and needs physical replacement. 
Recovery  Keyword Name of the instance that is to be replaced. This value is the hostname of the system that is being 
replaced. After you submit this information, this instance connects to the primary instance. 
The primary instance finds the associated ACS instance records based on the keyword, and 
marks each record as registered.
Register to Primary Connects to the remote primary and registers the secondary instance to the primary instance.
Backup
Backup Backs up the current instance.
Local Mode
Admin Username Username of an administrator account.
Admin Password Password for the administrators account. 
						

							16
Configuring System Operations
 
Registering a Secondary Instance to a Primary Instance
Reconnect
This option appears only 
on the local mode node 
and prompts you for 
credentials.Click Reconnect to reconnect to the primary instance. 
Once you reconnect to the primary instance, you lose the configuration changes that you have 
made to the local secondary instance.
If you want to retain the configuration changes that you have made to the local secondary 
instance, you must:
1.Deregister the local secondary instance (this instance would become your new primary)
2.Deregister all the instances from the deployment.
3.Register all the instances to the new primary, whose configuration changes you want to 
retain.
Request Local Mode
This option appears only 
on a registered 
secondary page.Request to place the secondary instance in local mode. This enables administrators to make 
configuration changes only to this instance. Any changes made to the secondary instance are not 
automatically updated when you reconnect to the primary instance. You must manually enter your 
changes for the secondary instance.
Table 6 System Operations: Deployment Operations Page   (continued)
Option Description 
						

							17   
Configuring System Operations
Deregistering Secondary Instances from the Distributed System Management Page
4.Specify the appropriate values in the Registration Section. 
5.Click Register to Primary.
The following warning message is displayed.
This operation will register this ACS Instance as a secondary to the specified Primary Instance. 
ACS will be restarted. You will be required to login again. Do you wish to continue?
6.Click OK.
The Secondary Instance is restarted automatically. 
The credentials and the configurations that you create on the primary instance are applied to the secondary instance.
7.Register another ACS machine as secondary to the same deployment after the first secondary instance is up and 
running, successfully. Follow the same procedure to register all the secondary machines on the deployment.
Note: Memory utilization of 90% is considered normal in the secondary instance if the log collector is running and the 
server is under heavy load. If Memory utilization increases beyond 90% and keeps increasing, it may be abnormal and 
needs to be analyzed.
Deregistering Secondary Instances from the Distributed System Management Page
To deregister secondary instances from the Distributed System Management page:
1.Choose System Administration > Operations > Distributed System Management. 
The Distributed System Management page appears.
2.From the Secondary Instances table, check one of check boxes the secondary instances that you want to deregister. Deregistration
Deregister from Primary Deregisters the secondary from the primary instance. The secondary instance retains the 
database configuration from when it was deregistered. All nodes are marked as deregistered and 
inactive, and the secondary instance becomes the primary instance.
W h e n  f u l l  r e p l i c a t i o n  i s  i n  p r o g r e s s  o n  a n  i n s t a n c e ,  d o  n o t  a t t e m p t  t o  d e r e g i s t e r  t h a t  i n s t a n c e .  W a i t  
until the full replication is complete and the secondary instance is restarted before you deregister 
the secondary instance. 
Promotion
Promote to Primary Request to promote a secondary instance to primary instance. All updates to the current primary 
instance are stopped so that all replication updates can complete. The secondary instance gets 
primary control of the configuration when the replication updates complete. 
Replication
Force Full Replication Replicates the primary instance’s database configuration for the secondary instance.
W h e n  f u l l  r e p l i c a t i o n  i s  i n  p r o g r e s s  o n  a n  i n s t a n c e ,  d o  n o t  a t t e m p t  t o  d e r e g i s t e r  t h a t  i n s t a n c e .  W a i t  
until the full replication is complete and the secondary instance is restarted before you deregister 
the secondary instance. 
Table 6 System Operations: Deployment Operations Page   (continued)
Option Description 
						

							18
Configuring System Operations
 
Deregistering a Secondary Instance from the Deployment Operations Page
3.Click Deregister.
The system displays the following warning message:
This operation will deregister this server as a secondary with the primary server. ACS will be 
restarted. You will be required to login again. Do you wish to continue?
4.Click OK.
5.Log into the ACS machine.
6.Choose System Administration > Operations > Distributed System Management.
The Distributed System Management page appears with the secondary instance deregistered from the primary 
instance.
Related Topics
Viewing and Editing a Secondary Instance, page 13
Deleting a Secondary Instance, page 14
Activating a Secondary Instance, page 14
Deregistering a Secondary Instance from the Deployment Operations Page, page 18
Promoting a Secondary Instance from the Distributed System Management Page, page 19
Using the Deployment Operations Page to Create a Local Mode Instance, page 22
Deregistering a Secondary Instance from the Deployment Operations Page
Note: In this case, the secondary instance is the local machine you are logged in to.
To deregister a secondary instance from the Deployment Operations page:
1.Choose System Administration > Operations > Local Operations > Deployment Operations. 
The Deployment Operations page appears with the secondary instance that you are logged in to. See Ta b l e 6  o n  
page 15 for valid field options.
2.Click Deregister from Primary.
The system displays the following warning message:
This operation will deregister this server as a secondary with the primary server. ACS will be restarted. You will be 
required to login again. Do you wish to continue?
3.Click OK.
4.Log into the ACS machine.
5.Choose System Administration > Operations > Local Operations > Deployment Operations.
The Deployment Operations page appears with the secondary instance you were logged in to deregistered from the 
primary instance. 
Related Topics
Viewing and Editing a Secondary Instance, page 13 
						

							19   
Configuring System Operations
Promoting a Secondary Instance from the Distributed System Management Page
Deleting a Secondary Instance, page 14
Activating a Secondary Instance, page 14
Deregistering Secondary Instances from the Distributed System Management Page, page 17
Promoting a Secondary Instance from the Distributed System Management Page, page 19
Using the Deployment Operations Page to Create a Local Mode Instance, page 22
Promoting a Secondary Instance from the Distributed System Management Page
To promote a secondary instance to a primary instance from the Distributed System Management page:
1.Choose System Administration > Operations > Distributed System Management. 
The Distributed System Management page appears. See Table 4 on page 10 for valid field options.
2.From the Secondary Instances table, check the box the secondary instance that you want to promote to a primary 
instance. 
3.Click Promote.
The Distributed System Management page appears with the promoted instance.
Related Topics
Viewing and Editing a Secondary Instance, page 13
Deleting a Secondary Instance, page 14
Activating a Secondary Instance, page 14
Deregistering Secondary Instances from the Distributed System Management Page, page 17
Using the Deployment Operations Page to Create a Local Mode Instance, page 22
Promoting a Secondary Instance from the Deployment Operations Page
To promote a secondary instance to a primary instance from the Deployment Operations page:
1.Choose System Administration > Operations > Distributed System Management.
The Deployment Operations page appears. See the Table 6 on page 15 for valid field options.
2.Register the secondary instance to the primary instance. See Registering a Secondary Instance to a Primary 
Instance, page 15.
3.Choose System Administration > Operations > Distributed System Management.
The Deployment Operations page appears.
4.Check the box the secondary instance that you want to promote to a primary instance. 
5.Click Promote to Primary.
The Distributed System Management page appears with the promoted instance. 
						

							20
Configuring System Operations
 
Replicating a Secondary Instance from a Primary Instance
Related Topics
Viewing and Editing a Secondary Instance, page 13
Deleting a Secondary Instance, page 14
Replicating a Secondary Instance from a Primary Instance, page 20
Activating a Secondary Instance, page 14
Deregistering Secondary Instances from the Distributed System Management Page, page 17
Promoting a Secondary Instance from the Distributed System Management Page, page 19
Using the Deployment Operations Page to Create a Local Mode Instance, page 22
Replicating a Secondary Instance from a Primary Instance
You can use two different pages to replicate a secondary instance:
Replicating a Secondary Instance from the Distributed System Management Page, page 20
Replicating a Secondary Instance from the Deployment Operations Page, page 20
Note: For more information on replication, see ACS 4.x and 5.7 Replication, page 2.
Replicating a Secondary Instance from the Distributed System Management Page
Note: All ACS appliances must be in sync with the AD domain clock.
To replicate a secondary instance:
1.Choose System Administration > Operations > Distributed System Management. 
The Distributed System Management page appears.
2.From the Secondary Instances table, check one of check boxes the secondary instances that you want to replicate.
3.Click Full Replication.
The system displays the following warning message:
This operation will force a full replication for this secondary server. ACS will be restarted. You 
will be required to login again. Do you wish to continue?
4.Click OK.
5.Log into the ACS machine.
6.Choose System Administration > Operations > Distributed System Management.
The Distributed System Management page appears. On the Secondary Instance table, the Replication Status column 
shows UPDATED. Replication is complete on the secondary instance. Management and runtime services are current 
with configuration changes from the primary instance.
Replicating a Secondary Instance from the Deployment Operations Page
Note: All ACS appliances must be in sync with the AD domain clock.