What is the reason reload of Cisco Catalyst 6500?

[mickolay_net]

Cisco WS-C6506-E:

- VS-SUP2T-10G

- VS-F6K-PFC4
- VS-F6K-MSFC5

- 3xWS-X6148A-GE-TX

s2t54-adventerprisek9-mz.SPA.151-2.SY1.bin

Switch reload repeatedly:

Last reload reason: address error at PC 0x6818290, address 0x6818290

What is the reason of this reload?

[nagasheshu2010]

Hi Mick,

Please check the below link which might help.

https://supportforums.cisco.com/discussion/11579536/2911-reboot-reason

Sheshu.

[Mark Malone]

if its reloading continuously you could change the software you could of hit a bug it will rule out a whether its a hardware error , if its a hardware crash you will need TAC 

Did you get a crash file in flash when it failed in any of the flash partitions , that will contain the most information

[mickolay_net]

Thanks.

This problem was in production's switch and I don't have enough time for troubleshoting, I rapidly return sup-32. Now that sup-2t works propely in lab's switch and I  afraid to return her in production.

I have some problem with crash file:

04/11/2016 13:25:34.061: nvlog_crash_hook:System crashed on slot 5. Check value of Rommon variable CRASHINFO

The last crashinfo failed to be written.
Please verify the exception crashinfo configuration
the filesytem devices, and the free space on the
filesystem devices.
Using crashinfo_FAILED.

%Error opening bootdisk:crashinfo_FAILED (File not found)

When reload:

TEXT_START : 0x04100144
DATA_START : 0x0C000000File bootdisk:crashinfo_20160411-145933-BLR open failed (-1): Directory entries are corrupted, please format the disk
File bootdisk:crashinfo_20160411-145933-BLR open failed (-1): Directory entries are corrupted, please format the disk
File disk0:crashinfo_20160411-145933-BLR Device Error :No such device
File bootdisk:crashinfo_20160411-145933-BLR open failed (-1): Directory entries are corrupted, please format the disk
File disk0:crashinfo_20160411-145933-BLR Device Error :No such device

*** System received a SegV exception ***
signal= 0xb, code= 0x1400, context= 0xe09180c
PC = 0x6818290, Vector = 0x1400, SP = 0x1a9e64b8

[Mark Malone]

so you have 2 SUP2Ts and 1 went so you replaced it with SUP32 and it works fine now , if its prod I wouldn't touch it until you get a proper maintenance window to check, whatever testing needs to be done its going to be service effect

regarding that crash errors in last post see this below , one the internal Cisco guys made a post against it before what to try for that exact log

https://supportforums.cisco.com/discussion/10960031/switch-error-nvlogcrashhooksystem-crashed-slot-7-check

[mickolay_net]

Thanks.

I have quastion for you, if it possible. May be the reason of fail my SUP2T is chassis. What principle differences between hardware connections in chassis SUP2T and SUP32. What hardware of chassis not use when I install SUP32. And what is using with SUP2T.

[Mark Malone]

sorry I cant answer that exactly , TAC LAN architecture team probably could , I know the 2T is a much more advanced card than the 32 it should also work fine in a 6506-E though , could be just a bad card or triggered a parity bug

maybe is you have a quick look through the data sheets in comparison to your setup it might give you something

http://www.cisco.com/c/en/us/products/collateral/interfaces-modules/catalyst-6500-series-supervisor-engine-2t/data_sheet_c78-648214.html

http://www.cisco.com/c/en/us/products/collateral/interfaces-modules/catalyst-6500-supervisor-engine-32/product_data_sheet0900aecd801c5cab.html

[mickolay_net]

Ok. Thank you for your time.

[mickolay_net]

Hi, Sheshu.

Thanks for your answer.

But I think, that there is big differences between architecture of cisco 2900 and Catalyst 6500. And that post does not have correct answer.

I have two identic switches (with same IOS and sup) and one of them repeatedly reload! But with old sup-32 in this switch I have no problem!