Avaya 8800 Troubleshooting Manual page 116

Software troubleshooting tool configuration using CLI
Using the trace tool inappropriately can cause primary CPU lockup conditions, loss of access
to the switch, loss of protocols, and service degradation.
• For information about how to use trace appropriately, see
Procedure steps
1. Clear the trace:
2. Begin the trace operation:
3. Stop the trace:
4. View the trace results:
5. Save the trace file to the PCMCIA (or external flash) card for retrieval.
R series modules use different trace commands:
config r-module <slot#> trace level [<modid>] [level>]
config r-module <slot#> trace grep [<keyword>]
Variable definitions
Use the information in the following table to help you use the trace command.
clear
filter
116 Troubleshooting
trace clear
trace level <modid> <level>
For example, to trace the CP port, verbose level:
trace level 9 3
Wait approximately thirty seconds.
The default trace settings for CPU utilization are: High CPU Utilization: 90%, High
Track Duration: 5 seconds, Low CPU Utilization:75%, and Low Track Duration: 5
seconds.
trace off
trace info
OR
show trace file [tail]
save trace
The file is saved with a file name of systrace.txt.
Variable
Comments? infodev@avaya.com
Clears any previous trace output.
Filters the trace output.
Trace on page 42.
Value
July 2013