Using Trace Ethernet To Diagnose Problems - Avaya 8800 Troubleshooting Manual

Software troubleshooting tool configuration using ACLI
low-percentage <50-90>
low-track-duration
<3-10>
module add <0-107> <0-4>
module remove <0-107>

Using trace ethernet to diagnose problems

The trace command is the main debugging tool for the ERS 8800/8600. To alleviate some
of the overhead and make tracing more efficient, Avaya enhanced the current tracing
mechanism by adding Ethernet tracing. With this enhancement, trace messages are
transmitted out as Ethernet packets thereby avoiding the overhead caused by the traces for
displaying the messages on the switch console and logging to a file. An external entity captures
these Ethernet trace packets and decodes them appropriately.
You can capture Ethernet trace packets and then decode them from either a file or in real
time.
• If you decode them from a file, capture the Ethernet trace packets with a packet capture
tool such as PCAP and save them to a file. Then use the file as an input to a decoder that
decodes it into a readable format.
• If you decode them in real time, start the decoder in a PC first which in turn would capture
and decode the Ethernet trace packets received from the switch.
Important:
Note the following points:
• When enabled, the output will not be sent to the trace buffer.
• The port must be an inband Ethernet I/O port. This command does not work with the
CPU management port.
206 Troubleshooting
Variable
Comments? infodev@avaya.com
Value
Specifies the low-percentage threshold for a
module. The range is 50 to 90%.
Specifies, in seconds, the minimum amount of time
that the activity must be sustained to trigger the
trace. The range is 3 to 10 s.
Configures the trace auto-enable function by
specifying the module ID and level.
<0-107>
• specifies the module ID from 0 to 107.
<0-4>
• specifies the trace level from 0 to 4, where
0 is disabled; 1 is very terse; 2 is terse; 3 is very
verbose, 4 is verbose.
Removes a module ID from the auto-trace
instance.
July 2013