Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Input and crc errors 1

Status
Not open for further replies.

jdbofh

IS-IT--Management
Sep 9, 2003
6
US
I have 2 routers connected via T1. (3600 <-> 2600) Both have serial T1 cards and external CSU/DSU's. The issue is that I am getting tons of input and crc errors on both ends of this connection.

Results of sh int on the 3600
10807488 input errors, 10217351 CRC, 0 frame, 1448 overrun, 0 ignored, 588689 abort
123698 packets output, 29457060 bytes, 0 underruns
0 output errors, 0 collisions, 17 interface resets
0 output buffer failures, 0 output buffers swapped out
28869 carrier transitions
DCD=up DSR=up DTR=up RTS=up CTS=up

results of sh int on the 2600
531827 input errors, 12225 CRC, 509242 frame, 0 overrun, 0 ignored, 10360 abort
93243 packets output, 12461379 bytes, 0 underruns
0 output errors, 0 collisions, 31 interface resets
0 output buffer failures, 0 output buffers swapped out
88 carrier transitions
DCD=up DSR=up DTR=up RTS=up CTS=up

I have already replaced CSU's an cables on both ends...does anyone have any thoughts as to what the problem may be????

Any help is greatly appreciated
 
I know I'm not being much help, but I would normally put this down to a fault with your circuit.

Have your called you provider?

Andy


Andy Leates MCSE CCNA MCP+I
 
Yes...repeatedly...(grrrrrr)....they say that the line tests clean....
Telco is where I started as well....as most of the time that I've seen issues like this they have almost always been circuit related.
 
What kind of connection is it, is it a transparent or do they provide you with clocking.
Of the amount of crc errors it sound like a clocking err.

Fredrik
 
Make sure that the clocking, framing and line coding is set as appropriate to your circuit. Is your cable length excessive? Have you tried loopback tests? See the following for help with these:
Please provide an output of the SHOW CONTROLLER T1 or the SHOW SERVICE-MODULE commands.

Let us know how you make out.

andf1
 
Posting output from &quot;sh controller s0/0&quot;


Interface Serial0/0
Hardware is PowerQUICC MPC860
DTE V.35 TX and RX clocks detected.
idb at 0x80870E68, driver data structure at 0x80876218
SCC Registers:
General [GSMR]=0x2:0x00000030, Protocol-specific [PSMR]=0x8
Events [SCCE]=0x0000, Mask [SCCM]=0x001F, Status [SCCS]=0x06
Transmit on Demand [TODR]=0x0, Data Sync [DSR]=0x7E7E
Interrupt Registers:
Config [CICR]=0x00367F80, Pending [CIPR]=0x00008000
Mask [CIMR]=0x40204000, In-srv [CISR]=0x00000000
Command register [CR]=0x600
Port A [PADIR]=0x0000, [PAPAR]=0xFFFF
[PAODR]=0x0000, [PADAT]=0xB9FA
Port B [PBDIR]=0x03A0F, [PBPAR]=0x0C00E
[PBODR]=0x0000E, [PBDAT]=0x3275D
Port C [PCDIR]=0x00C, [PCPAR]=0x000
[PCSO]=0x0A0, [PCDAT]=0xFC0, [PCINT]=0x00F
Receive Ring
rmd(68012230): status 9000 length 34 address 1320A00
rmd(68012238): status 9000 length 34 address 131C9C8
rmd(68012240): status 9000 length 34 address 131D034
rmd(68012248): status 9000 length 34 address 13216D8
rmd(68012250): status 9000 length 42 address 13216D8
rmd(68012258): status 9000 length 37 address 132106C
rmd(68012260): status 9000 length 37 address 131D6A0
rmd(68012268): status 9000 length 125 address 1320394
rmd(68012270): status 9000 length 34 address 131E9E4
rmd(68012278): status 9000 length 34 address 13236F4
rmd(68012280): status 9000 length 34 address 13270C0
rmd(68012288): status 9000 length 34 address 13290DC
rmd(68012290): status 9000 length 34 address 131E378
rmd(68012298): status 9000 length 34 address 1325D7C
rmd(680122A0): status 9000 length 34 address 132772C
rmd(680122A8): status B000 length 34 address 1321D44
Transmit Ring
tmd(680122B0): status 5C00 length 2D address 13394D8
tmd(680122B8): status 5C00 length 2D address 13394D8
tmd(680122C0): status 5C00 length 2D address 1339B58
tmd(680122C8): status 5C00 length 2D address 1339B58
tmd(680122D0): status 5C00 length 2D address 1339B58
tmd(680122D8): status 5C00 length 2D address 1339B58
tmd(680122E0): status 5C00 length 2E address 1339B58
tmd(680122E8): status 5C00 length 258 address 13394D8
tmd(680122F0): status 5C00 length 1DE address 133A1D8
tmd(680122F8): status 5C00 length 40 address 1337098
tmd(68012300): status 5C00 length 18 address 1337F98
tmd(68012308): status 5C00 length 40 address 1337098
tmd(68012310): status 5C00 length 2C address 1337F98
tmd(68012318): status 5C00 length 258 address 133A1D8
tmd(68012320): status 5C00 length 258 address 13394D8
tmd(68012328): status 7C00 length 2D address 13394D8

