Logging Levels; Enabling Logging For Telnet Or Ssh - Cisco 9134 - MDS Multilayer Fabric Switch Troubleshooting Manual

Mds 9000 family
Hide thumbs Also See for 9134 - MDS Multilayer Fabric Switch:
Table of Contents

Advertisement

Using Cisco MDS 9000 Family Tools
S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m
A unique feature within the Cisco MDS 9000 Family switches is the ability to send RADIUS accounting
records to the Syslog service. The advantage of this feature is that you can consolidate both types of
messages for easier correlation. For example, when you log into a switch and change an FSPF parameter,
Syslog and RADIUS provide complimentary information that will help you formulate a complete picture
of the event.
Log messages are not saved across system reboots. However, a maximum of 100 log messages with a
severity level of critical and below (levels 0, 1, and 2) are saved in NVRAM. You can view this log at
any time with the show logging nvram command.

Logging Levels

The MDS supports the following logging levels:
By default, the switch logs normal but significant system messages to a log file and sends these messages
to the system console. Users can specify which system messages should be saved based on the type of
facility and the severity level. Messages are time-stamped to enhance real-time debugging and
management.

Enabling Logging for Telnet or SSH

System logging messages are sent to the console based on the default or configured logging facility and
severity values.
Users can disable logging to the console or enable logging to a given Telnet or SSH session.
Note: When logging to a console session is disabled or enabled, that state is applied to all future console
Note
sessions. If a user exits and logs in again to a new session, the state is preserved. However, when logging
to a Telnet or SSH session is enabled or disabled, that state is applied only to that session. The state is
not preserved after the user exits the session.
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
B-22
0-emergency
1-alert
2-critical
3-error
4-warning
5-notification
6-informational
7-debugging
To disable console logging, use the no logging console command in CONFIG mode.
To enable logging for telnet or SSH, use the terminal monitor command in EXEC mode.
Appendix B
Troubleshooting Tools and Methodology
OL-9285-05

Hide quick links:

Advertisement

Table of Contents

Troubleshooting

loading

Table of Contents