%PLATFORM-1-CRASHED: C3750E - Version 15.2(4)E9

[SHAIKN]

I see the CRASHED logs in one of the switches and this model is already out of service.

Is there any way we may mitigate the over time rather than replacing it with a new model?

If there aren't any long-term choices, how can we fix the problem until the equipment is replaced?

Is there any long-term impact of these cached logs on device performance or services

%PLATFORM-1-CRASHED: System previously crashed with the following message:
%PLATFORM-1-CRASHED: Cisco IOS Software, C3750E Software (C3750E-UNIVERSALK9-M), Version 15.2(4)E9, RELEASE SOFTWARE (fc2)
%PLATFORM-1-CRASHED: Technical Support: http://www.cisco.com/techsupport
%PLATFORM-1-CRASHED: Copyright (c) 1986-2019 by Cisco Systems, Inc.
%PLATFORM-1-CRASHED: Compiled Mon 23-Sep-19 06:49 by prod_rel_team
%PLATFORM-1-CRASHED:
%PLATFORM-1-CRASHED: Debug Exception (Could be NULL pointer dereference) Exception (0x2000)!
%PLATFORM-1-CRASHED:
%PLATFORM-1-CRASHED: SRR0 = 0x02DA4AC8 SRR1 = 0x00029230 SRR2 = 0x03252EB0 SRR3 = 0x00029230
%PLATFORM-1-CRASHED: ESR = 0x00000000 DEAR = 0x00000000 TSR = 0x84000000 DBSR = 0x10000000
%PLATFORM-1-CRASHED:
%PLATFORM-1-CRASHED: CPU Register Context:
%PLATFORM-1-CRASHED: Vector = 0x00002000 PC = 0x03252EB0 MSR = 0x00029230 CR = 0x30099053
%PLATFORM-1-CRASHED: LR = 0x03252E4C CTR = 0x01EAF700 XER = 0xC0000000
%PLATFORM-1-CRASHED: R0 = 0x03252E4C R1 = 0x067B3B90 R2 = 0x00000000 R3 = 0x083242D0
%PLATFORM-1-CRASHED: R4 = 0x00000000 R5 = 0x00000000 R6 = 0x067B3B60 R7 = 0x052C0000
%PLATFORM-1-CRASHED: R8 = 0x00029230 R9 = 0x00000000 R10 = 0x00008000 R11 = 0x083242CC
%PLATFORM-1-CRASHED: R12 = 0x30099059 R13 = 0x1B981A10 R14 = 0x026FD5E4 R15 = 0x00000000
%PLATFORM-1-CRASHED: R16 = 0x00000000 R17 = 0x00000000 R18 = 0x067B3C20 R19 = 0x03D99BAC
%PLATFORM-1-CRASHED: R20 = 0x04611BD8 R21 = 0x04611BF0 R22 = 0x052C0000 R23 = 0x052C0000
%PLATFORM-1-CRASHED: R24 = 0x05870000 R25 = 0x03D99E64 R26 = 0x00000006 R27 = 0xEF4321CD
%PLATFORM-1-CRASHED: R28 = 0x00000002 R29 = 0x00000000 R30 = 0x06EF6994 R31 = 0x00000000
%PLATFORM-1-CRASHED:
%PLATFORM-1-CRASHED: Stack trace:
%PLATFORM-1-CRASHED: PC = 0x03252EB0, SP = 0x067B3B90
%PLATFORM-1-CRASHED: Frame 00: SP = 0x067B3BA0 PC = 0x03252E4C
%PLATFORM-1-CRASHED: Frame 01: SP = 0x067B3BE0 PC = 0x026E2F5C
%PLATFORM-1-CRASHED: Frame 02: SP = 0x067B3C18 PC = 0x026E3B50
%PLATFORM-1-CRASHED: Frame 03: SP = 0x067B3C68 PC = 0x026FD708
%PLATFORM-1-CRASHED: Frame 04: SP = 0x067B3C70 PC = 0x032541A0
%PLATFORM-1-CRASHED: Frame 05: SP = 0x00000000 PC = 0x03250514
%PLATFORM-1-CRASHED:

[Leo Laohoo]

Crash log files and folders can be deleted.

[SHAIKN]

Hi Leo, thank you for the response.

what if the device still generates the CRASHED logs though we deleted ?

[Leo Laohoo]

Post the complete output to the following command: 

sh log on uptime detail

[SHAIKN]

--------------------------------------------------------------------------------
UPTIME SUMMARY INFORMATION
--------------------------------------------------------------------------------
First customer power on : 03/01/1993 10:20:20
Total uptime : 0 years 0 weeks 0 days 17 hours 5 minutes
Total downtime : 0 years 0 weeks 0 days 0 hours 0 minutes
Number of resets : 4
Number of slot changes : 0
Current reset reason : 0x0
Current reset timestamp : 12/07/2023 11:23:07
Current slot : 1
Current uptime : 0 years 0 weeks 0 days 0 hours 0 minutes
--------------------------------------------------------------------------------
Reset | |
Reason | Count |
--------------------------------------------------------------------------------
No historical data to display
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
UPTIME CONTINUOUS INFORMATION
--------------------------------------------------------------------------------
Time Stamp | Reset | Uptime
MM/DD/YYYY HH:MM:SS | Reason | years weeks days hours minutes
--------------------------------------------------------------------------------
03/01/1993 10:20:20 0x0 0 0 0 0 0
03/01/1993 10:20:20 0x0 0 0 0 0 5
03/01/1993 10:20:20 0x0 0 0 0 2 0
03/01/1993 10:20:20 0x0 0 0 0 15 0
--------------------------------------------------------------------------------

[Leo Laohoo]

Ok, nothing there. 

Can we see the output to the command "dir"?

[SHAIKN]

2 -rwx 3624 Jan 2 2006 10:01:40 +10:00 vlan.dat
3 -rwx 25553920 May 24 2021 03:32:17 +10:00 c3750e-universalk9-mz.152-4.E9.bin
4 -rwx 3096 Dec 7 2023 11:28:13 +10:00 multiple-fs
470 drwx 4096 Jan 2 2006 10:00:11 +10:00 crashinfo
5 -rwx 30315 Dec 7 2023 11:28:12 +10:00 config.text
7 drwx 4096 May 24 2021 07:49:27 +10:00 c3750e-universalk9-mz.150-1.SE3
472 -rwx 6589 Dec 7 2023 11:28:12 +10:00 private-config.text

119144448 bytes total (86298624 bytes free)

[Leo Laohoo]

Post the output to the command "dir flash:crashinfo".

[SHAIKN]

Directory of flash:/crashinfo/

471 -rwx 1492 Jan 2 2006 10:00:11 +10:00 crashinfo_1

119144448 bytes total (86298624 bytes free)

[Leo Laohoo]

The actual date of when the switch crashed is not clear, however, the final IOS version released for 3750X is 15.2(4)E10.

[SHAIKN]

if we plan for upgrade, what level of safety we expect ? what if something goes wrong? 
and yeah, we all know this model already reached EOL.. 

[Leo Laohoo]

All bets are off. 

Nobody knows the network more than you do. 

Read the Release Notes and make the judgement from there.