HP ProCurve 1600M, Management And Configuration Manual

Page: 622 / 690

Troubleshooting
Debug and Syslog Messaging Operation
Debug Destinations
Debug enables you to disable and re-enable Syslog messaging to configured
servers, and to designate a CLI session to receive messaging of any debug type.
Syntax: [no] debug destination < logging | session >
logging
This command enables Syslog logging to the configured
Syslog server(s). That is, the switch sends the debug mes­
sage types (specified by the
debug < debug-type > command
in the preceding section) to the configured Syslog server(s).
(Default: Logging disabled)
(To configure a Syslog server IP address, refer to “Syslog
Operation” on page C-39.)
Note: Debug messages from the switches covered in this
guide carry a “debug” severity level. Because some Syslog
servers, in their default configuration, ignore Syslog mes­
sages with this severity level, you should ensure that the
Syslog servers you intend to receive debug messages are
configured to accept the “debug” severity level. For more
information, refer to
“Operating Notes for Debug and Sys­
log” on page C-43 .
session
Enables or disables transmission of event notification mes­
sages to the CLI session that most recently executed this
command. The session can be on any one terminal emula­
tion device with serial, Telnet, or SSH access to the CLI at
the Manager level prompt (
ProCurve#_
). If more than one
terminal device has a console session with the CLI, you can
redirect the destination from the current device to another
device. Do so by executing
debug destination session
in the
CLI on the terminal device on which you now want to
display event messages.
Event message types received on the selected CLI session are
those specified by the
debug < debug-type >
command. (Refer
to “Debug Types” on page C-36 .)
C-38