Troubleshooting
Note Use the information in this chapter in conjunction with the CLI Command Reference for Cisco Unified SIP Proxy Release 10.2. That document contains detailed information about each CLI command listed here, including when to use it, how to use it, and any cautionary information.
This chapter contains a brief overview of troubleshooting using the CLI and contains the following sections:
Using CLI Commands to Troubleshoot the System
Cisco technical support personnel may request that you run one or more of these commands when troubleshooting a problem. Cisco technical support personnel provides additional information about the commands at that time.
About Logging
You can use log messages to help you debug system problems. Log messages are saved to the messages.log file.
Logging and tracing to the hard disk is turned off by default. Executing the log trace boot command starts the log and trace functions immediately.
To check the log and trace files on the hard disk, use the show logs command in Cisco Unified SIP Proxy EXEC mode. It displays the list of logs available, their size and their dates of most recent modification.
Each file has a fixed length of 10 MB, and tracing or logging stops automatically when the file reaches this length. New files overwrite the old files.
Tip If you cannot view the contents of the log files, copy the log files from Cisco Unified SIP Proxy to an external server and use a text editor, such as vi, to display the content.
Log Commands
Example of Log Output
The following is an example of the log output:
Using Trace Commands
To troubleshoot network configuration in Cisco Unified SIP Proxy, use the trace enable command in Cisco Unified SIP Proxy EXEC mode.
Using Show Commands
In addition to the standard show commands, use the following commands to troubleshoot your Cisco Unified SIP Proxy configuration:
Troubleshooting Configuration Changes
Problem You lost some configuration data.
Recommended Action Copy your changes to the running configuration at frequent intervals. See Copying Configurations.
Problem You lost configuration data when you rebooted the system.
Explanation You did not save the data before the reboot.
Recommended Action Use the copy running-config startup-config command to copy your changes from the running configuration to the startup configuration. When Cisco Unified SIP Proxy reboots, it reloads the startup configuration. See Copying Configurations.
Note Messages are considered application data and are saved directly to the disk in the startup configuration. (They should be backed up on another server in case of a power outage or a new installation.) All other configuration changes require an explicit “save configuration” operation to preserve them in the startup configuration.
Related Topics
- For information about the CLI commands, see the CLI Command Reference for Cisco Unified SIP Proxy Release 10.1.
- For information about copying configurations, see Copying Configurations.