SCC GENERAL PARAMETER RAM (at 0x68013C00)
Rx BD Base [RBASE]=0x2230, Fn Code [RFCR]=0x18
Tx BD Base [TBASE]=0x22B0, Fn Code [TFCR]=0x18
Max Rx Buff Len [MRBLR]=1548
Rx State [RSTATE]=0x18008440, BD Ptr [RBPTR]=0x2288
Tx State [TSTATE]=0x18000548, BD Ptr [TBPTR]=0x22B0

SCC HDLC PARAMETER RAM (at 0x68013C38)
CRC Preset [C_PRES]=0xFFFF, Mask [C_MASK]=0xF0B8
Errors: CRC [CRCEC]=1208, Aborts [ABTSC]=894, Discards [DISFC]=0
Nonmatch Addr Cntr [NMARC]=0
Retry Count [RETRC]=0
Max Frame Length [MFLR]=1608
Rx Int Threshold [RFTHR]=0, Frame Cnt [RFCNT]=4789
User-defined Address 0000/0000/0000/0000
User-defined Address Mask 0x0000


buffer size 1524

PowerQUICC SCC specific errors:
58730 input aborts on receiving flag sequence
0 throttles, 0 enables
0 overruns
0 transmitter underruns
0 transmitter CTS losts
 
That is not the output of SHOW CONTROLLERS T1. If the command does not work try SHOW SERVICE-MODULE.

andf1
 
Whoops....sorry about that.
Module type is T1/fractional
Hardware revision is 0.88, Software revision is 1.07,
Image checksum is 0x8510A6B6, Protocol revision is 0.1
Transmitter is sending remote alarm.
Receiver has loss of signal, loss of frame,
Framing is ESF, Line Code is B8ZS, Current clock source is line,
Fraction has 6 timeslots (64 Kbits/sec each), Net bandwidth is 384 Kbits/sec.
Last module self-test (done at startup): Passed
Last clearing of alarm counters 1w0d
loss of signal : 1, current duration 1w0d
loss of frame : 1, current duration 1w0d
AIS alarm : 0,
Remote alarm : 0,
Module access errors : 0,
Total Data (last 96 15 minute intervals):
24480 Line Code Violations, 0 Path Code Violations
4207 Slip Secs, 86400 Fr Loss Secs, 86400 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 86400 Unavail Secs
Data in current interval (179 seconds elapsed):
255 Line Code Violations, 0 Path Code Violations
8 Slip Secs, 179 Fr Loss Secs, 179 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 179 Unavail Secs
 
You said the line was full T1. Why are you only using 6 time slots? Please post the configuration of your controllers and your serial interfaces.

andf1
 
It is a full T1--upgraded from a frac
the former frac was configured on s0/1 and is shutdown


sh controller s0/0
Interface Serial0/0
Hardware is PowerQUICC MPC860
DTE V.35 TX and RX clocks detected.
idb at 0x80870E68, driver data structure at 0x80876218
SCC Registers:
General [GSMR]=0x2:0x00000030, Protocol-specific [PSMR]=0x8
Events [SCCE]=0x0000, Mask [SCCM]=0x001F, Status [SCCS]=0x06
Transmit on Demand [TODR]=0x0, Data Sync [DSR]=0x7E7E
Interrupt Registers:
Config [CICR]=0x00367F80, Pending [CIPR]=0x00008000
Mask [CIMR]=0x40204000, In-srv [CISR]=0x00000000
Command register [CR]=0x600
Port A [PADIR]=0x0000, [PAPAR]=0xFFFF
[PAODR]=0x0000, [PADAT]=0xB9FA
Port B [PBDIR]=0x03A0F, [PBPAR]=0x0C00E
[PBODR]=0x0000E, [PBDAT]=0x3275D
Port C [PCDIR]=0x00C, [PCPAR]=0x000
[PCSO]=0x0A0, [PCDAT]=0xFC0, [PCINT]=0x00F
Receive Ring
rmd(68012230): status 9000 length 34 address 1320A00
rmd(68012238): status 9000 length 34 address 131C9C8
rmd(68012240): status 9000 length 34 address 131D034
rmd(68012248): status 9000 length 34 address 13216D8
rmd(68012250): status 9000 length 42 address 13216D8
rmd(68012258): status 9000 length 37 address 132106C
rmd(68012260): status 9000 length 37 address 131D6A0
rmd(68012268): status 9000 length 125 address 1320394
rmd(68012270): status 9000 length 34 address 131E9E4
rmd(68012278): status 9000 length 34 address 13236F4
rmd(68012280): status 9000 length 34 address 13270C0
rmd(68012288): status 9000 length 34 address 13290DC
rmd(68012290): status 9000 length 34 address 131E378
rmd(68012298): status 9000 length 34 address 1325D7C
rmd(680122A0): status 9000 length 34 address 132772C
rmd(680122A8): status B000 length 34 address 1321D44
Transmit Ring
tmd(680122B0): status 5C00 length 2D address 13394D8
tmd(680122B8): status 5C00 length 2D address 13394D8
tmd(680122C0): status 5C00 length 2D address 1339B58
tmd(680122C8): status 5C00 length 2D address 1339B58
tmd(680122D0): status 5C00 length 2D address 1339B58
tmd(680122D8): status 5C00 length 2D address 1339B58
tmd(680122E0): status 5C00 length 2E address 1339B58
tmd(680122E8): status 5C00 length 258 address 13394D8
tmd(680122F0): status 5C00 length 1DE address 133A1D8
tmd(680122F8): status 5C00 length 40 address 1337098
tmd(68012300): status 5C00 length 18 address 1337F98
tmd(68012308): status 5C00 length 40 address 1337098
tmd(68012310): status 5C00 length 2C address 1337F98
tmd(68012318): status 5C00 length 258 address 133A1D8
tmd(68012320): status 5C00 length 258 address 13394D8
tmd(68012328): status 7C00 length 2D address 13394D8

