cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
344
Views
0
Helpful
3
Replies

two c6500 switches rebooted unexpectedly in 4 hours interval, and trunk ports down for 1.5 hours. While analyzing there is 0 bytes size of debug crashinfo files, so no root cause can be found. Is this known issue, or any bugs?

skoirala
Cisco Employee
Cisco Employee

two c6500 switches rebooted unexpectedly in 4 hours interval, and trunk ports down for 1.5 hours. While analyzing there is 0 bytes size of debug crashinfo files, so no root cause can be found. Is this known issue, or any bugs?

c6500switch#sh slavesup-bootflash:
-#- --length-- -----date/time------ path
1 80465924 Apr 14 2007 02:40:52 +00:00 s72033-ipservices_wan-mz.122-18.SXF8.bin
2 33554432 May 15 2008 03:36:40 +00:00 sea_log.dat
3 342747 May 6 2010 16:45:08 +00:00 crashinfo_20100506-164509-MDT
4 445005 Apr 30 2014 23:32:40 +00:00 crashinfo_20140430-233241-UTC
5 0 Apr 28 2016 23:29:02 +00:00 debuginfo_20160428-232903-UTC

397197312 bytes available (114827264 bytes used)

No root cause can be found because of 0 bytes size of data in this crash info files. The main concern is all trunk ports connected to these two c6500 switches were bouncing/flapping for one and half hours from neighbor devices, and this happened after reloaded the system. Any known bugs or known issue yet ? the code version is 15.0 experimental extended version supported to provider edge devices.

Appreciate in advance for any help.

3 Replies 3

Leo Laohoo
Hall of Fame
Hall of Fame

Post the complete output to the command "sh version" & "dir".

Ben Samayoa
Level 1
Level 1

Hi there,

I can see clearly you have crash info logs back to 2010 & 2014.

The system has been experiencing technical issues since then and the logs have been accumulating to the point of bootflash itself running out of space. Automatically the system when had ran out of space will crash and restart.

I recommend you to format the bootflash, but before that make sure you copy those old crash files into your pc, in order to find out how did it all start it. At simple inspection I see you IOS in very OLD. IT is most likely that it has a bug giving you hard time.

Search within Cisco Tools to see if your current IOS is affected by bugs.

regards,

Ben

Vinit Jain
Cisco Employee
Cisco Employee

Please attach the below logs:

- show diagnostic events

- show fabric channel-counters

- show fabric errors

 Regarding crashinfo, you might want to check the crashinfo file on both the RP and the SP. The cause of the crash can be either of them.

Regards

Vinit

Thanks
--Vinit