Send documentation comments to mdsfeedback-doc@cisco.com
1-43
Cisco MDS 9000 Family Command Reference
OL-8413-07, Cisco MDS SAN-OS Release 3.x
Chapter 1 CLI Overview
Using Debug Commands
Note Be aware that the debugging destination you use affects system overhead. Logging to the console
produces very high overhead, whereas logging to a virtual terminal produces less overhead. Logging to
a syslog server produces even less, and logging to an internal buffer produces the least overhead of any
method.
To configure message logging, you need to be in configuration command mode. To enter this mode, use
the configure terminal command at the EXEC prompt.
Enabling Message Logging
To enable message logging to all supported destinations other than the console, enter the following
command:
logging on
The default condition is logging on.
To direct logging to the console only and disable logging output to other destinations, enter the following
command:
no logging on
Setting the Message Logging Levels
You can set the logging levels when logging messages to the following devices:
• Console
• Monitor
• Syslog server
Table 1-8 lists and briefly describes the logging levels and corresponding keywords you can use to set
the logging levels for these types of messages. The highest level of message is level 0, emergencies. The
lowest level is level 7, debugging, which also displays the greatest amount of messages. For information
about limiting these messages, see sections later in this chapter.
Table 1-8 Message Logging Keywords and Levels
Level Keyword Description Syslog Definition
0 emergencies System is unusable. LOG_EMERG
1 alerts Immediate action is needed. LOG_ALERT
2 critical Critical conditions exist. LOG_CRIT
3 errors Error conditions exist. LOG_ERR
4 warnings Warning conditions exist. LOG_WARNING
5 notification Normal, but significant, conditions
exist.
LOG_NOTICE
6 informational Informational messages. LOG_INFO
7 debugging Debugging messages. LOG_DEBUG
To Next Page
Loading...
Need help?
General