Troubleshooting
Debug and Syslog Messaging Operation
Syntax: [no] logging facility < facility-name >
The logging facility specifies the destination subsystem the
Syslog server(s) must use. (All configured Syslog servers must
use the same subsystem.) ProCurve recommends the default
(user) subsystem unless your application specifically requires
another subsystem. Options include:
user (the default) — Random user-level messages
kern — Kernel messages
mail — Mail system
daemon — System daemons
auth — Security/Authorization messages
syslog — Messages generated internally by Syslog
lpr — Line-Printer subsystem
news — Netnews subsystem
uucp — uucp subsystem
cron — cron/at subsystem
sys9 — cron/at subsystem
sys10 - sys14 — Reserved for system use
local10 - local17 — Reserved for system use
For a listing of applicable ProCurve switches, refer to the Note
on page C-35.
Viewing the Debug Configuration
Syntax: show debug
This command displays the currently configured debug log-
ging destination(s) and type(s). For examples of show debug
output, refer to figure C-14 on page C-42.
Steps for Configuring Debug and Syslog Messaging
1. Skip this step if you do not want to use a Syslog server.
If you want a Syslog server as a destination for debug messaging:
a. Use this command to configure the Syslog server IP address and
enable Syslog logging:
ProCurve(config)# logging < ip-addr >
C-40
To Next Page
Loading...
Need help?
General