Troubleshooting

Debug/Syslog Operation

messages sent to the Syslog server, specify a set of messages by entering the logging severity and logging system-modulecommands.

ProCurve(config)# show debug

Debug Logging

Destination: None

Enabled debug types:

None are enabled

ProCurve(config)# logging 10.28.38.164 ProCurve(config)# write memory ProCurve(config)# show debug

Debug Logging

Destination:

Logging -- 10.28.38.164 Facility=user Severity=debug System module=all-pass Enabled debug types: event

Displays the default debug configuration. (No Syslog server IP addresses or debug types are configured.)

When you configure a Syslog IP address with the logging command, by default, the switch enables debug messaging to the Syslog address and the user facility on the Syslog server, and sends Event Log messages of all severity levels from all system modules.

You can enter the logging severity and logging system-modulecommands to specify a subset of Event Log messages to send to the Syslog server.

ProCurve(config)# logging severity error ProCurve(config)# logging system-module iplock

Figure C-2. Syslog Configuration to Receive Event Log Messages From Specified System Module and Severity Levels

As shown at the top of Figure C-2, if you enter the show debug command when no Syslog server IP address is configured, the configuration settings for Syslog server facility, Event Log severity level and system module are not displayed.

However, after you configure a Syslog server address and enable Syslog logging, all debug and logging settings are displayed with the show debug command. If you do not want Event Log messages sent to Syslog servers, you can block the messages from being sent by entering the no debug event command. (There is no effect on the normal logging of messages in the switch’s Event Log.)

C-42