07-11-2012 08:34 PM - edited 03-04-2019 04:56 PM
I have a multilink set up with 8T1's. Have been having chronic issues with one of the controllers taking errors (also causing the serial interface to take errors). All intrusive tests to the internal CSU have been clean. I changed the LBO (cablelength) on the controller to short 220ft being that it's not that far from the demarcation point. now the controller is perfectly clean but I am still incrementing errors on the serial interface link =
T1 0/1/1 is up.
Applique type is Channelized T1
Cablelength is short 220
No alarms detected.
alarm-trigger is not set
Soaking time: 3, Clearance time: 10
AIS State:Clear LOS State:Clear LOF State:Clear
Version info FPGA Rev: 08121917, FPGA Type: PRK4
Framing is ESF, FDL is ansi & att, Line Code is B8ZS, Clock Source is Line.
CRC Threshold is 320. Reported from firmware is 320.
Serial0/1/1:0 is up, line protocol is up
Hardware is DSX1
Description:
MTU 1700 bytes, BW 1536 Kbit/sec, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 2/255
Encapsulation PPP, LCP Open, multilink Open
Link is a member of Multilink bundle Multilink1, crc 16, 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 18:15:22
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 16000 bits/sec, 17 packets/sec
5 minute output rate 3000 bits/sec, 3 packets/sec
1193949 packets input, 150331723 bytes, 0 no buffer
Received 0 broadcasts, 248 runts, 0 giants, 0 throttles
250 input errors, 250 CRC, 0 frame, 0 overrun, 0 ignored, 2 abort
185360 packets output, 26076387 bytes, 0 underruns
0 output errors, 0 collisions, 72 interface resets
630 unknown protocol drops
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
why would the link be getting these input errors and all of the unknown protocol drops?
07-12-2012 01:20 AM
you can do loopback in your modem and verifiy if errors still exists or not ( with this method you will verifiy if the problem is locally or cames from remote site)
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide