Troubleshooting Guide

Table Of Contents
clear trace
2. Identify the module ID for which you want to use the trace tool:
show trace modid-list
3. Begin the trace operation:
trace level [<0-234>] [<0-4>]
4. Wait approximately 30 seconds.
The default trace settings for CPU utilization are:
High CPU Utilization: 90%
High Track Duration: 5 seconds
Low CPU Utilization: 75%
Low Track Duration: 5 seconds
5. Stop tracing:
trace shutdown
6. View the trace results:
show trace file [tail]
7. Save the trace file to the Flash card for retrieval.
save trace [file WORD<1–99>]
If you do not specify a file name, the file name is systrace.txt.
8. Search trace results for a specific string value, for example, the word error:
trace grep [WORD<0-128>]
If you use this command and do not specify a string value, you clear the results of a previous
search.
9. Stop tracing:
trace shutdown
Example
Swtich:1>enable
Clear the trace:
Swtich:1#clear trace
Identify the module ID for which you want to use the trace tool:
Switch:1#show trace modid-list
0 - COMMON 119 - ISIS
1 - SNMP 120 - CFM
2 - RMON 121 - OERCD
3 - PORT_MGR 122 - PWE3
4 - CHAS_MGR 123 - EXTENDED_PING
Using trace to diagnose problems
January 2017 Troubleshooting 101
Comments on this document? infodev@avaya.com