Cisco Catalyst 9500 Manual page 276

Hide thumbs Also See for Catalyst 9500:
Table of Contents

Advertisement

Configuring Conditional Debugging
Command or Action
Device# debug platform condition stop
Step 6
request platform software trace archive [last {number}
days] [target {crashinfo: | flashinfo:}]
Example:
# request platform software trace archive last 2
days
Step 7
show platform software trace [filter-binary | level |
message]
Example:
Device# show platform software trace message
Step 8
clear platform condition all
Example:
Device# clear platform condition all
What to do next
Note
The commands request platform software trace filter-binary and show platform software trace
filter-binary work in a similar way. The only difference is:
• request platform software trace filter-binary - Sources the data from historical logs.
• show platform software trace filter-binary – Sources the data from the flash Temp directory.
Of these, mac_log <..date..> is the most important file, as it gives the messages for the MAC we are debugging.
The command show platform software trace filter-binary also generates the same flash files, and also prints
the mac_log on the screen.
System Management Configuration Guide, Cisco IOS XE Fuji 16.8.x (Catalyst 9500 Switches)
262
Conditional Debug and Radioactive Tracing
Purpose
(Optional) Displays historical logs of merged tracefiles on
the system. Filter on any combination of number of days
or location.
(Optional) Displays logs merged from the latest tracefile.
Filter on any combination of application condition, trace
module name, and trace level.
• filter-binary - Filter the modules to be collated
• level - Show trace levels
• message - Show trace message ring contents
Note
On the device:
• Available from IOS console in addition to
linux shell.
• Generates a file with merged logs.
• Displays merged logs only from staging
area
Clears all conditions.

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents