CCIE Pilot

I have a customer that is complaining a lot of CRC and input errors on the interface.
This has been diagnosed with the help of Cisco's Output Interpreter.

R1#sh int s0/0/0
Serial0/0/0 is up, line protocol is up
 Hardware is GT96K Serial
 Description: R1
 MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,
 reliability 255/255, txload 39/255, rxload 38/255
 Encapsulation FRAME-RELAY IETF, loopback not set
 Keepalive set (10 sec)
 Carrier delay is 15 sec
 LMI enq sent  1146, LMI stat recvd 1146, LMI upd recvd 0, DTE LMI up
 LMI enq recvd 0, LMI stat sent  0, LMI upd sent  0
 LMI DLCI 1023  LMI type is CISCO  frame relay DTE
 FR SVC disabled, LAPF state down
 Broadcast queue 0/64, broadcasts sent/dropped 603/0, interface broadcasts 412
 Last input 00:00:00, output 00:00:00, output hang never
 Last clearing of "show interface" counters 03:10:56
 Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 751448
 Queueing strategy: weighted fair
 Output queue: 63/1000/64/751448 (size/max total/threshold/drops)
 Conversations  1/3/256 (active/max active/max total)
 Reserved Conversations 0/0 (allocated/max allocated)
 Available Bandwidth 1158 kilobits/sec
 5 minute input rate 235000 bits/sec, 22 packets/sec
 5 minute output rate 237000 bits/sec, 21 packets/sec
 34006 packets input, 39923277 bytes, 0 no buffer
 Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
 4 input errors, 4 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
 38081 packets output, 42136153 bytes, 0 underruns
 0 output errors, 0 collisions, 0 interface resets
 0 output buffer failures, 0 output buffers swapped out
 0 carrier transitions
 DCD=up  DSR=up  DTR=up  RTS=up  CTS=up
R1#

If you paste this on the CISCO OUTPUT Interpreter you would get the following:

SHOW INTERFACE SERIAL NOTIFICATIONS (if any)

Interface Serial0/0/0 (up/up)
  WARNING: The counters for this interface have not been cleared for 3 hours 10
  minutes 56 seconds.
  TRY THIS: Use the 'clear counters Serial0/0/0' command to ensure current information
  is being displayed. This will assist when troubleshooting serial interface issues.

  WARNING: This interface has a high number of output drops.
  The input rate to this interface has exceeded the bandwidth available on the
  serial link.
  TRY THIS:
  1. Minimize periodic broadcast traffic like routing and Service Advertising
     Protocol (SAP) updates (if applicable) by using access lists or by other
     means.
  2. Turn off fast switching for heavily used protocols. For example, turn off
     IP fast switching by using the 'no ip route-cache' interface configuration
     command.
  3. Implement priority queuing on slower serial links.
  4. Submit the output from 'show buffers' to Output Interpreter to determine
     if buffers need to be tuned.
  REFERENCE: For more information see: Troubleshooting Output Drops

  WARNING: This interface has received a high number (0.01176% of input packets)
  of packets with incorrect CRCs (corrupted data).
  Problems that may cause this symptom include:
  a. Noisy serial line
  b. Serial cable is too long or cable from the CSU/DSU to the router is not
     shielded
  c. SCTE mode is not enabled on the DSU
  d. The CSU line clock is incorrectly configured
  e. A Ones density problem on the link (incorrect framing or coding
     specification), exists
  f. Verify the queuing strategies are the same on both ends of the link.
  TRY THIS:
  1. Ensure that the line is clean enough for transmission requirements. Shield
     the cable if necessary.
  2. Make sure the cable is within the recommended length (no more than 50 feet
     [15.24 meters], or 25 feet [7.62 meters] for the link).
  3. Ensure that all devices are properly configured for a common line clock.
     Set serial clock transmit external (SCTE) on the local and remote DSU. If
     you are attempting serial connections at speeds greater than 64 kbps with
     a CSU/DSU that does not support (SCTE), you might have to invert the
     transmit clock on the router. Inverting the transmit clock compensates
     for phase-shifts between the data and clock signals.
  4. Make certain that the local and remote CSU/DSU are configured for the
     same framing and coding scheme as that used by the leased-line or other
     carrier service (for example, ESF/B8ZS).
  5. Contact your leased-line or other carrier service and have them perform
     integrity tests on the line.

REFERENCE: For more information on Serial Lines, see:
  Troubleshooting Serial Line Problems
  Configuring Serial Interfaces
  Troubleshooting Serial Lines
  Loopback Tests for T1/56K Lines

REFERENCE: For more information on Frame-Relay, see:
  Frame Relay
  Configuring Frame Relay
  Configuring and Troubleshooting Frame Relay
  Configuring and Troubleshooting Frame Relay Broadcase Queue
  Troubleshooting Frame Relay Networks