T1 errors

[FireFighter78]

I have been getting DTA015 and DTA019 errors from my T1. After some time the Option 11 drops the T1. This has been going on since we installed it 6 weeks ago. We have been having higher call volume recently and the T1 has gone down more often.

Our setup – DMARC (it is new last week the old was fried in a lightning storm) carried about 300 feet on CAT5 (also new last week) to the Adtran T1 CSU ACE (new last year, fried in a lightning storm) carried through one additional building on old CAT3 to the Opt 11.

We have changed the switch settings on our NTAK09 DTI/PRI card to 266 – 399 feet and the Adtran CSU device to that same setting.

I have swapped the NTAK09 with clock control with a spare.

What have we missed? Ideas? Suggestions (besides a closer more direct lightning strike)?



.ssck 0
ENBL
CLOCK ACTIVE
CLOCK CONTROLLER - LOCKED TO SLOT 4
PREF - 4
SREF - FREE RUN
AUTO SWREF CLK - ENBL
NO ERROR

IP DB PORT 1 DSBL
IP DB PORT 2 DSBL
IP DB PORT 3 DSBL
IP DB PORT 4 DSBL
CALL SERVER CLK SRC: CC
.
DTA015 4

DTA015 4

DTA015 4

TIM000 14:00 10/7/2009 CPU 0

DTA019 4

DTA019 4

DTA019 4

DTA019 4

DTA019 4

DTA019 4

DTA019 4

DTA019 4

DTA019 4
lcnt

DTI TRK LOOP 4
TRSH CNT:
BPV -002
SLIPD -001
SLIPR -003
LOSFA -026
OS_BPV -000
OS_LOSFA-000
OS_YEL -000


.
DTA019 4

DTA019 4

DTA019 4

DTA019 4

DTA019 4

DTA019 4

DTA019 4
lcnt

DTI TRK LOOP 4
TRSH CNT:
BPV -002
SLIPD -001
SLIPR -003
LOSFA -033
OS_BPV -000
OS_LOSFA-000
OS_YEL -000


. *** this is about 14:22

 

[bigindian65]

1st thing I would do is by-pass the csu/dsu just to get it out of the picture.

Mato' Was'aka

 

[PERRYPJ]

With it taking Loss of Frame that often I would loop it back at the Telco's Smart Jack and see if it runs clean, if so call Telco

OLD ROLMEN WORKING ON NORTELS AND AVAYA

 

[FireFighter78]

I was able to remove the Adtran CSU thing, no change same errors.

It was running a loop back at the demarc that got them to send some one out. It did run clean under loop back.

Last week when Telco was here they ran "Quasi" at the demarc and said every thing was fine.

 

[oldestgeek]

Firefighter, I would suspect the demark extension. I had a circuit doing the same thing. I found that there was a second T1 in the same cat 3 house cable that was interferring with it. Fortunately, it was a 100 pair cable and moving it to a different binder group resolved the problem. I also had one giving errors and the problem was the cable was lying across a flourescent light ballast in the ceiling. Just moving the cable a few feet fixed that one.

 

[johnpoole]

i would recogmend moving the demark to the switch location. can the provider run clean to your csu? if so what test and how long? they can run clean to any ckt if they only run 2 seconds all ones..

the csu may be the problem but most bpv's come from the distance between the smart jack and the csu or switch..

did you use factory cables? if not recrimp the ends making sure you get perfect connections..

running 1.54 bits per second, getting 6 hits over 15 minutes... a connection has to be perfect.. you can change your thresholds, but it will only stall disl not cure it

john poole
bellsouth business
columbia,sc

 

[FireFighter78]

I never thought of moving the demark closer, we will look into it; I am sure that there is some history that I do not know about.

I have suspected that the conduit that carries the T1 from the demark to the first building has been compromised and the cat5 cable caring it might also be - it has not rained in a couple of days and surprise surprise no more errors.

If issues start up again I will check my new terminations to see if they might be a problem.

Thanks guys!!!

 

[FireFighter78]

I found the source of most my errors - our synchronized clocks.

By the middle of next month the dmarc will be moved within a couple of feet of the switch. be on the lookout for my new series of questions relating to PRIs and D-Channels. LOL

Thanks again for all your help