Cisco Cisco Unified MeetingPlace Audio Server Quick Setup Guide

Page of 766
 
Using Alarms and Logs on Cisco Unified MeetingPlace
Configuring the Media Server Logging Levels
11
 
Note
During normal system use, you may use the su command to switch to the root user level. If you 
accidentally enter the root password into the command line, it is possible that the root password will be 
recorded in the BASH history file (~/.bash_history). If this happens, you should use the history –c 
command to clear the history; otherwise, the root password may be visible to other users and it might be 
captured as part of the infocap log. 
Procedure
Step 1
Log in to the Administration Center.
Step 2
Click Services > Logs > System Information Capture.
Step 3
Enter or change the values on the 
Note
To receive better and faster service from Cisco TAC, enter as much information as you can. The 
details you provide will help Cisco TAC quickly understand and troubleshoot the problem.
Step 4
Click Capture Logs.
Step 5
Click OK.
Step 6
Obtain the data by taking one of the following actions:
  •
Navigate to the zip file specified on the page. The name of the zip file is based on the date and time 
parameters that you entered on the 
.
  •
Click Export to File.
Step 7
To view the System Information Capture log:
a.
Extract the files from the zip file.
b.
Open the index.html file.
Related Topics
  •
 in the 
 module 
What To Do Next
We recommend that you delete the zip file from the /tmp directory to save space on your system.
Configuring the Media Server Logging Levels
How to Configure Log Levels
On the Configure Log Levels Page, you can define log levels for Cisco Unified MeetingPlace web 
applications and for the Media Server. The system collects messages for the specified log level and all 
the levels below it. The higher the log level you specify, the more information is collected. Debug is the 
highest log level.