Troubleshooting guide

Diagnosing Problems
205
Hardware
Using LEDs to Diagnose Faults
Controllers, units, modules and cards have light-emitting diodes (LEDs) that indicate their
current status. Refer to the Technician's Handbook for tables that list the LED states and the
meaning of each state.
R2 Card Debugging
You can enter the following commands through the maintenance port of the R2 card/NSU to
turn on R2 debug traces. The traces are output to the maintenance port of the R2 card/NSU.
You must capture them for analysis because they are not saved to a file by the system.
Note: The baud rate for the maintenance port of the R2 card/NSU is 38400, 8N1.
Note: Most of the “r2trace” commands are a subset of the “logl3” option. Because only
a subset of the logs are presented, you can focus on the R2 card debug traces.
Table 70: R2 card trace commands
Command Purpose
option logl3 Turns on the entire R2 debug trace. The full trace can be intrusive if traffic volume is
high. To toggle the debug trace off, type “option logl3” again.
r2trace all Turns on the entire R2 debug trace. (Equivalent to option logl3).
r2trace info Turns on R2 stack trace informational (This is a subset of option logl3
r2trace debug Turns on R2 stack trace debug
r2trace line+ Turns on R2 stack trace line + debug
r2trace register+ Turns on R2 stack trace register + debug
r2trace call Turns on R2 stack trace call
r2trace line Turns on R2 stack trace line
r2trace register Turns on R2 stack trace register
r2trace trunk Turns on R2 stack trace trunk
r2trace pbx Turns on R2 stack trace pbx
r2trace msg Turns on R2 stack trace msgs
r2trace high Turns on R2 stack high-level line + reg + pbx traces
r2trace low Turns on R2 stack low-level line + reg + pbx traces