Using On-Board Failure Logging - Cisco 3032 Software Configuration Manual

Using On-Board Failure Logging

Using On-Board Failure Logging
You can use the on-board-failure logging (OBFL) feature to collect information about the switch. The
information includes uptime, temperature, and voltage information and helps Cisco technical support
representatives to troubleshoot switch problems. We recommend that you keep OBFL enabled and do
not erase the data stored in the flash memory.
This section has this information:
•
•
•
Understanding OBFL
By default, OBFL is enabled. It collects information about the switch and small form-factor pluggable
(SFP) modules. The switch stores this information in the flash memory:
•
•
•
•
•
•
You should manually set the system clock or configure it by using Network Time Protocol (NTP).
When the switch is running, you can retrieve the OBFL data by using the show logging onboard
privileged EXEC commands. If the switch fails, contact your Cisco technical support representative to
find out how to retrieve the data.
When an OBFL-enabled switch is restarted, there is a 10-minute delay before logging of new data
begins.
Configuring OBFL
To enable OBFL, use the hw-module module [switch-number] logging onboard [message level level]
global configuration command. On stacking-capable switches, the range for switch-number is from 1
to 9. On nonstacking-capable switches, the switch number is always 1. Use the message level level
parameter to specify the severity of the hardware-related messages that the switch generates and stores
in the flash memory.
To copy the OBFL data to the local network or a specific file system, use the copy logging onboard
module stack-member destination privileged EXEC command.
Cisco Catalyst Blade Switch 3130 and 3032 for Dell Software Configuration Guide
47-22
Understanding OBFL, page 47-22
Configuring OBFL, page 47-22
Displaying OBFL Information, page 47-23
CLI commands—Record of the OBFL CLI commands that are entered on a standalone switch or a
switch stack member
Environment data—Unique device identifier (UDI) information for a standalone switch or a stack
member and for all the connected FRU devices: the product identification (PID), the version
identification (VID), and the serial number
Message—Record of the hardware-related system messages generated by a standalone switch or a
stack member
Temperature—Temperature of a standalone switch or a stack member
Uptime data—Time when a standalone switch or a stack member starts, the reason the switch
restarts, and the length of time the switch has been running since it last restarted
Voltage—System voltages of a standalone switch or a stack member
Chapter 47 Troubleshooting
OL-12247-04