Core issue
The actual messages can look similar to this:
%SYS-3-SYS_LCPERR3:Module 4: Pinnacle #0 : Port #2, Frames with CRC errors on RBus (PI_PN_S_RBUS_ERR_CNT_REG - 0x159) = 255:
%SYS-3-SYS_LCPERR3:Module 8: Pinnacle #0, Frames with Bad Packet CRC Error (PI_CI_S_PKTCRC_ERR - 0xC7) = 1087:
%SYS-3-SYS_LCPERR3:Module 1: Bus Asic #0 out of sync error: Module needs troubleshooting or TAC assistance
This message indicates that the module has detected frames with a bad packet cyclic redundancy check (CRC) received by the bus ASIC from the DBus. The first [dec] is the module number. The second [dec] is the ASIC number that reports the error. The third [dec] is the error count.
Resolution
In order to run a complete diagnostic test on the module numbers mentioned in the error message and check for any problems, complete these steps:
Issue the set test diaglevel complete command in the global configuration mode to set the diagnostics level to complete.
Issue the reset [module#] command in order to soft-reset the module. After the module is up again, capture the output of the show module command and the show test command in order to display the errors reported from the diagnostic tests.
Physically pull out and reseat the module firmly in the chassis in order to hard-reset the module. After the module is up again, capture the output of the show module command and the show test command.
If the error persists, then use the TAC Service Request Tool in order to open a case with Cisco Technical Support.
