Introduction to System Messages for the Cisco MDS 9000 Family

Similar documents
System Message Format

Configuring System Message Logging

Configuring System Message Logging

Configuring System Message Logging

Configuring System Message Logging

Configuring System Message Logging

System Message Overview

Configuring System Message Logs

Configuring System Message Logging

Configuring System Message Logging

Configuring System Message Logs

Alarm and System Message Overview

Configuring Bidirectional Forwarding Detection on Cisco IOS XR

Configuring System Message Logs

Using Debug Commands

Configuring System Message Logs

Configuring System Message Logging

Configuring Clear Channel T3/E3 and Channelized T3 and T1/E1 Controllers on the Cisco ASR 9000 Series Router

Viewing Log Files. Understanding GSS Logging Levels CHAPTER

Configuring Clear Channel SONET Controllers on the Cisco ASR 9000 Series Router

Implementing Virtual Private LAN Services

Configuring System Message Logging

Implementing Access Lists and Prefix Lists on Cisco ASR 9000 Series Routers

Table of Contents 1 Information Center 1-1

Advanced Configuration and Modification of the Management Ethernet Interface on the Cisco ASR 9000 Series Router

Implementing Layer 2 Access Lists

Implementing Keychain Management oncisco IOS XR Software

Configuring Dense Wavelength Division Multiplexing Controllers on the Cisco ASR 9000 Series Router

Managing Events and Alarms

Chapter 1 Getting Started

Flash Devices in the Cisco MDS 9000 Supervisor Module. External CompactFlash in the Cisco MDS 9000 Supervisor Module.

External Alerting with Alert Responses

ACL Syslog Correlation

Cisco ISR G2 Multi Gigabit Fabric

Using Debug Commands on Cisco IOS XR Software

Configuring LAN/WAN-PHY Controllers on Cisco IOS XR Software

Lab - Establish a Console Session with Tera

Configuring Virtual Loopback and Null Interfaces on Cisco IOS XR Software

Configuring System Logs

External Alerting for Intrusion Events

Configuring Logging. Information About Logging CHAPTER

Reliable Delivery and Filtering for Syslog

GMAT User-Defined Function Requirements

Configuring Logical Routers on Cisco IOS XR Software

Configuring ARP on Cisco ASR 9000 Series Routers

Reset and Restart Cisco Unified IP Phones

Logging. About Logging. This chapter describes how to log system messages and use them for troubleshooting.

1-, 2-, and 4-Port T1/E1 HWICs and 8-Port T1/E1 Network Module

Troubleshooting Tools. Tools for Gathering Information

System Management Commands

Information About Tracing

Using the Command-Line Interface

System Monitoring SUNNY WEBBOX with Bluetooth Wireless Technology

Tracing Commands. Information About Tracing. Tracing Overview

Configuring the VSA. Overview. Configuration Tasks CHAPTER

Configuring Serial Interfaces on the Cisco ASR 9000 Series Router

Before starting installation process, make sure the USB cable is unplugged.

Configuring SRP Interfaces on Cisco IOS XR Software

Implementing BGP on Cisco ASR 9000 Series Routers

Troubleshooting and Fault Management Commands

Packet Tracer - Navigating the IOS

Viewing Logs. CIMC Log. Viewing the CIMC Log. Procedure. This chapter includes the following sections: CIMC Log, page 1 System Event Log, page 4

Smart Install in LMS CHAPTER

DMVPN Event Tracing. Finding Feature Information

Scheduling Maintenance Jobs

Configuring NTP. Information About NTP NTP. This chapter describes how to configure the Network Time Protocol (NTP) on Cisco MDS 9000 Series switches.

Error and Event Messages

Configuring ITU-T Y.1731 Fault Management Functions

Logging Mechanism. Cisco Logging Mechanism

If any problems occur after making BIOS settings changes (poor performance, intermittent issues, etc.), reset the desktop board to default values:

Reliability Standard Audit Worksheet 1

Boot Commands on. System Management Command Reference for the Cisco NCS 6000 Series Routers OL

DHCP Server RADIUS Proxy

Configuration Commands. Generic Commands. description. shutdown SR OS System Management Guide Page 399. Event and Accounting Logs

EventTracker v7.x. Integrating Cisco Catalyst. EventTracker 8815 Centre Park Drive Columbia MD

DGS-1510 Series Gigabit Ethernet SmartPro Switch Web UI Reference Guide. Figure 3-1 Device Information window

Using the Command-Line Interface

Device management commands 1

ISCOM 2126 Series Switch Command Notebook

