![Cisco Catalyst Blade 3032 Скачать руководство пользователя страница 1257](http://html.mh-extra.com/html/cisco/catalyst-blade-3032/catalyst-blade-3032_software-configuration-manual_676651257.webp)
48-21
Cisco Catalyst Blade Switch 3130 and 3032 for Dell Software Configuration Guide
OL-13270-06
Chapter 48 Troubleshooting
Using the crashinfo Files
Output Packets:
------------------------------------------
Packet 1
Lookup Key-Used Index-Hit A-Data
OutptACL 50_10010A05_0A010505-00_40000014_000A0000 01FFE 03000000
Port Vlan SrcMac DstMac Cos Dscpv
Gi1/0/2
0007 XXXX.XXXX.0246 0009.43A8.0147
Using the crashinfo Files
The crashinfo files save information that helps Cisco technical support representatives to debug
problems that caused the Cisco IOS image to fail (crash). The switch writes the crash information to the
console at the time of the failure. The switch creates two types of crashinfo files:
•
Basic crashinfo file—The switch automatically creates this file the next time you boot up the Cisco
IOS image after the failure.
•
Extended crashinfo file—The switch automatically creates this file when the system is failing.
Basic crashinfo Files
The information in the basic file includes the Cisco IOS image name and version that failed, a list of the
processor registers, and a stack trace. You can provide this information to the Cisco technical support
representative by using the
show tech-support
privileged EXEC command.
Basic crashinfo files are kept in this directory on the flash file system:
flash:/crashinfo/.
The filenames are crashinfo_
n
where
n
is a sequence number.
Each new crashinfo file that is created uses a sequence number that is larger than any previously existing
sequence number, so the file with the largest sequence number describes the most recent failure. Version
numbers are used instead of a timestamp because the switches do not include a real-time clock. You
cannot change the name of the file that the system will use when it creates the file. However, after the
file is created, you can use the
rename
privileged EXEC command to rename it, but the contents of the
renamed file will not be displayed by the
show stacks
or the
show tech-support
privileged EXEC
command. You can delete crashinfo files by using the
delete
privileged EXEC command.
You can display the most recent basic crashinfo file (that is, the file with the highest sequence number
at the end of its filename) by entering the
show stacks
or the
show tech-support
privileged EXEC
command. You also can access the file by using any command that can copy or display files, such as the
more
or the
copy
privileged EXEC command.
Extended crashinfo Files
The switch creates the extended crashinfo file when the system is failing. The information in the
extended file includes additional information that can help determine the cause of the switch failure. You
provide this information to the Cisco technical support representative by manually accessing the file and
using the
more
or the
copy
privileged EXEC command.
Extended crashinfo files are kept in this directory on the flash file system:
flash:/crashinfo_ext/.
Содержание Catalyst Blade 3032
Страница 46: ...Contents xlvi Cisco Catalyst Blade Switch 3130 and 3032 for Dell Software Configuration Guide OL 13270 06 ...
Страница 50: ...lii Cisco Catalyst Blade Switch 3130 and 3032 for Dell Software Configuration Guide OL 13270 06 Preface ...
Страница 1380: ...Index IN 54 Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide OL 12189 06 ...