Troubleshooting

Debug/Syslog Operation

To disable Syslog logging on the switch without deleting configured server addresses, enter the no debug destination logging command. Note that, unlike the case in which no Syslog servers are configured, if one or more Syslog servers are already configured and Syslog messaging is disabled, configuring a new server address does not re-enable Syslog messaging. To reenable Syslog messaging, you must enter the debug destination logging command.

Syntax: [no] logging facility < facility-name >

The logging facility specifies the destination subsystem used in a configured Syslog server. (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 (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

 

Use the no form of the command to remove the configured

 

facility and reconfigure the default (user) value.

 

For a list of supported ProCurve switches, refer to the Note on

 

page C-39.

 

Adding a Description for a Syslog Server

 

You can associate a user-friendly description with each of the IP addresses

 

(IPv4 only) configured for syslog using the CLI or SNMP.

 

 

N o t e

The HP enterprise MIB hpicfSyslog.mib allows the configuration and moni-

 

toring of syslog for SNMP (RFC 3164 supported).

 

 

C-51