61
DarkStar User Guide
4: Troubleshooting
www.xkl.com
Connecting...
File transferred successfully.
...Completing flash write.
0.002 sec
;;;;;;;;
version 3.0
...[snipped contents of configuration file]...
The system will now proceed using this configuration.
Are you sure? [yes/NO]
yes
recovery-mode# Fan Module 0 added to system
Fan Module 0 online, initializing
Fan Module 2 added to system
Fan Module 2 online, initializing
Power Supply 0 returned to normal
Power Supply 1 returned to normal
Initializing AMPs...
Amplifier edfa west 0 online
Amplifier edfa east 0 online
localhost> ;;;;;;;;
localhost> version 3.0
...[snipped contents of configuration file]...
localhost>
4.5 Using the Debug Command
The
debug
command is an XKL diagnostic tool that displays detailed trace information about DarkStar system functions and
network operations. In a production network, using debug can generate a high volume of trace information at the console
and may degrade system performance, so XKL recommends that:
•
You use the
debug
command only when working with XKL technical support to diagnose a specific problem with your
system.
•
You avoid using the
debug
command in a production network. The system gives high priority to debug requests, so using
debug
may impact business applications.
•
To monitor system operations, use the
show
commands,
logging
command, and SNMP traps to monitor system opera-
tions and events, rather than the
debug
command.
If a
debug
command is running, use the
undebug all
command (or the
no debug all
command) followed by a
<CR>
to instantly quiet all debugging output. You can type these commands at the console even if the console seems overwhelmed
with debug trace messages and fails to echo your keystrokes.
