Table Of Contents
Configuring System Message Logging
About System Message Logging
System Message Logging Configuration
Facility Severity Level
Log Files
System Message Logging Servers
Outgoing System Message Logging Server Facilities
Displaying System Message Logging Information
Default Settings
Configuring System Message Logging
This chapter describes how to configure system message logging on the Cisco MDS 9020 Fabric Switch. It includes the following sections:
•About System Message Logging
•System Message Logging Configuration
•Displaying System Message Logging Information
•Default Settings
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:
•Provides logging information for monitoring and troubleshooting
•Allows you to select the types of captured logging information
•Allows you to select the destination server to forward the captured logging information
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 14-1) and the severity level (see Table 14-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 messages in a file that can save up to 1200 entries. 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 When the switch first initializes, the network is not connected until initialization completes. Therefore, messages are not redirected to a system message logging server for a few seconds.
Table 14-1 describes some samples of the facilities supported by the system message logs.
Table 14-1 Internal Logging Facilities
Facility Keyword
|
Description
|
all
|
All facilities
|
auth
|
Authorization system
|
fcdomain
|
fcdomain
|
fcns
|
Name server
|
fcs
|
FCS
|
fspf
|
FSPF
|
ipconf
|
IP configuration
|
module
|
Switching module
|
ntp
|
NTP
|
port
|
Port
|
sysmgr
|
System manager
|
user
|
User process
|
zone
|
Zone server
|
Table 14-2 describes the severity levels supported by the system message logs.
Table 14-2 Error Message Severity Levels
Level Keyword
|
Level
|
Description
|
System Message Definition
|
emergencies
|
0
|
System unusable
|
LOG_EMERG
|
alerts
|
1
|
Immediate action needed
|
LOG_ALERT
|
critical
|
2
|
Critical conditions
|
LOG_CRIT
|
errors
|
3
|
Error conditions
|
LOG_ERR
|
warnings
|
4
|
Warning conditions
|
LOG_WARNING
|
notifications
|
5
|
Normal but significant condition
|
LOG_NOTICE
|
informational
|
6
|
Informational messages only
|
LOG_INFO
|
debugging
|
7
|
Debugging messages
|
LOG_DEBUG
|
Note Refer to the Cisco MDS 9020 Fabric Switch System Messages Reference for details on the error log message format.
System Message Logging Configuration
System logging messages are sent to the console based on the default (or configured) logging facility and severity values.
Facility Severity Level
To configure the severity level for a logging facility, perform this task:
|
Command
|
Purpose
|
Step 1
|
switch# config t
switch(config)#
|
Enters configuration mode.
|
Step 2
|
switch(config)# logging level all 4
|
Configures Telnet or SSH logging for the all facilities at level 4 (warning). As a result, logging messages with a severity level of 4 or above are displayed.
|
Log Files
You can display the log file using the show logging logfile command.
System Message Logging Servers
You can configure a maximum of three 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 Add a line like the following to the /etc/syslog.conf file:
local0.debug /var/log/myfile.log
Note As shown in this example, you must add five tab characters between local0.debug and /var/log/myfile.log. Refer to entries in the /etc/syslog.conf file for further examples.
The switch sends messages based on the specified facility types and severity levels. The local0 keyword specifies the UNIX logging facility; local0 is the only facility type that Cisco FabricWare supports. 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 Create the log file by entering these commands at the UNIX shell prompt:
$ touch /var/log/myfile.log
$ chmod 666 /var/log/myfile.log
Step 3 Make sure the system message logging daemon reads the new changes by entering this command:
$ kill -HUP ~cat /etc/syslog.pid~
To configure system message logging servers, perform this task:
|
Command
|
Purpose
|
Step 1
|
switch# config t
switch#
|
Enters configuration mode.
|
Step 2
|
switch(config)# logging server
172.22.00.00
|
Configures the switch to forward log messages according to the specified facility types and severity levels to remote multiple servers specified by its hostname or IP address (172.22.00.00).
|
switch(config)# no logging server
172.16.00.00
|
Removes the specified server (172.16.00.00) and reverts to factory default.
|
Outgoing System Message Logging Server Facilities
All system 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 14-1 and the outgoing logging facilities are listed in Table 14-3.
Table 14-3 External Logging Facilities
Facility Keyword
|
Description
|
Standard or Cisco MDS Specific
|
auth
|
Authorization system
|
Standard
|
authpriv
|
Authorization (private) system
|
Standard
|
cron
|
Cron or at facility
|
Standard
|
daemon
|
System daemons
|
Standard
|
ftp
|
File Transfer Protocol
|
Standard
|
kernel
|
Kernel
|
Standard
|
local0 to local7
|
Locally defined messages
|
Standard (local7 is the default)
|
lpr
|
Line printer system
|
Standard
|
mail
|
Mail system
|
Standard
|
news
|
USENET news
|
Standard
|
syslog
|
Internal system messages
|
Standard
|
user
|
User process
|
Standard
|
uucp
|
UNIX-to-UNIX Copy Program
|
Standard
|
Note The only facility type that Cisco FabricWare supports is local0.
Displaying System Message Logging Information
Use the show logging command to display the current system message logging configuration. (See Examples 14-1 to 14-7.)
Example 14-1 Displays Current System Message Logging
Logging monitor: disabled
Logging logfile: enabled (Severity: information)
Facility Default Severity Current Session Severity
-------- ---------------- ------------------------
[1][Fri Jan 21 17:50:12.072 UTC 2005][I][8400.0001][Switch][Modifying configured DomainID
1 to negotiated value 97]
[2][Fri Jan 21 17:50:18.629 UTC 2005][A][1005.0040][Port: 1][Unsupported SFP within port.]
[3][Fri Jan 21 17:50:18.662 UTC 2005][A][1005.0040][Port: 2][Unsupported SFP within port.]
[4][Fri Jan 21 18:47:27.879 UTC 2005][I][8400.0023][Switch][Successful login user
(admin@OB-session4) with admin privilege from address 10.0.0.254]
[5][Fri Jan 21 19:24:27.097 UTC 2005][I][8400.0023][Switch][Successful login user
(maint@OB-session5) with admin privilege from address 10.0.0.254]
Example 14-2 Displays the Log File
switch# show logging logfile
Jul 16 21:06:50 %DAEMON-3-SYSTEM_MSG: Un-parsable frequency in /mnt/pss/ntp.drift
Jul 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 up
Jul 16 21:06:58 172.22.91.204 %MODULE-5-ACTIVE_SUP_OK: Supervisor 5 is active
Example 14-3 Displays Logging Facility
switch# show logging level
Facility Default Severity Current Session Severity
-------- ---------------- ------------------------
Example 14-4 Displays Logging Information
switch# show logging info
Logging monitor: disabled
Logging logfile: enabled (Severity: critical)
Facility Default Severity Current Session Severity
-------- ---------------- ------------------------
Example 14-5 Displays Last Few Lines of a Log File
switch# show logging last 2
[7][Fri Jan 21 22:45:07.672 UTC 2005][I][8400.0023][Switch][Successful login user
(admin@OB-session3) with admin privilege from address 10.0.0.254]
[8][Fri Jan 21 22:49:06.768 UTC 2005][I][8400.0023][Switch][Successful login user
(maint@OB-session4) with admin privilege from address 10.0.0.254]
Example 14-6 Displays Monitor Logging Status
switch# show logging monitor
Example 14-7 Displays Server Information
switch# show logging server
Default Settings
Table 14-4 lists the default settings for system message logging.
Table 14-4 Default System Message Log Setting
Parameters
|
Default
|
System message logging to the console
|
Enabled for messages at the critical severity level.
|
System message logging to Telnet sessions
|
Disabled.
|
Logging file size
|
1200 entries.
|
Log file name
|
Message (change to a name with up to 200 characters).
|
Logging server
|
Disabled.
|
Syslog server IP address
|
Not configured.
|
Number of servers
|
Three servers.
|
Server facility
|
Local 7.
|