C6500 + SUP 720 reload - CPU Signal 23

[EURL_IPSENS]

Hi guys,

I've just got an unwanted Catalyst 6500 reboot.

Attached file is the crashinfo log.

Does someone is having any idea of what happened ? And how to fix it ?

Having a redundant Supervisor, would had avoid this issue ? It's a production system, would like to avoid any downtime...

Thanks

[Mark Malone]

where did you get the crash file , is there an SP crashfile in the supbootflash or supbootdisk too as below looks like the SP caused it RP to be reset though software crash so usually theres a crash file for that too

can you post the show version too

always good to have a standby sup in pace if the switch isn't in vss so there is some form of redundancy , all of our 65s have dual sups in sso state or vss at core layer with 2 sups a piece , all depends on budget too but your core should have redundancy just in case to avoid issues like this

CMD: 'show run' 12:33:11 WEST Fri May 19 2017
%C6K_PLATFORM-2-PEER_RESET: RP is being reset by the SP

[EURL_IPSENS]

The crashinfo is coming from supbootdisk:/, only have this file in this dir + boot image of course.

Original name : crashinfo_SP_20170605-194832-WEST

#show vers
Cisco IOS Software, s72033_rp Software (s72033_rp-ADVENTERPRISEK9_WAN-M), Version 12.2(33)SXJ10, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2015 by Cisco Systems, Inc.
Compiled Fri 14-Aug-15 08:58 by prod_rel_team

ROM: System Bootstrap, Version 12.2(17r)SX7, RELEASE SOFTWARE (fc1)

Cat6506E-1 uptime is 23 hours, 44 minutes
Uptime for this control processor is 23 hours, 43 minutes
Time since Cat6506E-1 switched to active is 23 hours, 42 minutes
System returned to ROM by s/w reset at 19:48:38 WEST Mon Jun 5 2017 (SP by bus error at PC 0x404396F8, address 0x51B14FF8)
System restarted at 19:52:37 WEST Mon Jun 5 2017
System image file is "sup-bootflash:s72033-adventerprisek9_wan-mz.122-33.SXJ10.bin"
Last reload reason: reload

This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email to
export@cisco.com.

cisco WS-C6506-E (R7000) processor (revision 1.1) with 983008K/65536K bytes of memory.
Processor board ID SAL1126T1KQ
SR71000 CPU at 600Mhz, Implementation 0x504, Rev 1.2, 512KB L2 Cache
Last reset from s/w reset
9 Virtual Ethernet interfaces
59 Gigabit Ethernet interfaces
10 Ten Gigabit Ethernet interfaces
1917K bytes of non-volatile configuration memory.
8192K bytes of packet buffer memory.

65536K bytes of Flash internal SIMM (Sector size 512K).
Configuration register is 0x2102

[Mark Malone]

This looks like it was software related , is this the first time its occurred ?

I ran the output you hit a software parity that's what I know so far , I would wait they can be a once off , the other option is to upgrade , you  will take a hit either way as system will reload , maybe add new software to the flash set the boot statement so if it at least crashes again and comes up it will come up with the new image

A parity error occurs when a bit is changed from its original value (0 or a 1) to the opposite value. This problem can occur as one of two different types of parity errors, soft parity errors or hard parity errors. 

Soft parity errors occur when the bit value is changed due to an external influence on the router. This means that something out side the router, caused the energy level representing the bit value to be changed. This type of problem is transient and will not reoccur.

Hard parity errors occur when the hardware itself causes the bit value to be changed due to hardware damage. This type of a problem will occur every time that information crosses that point in memory, and the parity error will occur again. 

The only way to differentiate between a soft parity error and a hard parity error is to monitor for a second occurrence. It is recommended that this monitoring take place over a period of a few days to a week. If the issue is a soft parity error there will be no reoccurrence, however in the event that a subsequent parity error occurs during the monitoring period a replacement should be requested. 
For details please refer to: http://www.cisco.com/en/US/products/hw/routers/ps341/products_tech_note09186a0080094793.shtml