Using Trace To Diagnose Problems - Avaya 8800 Troubleshooting Manual

Software troubleshooting tool configuration using ACLI
<0-64>
<WORD 1-1536>
<0-3>

Using trace to diagnose problems

Use trace to observe the status of a software module at a given time.
For example, if a CPU utilization issue is observed (generally a sustained spike above 90%)
perform a trace of the control plane (CP) activity.
Prerequisites
Caution:
Risk of traffic loss
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
• Access Privileged EXEC mode.
Procedure steps
1. Clear the trace:
2. Begin the trace operation:
202 Troubleshooting
Variable
clear trace
trace level [<0-107>] [<0-4>]
For example, to trace the CP port, verbose level:
trace level 9 3
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%, and Low Track Duration: 5
seconds.
Comments? infodev@avaya.com
Specifies the OctaPID assignment from 1 to 64.
Specifies a record type in the AR table. Options include
vlan, ip_subnet, mac_vlan, mac, arp, ip, ipx, ipmc,
ip_filter, protocol, sys_rec, all.
Specifies the verbosity from 0 to 3. Higher numbers
specify more verbosity.
Value
Trace on page 42.
July 2013