Cisco Catalyst 9500 Manual page 286
Hide thumbs
Also See for Catalyst 9500:
- Manual (360 pages) ,
- Configuration manual (223 pages) ,
- Hardware installation manual (122 pages)
Table of Contents
Advertisement
Onboard Failure Logging on the Switch
null:
nvram:
rcp:
running-config Update (merge with) current system configuration
scp:
startup-config Copy to startup configuration
syslog:
system:
tftp:
tmpsys:
The general syntax for copying onto TFTP server is as follows:
Switch#copy crashinfo: tftp:
Source filename [system-report_1_20150909-092728-UTC.gz]?
Address or name of remote host []? 1.1.1.1
Destination filename [system-report_1_20150909-092728-UTC.gz]?
The tracelogs can be collected by issuing a trace archive command. This command provides time period
options. The command syntax is as follows:
Switch#request platform software trace archive ?
last
target
The tracelogs stored in crashinfo: or flash: directory from within the last 3650 days can be collected.
Switch# request platform software trace archive last ?
<1-3650> Number of days (1-3650)
Switch#request platform software trace archive last 3650 days target ?
crashinfo: Archive file name and location
flash:
Note
It is important to clear the system reports or trace archives from flash or crashinfo directory once they are
copied out, in order to have space available for tracelogs and other purposes.
In a complex network it is difficult to track the origin of a system-report file. This task is made easier if the
system-report files are uniquely identifiable. Starting with the Cisco IOS XE Amsterdam 17.3.x release, the
hostname will be prepended to the system-report file name making the reports uniquely identifiable.
The following example displays system-report files with the hostname prepended:
HOSTNAME#dir flash:/core | grep HOSTNAME
40486
HOSTNAME-system-report_20191021-200748-UTC.tar.gz
40487
HOSTNAME-system-report_20191021-200748-UTC-info.txt
40484
HOSTNAME-system-report_20191021-205523-UTC.tar.gz
40488
HOSTNAME-system-report_20191021-205523-UTC-info.txt
Onboard Failure Logging on the Switch
You can use the onboard failure logging (OBFL) feature to collect information about the device. The information
includes uptime, temperature, and voltage information and helps Cisco technical support representatives to
troubleshoot device problems. We recommend that you keep OBFL enabled and do not erase the data stored
in the flash memory.
System Management Configuration Guide, Cisco IOS XE Fuji 16.8.x (Catalyst 9500 Switches)
272
Copy to null: file system
Copy to nvram: file system
Copy to rcp: file system
Copy to scp: file system
Copy to syslog: file system
Copy to system: file system
Copy to tftp: file system
Copy to tmpsys: file system
Archive trace files of last x days
Location and name for the archive file
Archive file name and location
-rw-
108268293
Oct 21 2019 16:07:50 -04:00
-rw-
17523
Oct 21 2019 16:07:56 -04:00
-rw-
48360998
Oct 21 2019 16:55:24 -04:00
-rw-
14073
Oct 21 2019 16:55:26 -04:00
Troubleshooting the Software Configuration
Hide quick links:
Advertisement
Table of Contents
