Troubleshooting guide

6-91
Cisco PGW 2200 Softswitch Release 9.8 Operations, Maintenance, and Troubleshooting Guide
OL-0800-14
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform
Troubleshooting with System Logs
Understanding System Log Messages
Each system log message conforms to the following format:
Timestamp, Process Name, Process ID, <Log Level>, Log ID:<Message Text>
• Timestamp—Displays the date and time on the system when the log message was created, for
example, “May 8 01:35:23:047 2001 EST”. The time that is displayed is presented to the millisecond
level.
• Process Name—Displays the name of the process that created the log message, for example,
“engine”.
• Process ID—Displays the identification number of the process that created the log message, for
example, “(PID29974)”.
• Log Level—Displays the severity level of the log message, for example, “Info”.
• Log ID—Displays a short, symbolic name for the message, for example,
“GEN_ERR_GETCFGPARM:”.
• Message Text—Displays the log message text, for example, “installed time handler, hdlrId = 1”.
Typically, the message text requires only a single line, but the text can extend to multiple lines.
Changing the Log Level for Processes
To control the types of log messages that are written to the system log file, use the set-log MML
command to change the logging level for system processes. The Cisco PGW 2200 Softswitch can
generate many logged events, which can result in large numbers of archived system log files in the
opt/CiscoMGC/var/spool directory. For example, if the maxTime parameter in the dmprSink.dat file is
set to 15 minutes, the Cisco PGW 2200 Softswitch creates over 2000 files in the
opt/CiscoMGC/var/spool directory daily. Therefore, you might want to limit the number of logs that are
created by changing the logging level of the Cisco PGW 2200 Softswitch software processes.
Table 6-1 lists the logging levels that you can select for the Cisco PGW 2200 Softswitch software
processes without severely degrading system performance.
Caution Debug level logging provides extremely verbose output and, if misused, can cause severe system
performance degradation.
Table 6-1 Processes and their Lowest Possible Logging Levels
Process Lowest Logging Level Without Severe Performance Degradation
Engine Informational (the debug level causes major performance impacts—do
not set).
All others Debug, but only a single process can be in debug at any time.