We recently installed a full ds3 into our router. I had several issues with getting it to work. We keep getting the following errors when I do a sh serial and controller
Internet02#sh controller t3 2/0
T3 2/0 is up.
Applique type is Subrate T3
No alarms detected.
MDL transmission is disabled
FEAC code received: No code is being received
Framing is C-BIT Parity, Line Code is B3ZS, Clock Source is Line
Data in current interval (370 seconds elapsed):
65535 Line Code Violations, 65535 P-bit Coding Violation
65535 C-bit Coding Violation, 0 P-bit Err Secs
0 P-bit Severely Err Secs, 0 Severely Err Framing Secs
370 Unavailable Secs, 0 Line Errored Secs
0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
Output queue: 0/40 (size/max)
30 second input rate 17000 bits/sec, 16 packets/sec
30 second output rate 12000 bits/sec, 16 packets/sec
20635968 packets input, 3398537602 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
34843245 input errors, 34843237 CRC, 2222728 frame, 5242 overrun, 0 ignored
, 2735365 abort
I called verizon numorous times and the first time they found a problem with a CO cwitch in the path. 2 weeks later same issue happened and they saw erros on the line but the remote router could loop to the optera switch in my building fine. Now if I set my end to loop back they saw packet loss. So we started to think cabling/hardware on my end. Our DS3 is conencted via coax. So I took a coupler and conencted te Tx to the Rx. Did a extended ping of 50000 and with the following data patterns 0x1111 / 2222 .......
100 % successful.
So we looped the cable on the CO switch in our building and they were able to run clean. When we connected everything back it worked fine. The issue was gone.
Well the problem came back again and verizon sent a tech out to look at their switch in our building. No issue found but the next morning again it was working fine. This was last week and today the problem came back. we are getting slow speeds int surf. About 15-30 % packet loss on the line and we are only sending about 2 megs of traffic on it. So we are not maxing it out.
Has anyone ever seen this or had this problem because the carrier keeps saying its nothing and this problem keeps coming back.
