6509, line card error

[faghouri83]

Hi Everyone,

I have a switch where one of the line cards went down but is now back up. I just want to know what might have caused this. Thanks for your help!

output:

Feb 18 04:45:34.012: %SYS-5-RESTART: System restarted --
Cisco Internetwork Operating System Software
IOS (tm) s222_rp Software (s222_rp-IPSERVICESK9-M), Version 12.2(18)SXF7, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2006 by cisco Systems, Inc.
Compiled Thu 23-Nov-06 01:42 by kellythw
Feb 18 04:45:34.344: %SNMP-5-COLDSTART: SNMP agent on host WC1_C6000S is undergoing a cold start
Feb 18 04:45:34.352: %SYS-6-BOOTTIME: Time taken to reboot after reload = 62901774 seconds
Feb 18 04:46:13.268: %SNMP-5-MODULETRAP: Module 5 [Up] Trap
Feb 18 04:46:32.252: %SNMP-5-MODULETRAP: Module 1 [Up] Trap
Feb 18 04:46:38.300: %SNMP-5-MODULETRAP: Module 2 [Up] Trap
Feb 18 04:46:48.936: %SNMP-5-MODULETRAP: Module 3 [Up] Trap
Feb 18 04:46:57.972: %SNMP-5-MODULETRAP: Module 7 [Up] Trap
Feb 18 04:46:58.312: %CPU_MONITOR-3-PEER_EXCEPTION: CPU_MONITOR peer has failed due to exception , r
eset by [1/1]

%Software-forced reload

Breakpoint exception, CPU signal 23, PC = 0x41CBCA64

-Traceback= 41CBCA64 41CBA9F0 41A8B4B4 41A8B4E0 41971B40 419AE30C 419A46DC 419A4734 407442BC 40744FA
4 418CE174 418CDF90 41A2CBD4 41A29AF8 41A29D14 41CAF1CC
$0 : 00000000, AT : 1E020000, v0 : 43CF0000, v1 : 00000030
a0 : 45036CD8, a1 : 43D1EB0C, a2 : 00000005, a3 : FFFFFFFC
t0 : 00000012, t1 : 00000000, t2 : 00000162, t3 : 00000002
t4 : 43D1EAB8, t5 : 00000000, t6 : 00004342, t7 : 43D1EAB0
s0 : 00000000, s1 : 42EE0000, s2 : 442EABD8, s3 : 0E4BF948
s4 : 44EC9A18, s5 : 44DF2EE8, s6 : 00000040, s7 : 436D0000
t8 : 43D1EA94, t9 : 00000000, k0 : 00000000, k1 : 00000000
gp : 42F357C0, sp : 43D1EB40, s8 : 00000000, ra : 41CBA9F0
EPC  : 41CBCA64, ErrorEPC : 00010000, SREG     : 3401F103
MDLO : 00000044, MDHI     : 00000110, BadVaddr : B7DCDFCE
CacheErr : 80BFFFFB, DErrAddr0 : 1E02000C, DErrAddr1 : 02F3FB78
Cause 00000024 (Code 0x9): Breakpoint exception

[Giuseppe Larosa]

Hello Faghouri83,

have you got two supervisors in the chassis?

it looks that one supervisor crashed

Feb 18 04:46:58.312: %CPU_MONITOR-3-PEER_EXCEPTION: CPU_MONITOR peer has failed due to exception , r
eset by [1/1]

this message should mean the other supervisor detected the reload of the other supervisor.

%Software-forced reload

Breakpoint exception, CPU signal 23, PC = 0x41CBCA64

Hope  to help

Giuseppe

[sachinraja]

Hi

software forced crash are more due to IOS bugs, and can also be caused due to some hardware problems... what ios version are you using ? Did you go through the release notes to see if there are any bugs related to this reloads ? you can probably try upgrading the device with the new IOS.. software crash can also be due to watchdog timeouts, memory allocation (low) , corrupt software image, or other faults. can u send us the "show stack" output ? We can probably try finding this.. is this device on service contract ?

Regards

Raj

[faghouri83]

image is: s222-ipservicesk9-mz.122-18.SXF7.bin

Ive not checked the release notes, but basically the lights turned amber and to put it back to normal, the card was taken out and then reinserted to bring it back up if that helps.

[sachinraja · Accepted solution]

oh.. so you mean SUP restarted since one of your linecards went faulty ? and you reseated the line card ?

[faghouri83]

Basically the card went down and to get it back up and running, it was re-seated.

[sachinraja]

As said before software forced crash can happen through IOS bugs.. I was going through the bug list for the IOS given. You are hitting the following bug:

CSCed51952 Bug Details

Hotswapping linecards while configuring i/f can crash the box

Symptoms: A Cisco router may crash when you perform and online insertion removal (OIR) of a line card. Conditions: This symptom is observed when an interface on the line card is being configured through the CLI while the OIR of the line card removes the interface. Workaround: There is no workaround.

You can try upgrading the IOS to latest, and see if this issue solves.

Hope this helps.. all the best

Raj

[faghouri83]

Ok ill try that

Thanks for your help guys!