Troubleshooting guide

6-92
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
To change the log level of a single process, log in to the active Cisco PGW 2200 Softswitch, start an
MML session, and enter the set-log:process_name:log_level,[confirm] command.
Where:
• process_name—Name of the process for which you want to change the logging level. Processes are
listed in the “Understanding Processes” section on page 3-5.
• log_level—Desired logging level. The valid log levels are as follows:
– CRIT—Critical level messages
– WARN—Warning condition messages
– ERR—Error condition messages
– TRACE—Trace messages
– INFO—Informational messages
– DEBUG—Debug-level messages (lowest level). Do not set the process to this logging level
unless directed to do so by the Cisco Technical Assistance Center (TAC).
• confirm—Used when changing the logging level of a process to debug (DEBUG).
Note When you set a log level, the system also generates information for all levels above the level that you
select. That is, if you set a process to the INFO log level, the system also displays information for the
TRACE, ERR, WARN, and CRIT levels. The order of the log levels also constitutes levels of verbosity.
For instance, the CRIT level generates the least information; the DEBUG level generates the most
information.
For example, to change the log level of the engine, enter the set-log:eng-01:info command.
To change the log level of all processes, log in to the active Cisco PGW 2200 Softswitch, start an MML
session, and enter the set-log:all:log_level command.
Where:
log_level—Desired logging level. The valid log levels are as follows:
• CRIT—Critical level messages
• WARN—Warning condition messages
• ERR—Error condition messages
• TRACE—Trace messages
• INFO—Informational messages
Note When you set a log level, the system also generates information for all levels above the level that you
select. That is, if you set a process to the INFO log level, the system also displays information for the
TRACE, ERR, WARN, and CRIT levels. The order of the log levels also constitutes levels of verbosity.
For instance, the CRIT level generates the least information; the DEBUG level generates the most
information.
For example, to change the log level of all processes to warning, enter the set-log:all:warn command.