[c-nsp] Cat 6500 Syslog Messages

Sukumar Subburayan sukumars at cisco.com
Mon Sep 4 20:38:33 EDT 2006


The error reported below is related to internal ASIC memory errors. 
If you continue to see the problem again you may want to open a TAC case 
and replace the card, and setup for a Failure Analysis.

The syslog level for this error message was bumped upto to Level-3 
(originally it was at Level-6) in recent code. That is probably why you 
started seeing this message when you upgraded the code.

sukumar



On Mon, 4 Sep 2006, William Chu wrote:

> Hi:
>
> My cat6500 had a bunch of these messages showing up earlier today, see
> below:
>
> Sep  4 01:53:22 2006 Sep 04 01:53:21 %SYS-3-SYS_LCPERR3:Module 4: RChip
> Port#3 Boc Payload Crc Error: Module requires attention - troubleshoot or
> contact TAC for assistance
>
> Sep  4 01:53:22 2006 Sep 04 01:53:21 %SYS-3-SYS_LCPERR3:Module 4: RChip
> Port#21 Boc Payload Crc Error: Module requires attention - troubleshoot or
> contact TAC for assistance
>
> Sep  4 01:53:22 2006 Sep 04 01:53:21 %SYS-3-SYS_LCPERR3:Module 4: RChip
> Port#39 Boc Payload Crc Error: Module requires attention - troubleshoot or
> contact TAC for assistance
>
> Sep  4 07:48:39 2006 Sep 04 07:48:38 %SYS-3-SYS_LCPERR3:Module 4: RChip
> Port#3 Boc Payload Crc Error: Module requires attention - troubleshoot or
> contact TAC for assistance
>
> Sep  4 07:48:39 2006 Sep 04 07:48:38 %SYS-3-SYS_LCPERR3:Module 4: RChip
> Port#21 Boc Payload Crc Error: Module requires attention - troubleshoot or
> contact TAC for assistance
>
> Sep  4 07:48:39 2006 Sep 04 07:48:38 %SYS-3-SYS_LCPERR3:Module 4: RChip
> Port#40 Boc Header Crc Error: Module requires attention - troubleshoot or
> contact TAC for assistance
>
> All messages came were tied to the same module (WS-X6548-RJ-45) in the 6500,
> and resetting the linecard cleared the problem.
>
> This module (a WS-X6548-RJ-45) had been running fine for a couple of years
> but the Cat OS was recently upgraded to 7.6(18) so I would like to know if
> anyone else had run into the same error messages.
>
> Thanks,
>
> William
>
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>


More information about the cisco-nsp mailing list