Is this a Cat 6K? If so, can you try to reseat module 1? If this does not fix the problem, it could be hardware related. I would suggest a TAC case.
https://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-series-switches/41265-186-ErrormsgIOS-41265.html#module
%CONST_DIAG-SP-4-ERROR_COUNTER_WARNING: Module 7 Error counter exceeds threshold, system operation continue
Problem
The switch reports this error message:
%CONST_DIAG-SP-4-ERROR_COUNTER_WARNING: Module 7 Error counter
exceeds threshold, system operation continue.
%CONST_DIAG-SP-4-ERROR_COUNTER_DATA: ID:42 IN:0 PO:255 RE:200 RM:255 DV:2 EG:2 CF:10 TF:117
Description
Check the diagnostic results:
TestErrorCounterMonitor ---------> .
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 33658
Last test execution time ----> Apr 15 2012 11:17:46
First test failure time -----> Apr 03 2012 20:11:36
Last test failure time ------> Apr 08 2012 19:24:47
Last test pass time ---------> Apr 15 2012 11:17:46
Total failure count ---------> 5
Consecutive failure count ---> 0
Error Records ---------------> n/a
The TestErrorCounterMonitor monitors the errors/interrupts on each module in the system by periodically polling for the error counters maintained in the line card.
This error message pops up when an ASIC on the line card receives packets with bad CRC. The issue can be local to this module or can be triggered by some other faulty module in the chassis. This can also be due to frames with bad CRC received by pinnacle asic from the DBUS. That is, the error messages imply that bad packets are being received across the bus on module 7.
One of the reasons for the error messages to occur is the inability of the module to properly communicate with the backplane of the chassis due to mis-seating of the module. The problem is with the line card (mis-seated module), supervisor or the Data Bus. However, it is not possible to say what component is corrupting the data and causing a bad CRC.
Workaround
-
First perform a re-seat of module 7 and make sure the screws are tightened well. Also, before the reseat, set the diagnostics to complete with the diagnostic bootup level complete command.
-
Once the re-seat is done, full diagnostics will run on the module. Then, you can confirm that there are no hardware issues on the module 7.
