Lucent Technologies Stinger, Administration Manual

Page: 324 / 374

A-2 Stinger® Administration Guide
Using Debug Commands
Enabling debug output
This is a hidden parameter. It does not appear in the interface.
3 Write the profile to save the changes:
admin> write
Note When you are logged into a Stinger unit with debug privileges, the interface
might display normally unavailable parameters and commands, some of which are
not configurable in certain situations. Therefore, Lucent Technologies recommends
that you create a special profile for debugging purposes, and use that profile only
when you are debugging the Stinger unit.
Enabling debug output
To enable debug output for all commands on the system or on a module, use the
debug command as in the following examples.
To enable debug output:
admin> debug on
Diagnostic output enabled
To disable debug output:
admin> debug off
Diagnostic output disabled
When you enable debug output, the Stinger unit displays the debug messages on the
terminal screen.
Setting debug levels
Debug levels vary depending on the command. But generally, the lower you set the
debug level, the fewer messages the Stinger unit displays. Setting the debug level to
0
(zero) disables the debug output for the command.
Set the debug level with the -t toggle option, as in the following examples:
admin> ifmgr -t 0
ifmgr debug level is now 0 (disabled)
admin> ifmgr -t 4
ifmgr debug level is now 4 (enabled)
Getting online help for debug commands
To see a list of all commands, including the debug commands, enter a question mark
(
?)
at the command prompt, as in the following example:
admin> ?
? ( user )
acct-failsafe ( debug )
...
To get basic help for a debug command, enter the
help
command, followed by the
name of the debug command, as in the following example:
admin> help ifmgr
ifmgr usage: ifmgr [-r <vRouterName>] -option
-d (d)isplay interface table entries.