08-01-2013 09:04 PM - last edited on 03-25-2019 04:25 PM by ciscomoderator
Supervisor card restart itself on Catalyst 6509E please help me find root cause.Below are information, If you need more please let me know thanks.
Product Number: WS-C6509E-S32-GE
Description: Cisco Catalyst 6509E, WS-SUP32-GE-3B, Fan Tray (req. P/S)
here is last log before forced restart.
xxx#sh tech
Jul 26 15:31:24.788 UTC: %CPU_MONITOR-3-PEER_EXCEPTION: CPU_MONITOR peer has failed due to exception , reset by [5/0]
%Software-forced reload
17:31:24 CEST Fri Jul 26 2013: Breakpoint exception, CPU signal 23, PC = 0x420035B0
xxx#sh ver
Cisco IOS Software, s3223_rp Software (s3223_rp-IPSERVICESK9_WAN-M), Version 12.2(33)SXH1, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2008 by Cisco Systems, Inc.
Compiled Wed 16-Jan-08 19:09 by prod_rel_team
ROM: System Bootstrap, Version 12.2(17r)SX3, RELEASE SOFTWARE (fc1)
xxx uptime is 4 days, 13 hours, 1 minute
Uptime for this control processor is 4 days, 13 hours, 1 minute
Time since xxx switched to active is 4 days, 13 hours, 0 minutes
System returned to ROM by s/w reset at 14:51:34 BKK Tue Apr 14 2009 (SP by processor memory parity error at PC 0x40AC7378, address 0x0)
System restarted at 17:34:12 CEST Fri Jul 26 2013
System image file is "bootdisk:s3223-ipservicesk9_wan-mz.122-33.SXH1.bin"
08-01-2013 10:51 PM
Hi,
Kindly provide me the below requested information for me to assist you further.
1) Show log from the device
2) Crashinfo file
3) Show module
Thanks & Regards,
Vignesh R P
08-02-2013 12:20 AM
08-02-2013 12:58 AM
Hi,
Thanks a lot for the outputs. Also kindly do provide the output of dir from the device.
T & R,
Vignesh R P
08-02-2013 01:03 AM
Hi,
Kindly check if there is a crashinfo file in the location sup-bootdisk: . If yes, then kindly do provide that crashinfo file too.
T & R,
Vignesh R P
08-01-2013 10:52 PM
System returned to ROM by s/w reset at 14:51:34 BKK Tue Apr 14 2009 (SP by processor memory parity error at PC 0x40AC7378, address 0x0)
Software-caused crash.
08-01-2013 10:56 PM
Hi Leo,
The one that you are referring to has happened on the 14th of April 2009. I believe help is required to understand the reason behind the crash that took place on 26th July, 2013.
T & R,
Vignesh R P
08-01-2013 10:59 PM
LOL!
Good point.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide