Message Logging - Cisco Catalyst 4500 Series Configuration Manual

Release ios xe 3.3.0sg and ios 15.1(1)sg
Hide thumbs Also See for Catalyst 4500 Series:
Table of Contents

Advertisement

Information About OBFL

Message Logging

The OBFL feature logs standard system messages. Instead of displaying the message to a terminal, the
message is written to and stored in a file, so the message can be accessed and read at a later time. System
messages range from level 1 alerts to level 7 debug messages, and these levels can be specified in the
hw module logging onboard command.
Error Message Log Example
Switch# sh logging onboard message det
--------------------------------------------------------------------------------
ERROR MESSAGE SUMMARY INFORMATION
--------------------------------------------------------------------------------
Facility-Sev-Name
MM/DD/YYYY HH:MM:SS
--------------------------------------------------------------------------------
%CAT4K-3-DIAGNOSTICS_PASSED :
11/24/2010 15:46:20 module passed diagnostics
%CAT4K-2-DIAGNOSTIC_STATUS :
11/24/2010 15:46:20 diagnostic Packet memory Skipped
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
ERROR MESSAGE CONTINUOUS INFORMATION
--------------------------------------------------------------------------------
MM/DD/YYYY HH:MM:SS Facility-Sev-Name
--------------------------------------------------------------------------------
12/15/2010 11:32:39
12/15/2010 11:32:39
12/15/2010 13:03:41
12/15/2010 13:03:41
12/15/2010 13:25:02
12/15/2010 13:25:02
12/15/2010 13:45:34
12/15/2010 13:45:34
12/15/2010 14:05:01
12/15/2010 14:05:01
12/15/2010 14:35:51
12/15/2010 14:35:51
--------------------------------------------------------------------------------
Switch#
To interpret this data:
Software Configuration Guide—Release IOS XE 3.4.0SG and IOS 15.1(2)SG
59-8
| Count | Persistence Flag
%CAT4K-3-DIAGNOSTICS_PASSED : module passed diagnostics
%CAT4K-2-DIAGNOSTIC_STATUS : diagnostic Packet memory Skipped
%CAT4K-3-DIAGNOSTICS_PASSED : module passed diagnostics
%CAT4K-2-DIAGNOSTIC_STATUS : diagnostic Packet memory Skipped
%CAT4K-3-DIAGNOSTICS_PASSED : module passed diagnostics
%CAT4K-2-DIAGNOSTIC_STATUS : diagnostic Packet memory Skipped
%CAT4K-3-DIAGNOSTICS_PASSED : module passed diagnostics
%CAT4K-2-DIAGNOSTIC_STATUS : diagnostic Packet memory Skipped
%CAT4K-3-DIAGNOSTICS_PASSED : module passed diagnostics
%CAT4K-2-DIAGNOSTIC_STATUS : diagnostic Packet memory Skipped
%CAT4K-3-DIAGNOSTICS_PASSED : module passed diagnostics
%CAT4K-2-DIAGNOSTIC_STATUS : diagnostic Packet memory Skipped
A timestamp shows the date and time the message was logged.
Facility-Sev-Name is a coded naming scheme for a system message, as follows:
The Facility code consists of two or more uppercase letters that indicate the hardware device
(facility) to which the message refers.
Sev is a single-digit code from 1 to 7 that reflects the severity of the message.
Name is one or two code names separated by a hyphen that describe the part of the system from
where the message is coming.
The error message follows the Facility-Sev-Name codes. For more information about system
messages, see the
Cisco IOS System and Error Messages
Count indicates the number of instances of this message that is allowed in the history file. Once that
number of instances has been recorded, the oldest instance will be removed from the history file to
make room for new ones.
22
LAST
22
LAST
Chapter 59
Onboard Failure Logging (OBFL)
guide.
OL-27597-01

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents