Table of Contents
Advertisement
416
C
A: T
HAPTER
ROUBLESHOOTING A
Displaying Trace
Results
WX S
WITCH
Because traces use the logging facility, any other logging target can be
used to capture trace messages if its severity is set to debug. However,
since tracing can be voluminous, 3Com discourages this in practice. To
enable trace output to the console, enter the command set log console
severity debug.
If you attempt to send trace output to a Telnet session, be aware that
tracing is disabled for areas processing packets that might be associated
with the Telnet session.
To view the output of currently running trace commands, use the
following command:
display log trace [{+|-|/}number-of-messages]
[facility facility-name] [matching string]
[severity severity-level]
For example, the following command displays a trace log of error-level
events:
WX1200# display log trace severity error
KERNEL Jan 15 23:08:10 ERROR duplicate IP address
10.7.122.102 sent from link address 00:05:5d:45:ae:cd
To display a specific number of trace log messages, you must enter a plus
sign (+), minus sign (-), or slash (/) before the number. These characters
filter the messages displayed as follows:
+number-of-messages — Displays the specified number of log entries,
starting with the oldest in the log.
-number-of-messages — Displays the specified number of entries,
starting with the newest in the log.
/number-of-messages — Displays the specified number of the most
recent entries in the log, starting with the least recent.
To filter trace output by MSS area, use the facility facility-name keyword.
For a list of valid facilities for which you can view event messages, type
the following command:
Advertisement
Table of Contents
