01-02-2008 08:42 AM - edited 03-03-2019 08:06 PM
I need assistance in figuring out what is going on with a Sprint DS3. I called Sprint and they said they had a problem, but now it's fixed. I noticed at first the interface was flapping, but now it's just down. I've inherited this so I'm not at all familiar with DS3. I'm needing some suggestions on what to try to get this thing back up or verify that the problem still with the carrier.
show controllers t3
T3 1/0 is down.
Applique type is Subrate T3
Transmitter is sending remote alarm.
Receiver has loss of frame.
MDL transmission is disabled
FEAC code received: No code is being received
Framing is C-BIT Parity, Line Code is B3ZS, Clock Source is Internal
Data in current interval (860 seconds elapsed):
65535 Line Code Violations, 40914 P-bit Coding Violation
41412 C-bit Coding Violation, 0 P-bit Err Secs
0 P-bit Severely Err Secs, 0 Severely Err Framing Secs
860 Unavailable Secs, 0 Line Errored Secs
0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
Total Data (last 31 15 minute intervals):
1966050 Line Code Violations, 242914 P-bit Coding Violation,
252595 C-bit Coding Violation, 41 P-bit Err Secs,
9 P-bit Severely Err Secs, 0 Severely Err Framing Secs,
25634 Unavailable Secs, 44 Line Errored Secs,
40 C-bit Errored Secs, 9 C-bit Severely Errored Secs
show interfaces serial 1/0
Serial1/0 is down, line protocol is down
Hardware is DSXPNM Serial
Internet address is xxx.xxx.xxx.xxx
MTU 4470 bytes, BW 44210 Kbit, DLY 200 usec,
reliability 197/255, txload 1/255, rxload 1/255
Encapsulation HDLC, crc 16, loopback not set
Keepalive set (10 sec)
Last input 23:14:27, output 00:30:37, output hang never
Last clearing of "show interface" counters 5d00h
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 7
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
5461 packets input, 758807 bytes, 0 no buffer
Received 231 broadcasts, 858 runts, 552 giants, 0 throttles
186378003 input errors, 186375374 CRC, 12111197 frame, 123392673 overrun, 0 ignored, 16788171 abort
6479 packets output, 2393729 bytes, 0 underruns
0 output errors, 0 collisions, 14436 interface resets
0 output buffer failures, 0 output buffers swapped out
16 carrier transitions
DSU mode 0, bandwidth 44210, real bandwidth 44210, scramble 1
01-02-2008 08:46 AM
Hi,
you interface is down due to garbage instead of date being received., provider's fault.
If you want to be extra cautious, do "shut / no shut" under controller t3 1/0, but likely that won't change things.
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