Troubleshooting Using the CLI

Cisco technical support personnel may request that you run one or more of these commands when troubleshooting a problem. Cisco technical support personnel will provide additional information about the commands at that time.

caut.gif
Caution blank.gif Some of these commands may impact the performance of your system. It is strongly recommended that you not use these commands unless directed to do so by Cisco Technical Support.

Log and Trace Files

About Logging

To check the log and trace files on the hard disk, use the show logs command in EXEC mode. This command displays the list of logs available, their size, and their dates of most recent modification.

When the log file reaches its maximum length, Cisco Unified SRST Manager renames the file and creates a new logging file.

For a detailed list of all the arguments associated with the trace command, see trace.

note.gif

Noteblank.gif Logs for E-SRST are turned on by default.

Example of Log Output

The following is an example of the show logs output:

se-100-1-1-100# show logs
SIZE LAST_MODIFIED_TIME NAME
14872 Thu Aug 09 06:10:07 PDT 2012 dmesg
3753146 Sun Aug 12 22:00:46 PDT 2012 atrace.log
200 Thu Aug 09 06:10:08 PDT 2012 debug_server.log
1258 Thu Aug 09 06:10:08 PDT 2012 sshd.log
2435 Thu Aug 09 06:10:08 PDT 2012 syslog.log
25197 Thu Aug 09 06:10:15 PDT 2012 install.log
2654089 Mon Aug 13 11:33:40 PDT 2012 messages.log
494 Thu Aug 09 06:10:10 PDT 2012 klog.log
8332 Thu Aug 09 06:10:22 PDT 2012 postgres.log
4289 Thu Aug 09 06:10:28 PDT 2012 csl.log
10415 Wed Aug 08 09:48:20 PDT 2012 postgres.log.prev
461 Thu Aug 09 06:10:32 PDT 2012 HttpServ_management_registry.log
0 Wed Aug 08 10:22:50 PDT 2012 _cpftpserver.log
741308 Fri Aug 10 09:07:54 PDT 2012 _cpgeneric.log
602 Fri Aug 10 09:07:53 PDT 2012 _cpnotify.log
298191 Fri Aug 10 09:07:54 PDT 2012 _cppstats.log
508407 Fri Aug 10 09:07:54 PDT 2012 _cptransport.log
72512 Fri Aug 10 09:07:02 PDT 2012 _cpconversion.log
0 Wed Aug 08 10:22:50 PDT 2012 _cpunittest.log
0 Wed Aug 08 10:22:50 PDT 2012 _cpunittestError.log
537262 Fri Aug 10 09:06:57 PDT 2012 _cploader.log
110899 Fri Aug 10 09:06:43 PDT 2012 _cpperformance.log
0 Wed Aug 08 10:22:50 PDT 2012 _cplegacy.log
0 Wed Aug 08 10:22:50 PDT 2012 _cpxdm.log
0 Wed Aug 08 10:22:50 PDT 2012 _cptest.log
0 Wed Aug 08 10:22:50 PDT 2012 _cpapp.log
0 Wed Aug 08 10:22:50 PDT 2012 _cpui.log
0 Wed Aug 08 10:22:50 PDT 2012 _cpuiperformance.log
0 Wed Aug 08 10:22:50 PDT 2012 _cpuinotify.log
123693 Fri Aug 10 09:06:56 PDT 2012 _cphibernate.log
404019 Fri Aug 10 09:07:49 PDT 2012 _cpcommands.log
1047488 Thu Aug 09 06:07:44 PDT 2012 atrace_save.log

Log Commands in Configuration Mode

  • log console errors —Displays error messages (severity=3)
  • log console info —Displays information messages (severity=6)
  • log console notice —Displays notices (severity=5)
  • log console warning —Displays warning messages (severity=4)
  • log server address a.b.c.d

log trace

  • log trace local enable
  • log trace server enable
  • log trace server url ftp-url

Log Commands in EXEC Mode

  • log console monitor
  • log trace boot
  • log trace buffer save

Saving and Viewing Log Files

Problem You must be able to save log files to a remote location.

Recommended Action Log files are saved to a disk by default. You can configure Cisco Unified SRST Manager to store the log files on a separate server by using the log server address command. Also, you can copy log files on the disk to a separate server if they need to be kept for history purposes, for example:

copy log filename.log url ftp://ftp-user-id:ftp-user-passwd@ftp-ip-address/directory
 
srstmgr# copy log messages.log url ftp://admin:messaging@172.168.0.5/log_history
 

Problem You cannot display the contents of the log files.

Recommended Action Copy the log files from Cisco Unified SRST Manager to an external server and use a text editor, such as vi, to display the content.

Using Trace Commands

To troubleshoot network configuration in Cisco Unified SRST Manager, use the trace command in EXEC mode. For a detailed list of all the arguments associated with the trace command, see trace.