logging
Enables syslog logging to configured syslog servers so that the debug message types
specified by the
debug <
debug-type
>
command (see
on page 517)
are sent.(Default: Logging disabled)To configure a syslog server IP address, see
on page 521.
NOTE:
Debug messages from the switches covered in this guide have a
debug severity level. Because the default configuration of some syslog
servers ignores syslog messages with the debug severity level, ensure that
the syslog servers you want to use to receive debug messages are
configured to accept the debug level. For more information, see
on page 526.
session
Enables transmission of event notification messages to the CLI session that most recently
executed this command. The session can be on any one terminal emulation device with
serial, Telnet, or SSH access to the CLI at the Manager level prompt (
switch#_
).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
configured with the
debug <
debug-type
>
command.
buffer
Enables syslog logging to send the debug message types specified by the
debug
<
debug-type
>
command to a buffer in switch memory.To view the debug messages
stored in the switch buffer, enter the
show debug buffer
command.
Logging command
At the global configuration level, the
logging
command allows you to enable debug logging on specified syslog
servers and select a subset of Event Log messages to send for debugging purposes according to:
• Severity level
• System module
By specifying both a severity level and system module, you can use both configured settings to filter the Event
Log messages you want to use to troubleshoot switch or network error conditions.
CAUTION:
After you configure a syslog server and a severity level and/or system module to filter the Event Log
messages that are sent, if you save these settings to the startup configuration file by entering the
write memory
command, these debug and logging settings are automatically re-activated after a
switch reboot or power recycle. The debug settings and destinations configured in your previous
troubleshooting session will then be applied to the current session, which may not be desirable.
After a reboot, messages remain in the Event Log and are not deleted. However, after a power
recycle, all Event Log messages are deleted.
If you configure a severity level, system module, or both to temporarily filter Event Log messages, be
sure to reset the values to their default settings by entering the
no
form of the following commands to
ensure that Event Log messages of all severity levels and from all system modules are sent to
configured syslog servers:
switch(config)# no logging severity <debug | major | error | warning |
info>
switch(config)# no logging system-module <
system-module
>
520
Aruba 2930F / 2930M Management and Configuration Guide
for ArubaOS-Switch 16.08