Logging. About Logging. This chapter describes how to log system messages and use them for troubleshooting.

Allen-Bradley Interfacing

Nexus 7000 and 7700 Series Switches Optimized ACL Logging Configuration Example

Configuring SNMP. Understanding SNMP CHAPTER

This chapter describes how to configure ATM on Cisco routers.

Controller 3000, dependent on reader technology and site configuration. All I/O functionality is provided on the Controller 3000.

Configuring Ethernet OAM on the Cisco ASR 9000 Series Router

Draft EN V1.2.3 ( )

Meridian Digital Telephones

Available Commands CHAPTER

IBM ERserver. System Message Guide. Cisco Systems Intelligent Gigabit Ethernet Switch Module for the IBM Eserver BladeCenter

Never Lose a Syslog Message

Configuring VSANs and Interfaces

EEM Action Tcl Command Extension

System Management Configuration Guide, Cisco IOS XE Everest 16.6.x (Catalyst 9400 Switches)

Guide to Interconnecting 3Com Switches Using 10-Gigabit Ethernet

User Commands ps ( 1 )

The Lab. The lab (cont ) 5 (6) routers ETSF05 + ETSF The routing lab. Jens A Andersson. Many links (vlans) Front-end server

Onboard Failure Logging Commands

Using the Command-Line Interface

Logging to Local Nonvolatile Storage (ATA Disk)

Transcription:

CHAPTER 1 Introduction to System Messages f the Cisco MDS 9000 Family This chapter describes system messages, as defined by the syslog protocol (RFC 3164). It describes how to understand the syslog message fmat and how to capture system messages f review. This chapter contains the following sections: System Log Message Fmat, page 1-1 Capturing System Messages and Histy, page 1-4 System Log Message Fmat System log messages begin with a percent sign (%) and are displayed in the following fmat (see ). Syslog Fmat On a Resident Switch The fmat f a resident syslog is: month dd hh:mm:ss switchname facility-severity-mnemonic month dd hh:mm:ss switchname facility-slotnumber-severity-mnemonic month dd hh:mm:ss switchname facility-standby-severity-mnemonic F example: Nov 1 14:07:58 excal-113 %MODULE-5-MOD_OK: Module 1 is online Nov 1 14:07:58 excal-113 %PORT-3-IF_UNSUPPORTED_TRANSCEIVER: Transceiver f interface fc1/13 is not suppted. Warning System Log Message Fmat Element month dd hh:mm:ss switchname facility The date and month of the err event The time of the err event The name of the switch The facility of the err event (daemon, kernel, VSHD, other facility) 1-1

System Log Message Fmat Chapter 1 Warning System Log Message Fmat (continued) Element severity MNEMONIC %$VSAN #%$ Single-digit code from 0 to 7 that indicates the severity of the message Text string that uniquely describes the system message An optional VLAN ID that appears in the f messages requiring VLAN IDs Text string containing detailed infmation about the event being repted FACILITY is a code consisting of two me uppercase letters that indicate the facility to which the system message refers. A facility is a hardware device, a protocol, a feature, a module of the system software. System message SEVERITY codes range from 0 to 7 and reflect the severity of the condition. The lower the number, the me serious the situation. Table 1-1 lists the severity levels. Table 1-1 System Message Severity Levels Level 0 emergency System unusable 1 alert Immediate action needed 2 critical Critical condition 3 err Err condition 4 warning Warning condition 5 notification Nmal but significant condition 6 infmational Infmational message only 7 debugging Appears during debugging only MNEMONIC is a code that uniquely identifies the system message. Message-text is a text string that describes the condition. This ption of the message might contain detailed infmation about the event, including terminal pt numbers, netwk addresses, addresses that crespond to locations in the system memy address space. Because the infmation in these variable fields changes from message to message, it is represented here by sht strings enclosed in square brackets ([ ]). A decimal number, f example, is represented as [dec]. Table 1-2 lists the representations of variable fields and the type of infmation in the fields. Table 1-2 Representation [dec] [hex] [char] [chars] Representation of Variable Fields in System Messages Type of Infmation Decimal number Hexadecimal number Single character Character string 1-2

