S e n d c o m m e n t s t o n e x u s 3 k - d o c f e e d b a c k @ c i s c o . c o m
-SM-222
Cisco Nexus 3000 Series NX-OS System Management Command Reference
OL-29557-04
Chapter System Management Commands
show logging onboard
–
-i
—Ignores the case difference when comparing the strings.
–
-x
—Prints only the lines where the match is a whole line.
–
word
—Specifies for the expression.
•
last
[
num
]—Displays the last lines to print. The optional
num
specifies the number of lines to print.
Range: 0 to 9999.
•
less [-E
|
-d
]—Quits at the end of the file.
–
-E
—(Optional) Quits at the end of the file.
–
-d
—(Optional) Specifies a dumb terminal.
•
no-more
—Turns off pagination for command output.
•
sed
command
—Stream Editor
•
wc
—Counts words, lines, and characters.
–
-c
—(Optional) Specifies the output character count.
–
-l
—(Optional) Specifies the output line count.
–
-w
—(Optional) Specifies the output word count.
–
>
—Redirects it to a file.
–
|
—Pipes command output to filter.
Use this command to view OBFL data from the 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.
Starting with Release 7.0(3)I2(1), while the induced errors are corrected on the switches, the log
messages that notify the corrections stop after hitting a threshold (usually after 15 or 19 corrections).
Also, an extra message gets printed when the parity error is injected.
Examples
This example shows how to display the OBFL boot and uptime information:
switch#
show logging onboard boot-uptime
This example shows how to display the OBFL logging device information:
switch#
show logging onboard device-version
This example shows how to display the OBFL history information:
switch#
show logging onboard obfl-history
The
show logging onboard obfl-history
command displays the following information:
•
Timestamp when OBFL is manually disabled.
•
Timestamp when OBFL is manually enabled.