SCC GENERAL PARAMETER RAM (at 0x68013C00)
Rx BD Base [RBASE]=0x2230, Fn Code [RFCR]=0x18
Tx BD Base [TBASE]=0x22B0, Fn Code [TFCR]=0x18
Max Rx Buff Len [MRBLR]=1548
Rx State [RSTATE]=0x18008440, BD Ptr [RBPTR]=0x2288
Tx State [TSTATE]=0x18000548, BD Ptr [TBPTR]=0x22B0

SCC HDLC PARAMETER RAM (at 0x68013C38)
CRC Preset [C_PRES]=0xFFFF, Mask [C_MASK]=0xF0B8
Errors: CRC [CRCEC]=1208, Aborts [ABTSC]=894, Discards [DISFC]=0
Nonmatch Addr Cntr [NMARC]=0
Retry Count [RETRC]=0
Max Frame Length [MFLR]=1608
Rx Int Threshold [RFTHR]=0, Frame Cnt [RFCNT]=4789
User-defined Address 0000/0000/0000/0000
User-defined Address Mask 0x0000


buffer size 1524

PowerQUICC SCC specific errors:
58730 input aborts on receiving flag sequence
0 throttles, 0 enables
0 overruns
0 transmitter underruns
0 transmitter CTS losts

show int s0/0
interface Serial0/0
description T1 connection
ip address x.x.x.x 255.255.255.0

show int s0/0
Serial0/0 is up, line protocol is up
Hardware is PowerQUICC Serial
Description: T1 connection
Internet address is 192.168.3.1/24
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation HDLC, loopback not set, keepalive set (10 sec)
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of &quot;show interface&quot; counters 00:58:36
Input queue: 0/75/0 (size/max/drops); Total output drops: 0
Queueing strategy: weighted fair
Output queue: 0/1000/64/0 (size/max total/threshold/drops)
Conversations 0/8/256 (active/max active/max total)
Reserved Conversations 0/0 (allocated/max allocated)
5 minute input rate 1000 bits/sec, 1 packets/sec
5 minute output rate 1000 bits/sec, 1 packets/sec
5220 packets input, 929734 bytes, 0 no buffer
Received 410 broadcasts, 0 runts, 0 giants, 0 throttles
32462 input errors, 1138 CRC, 30683 frame, 0 overrun, 0 ignored, 641 abort
5672 packets output, 620150 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 output buffer failures, 0 output buffers swapped out
2 carrier transitions
DCD=up DSR=up DTR=up RTS=up CTS=up
 
Your CSU/DSU is still configured for a fractional T1. Change the settings so that all 24 time slots are used.

andf1
 
This is your clue:

Fraction has 6 timeslots (64 Kbits/sec each), Net bandwidth is 384 Kbits/sec.

andf1
 
OK.... am trying to see how to change the setings from frac to full...but the csu is configured for 24 channels. Is there somewhere I am missing on where to change these settings?

CSU is an Adtran CSU Ace
 
Hey jdbofh,

Atleast From my own past expereinces... Ive found that often times when taking excessive Carrier Transistions, (as you certainly are) Carrier Transistions often (not always) seem to go hand in hand with a bad physical cable termination.
Maybe start by contacting the ILEC/CLEC who provides your local loop and ask them to plug in @ a DSX panel to monitor your Circuit for 24 hours... According to the data you provided, Id gamble in saying theyll likely see BPV's over the circuit. (Bi-Polar Violations) which once again are usually caused by a bad cable termination- If the issue isnt identified after checking the copper itself out... Maybe try checking your Line-Build-Out. Experiment with different db levels depending on your cable length from HRU to CSU. Hope that helps out, Let me know what happens when you get a chance!
Regards,
Grumpywanguy
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top