Cisco NAC Guest Server Installation and Configuration Guide, Release 1.1.2
Logging and Troubleshooting

Table Of Contents

Logging and Troubleshooting

System Logging

Log Files

Downloading the log files

Application Logging

Email Logging

RADIUS Logging

CAM Update Logging

Web Server Logging


Logging and Troubleshooting


This chapter describes the following:

System Logging

Log Files

System Logging

All actions within the Cisco NAC Guest Server are logged into the database. This enables you to see any action that occurred as part of the normal operating process of the application.

To access the system log from the administration interface select Server > System Log from the left hand menu (Figure 13-1).

Figure 13-1 System Log

Log Files

The system records information in different log files depending on the application function:

Downloading the log files

Application Logging

Email Logging

RADIUS Logging

CAM Update Logging

Web Server Logging

Downloading the log files


Step 1 To download the files from the administration interface select Server > Support Logs from the left hand menu (Figure 13-2).

Figure 13-2 Download the log files

Step 2 Click the download button and save the log file on your computer. The support logs are contained within the tar file.


Application Logging

All the application error and warning messages are stored in the application.log file. You may need to view this file to see errors with the main application.

Email Logging

Email is processed by the sendmail daemon on the Guest Server. To troubleshoot issues, you need to view the email log file called maillog.

RADIUS Logging

RADIUS is processed by the radiusd daemon on the Guest Server. To troubleshoot issues, you need to view the radius.log file.

CAM Update Logging

The accounts on the Cisco NAC Appliance Clean Access Manager are created by a process that runs every minute on the Cisco NAC Guest Server. To troubleshoot issues, you need to view the camlog file.

Web Server Logging

The httpd daemon on the appliance runs the application web server. To troubleshoot issues, you need to view the error_log file.