Cisco Acs 57 User Guide

41   
Managing System Administration Configurations
Adding Deployment License Files
Adding Deployment License Files
To add a new base deployment license file:
1.Select System Administration > Configuration > Licensing > Feature Options.
The Feature Options page appears with a description of the ACS deployment configuration and a list of the available 
deployment licenses and their configurations. See Add-on Licenses in Types of Licenses, page 37 for a list of 
deployment licenses. See Viewing License...

42
Managing System Administration Configurations
 
Deleting Deployment License Files
4.Click Submit to download the license file.
The Feature Options page appears with the additional license.
Related Topics
Licensing Overview, page 36
Types of Licenses, page 37
Installing a License File, page 38
Viewing and Upgrading the Base Server License, page 38
Deleting Deployment License Files, page 42
Deleting Deployment License Files
To delete deployment license files:
1.Select System Administration >...

43   
Managing System Administration Configurations
Available Downloads
Downloading UCP Web Service Files, page 43
Downloading Sample Python Scripts, page 43
Downloading Rest Services, page 44
Downloading Migration Utility Files
To download migration application files and the migration guide for ACS 5.7:
1.Choose System Administration > Downloads > Migration Utility.
The Migration from 4.x page appears.
2.Click Migration application files, to download the application file you want to use to run the...

44
Managing System Administration Configurations
 
Available Downloads
The Sample Python Scripts page appears.
2.Click one of the following:
Python Script for Using the User Change Password Web Service—To download the sample script for the UCP web 
service.
Python Script for Performing CRUD Operations on ACS Objects—To download the sample script for the import and 
export process.
3.Save the script to your local hard drive.
The scripts come with installation instructions. For more information on how to...

1
Cisco Systems, Inc.www.cisco.com
 
Understanding Logging
This chapter describes logging functionality in ACS 5.7. Administrators and users use the various management interfaces 
of ACS to perform different tasks. Using the administrative access control feature, you can assign permissions to 
administrators and users to perform different tasks.
Apart from this, you also need an option to track the various actions performed by the administrators and users. ACS 
offers you several logs that you can use to...

2
Understanding Logging
 
About Logging
In a distributed deployment, you should designate one of the secondary ACS servers as the Monitoring and Reports 
server, and specify that it receive the logs from all servers in the deployment. By default, a Log Target called the 
LogCollector identifies the Monitoring and Reports server.
In cases where a distributed deployment is used, the Log Collector option on the web interface designates which server 
collects the log information. It is recommended that you...

3   
Understanding Logging
About Logging
AAA audit, which can include RADIUS and TACACS+ successful or failed authentications, command-access passed 
or failed authentications, password changes, and RADIUS request responses.
AAA diagnostics, which can include authentication, authorization, and accounting information for RADIUS and 
TACACS+ diagnostic requests and RADIUS attributes requests, and identity store and authentication flow 
information. Logging these messages is optional.
System diagnostic,...

4
Understanding Logging
 
About Logging
Global and Per-Instance Logging Categories 
By default, a single log category configuration applies to all servers in a deployment. For each log category, the threshold 
severity of messages to be logged, whether messages are to be logged to the local target, and the remote syslog targets 
to which the messages are to be sent to, are defined. 
The log categories are organized in a hierarchical structure so that any configuration changes you make to a parent...

5   
Understanding Logging
About Logging
time stamp sequence_num msg_code msg_sev msg_class msg_text attr=value
Table 37 on page 5 describes the content of the local store syslog message format.
You can use the web interface to configure the number of days to retain local store log files; however, the default setting 
is to purge data when it exceeds 5 MB or each day, whichever limit is first attained.
Table 37 Local Store and Syslog Message Format
Field Description
timestamp Date of the message...

6
Understanding Logging
 
About Logging
If you do configure more than one day to retain local store files and the data size of the combined files reaches 95000Mb, 
a FATAL message is sent to the system diagnostic log, and all logging to the local store is stopped until data is purged. 
Use the web interface to purge local store log files. Purging actions are logged to the current, active log file. See Deleting 
Local Log Data, page 27.
The current log file is named acsLocalStore.log. Older log files are...