Avaya 8800 Troubleshooting Manual page 475

Table 44: CPU spike troubleshooting commands
CLI command
trace clear
trace screen off
trace level 9 3
config cli more
false
trace info
config cli more
true
trace off
trace clear
Caution:
Using the trace tool inappropriately can cause primary CPU lockup conditions, loss of access
to the switch, loss of protocols, and service degradation. While these occurrences are
uncommon, when using the trace level tool, minimize this risk by following these Avaya
recommendations:
• In situations where trace data is required concurrently from multiple modules,
troubleshooting during a maintenance window should be considered if feasible. A
maintenance window period should also be considered if the switch is stable but CPU
utilization is high and CPU traces (example trace levels 9 and 11) are required to
diagnose the cause.
• To avoid potential issues due to logging trace data to the PCMCIA (or external flash)
card, the trace-logging feature should be disabled (config bootconfig flags trace-logging
false).
• Run trace commands from the console port whenever the CPU utilization is already
high. While tracing may be enabled or disabled from the console port, the trace info
should be dumped from a SSH or Telnet connection.
• Activate tracing on one software module at a time Avoid leaving traces active for
extended periods of time. For high CPU utilizations, a few seconds (typically less than
5 seconds) is generally sufficient to identify the cause for sustained high CPU
utilization.
Troubleshooting
ACLI command
clear trace
trace screen
disable
trace level 9 3
terminal more
disable
show trace file
terminal more
enable
trace shutdown
clear trace
Data collection commands
Description
Clears the trace file.
Sets the trace screen to off.
Sets the trace level. Wait for
5–10 seconds.
Disables more scrolling of
the display.
Shows the trace file. Dump
this to a file.
Reenables more scrolling of
the display.
Disables trace.
Clears the trace file.
July 2013 475