Troubleshooting
Debug and Syslog Messaging Operation
Debug logging requires a logging destination (Syslog server and/or a session
type), and involves the logging and debug destination commands. Actions you
can perform with Debug and Syslog operation include:
â– Configure the switch to send Event Log messages to one or more Syslog
servers. Included is the option to send the messages to the User log facility
(default) on the configured server(s) or to another log facility.
Note As of June 2007, the logging facility < facility-name > option (described on page
C-40) is available on these switch models:
â– 8212zl Switch
â– Series 6400cl switches
â– 6200yl Switch
â– Series 5400zl switches
â– Series 5300xl switches
â– Series 4200vl switches
â– Series 4100gl switches (software release G.07.50 or greater)
â– Series 3500yl switches
â– Series 3400cl switches
â– Series 2800 switches
â– Series 2600 switches and the Switch 6108 (software release H.07.30 or
greater)
For the latest feature information on ProCurve switches, visit the ProCurve
Networking web site and check the latest release notes for the switch products
you use.
â– Configure the switch to send Event Log messages to the current manage-
ment-access session (serial-connect CLI, Telnet CLI, or SSH).
â– Disable all Syslog debug logging while retaining the Syslog addresses from
the switch configuration. This allows you to configure Syslog messaging
and then disable and re-enable it as needed.
â– Display the current debug configuration. If Syslog logging is currently
active, this includes the Syslog server list.
â– Display the current Syslog server list when Syslog logging is disabled.
Debug Command Operation
As shown in figure C-14, the debug command performs two main functions:
â– Specifies the type(s) of event messaging to send to a destination.
â– Specifies the destination(s) of the selected message types.
C-35