![Cisco Catalyst Blade 3032 Software Configuration Manual Download Page 1254](http://html.mh-extra.com/html/cisco/catalyst-blade-3032/catalyst-blade-3032_software-configuration-manual_676651254.webp)
48-18
Cisco Catalyst Blade Switch 3130 and 3032 for Dell Software Configuration Guide
OL-13270-06
Chapter 48 Troubleshooting
Using Debug Commands
Possible destinations include the console, virtual terminals, internal buffer, and UNIX hosts running a
syslog server. The syslog format is compatible with 4.3 Berkeley Standard Distribution (BSD) UNIX
and its derivatives.
Note
Be aware that the debugging destination you use affects system overhead. Logging messages to the
console produces very high overhead, whereas logging messages to a virtual terminal produces less
overhead. Logging messages to a syslog server produces even less, and logging to an internal buffer
produces the least overhead of any method.
When stack members generate a system error message, the stack master displays the error message to
all stack members. The syslog resides on the stack master.
Note
Make sure to save the syslog to flash memory so that the syslog is not lost if the stack master fails.
For more information about system message logging, see
Chapter 32, “Configuring System Message
Logging.”