Filter
Top Products
680 Appendix A:Troubleshooting a WSS
NN47250-500 (320657-F Version 02.01)
Tracing 802.1X sessions
Tracing 802.1X sessions can help diagnose problems with wireless clients. For example, to trace 802.1X
activity for user tamara@example.com at level 4, type the following command:
WSS# set trace dot1x user tamara@example.com level 4
success: change accepted.
Displaying a trace
Use the show trace command to show the trace areas that are enabled. For example, to display all currently
running trace commands, type the following command:
WSS# show trace
milliseconds spent printing traces: 31.945
Trace Area Level Mac User Port Filter
---------------- -------------- -------- --------------
authentication 3 admin 0
authorization 5 0
sm 5 11 0
dot1x 2 0
Stopping a trace
The clear trace commands deletes running trace commands. To clear all traces or a particular trace area, type
the following command:
clear trace {all | trace area}
(For a list of all areas that can be traced, see “List of trace areas” (page 682).)
For example, to stop a trace of session manager activity, type the following command:
WSS# clear trace sm
success: change accepted.
About trace results
The trace commands use the underlying logging mechanism to deliver trace messages. Trace messages are
generated with the debug severity level. By default, the only log target that receives debug-level messages is
the volatile trace buffer. (To see the contents of the trace buffer, see “Displaying trace results” (page 681).)
The volatile trace buffer receives messages for all log severities when any trace area is active. However, if no
trace area is active, no messages are sent to the trace buffer regardless of their severity. If you do not enable
trace commands, the trace buffer is effectively disabled.
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, Nortel discourages this in practice. To
enable trace output to the console, enter the command set log console severity debug.