AP Crash File Upload
When a converted access point unexpectedly reboots, the access point stores a crash file on its local flash memory at the time of the crash. After the unit reboots, it sends the reason for the reboot to the device. If the unit rebooted because of a crash, the device pulls up the crash file using the existing CAPWAP messages and stores it in the device flash memory. The crash information copy is removed from the access point's flash memory when the device pulls it from the access point:
Note |
The system does not generate reports in case of a reload. |
During a process crash, the following are collected locally from the device:
-
Full process core
-
Trace logs
-
Cisco IOS syslogs (not guaranteed in case of nonactive crashes)
-
System process information
-
Bootup logs
-
Reload logs
-
Certain types of proc information
All this information is stored in separate files, which are then archived and compressed into one bundle. This makes it convenient to get a crash snapshot in one place, and can be then moved off the box for analysis. This report is generated before the device goes down to ROMMON/bootloader.
Note |
Except for the full core and tracelogs, everything else is a text file. |