Input and CRC errors but no controller errors?

Serial0/1/1:0 is up, line protocol is up Hardware is GT96K Serial Description: Connection to TP Provider MTU 1500 bytes, BW 1984 Kbit/sec, DLY 20000 usec,reliability 255/255, txload 122/255, rxload 118/255 Encapsulation PPP, LCP Open, multilink Open Link is a member of Multilink bundle Multilink1, loopback not set Keepalive set (10 sec) Last input 00:00:00, output 00:00:00, output hang never Last clearing of "show interface" counters 1w0d Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: weighted fair [suspended, using FIFO] FIFO output queue 0/40, 0 drops 5 minute input rate 923000 bits/sec, 229 packets/sec 5 minute output rate 955000 bits/sec, 173 packets/sec 7324391 packets input, 3315314073 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 26446 input errors, 14140 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
But no errors are present on the controller... Total Data (last 24 hours) 0 Line Code Violations, 0 Path Code Violations, 0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins, 0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs Could this be a problem with the multi-link config?

rtr03>sh ppp multilink
Multilink1
Bundle name: xxxxxxxx
Remote Endpoint Discriminator: [4] xxxxxxxx
Local Endpoint Discriminator: [1] xxxxxxxx
Bundle up for 1w5d, total bandwidth 3968, load 1/255
Receive buffer limit 24000 bytes, frag timeout 1000 ms 0/0 fragments/bytes in reassembly list 20610 lost fragments, 3927978 reordered 15227/8902947 discarded fragments/bytes, 0 lost received 0x3D1F6D received sequence, 0xC032F9 sent sequence
Member links: 2 active, 0 inactive (max not set, min 1)
/1/0:0, since 1w5d
Se0/1/1:0, since 1w5d
No inactive multilink interfacesrtr03>

Tips:

20610 lost fragments, 3927978 reordered

15227/8902947 discarded fragments/bytes, 0 lost received

0x3D1F6D received sequence, 0xC032F9 sent sequence

as you can see there are 20610 lost fragments and 15227 discarded fragments and this is roughly similar to physical interface error counters

Received 0 broadcasts, 0 runts, 0 giants, 0 throttles

26446 input errors, 14140 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

Citation - This blog post does not reflect original content from the author. Rather it summarizes content that are relevant to the topic from different sources in the web. The sources might include any online discussion boards, forums, websites and others.