-
Cisco MDS 9000 Family Configuration Guide, Release 1.3 (from Release 1.3(1) through Release 1.3(6))
-
New and Changed Information
-
Index
-
Preface
-
Product Overview
-
Before You Begin
-
Obtaining and Installing Licenses
-
Initial Configuration
-
Configuring High Availability
-
Software Images
-
Managing Modules
-
Managing System Hardware
-
Configuring and Managing VSANs
-
Configuring Interfaces
-
Configuring Trunking
-
Configuring PortChannels\r\n
-
Configuring and Managing Zones
-
Configuring Inter-VSAN Routing
-
Managing FLOGI, Name Server, FDMI, and RSCN Databases
-
Configuring Switch Security
-
Configuring Fabric Security
-
Configuring Port Security
-
Configuring Fibre Channel Routing Services and Protocols
-
Configuring IP Services
-
Configuring FICON
-
Configuring IP Storage
-
Configuring Call Home
-
Configuring Domain Parameters
-
Configuring Traffic Management
-
Configuring System Message Logging
-
Discovering SCSI Targets
-
Monitoring Network Traffic Using SPAN
-
Advanced Features and Concepts
-
Configuring Fabric Configuration Servers
-
Monitoring System Processes and Logs
-
Feedback
Table Of Contents
Configuring System Message Logging
Configuring System Message Logging
Configuring Console Severity Level
Configuring Facility Severity Level
Configuring System Message Logging Servers
Outgoing System Message Logging Server Facilities
Displaying System Message Logging Information
Configuring System Message Logging
This chapter describes how to configure system message logging on Cisco MDS 9000 Family switches. It includes the following sections:
•
Configuring System Message Logging
•
About System Message Logging
The system message logging software saves messages in a log file or directs the messages to other devices. This feature provides you with the following capabilities:
•
•
•
By default, the switch logs normal but significant system messages to a log file and sends these messages to the system console. You can specify which system messages should be saved based on the type of facility (see Table 26-1) and the severity level (see Table 26-2). Messages are time-stamped to enhance real-time debugging and management.
You can access logged system messages using the CLI or by saving them to a properly configured system message logging server. The switch software saves system message logging messages in a file that can be configured to save up to 4 MB. You can monitor system messages remotely by accessing the switch through Telnet, SSH, or the console port, or by viewing the logs on a system message logging server.
Note
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.
Table 26-1 describes some of the facilities supported by the system message logs.
Table 26-2 describes the severity levels supported by the system message logs.
Note
Configuring System Message Logging
System logging messages are sent to the console based on the default (or configured) logging facility and severity values.
Enabling Message Logging
You can disable logging to the console or enable logging to a given Telnet or SSH session.
•
•
To enable or disable the logging state for a Telnet, or SSH session, follow these steps:
Configuring Console Severity Level
When logging is enabled for a console session (default), you can configure the severity levels of messages that appear on the console. The default severity for console logging is 2 (critical).
To configure the severity level for a logging facility, follow these steps:
Tip
Configuring Module Logging
By default, logging is enabled at level 7 for all modules. You can enable or disable logging for each module at a specified level.
To configure the severity level for a logging facility, follow these steps:
Configuring Facility Severity Level
To configure the severity level for a logging facility, follow these steps:
Configuring Log Files
Logging messages may be saved to a separate log file. You can configure the name of this file and restrict its size as required. The default log file name is messages. You can rename this file using the logging logfile command. The file name can have up to 80 characters and the file size ranges from 4096 bytes to 4194304 bytes.
To send log messages to file, follow these steps:
The configured log file is saved in the /var/log/external directory. The location of the log file cannot be changed. You can use the show logging logfile filename and clear logging logfile filename commands to view and delete this file. It is not accessible using the dir command.
You can display the log file using the show logging logfile command and copy the logfile to a different location using the copy log command using additional copy syntax (see the "Copying Files" section).
Configuring System Message Logging Servers
To send log messages to a UNIX system message logging server, you must configure the system message logging daemon on a UNIX server. Log in as root, and follow these steps:
Step 1
local1.debug /var/log/myfile.log
Note
The switch sends messages according to the specified facility types and severity levels. The local1 keyword specifies the UNIX logging facility used. The messages from the switch are generated by user processes. The debug keyword specifies the severity level of the condition being logged. You can set UNIX systems to receive all messages from the switch.
Step 2
$ touch /var/log/myfile.log$ chmod 666 /var/log/myfile.logStep 3
$ kill -HUP ~cat /etc/syslog.pid~To configure system message logging servers, follow these steps:
Outgoing System Message Logging Server Facilities
All system message logging messages have a logging facility and a level. The logging facility can be thought of as where and the level can be thought of as what.
The single system message logging daemon (syslogd) sends the information based on the configured facility option. If no facility is specified, local7 is the default outgoing facility.
The internal facilities are listed in Table 26-1 and the outgoing logging facilities are listed in Table 26-3.
Displaying System Message Logging Information
Use the show logging command to display the current system message logging configuration. See Examples 26-1 to 26-10.
Example 26-1 Displays Current System Message Logging
switch# show loggingLogging console: enabled (Severity: critical)Logging monitor: enabled (Severity: debugging)Logging linecard: enabled (Severity: debugging)Logging server: enabled{172.20.102.34}server severity: debuggingserver facility: local7{10.77.202.88}server severity: debuggingserver facility: local7{10.77.202.149}server severity: debuggingserver facility: local7Logging logfile: enabledName - messages: Severity - debugging Size - 4194304Facility Default Severity Current Session Severity-------- ---------------- ------------------------kern 6 6user 3 3mail 3 3daemon 7 7auth 0 7syslog 3 3lpr 3 3news 3 3uucp 3 3cron 3 3authpriv 3 7ftp 3 3local0 3 3local1 3 3local2 3 3local3 3 3local4 3 3local5 3 3local6 3 3local7 3 3vsan 2 2fspf 3 3fcdomain 2 2module 5 5sysmgr 3 3zone 2 2vni 2 2ipconf 2 2ipfc 2 2xbar 3 3fcns 2 2fcs 2 2acl 2 2tlport 2 2port 5 5flogi 2 2port_channel 5 5wwn 3 3fcc 2 2qos 3 3vrrp_cfg 2 2ntp 2 2platform 5 5vrrp_eng 2 2callhome 2 2mcast 2 2rdl 2 2rscn 2 2bootvar 5 2securityd 2 2vhbad 2 2rib 2 2vshd 5 50(emergencies) 1(alerts) 2(critical)3(errors) 4(warnings) 5(notifications)6(information) 7(debugging)Feb 14 09:50:57 excal-113 %TTYD-6-TTYD_MISC: TTYD TTYD startedFeb 14 09:50:58 excal-113 %DAEMON-6-SYSTEM_MSG: precision = 8 usec...Use the show logging nvram command to view the log messages saved in NVRAM. Only log messages with a severity level of critical and below (levels 0, 1, and 2) are saved in NVRAM.
Example 26-2 Displays NVRM Log Contents
switch# show logging nvramJul 16 20:36:46 172.22.91.204 %KERN-2-SYSTEM_MSG: unable to alloc and fill in anew mtsbuf (pid=2209, ret_val = -105)Jul 16 20:36:46 172.22.91.204 %KERN-2-SYSTEM_MSG: unable to alloc and fill in anew mtsbuf (pid=2199, ret_val = -105)Jul 16 20:36:46 172.22.91.204 %KERN-2-SYSTEM_MSG: unable to alloc and fill in anew mtsbuf (pid=2213, ret_val = -105)Jul 16 20:36:46 172.22.91.204 %KERN-2-SYSTEM_MSG: unable to alloc and fill in anew mtsbuf (pid=2213, ret_val = -105)...Example 26-3 Displays the Log File
switch# show logging logfileJul 16 21:06:50 %DAEMON-3-SYSTEM_MSG: Un-parsable frequency in /mnt/pss/ntp.driftJul 16 21:06:56 %DAEMON-3-SYSTEM_MSG: snmpd:snmp_open_debug_cfg: no snmp_saved_dbg_uri ;Jul 16 21:06:58 172.22.91.204 %PORT-5-IF_UP: Interface mgmt0 is upJul 16 21:06:58 172.22.91.204 %MODULE-5-ACTIVE_SUP_OK: Supervisor 5 is active...Example 26-4 Displays Console Logging Status
switch# show logging consoleLogging console: enabled (Severity: notifications)Example 26-5 Displays Logging Facility
switch# show logging levelFacility Default Severity Current Session Severity-------- ---------------- ------------------------kern 6 6user 3 3mail 3 3daemon 7 7auth 0 7syslog 3 3lpr 3 3news 3 3uucp 3 3cron 3 3authpriv 3 7ftp 3 3local0 3 3local1 3 3local2 3 3local3 3 3local4 3 3local5 3 3local6 3 3local7 3 3vsan 2 2fspf 3 3fcdomain 2 2module 5 5sysmgr 3 3zone 2 2vni 2 2ipconf 2 2ipfc 2 2xbar 3 3fcns 2 2fcs 2 2acl 2 2tlport 2 2port 5 5flogi 2 2port_channel 5 5wwn 3 3fcc 2 2qos 3 3vrrp_cfg 2 2ntp 2 2platform 5 5vrrp_eng 2 2callhome 2 2mcast 2 2rdl 2 2rscn 2 2bootvar 5 2securityd 2 2vhbad 2 2rib 2 2vshd 5 50(emergencies) 1(alerts) 2(critical)3(errors) 4(warnings) 5(notifications)6(information) 7(debugging)Example 26-6 Displays Logging Information
switch# show logging infoLogging console: enabled (Severity: critical)Logging monitor: enabled (Severity: debugging)Logging linecard: enabled (Severity: debugging)Logging server: enabled{172.20.102.34}server severity: debuggingserver facility: local7{10.77.202.88}server severity: debuggingserver facility: local7{10.77.202.149}server severity: debuggingserver facility: local7Logging logfile: enabledName - messages: Severity - debugging Size - 4194304Facility Default Severity Current Session Severity-------- ---------------- ------------------------kern 6 6user 3 3mail 3 3daemon 7 7auth 0 7syslog 3 3lpr 3 3news 3 3uucp 3 3cron 3 3authpriv 3 7ftp 3 3local0 3 3local1 3 3local2 3 3local3 3 3local4 3 3local5 3 3local6 3 3local7 3 3vsan 2 2fspf 3 3fcdomain 2 2module 5 5sysmgr 3 3zone 2 2vni 2 2ipconf 2 2ipfc 2 2xbar 3 3fcns 2 2fcs 2 2acl 2 2tlport 2 2port 5 5flogi 2 2port_channel 5 5wwn 3 3fcc 2 2qos 3 3vrrp_cfg 2 2ntp 2 2platform 5 5vrrp_eng 2 2callhome 2 2mcast 2 2rdl 2 2rscn 2 2bootvar 5 2securityd 2 2vhbad 2 2rib 2 2vshd 5 50(emergencies) 1(alerts) 2(critical)3(errors) 4(warnings) 5(notifications)6(information) 7(debugging)Example 26-7 Displays Last Few Lines of a Log File
switch# show logging last 2Nov 8 16:48:04 excal-113 %LOG_VSHD-5-VSHD_SYSLOG_CONFIG_I: Configuring console from pts/1 (171.71.58.56)Nov 8 17:44:09 excal-113 %LOG_VSHD-5-VSHD_SYSLOG_CONFIG_I: Configuring console from pts/0 (171.71.58.72)Example 26-8 Displays Switching Module Logging Status
switch# show logging moduleLogging linecard: enabled (Severity: debugging)Example 26-9 Displays Monitor Logging Status
switch# show logging monitorLogging monitor: enabled (Severity: information)Example 26-10 Displays Server Information
switch# show logging serverLogging server: enabled{172.22.95.167}server severity: debuggingserver facility: local7{172.22.92.58}server severity: debuggingserver facility: local7Default Settings
Table 26-4 lists the default settings for system message logging.
