05-11-2017 06:51 PM
Hello my chassis have a error logging about L3 CACHE ERROR,is my hardware wrong and need RMA?
LC/0/2/CPU0:Apr 22 06:49:32.597 : p40x0mc[75]: ====== L3 CACHE ERROR #1 ======
LC/0/2/CPU0:Apr 22 06:49:32.648 : p40x0mc[75]: CPC Registers: OFF CPC1 CPC2
LC/0/2/CPU0:Apr 22 06:49:32.701 : p40x0mc[75]: CPCERRDET* e40 0x00000020 0x00000000
LC/0/2/CPU0:Apr 22 06:49:32.754 : p40x0mc[75]: CPCCAPTECC e28 0x2e00000b 0x00000000
LC/0/2/CPU0:Apr 22 06:49:32.807 : p40x0mc[75]: CPCERRINTEN e48 0x000000ec 0x000000ec
LC/0/2/CPU0:Apr 22 06:49:32.860 : p40x0mc[75]: CPCERRATTR e4c 0x7082033d 0x00000000
LC/0/2/CPU0:Apr 22 06:49:32.913 : p40x0mc[75]: CPCERRADDR e54 0x17edd580 0x00000000
LC/0/2/CPU0:Apr 22 06:49:32.966 : p40x0mc[75]: CPCERRCTL e58 0x0010a200 0x00100006
LC/0/2/CPU0:Apr 22 06:49:33.020 : p40x0mc[75]: CPCCSR0 000 0xc0000000 0xc0000000
LC/0/2/CPU0:Apr 22 06:49:33.073 : p40x0mc[75]: CPCCFG0 008 0x50b7c010 0x50b7c010
LC/0/2/CPU0:Apr 22 06:49:33.126 : p40x0mc[75]: CPCHDBCR0 f00 0x415e5000 0x415e5000
LC/0/2/CPU0:Apr 22 06:49:33.179 : p40x0mc[75]: CPCCAPTDTLO e24 0x101b8000 0x00000000
LC/0/2/CPU0:Apr 22 06:49:33.232 : p40x0mc[75]: CPCPIR0x0 200 0xffffffff 0xffffffff
LC/0/2/CPU0:Apr 22 06:49:33.285 : p40x0mc[75]: CPCPAR0x0 208 0x000003fb 0x000003fb
LC/0/2/CPU0:Apr 22 06:49:33.338 : p40x0mc[75]: CPCPWR0x0 20c 0xffffffff 0xffffffff
LC/0/2/CPU0:Apr 22 06:49:33.725 : p40x0mc[75]: EISR0: 0x00000010 [CPC1]
LC/0/2/CPU0:Apr 22 06:49:33.780 : p40x0mc[75]: CPC1 CPCERRDET : 0x00000020 [TSBECCERR] Count = 1
LC/0/2/CPU0:Apr 22 06:49:33.781 : p40x0mc[75]: ====== L3 CACHE ERROR #2 ======
LC/0/2/CPU0:Apr 22 06:49:33.782 : p40x0mc[75]: CPC Registers: OFF CPC1 CPC2
LC/0/2/CPU0:Apr 22 06:49:33.783 : p40x0mc[75]: CPCERRDET* e40 0x00000020 0x00000000
LC/0/2/CPU0:Apr 22 06:49:33.785 : p40x0mc[75]: CPCCAPTECC e28 0x2e00000b 0x00000000
LC/0/2/CPU0:Apr 22 06:49:33.786 : p40x0mc[75]: CPCERRINTEN e48 0x000000ec 0x000000ec
LC/0/2/CPU0:Apr 22 06:49:33.787 : p40x0mc[75]: CPCERRATTR e4c 0x7082023d 0x00000000
LC/0/2/CPU0:Apr 22 06:49:33.840 : p40x0mc[75]: CPCERRADDR e54 0x17ec5590 0x00000000
LC/0/2/CPU0:Apr 22 06:49:33.893 : p40x0mc[75]: CPCERRCTL e58 0x0010a000 0x00100000
LC/0/2/CPU0:Apr 22 06:49:33.946 : p40x0mc[75]: CPCCSR0 000 0xc0000000 0xc0000000
LC/0/2/CPU0:Apr 22 06:49:33.999 : p40x0mc[75]: CPCCFG0 008 0x50b7c010 0x50b7c010
LC/0/2/CPU0:Apr 22 06:49:34.052 : p40x0mc[75]: CPCHDBCR0 f00 0x415e5000 0x415e5000
LC/0/2/CPU0:Apr 22 06:49:34.106 : p40x0mc[75]: CPCCAPTDTLO e24 0x101b8000 0x00000000
LC/0/2/CPU0:Apr 22 06:49:34.159 : p40x0mc[75]: CPCPIR0x0 200 0xffffffff 0xffffffff
LC/0/2/CPU0:Apr 22 06:49:34.212 : p40x0mc[75]: CPCPAR0x0 208 0x000003fb 0x000003fb
LC/0/2/CPU0:Apr 22 06:49:34.265 : p40x0mc[75]: CPCPWR0x0 20c 0xffffffff 0xffffffff
LC/0/2/CPU0:Apr 22 06:49:34.651 : p40x0mc[75]: EISR0: 0x00000010 [CPC1]
LC/0/2/CPU0:Apr 22 06:49:34.652 : p40x0mc[75]: CPC1 CPCERRDET : 0x00000020 [TSBECCERR] Count = 2
LC/0/2/CPU0:Apr 22 06:49:34.686 : p40x0mc[75]: ====== L3 CACHE ERROR #3 ======
LC/0/2/CPU0:Apr 22 06:49:34.737 : p40x0mc[75]: CPC Registers: OFF CPC1 CPC2
LC/0/2/CPU0:Apr 22 06:49:34.790 : p40x0mc[75]: CPCERRDET* e40 0x00000020 0x00000000
LC/0/2/CPU0:Apr 22 06:49:34.843 : p40x0mc[75]: CPCCAPTECC e28 0x2e00000b 0x00000000
LC/0/2/CPU0:Apr 22 06:49:34.896 : p40x0mc[75]: CPCERRINTEN e48 0x000000ec 0x000000ec
LC/0/2/CPU0:Apr 22 06:49:34.949 : p40x0mc[75]: CPCERRATTR e4c 0x5082023d 0x00000000
LC/0/2/CPU0:Apr 22 06:49:35.003 : p40x0mc[75]: CPCERRADDR e54 0x00bc55a8 0x00000000
LC/0/2/CPU0:Apr 22 06:49:35.056 : p40x0mc[75]: CPCERRCTL e58 0x00105400 0x00100000
LC/0/2/CPU0:Apr 22 06:49:35.109 : p40x0mc[75]: CPCCSR0 000 0xc0000000 0xc0000000
LC/0/2/CPU0:Apr 22 06:49:35.162 : p40x0mc[75]: CPCCFG0 008 0x50b7c010 0x50b7c010
LC/0/2/CPU0:Apr 22 06:49:35.215 : p40x0mc[75]: CPCHDBCR0 f00 0x415e5000 0x415e5000
LC/0/2/CPU0:Apr 22 06:49:35.268 : p40x0mc[75]: CPCCAPTDTLO e24 0x101b8000 0x00000000
LC/0/2/CPU0:Apr 22 06:49:35.321 : p40x0mc[75]: CPCPIR0x0 200 0xffffffff 0xffffffff
LC/0/2/CPU0:Apr 22 06:49:35.374 : p40x0mc[75]: CPCPAR0x0 208 0x000003fb 0x000003fb
LC/0/2/CPU0:Apr 22 06:49:35.428 : p40x0mc[75]: CPCPWR0x0 20c 0xffffffff 0xffffffff
LC/0/2/CPU0:Apr 22 06:49:35.814 : p40x0mc[75]: EISR0: 0x00000010 [CPC1]
LC/0/2/CPU0:Apr 22 06:49:35.869 : p40x0mc[75]: CPC1 CPCERRDET : 0x00000020 [TSBECCERR] Count = 3
thanks
Solved! Go to Solution.
05-12-2017 12:08 AM
Hi,
are there any forwarding issues on this LC?
You could try to reload the LC and hope that the messages disappear.
What IOS-XR version are you running?
There is a fixed bug with similar messages.
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuy19768/?referring_site=bugquickviewclick
05-12-2017 12:08 AM
Hi,
are there any forwarding issues on this LC?
You could try to reload the LC and hope that the messages disappear.
What IOS-XR version are you running?
There is a fixed bug with similar messages.
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuy19768/?referring_site=bugquickviewclick
06-19-2018 10:42 AM
This is the TAC response for this specific reported problem:
Based on the case notes, I understand that your A9K-MOD80-TR in LC6 reported several L3 Cache error.
Problem Description
=====================
- Version : 4.2.3
- A9K-MOD80-TR card in LC6 reported L3 Cache error several times
Current status : : not occur anymore
Business Impact
=====================
- Low; no known service impact
Problem Analysis
=====================
- Reviewing the logs attached to the case note, I see that LC6 reported L3 Cache error several times on Jun/16 and no longer persist.
LC/0/6/CPU0:Jun 16 15:58:02.213 CHILE: p40x0mc[74]: ====== L3 CACHE ERROR #1 ======
LC/0/6/CPU0:Jun 16 15:58:02.263 CHILE: p40x0mc[74]: CPC Registers: OFF CPC1 CPC2
LC/0/6/CPU0:Jun 16 15:58:02.316 CHILE: p40x0mc[74]: CPCERRDET* e40 0x00000004 0x00000000
…
These indicate that LC6 experienced single bit soft parity error in L3 cache memory.
With fix of CSCuf38249 which you already have in your router, the processor is designed to recover from SBE automatically and enhanced to report these kind of errors.
Since this stopped on Jun 16, this looks like a transient soft parity issue and I would recommend to monitor for a few more days.
If you see this message again on the same LC, I would recommend to try reseating the LC.
Action plan
=====================
- Monitoring
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: