Cisco Cisco Clean Access 3.5

Page of 372
 
12-14
Cisco Clean Access Manager Installation and Administration Guide
OL-7044-01
Chapter 12      Monitoring
Log Files
Limiting the Number of Logged Events 
The event log threshold is the number of events to be stored in the Clean Access Manager database. The 
maximum number of log events kept on the CAM, by default, is 100,000. You can specify an event log 
threshold of up to 200,000 entries to be stored in the CAM database at a time. The event log is a circular 
log. The oldest entries will be overwritten when the log passes the event log threshold. 
To change the maximum number of events:
1.
Click the Logs Setting tab in the Monitoring > Event Logs pages. 
2.
Type the new number in the Maximum Event Logs fields.
3.
Click Update
Configuring Syslog Logging
System statistics are generated for each Clean Access Server managed by the Clean Access Manager 
every hour by default. By default, event logs are written to the CAM. You can have the logs directed to 
another server (such as your own syslog server). You can also configure how often system checks occur 
by setting the value in the Syslog Health Log Interval field.
To configure Syslog logging:
1.
Open the Syslog Setting tab in the Monitoring > Event Logs pages. 
2.
Specify the IP address and port for the Syslog event to be written in the Syslog Server Address and 
Syslog Server Port fields. 
3.
Specify how often you want the Clean Access Manager to log system status information, in minutes, 
in the System Health Log Interval field. This setting determines how frequently Cisco Clean 
Access Server statistics are logged in the event log. The default is 60 minutes. 
4.
Click the Update button to save your changes. 
Log Files
The Event Log is located in the Clean Access Manager database table and is named log_info table. 
 lists other logs in the Clean Access Manager. 
Table 12-5
Clean Access Manager Log Files
File
Description
/var/log/messages 
Startup
/var/log/dhcplog 
DHCP relay, DHCP logs
/tmp/perfigo-log0.log.* 
Perfigo service logs for 3.5(4) and below 
1
 
/perfigo/logs/perfigo-log0.log.* 
Perfigo service logs for 3.5(5) and above 
1,2
/var/nessus/logs/nessusd.messages 
Nessus plugin test logs 
/perfigo/control/apache/logs/* 
SSL (certificates), Apache error logs
/perfigo/control/tomcat/logs/localhost*. 
Tomcat, redirect, JSP logs
/var/log/ha-log
High availability logs (for CAM and CAS)