Onboard Failure Logging
Available Languages
Table Of Contents
Configuration Examples for OBFL
Enabling OBFL Message Logging: Example
OBFL Component Uptime Report: Example
OBFL Report for a Specific Time: Example
clear logging onboard (Cat 6K)
hw-module logging onboard (Cat 6K)
Onboard Failure Logging
First Published: August 10, 2007Last Updated: August 10, 2007The Onboard Failure Logging (OBFL) feature collects data such as operating temperatures, hardware uptime, interrupts, and other important events and messages from system hardware installed in a Cisco router or switch. The data is stored in nonvolatile memory and helps technical personnel diagnose hardware problems.
Finding Feature Information in This Module
Your Cisco IOS software release may not support all of the features documented in this module. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported, use the "Feature Information for OBFL" section.
Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Configuration Examples for OBFL
Restrictions for OBFL
Software Restrictions
If a device (router or switch) intends to use linear flash memory as its OBFL storage media, Cisco IOS software must reserve a minimum of two physical sectors (or physical blocks) for the OBFL feature. Because an erase operation for a linear flash device is done on per-sector (or per-block) basis, one extra physical sector is needed. Otherwise, the minimum amount of space reserved for the OBFL feature on any device must be at least 8 KB.
Firmware Restrictions
If a line card or port adapter runs an operating system or firmware that is different from the Cisco IOS operating system, the line card or port adapter must provide device driver level support or an interprocess communications (IPC) layer that allows the OBFL file system to communicate to the line card or port adapter. This requirement is enforced to allow OBFL data to be recorded on a storage device attached to the line card or port adapter.
Hardware Restrictions
To support the OBFL feature, a device must have at least 8 KB of nonvolatile memory space reserved for OBFL data logging.
Information About OBFL
To use the OBFL feature, you should understand the following concept:
Data Collected
The OBFL feature records operating temperatures, hardware uptime, interrupts, and other important events and messages that can assist with diagnosing problems with hardware cards (or modules) installed in a Cisco router or switch. Data is logged to files stored in nonvolatile memory. When the onboard hardware is started up, a first record is made for each area monitored and becomes a base value for subsequent records. The OBFL feature provides a circular updating scheme for collecting continuous records and archiving older (historical) records, ensuring accurate data about the system. Data is recorded in one of two formats: continuous information that displays a snapshot of measurements and samples in a continuous file, and summary information that provides details about the data being collected. The data is displayed using the show logging onboard command. The message "No historical data to display" is seen when historical data is not available.
The following sections describe the type of data collected in more detail.
Temperature
Temperatures surrounding hardware modules can exceed recommended safe operating ranges and cause system problems such as packet drops. Higher than recommended operating temperatures can also accelerate component degradation and affect device reliability. Monitoring temperatures is important for maintaining environmental control and system reliability. Once a temperature sample is logged, the sample becomes the base value for the next record. From that point on, temperatures are recorded either when there are changes from the previous record or if the maximum storage time is exceeded. Temperatures are measured and recorded in degrees Celsius.
Temperature Example
--------------------------------------------------------------------------------TEMPERATURE SUMMARY INFORMATION--------------------------------------------------------------------------------Number of sensors : 12Sampling frequency : 5 minutesMaximum time of storage : 120 minutes--------------------------------------------------------------------------------Sensor | ID | Maximum Temperature 0C--------------------------------------------------------------------------------MB-Out 980201 43MB-In 980202 28MB 980203 29MB 980204 38EARL-Out 910201 0EARL-In 910202 0SSA 1 980301 38SSA 2 980302 36JANUS 1 980303 36JANUS 2 980304 35GEMINI 1 980305 0GEMINI 2 980306 0---------------------------------------------------------------Temp Sensor ID0C 1 2 3 4 5 6 7 8 9 10 11 12---------------------------------------------------------------No historical data to display-----------------------------------------------------------------------------------------------------------------------------------------------TEMPERATURE CONTINUOUS INFORMATION--------------------------------------------------------------------------------Sensor | ID |--------------------------------------------------------------------------------MB-Out 980201MB-In 980202MB 980203MB 980204EARL-Out 910201EARL-In 910202SSA 1 980301SSA 2 980302JANUS 1 980303JANUS 2 980304GEMINI 1 980305GEMINI 2 980306-------------------------------------------------------------------------------Time Stamp |Sensor Temperature 0CMM/DD/YYYY HH:MM:SS | 1 2 3 4 5 6 7 8 9 10 11 12-------------------------------------------------------------------------------03/06/2007 22:32:51 31 26 27 27 NA NA 33 32 30 29 NA NA03/06/2007 22:37:51 43 28 29 38 NA NA 38 36 36 35 NA NA-------------------------------------------------------------------------------To interpret this data:
•
•
•
•
•
•
•
•
Operational Uptime
The operational uptime tracking begins when the module is powered on, and information is retained for the life of the module.
Operational Uptime Example
--------------------------------------------------------------------------------UPTIME SUMMARY INFORMATION--------------------------------------------------------------------------------First customer power on : 03/06/2007 22:32:51Total uptime : 0 years 0 weeks 2 days 18 hours 10 minutesTotal downtime : 0 years 0 weeks 0 days 8 hours 7 minutesNumber of resets : 130Number of slot changes : 16Current reset reason : 0xA1Current reset timestamp : 03/07/2007 13:29:07Current slot : 2Current uptime : 0 years 0 weeks 1 days 7 hours 0 minutes--------------------------------------------------------------------------------Reset | |Reason | Count |--------------------------------------------------------------------------------0x5 640x6 620xA1 4----------------------------------------------------------------------------------------------------------------------------------------------------------------UPTIME CONTINUOUS INFORMATION--------------------------------------------------------------------------------Time Stamp | Reset | UptimeMM/DD/YYYY HH:MM:SS | Reason | years weeks days hours minutes--------------------------------------------------------------------------------03/06/2007 22:32:51 0xA1 0 0 0 0 0--------------------------------------------------------------------------------The operational uptime application tracks the following events:
•
•
•
•
•
•
•
•
•
Interrupts
Interrupts are generated by system components that require attention from the CPU such as ASICs and NMIs. Interrupts are generally related to hardware limit conditions or errors that need to be corrected.
The continuous format records each time a component is interrupted, and this record is stored and used as base information for subsequent records. Each time the list is saved, a timestamp is added. Time differences from the previous interrupt are counted, so that technical personnel can gain a complete record of the component's operational history when an error occurs.
Interrupts Example
--------------------------------------------------------------------------------INTERRUPT SUMMARY INFORMATION--------------------------------------------------------------------------------Name | ID | Offset | Bit | Count--------------------------------------------------------------------------------No historical data to display----------------------------------------------------------------------------------------------------------------------------------------------------------------CONTINUOUS INTERRUPT INFORMATION--------------------------------------------------------------------------------MM/DD/YYYY HH:MM:SS mmm | Name | ID | Offset | Bit--------------------------------------------------------------------------------03/06/2007 22:33:06 450 Port-ASIC #2 9 0x00E7 6--------------------------------------------------------------------------------To interpret this data:
•
•
•
•
•
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
--------------------------------------------------------------------------------ERROR MESSAGE SUMMARY INFORMATION--------------------------------------------------------------------------------Facility-Sev-Name | Count | Persistence FlagMM/DD/YYYY HH:MM:SS--------------------------------------------------------------------------------No historical data to display----------------------------------------------------------------------------------------------------------------------------------------------------------------ERROR MESSAGE CONTINUOUS INFORMATION--------------------------------------------------------------------------------MM/DD/YYYY HH:MM:SS Facility-Sev-Name--------------------------------------------------------------------------------03/06/2007 22:33:35 %GOLD_OBFL-3-GOLD : Diagnostic OBFL: Diagnostic OBFL testingTo interpret this data:
•
•
–
–
–
•
•
•
How to Enable OBFL
This section contains the following procedure:
Enabling OBFL
The OBFL feature is enabled by default. Because of the valuable information this feature offers technical personnel, it should not be disabled. If you find the feature has been disabled, use the following steps to reenable it.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Configuration Examples for OBFL
The important OBFL feature is the information that is displayed by the show logging onboard module privileged EXEC command. This section provides the following examples of how to enable and display OBFL records.
•
•
•
Enabling OBFL Message Logging: Example
The following example shows how to configure OBFL message logging at level 3:
hw-module switch 2 module 1 logging onboard message level 3OBFL Message Log: Example
The following example shows how to display the system messages that are being logged for module 2:
Router# show logging onboard module 2 message continuous--------------------------------------------------------------------------------ERROR MESSAGE CONTINUOUS INFORMATION--------------------------------------------------------------------------------MM/DD/YYYY HH:MM:SS Facility-Sev-Name--------------------------------------------------------------------------------03/06/2007 22:33:35 %SWITCH_IF-3-CAMERR : [chars], for VCI [dec] VPI [dec] in stdby data path check, status: [dec]--------------------------------------------------------------------------------OBFL Component Uptime Report: Example
The following example shows how to display a summary report for component uptimes for module 2:
Router# show logging onboard module 2 uptime--------------------------------------------------------------------------------UPTIME SUMMARY INFORMATION--------------------------------------------------------------------------------First customer power on : 03/06/2007 22:32:51Total uptime : 0 years 0 weeks 0 days 0 hours 35 minutesTotal downtime : 0 years 0 weeks 0 days 0 hours 0 minutesNumber of resets : 1Number of slot changes : 0Current reset reason : 0xA1Current reset timestamp : 03/06/2007 22:31:34Current slot : 2Current uptime : 0 years 0 weeks 0 days 0 hours 35 minutes--------------------------------------------------------------------------------Reset | |Reason | Count |--------------------------------------------------------------------------------No historical data to display--------------------------------------------------------------------------------OBFL Report for a Specific Time: Example
The following example shows how to display continuous reports for all components during a specific time period:
Router# show logging onboard module 3 continuous start 15:01:57 1 Mar 2007 end 15:04:57 3 Mar 2007PID: WS-X6748-GE-TX , VID: , SN: SAL09063B85--------------------------------------------------------------------------------UPTIME CONTINUOUS INFORMATION--------------------------------------------------------------------------------Time Stamp | Reset | UptimeMM/DD/YYYY HH:MM:SS | Reason | years weeks days hours minutes--------------------------------------------------------------------------------03/01/2007 15:01:57 0xA1 0 0 0 10 003/03/2007 02:29:29 0xA1 0 0 0 5 0----------------------------------------------------------------------------------------------------------------------------------------------------------------TEMPERATURE CONTINUOUS INFORMATION--------------------------------------------------------------------------------Sensor | ID |--------------------------------------------------------------------------------MB-Out 930201MB-In 930202MB 930203MB 930204EARL-Out 910201EARL-In 910202SSA 1 930301SSA 2 930302JANUS 1 930303JANUS 2 930304GEMINI 1 930305GEMINI 2 930306-------------------------------------------------------------------------------Time Stamp |Sensor Temperature 0CMM/DD/YYYY HH:MM:SS | 1 2 3 4 5 6 7 8 9 10 11 12-------------------------------------------------------------------------------03/01/2007 15:01:57 26 26 NA NA NA NA 0 0 0 0 0 003/01/2007 15:06:57 39 27 NA NA NA NA 39 37 36 29 32 3203/01/2007 15:11:02 40 27 NA NA NA NA 40 38 37 30 32 3203/01/2007 17:06:06 40 27 NA NA NA NA 40 38 37 30 32 3203/01/2007 19:01:09 40 27 NA NA NA NA 40 38 37 30 32 3203/03/2007 02:29:30 25 26 NA NA NA NA 0 0 0 0 0 003/03/2007 02:34:30 38 26 NA NA NA NA 39 37 36 29 31 3103/03/2007 04:29:33 40 27 NA NA NA NA 40 38 36 30 32 3203/03/2007 06:24:37 40 27 NA NA NA NA 40 38 36 29 32 3203/03/2007 08:19:40 40 27 NA NA NA NA 40 38 36 29 32 3203/03/2007 10:14:44 40 27 NA NA NA NA 40 38 36 30 32 3203/03/2007 12:09:47 40 27 NA NA NA NA 40 38 36 30 32 3203/03/2007 14:04:51 40 27 NA NA NA NA 40 38 36 30 32 32---------------------------------------------------------------------------------------------------------------------------------------------------------------CONTINUOUS INTERRUPT INFORMATION--------------------------------------------------------------------------------MM/DD/YYYY HH:MM:SS mmm | Name | ID | Offset | Bit--------------------------------------------------------------------------------03/01/2007 15:01:59 350 Port-ASIC #0 7 0x00E7 603/03/2007 02:29:34 650 Port-ASIC #0 7 0x00E7 6----------------------------------------------------------------------------------------------------------------------------------------------------------------ERROR MESSAGE CONTINUOUS INFORMATION--------------------------------------------------------------------------------MM/DD/YYYY HH:MM:SS Facility-Sev-Name--------------------------------------------------------------------------------03/01/2007 15:02:15 %GOLD_OBFL-3-GOLD : Diagnostic OBFL: Diagnostic OBFL testing03/03/2007 02:29:51 %GOLD_OBFL-3-GOLD : Diagnostic OBFL: Diagnostic OBFL testing--------------------------------------------------------------------------------Additional References
The following sections provide references related to the OBFL feature.
Related Documents
Onboard Failure Logging for Cisco 12000 series routers running Cisco IOS XR Software v3.4
Onboard Failure Logging on Cisco IOS Software Release 3.4 feature module
Onboard Failure Logging for Catalyst 3750-E and 3560-E switches running Cisco IOS Software
Release 12.2(35)SE2"Using On-Board Failure Logging" section in the "Troubleshooting" chapter in the Catalyst 3750-E and 3560-E Switch Software Configuration Guide, 12.2(35)SE2
Other related logging commands
Catalyst 3750-E and 3560-E Switch Command Reference, Release 12.2(58)SE
Standards
MIBs
None
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
RFCs
Technical Assistance
Command Reference
This section documents only commands that are new or modified:
•
•
•
•
clear logging onboard (Cat 6K)
To clear the onboard failure logs (OBFL) on Cisco Catalyst 6000 series switches, use the clear logging onboard command in privileged EXEC mode.
clear logging onboard [module module-number]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use this command to clear all OBFL logs or only the logs in the module specified by the module module-number option.
Note
Examples
The following example shows how to clear the logs from module 2:
Router# clear logging onboard module 2Related Commands
copy logging onboard (Cat 6K)
To copy onboard failure logging (OBFL) data from the target OBFL-enabled module in Cisco Catalyst 6000 series switches to a local or remote file system, use the copy logging onboard command in privileged EXEC mode.
copy logging onboard module module-number destination-url
Syntax Description
Command Default
This command has no default condition.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
This command copies OBFL data from the target OBFL-enabled board to a local or remote file system. See the Cisco IOS Configuration Fundamentals Command Reference for more information about use of the copy command.
Examples
The following example shows the options for copying OBFL data:
Router# copy logging onboard module 2 ?bootflash: Copy onboard logging to bootflash: file systemconst_nvram: Copy onboard logging to const_nvram: file systemdfc#2-bootflash: Copy onboard logging to dfc#2-bootflash: file systemdfc#4-bootflash: Copy onboard logging to dfc#4-bootflash: file systemdisk0: Copy onboard logging to disk0: file systemdisk1: Copy onboard logging to disk1: file systemftp: Copy onboard logging to ftp: file systemhttp: Copy onboard logging to http: file systemhttps: Copy onboard logging to https: file systemnull: Copy onboard logging to null: file systemnvram: Copy onboard logging to nvram: file systemrcp: Copy onboard logging to rcp: file systemscp: Copy onboard logging to scp: file systemsup-bootflash: Copy onboard logging to sup-bootflash: file systemsup-image: Copy onboard logging to sup-image: file systemsyslog: Copy onboard logging to syslog: file systemsystem: Copy onboard logging to system: file systemtftp: Copy onboard logging to tftp: file systemtmpsys: Copy onboard logging to tmpsys: file systemThe following example shows how to transfer the OBFL data to a file on disk1:
Router# copy logging onboard module 2 disk1:tarmod2OBFL feature copy disk1:tarmod2 2% File transfer succeededThe following example shows how to transfer the OBFL data to a file on a remote server:
Router# copy logging onboard module 2 tftp://server1/user1/tars/tarmod2/mod2tarOBFL feature copy tftp://server1/user1/tars/tarmod2/mod2tar 2% File transfer succeededRelated Commands
hw-module logging onboard (Cat 6K)
To re-enable onboard failure logging (OBFL) on Cisco Catalyst 6000 series switches if logging has been disabled, use the hw-module logging onboard command in global configuration mode. To disable OBFL (not recommended), use the no form of this command.
hw-module switch switch-number module module-number logging onboard [message level {1-7}]
no hw-module switch switch-number module module-number logging onboard [message level {1-7}]
Syntax Description
Command Default
Enabled in all hardware and is the recommended state; all levels of system messages are logged.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
This command enables operating temperatures, hardware uptime, interrupts, and other important events and messages to be recorded in files stored in nonvolatile memory, so that the data can be used to diagnose problems with hardware cards installed in a Cisco router or switch. When the onboard hardware is started up, a first record is made for each area monitored and becomes a base value for subsequent records. This command provides a circular updating scheme for collecting continuous records and archiving older (historical) records, ensuring accurate data about the hardware. Data is recorded in one of two formats: continuous information that displays a snapshot of data in a continuous file, and summary information that provides details about the data being collected. Use the show logging onboard privileged EXEC command to see reports of current and historical data.
This configuration command is applicable to the module inserted in a device. When the module is removed and inserted into a new device, the configuration of this command follows the module to the new device.
This command is normally accessed through the route processor or supervisor command line interface; however, some system images do not provide full support for client remote terminal access. When using these images, use the attach command to connect to the console on the line card.
Examples
The following example shows how to configure OBFL message logging at level 7 (debugging):
Router> enableRouter# configure terminalRouter(config)# hw-module switch 2 module 1 logging onboard message level 7Router(config)# endRelated Commands
show logging onboard (Cat 6K)
To display onboard failure logs (OBFL) on Cisco Catalyst 6000 series switches, use the show logging onboard command in privileged EXEC mode.
show logging onboard [module module-number] [status | [[temperature | uptime | message] [[continuous [start start-time-and-date] [end end-time-and-date]] | [detail [start start-time-and-date] [end end-time-and-date]] | [summary]]]]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The show logging onboard command can be entered without any arguments, which is the same as entering the show logging onboard summary command to display summarized information about OBFL for the device residing on the same module where the command is entered.
Use this command to view OBFL data from system hardware. The OBFL feature is enabled by default and records operating temperatures, hardware uptime, interrupts, and other important events and messages that can assist with diagnosing problems with hardware cards (or modules) installed in a Cisco router or switch. Data is logged to files stored in nonvolatile memory. When the onboard hardware is started up, a first record is made for each area monitored and becomes a base value for subsequent records.
The OBFL feature provides a circular updating scheme for collecting continuous records and archiving older (historical) records, ensuring accurate data about the system. Data is recorded in one of two formats: continuous information that displays a snapshot of measurements and samples in a continuous file, and summary information that provides details about the data being collected. The message "No historical data to display" is seen when historical data is not available.
See the examples for more information about the type of data collected.
Examples
Temperature
Temperatures surrounding hardware modules can exceed recommended safe operating ranges and cause system problems such as packet drops. Higher than recommended operating temperatures can also accelerate component degradation and affect device reliability. Monitoring temperatures is important for maintaining environmental control and system reliability. Once a temperature sample is logged, the sample becomes the base value for the next record. From that point on, temperatures are recorded either when there are changes from the previous record or if the maximum storage time is exceeded. Temperatures are measured and recorded in degrees Celsius.
The following example shows how you might enter this command:
Router# show logging onboard module 2 temperature detail--------------------------------------------------------------------------------TEMPERATURE SUMMARY INFORMATION--------------------------------------------------------------------------------Number of sensors : 12Sampling frequency : 5 minutesMaximum time of storage : 120 minutes--------------------------------------------------------------------------------Sensor | ID | Maximum Temperature 0C--------------------------------------------------------------------------------MB-Out 980201 43MB-In 980202 28MB 980203 29MB 980204 38EARL-Out 910201 0EARL-In 910202 0SSA 1 980301 38SSA 2 980302 36JANUS 1 980303 36JANUS 2 980304 35GEMINI 1 980305 0GEMINI 2 980306 0---------------------------------------------------------------Temp Sensor ID0C 1 2 3 4 5 6 7 8 9 10 11 12---------------------------------------------------------------No historical data to display-----------------------------------------------------------------------------------------------------------------------------------------------TEMPERATURE CONTINUOUS INFORMATION--------------------------------------------------------------------------------Sensor | ID |--------------------------------------------------------------------------------MB-Out 980201MB-In 980202MB 980203MB 980204EARL-Out 910201EARL-In 910202SSA 1 980301SSA 2 980302JANUS 1 980303JANUS 2 980304GEMINI 1 980305GEMINI 2 980306-------------------------------------------------------------------------------Time Stamp |Sensor Temperature 0CMM/DD/YYYY HH:MM:SS | 1 2 3 4 5 6 7 8 9 10 11 12-------------------------------------------------------------------------------03/06/2007 22:32:51 31 26 27 27 NA NA 33 32 30 29 NA NA03/06/2007 22:37:51 43 28 29 38 NA NA 38 36 36 35 NA NA-------------------------------------------------------------------------------Table 2 describes the significant fields shown in the display.
Operational Uptime
The operational uptime tracking begins when the module is powered on, and information is retained for the life of the module.
The following example shows how you might enter this command:
Router# show logging onboard module 2 uptime detail--------------------------------------------------------------------------------UPTIME SUMMARY INFORMATION--------------------------------------------------------------------------------First customer power on : 03/06/2007 22:32:51Total uptime : 0 years 0 weeks 2 days 18 hours 10 minutesTotal downtime : 0 years 0 weeks 0 days 8 hours 7 minutesNumber of resets : 130Number of slot changes : 16Current reset reason : 0xA1Current reset timestamp : 03/07/2007 13:29:07Current slot : 2Current uptime : 0 years 0 weeks 1 days 7 hours 0 minutes--------------------------------------------------------------------------------Reset | |Reason | Count |--------------------------------------------------------------------------------0x5 640x6 620xA1 4----------------------------------------------------------------------------------------------------------------------------------------------------------------UPTIME CONTINUOUS INFORMATION--------------------------------------------------------------------------------Time Stamp | Reset | UptimeMM/DD/YYYY HH:MM:SS | Reason | years weeks days hours minutes--------------------------------------------------------------------------------03/06/2007 22:32:51 0xA1 0 0 0 0 0--------------------------------------------------------------------------------The operational uptime application tracks the following events:
•
•
•
•
•
•
•
•
•
Interrupts
Interrupts are generated by system components that require attention from the CPU, such as ASICs and NMIs. Interrupts are generally related to hardware limit conditions or errors that need to be corrected.
The continuous format records each time a component is interrupted, and this record is stored and used as base information for subsequent records. Each time the list is saved, a timestamp is added. Time differences from the previous interrupt are counted, so that technical personnel can gain a complete record of the component's operational history when an error occurs.
The following example shows how you might enter this command:
Router# show logging onboard module 2 interrupt detail--------------------------------------------------------------------------------INTERRUPT SUMMARY INFORMATION--------------------------------------------------------------------------------Name | ID | Offset | Bit | Count--------------------------------------------------------------------------------No historical data to display----------------------------------------------------------------------------------------------------------------------------------------------------------------CONTINUOUS INTERRUPT INFORMATION--------------------------------------------------------------------------------MM/DD/YYYY HH:MM:SS mmm | Name | ID | Offset | Bit--------------------------------------------------------------------------------03/06/2007 22:33:06 450 Port-ASIC #2 9 0x00E7 6--------------------------------------------------------------------------------Table 4 describes the significant fields shown in the display.
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.
The following example shows how you might enter this command:
Router# show logging onboard module 2 message detail--------------------------------------------------------------------------------ERROR MESSAGE SUMMARY INFORMATION--------------------------------------------------------------------------------Facility-Sev-Name | Count | Persistence FlagMM/DD/YYYY HH:MM:SS--------------------------------------------------------------------------------No historical data to display----------------------------------------------------------------------------------------------------------------------------------------------------------------ERROR MESSAGE CONTINUOUS INFORMATION--------------------------------------------------------------------------------MM/DD/YYYY HH:MM:SS Facility-Sev-Name--------------------------------------------------------------------------------03/06/2007 22:33:35 %GOLD_OBFL-3-GOLD : Diagnostic OBFL: Diagnostic OBFL testingTable 5 describes the significant fields shown in the display.
Table 5 Error Message Summary Information
A timestamp
Shows the date and time the message was logged.
Facility-Sev-Name
A coded naming scheme for a system message, as follows:
•
•
•
Error message
Follows the Facility-Sev-Name codes. For more information about system messages, see the Cisco IOS System and Error Messages guide.
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.
Persistence Flag
Gives a message priority over others that do not have the flag set.
Related Commands
Feature Information for OBFL
Table 6 lists the release history for this feature.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2007 Cisco Systems, Inc. All rights reserved.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)