776 Appendix A:Troubleshooting a WSS
NN47250-500 (Version 03.01)

Running traces

Trace commands enable you to perform diagnostic routines. You can set a trace command with a keyword,
such as authentication or sm, to trace activity for a particular feature, such as authentication or the session
manager.

Using the trace command

Tracing is used only for debugging WSS Software. The command set trace area enables you to view
messages about the status of a specific portion of the WSS Software.
There are many trace parameters that you can run. (See “List of trace areas” on page 780.) However, this
chapter describes only authentication, authorization, the session manager (sm), and 802.1X users (dot1x), four
areas that you might find most helpful.
To focus on the object of the trace, you can add one or more of these parameters to the set trace command:
set trace [area] [mac-addr mac-addr] [port port-num] [user username] [level level]

Tracing authentication activity

Tracing authentication activity can help you diagnose authentication problems. You can trace all authentica-
tion activity, or only the activity for a specific user, MAC address, or port.
For example, to trace all authentication activity at level 4, type the following command:
WSS# set trace authentication level 4
success: change accepted.

Tracing session manager activity

You can trace all session manager commands, or only those for a specific user, MAC address, or port. For
example, to trace all session manager (sm) activity at level 3, type the following command:
WSS# set trace sm level 3
success: change accepted.
Caution! Using the set trace command can have adverse effects on system
performance. Nortel recommends that you use the lowest levels possible for initial trace
commands, and slowly increase the levels to get the data you need.