Chapter 1 System Log Message Fmat The following example system message shows how the variable field might be used: %MODULE-5-MOD_MINORSWFAIL: Module [dec] repted a failure in service [chars] In this example, Facility code =MODULE (indicating that it is a module-specific err) Severity =5 (notification) Alarm/event code= MOD_MINORSWFAIL of the problem= Module [dec] repted a failure in service [chars] [dec] is the module slot number associated with this message. [chars] is the service name that experienced this failure. System log messages begin with a percent sign (%) and are displayed in the following fmat (see Table 1-3). Syslog Fmat On a Remote-Logging Server The syslog fmat on a remote-logging server is: month dd hh:mm:ss IP-addr-switch : year month day hh:mm:ss Timezone: facility-severity-mnemonic month dd hh:mm:ss IP-addr-switch : year month day hh:mm:sstimezone: facility-slotnumber-severity-mnemonic month dd hh:mm:ss IP-addr-switch : year month day hh:mm:ss Timezone: facility-standby-severity-mnemonic F example: sep 21 11:09:50 172.22.22.45 : 2005 Sep 04 18:18:22 UTC: %AUTHPRIV-3-SYSTEM_MSG: ttys1: togetattr: Input/output err - getty[28224] switch resident syslog 2005 Sep 4 18:18:22 switch %AUTHPRIV-3-SYSTEM_MSG: ttys1: togetattr: Input/output err - getty[28224] time on MDS : 2005 Sep 4 18:18:22 time on Loggng Server : Sep 21 11:09:50 fc1/13 is not suppted. Table 1-3 Element month dd hh:mm:ss IP-addr-switch facility severity MNEMONIC %$VSAN #%$ System Log Message Fmat The date and month of the err event The time of the err event The IP address of the switch The facility of the err event (daemon, kernel, VSHD, other facility) Single-digit code from 0 to 3 that indicates the severity of the message Text string that uniquely describes the system message An optional VLAN ID that appears in the f messages requiring VLAN IDs Text string containing detailed infmation about the event being repted FACILITY is a code consisting of two me uppercase letters that indicate the facility to which the system message refers. A facility is a hardware device, a protocol, a feature, a module of the system software. 1-3

Capturing System Messages and Histy Chapter 1 System message SEVERITY codes range from 0 to 3 and reflect the severity of the condition. The lower the number, the me serious the situation. Table 1-4 lists the severity levels. Table 1-4 System Log Message Fmat Level 0 emergency System unusable 1 alert Immediate action needed 2 critical Critical condition 3 notification Nmal but significant condition MNEMONIC is a code that uniquely identifies the system message. Message-text is a text string that describes the condition. This ption of the message might contain detailed infmation about the event, including terminal pt numbers, netwk addresses, addresses that crespond to locations in the system memy address space. Because the infmation in these variable fields changes from message to message, it is represented here by sht strings enclosed in square brackets ([ ]). A decimal number, f example, is represented as [dec]. Table 1-5 lists the representations of variable fields and the type of infmation in the fields. Table 1-5 Representation [dec] [hex] [char] [chars] Representation of Variable Fields in System Messages Type of Infmation Decimal number Hexadecimal number Single character Character string The following example system message shows how the variable field might be used: %AUTHPRIV-3-SYSTEM_MSG: AUTHPRIV [dec] repted a failure in service [chars] In this example, Facility code =AUTHPRIV (indicating that it is a authpriv-specific err) Severity =3 (notification) Alarm/event code= SYSTEM_MSG of the problem= Authpriv [dec] repted a failure in service [chars] [dec] is the module slot number associated with this message. [chars] is the service name that experienced this failure. Capturing System Messages and Histy The system messages are displayed instantly on the console, by default, are redirected to an internal log file, a syslog server. System message severity levels crespond to the keywds assigned by the logging global configuration commands. These keywds define where and at what level these messages appear (refer to the Cisco MDS 9000 Family CLI Configuration Guide and the Cisco MDS 9000 Family 1-4

Chapter 1 Capturing System Messages and Histy Fabric Manager Configuration Guide). Only system messages that crespond to the configured logging level higher severity messages are logged. As an example, if you set the logging level to 3 (err), then you get err, critical, alerts, and emergency system messages, but you do not get warning, notification, infmational, debugging system messages. Saving the System Messages Log The logging logfile global configuration command enables copying of system messages to an internal log file and optionally sets the size of the file. To display the messages that are logged in the file, use the show logging EXEC command. The first message displayed is the oldest message in the buffer. To clear the current contents of the buffer, use the clear debug-logfile privileged EXEC command. Logging System Messages to a Syslog Server The logging host-name command identifies a syslog server host to receive logging messages. The host-name argument is the name Internet address of the host. By issuing this command me than once, you build a list of syslog servers that receive logging messages. The no logging host-name command deletes the syslog server with the specified address from the list of syslog servers. 1-5

Capturing System Messages and Histy Chapter 1 1-6