DTA019, DTA021, DTA022, DTA023 ERRORS ON PBX, LOOPS GOING UP AND DOWN

[jscpbxguy]

i am getting all of the following errors on a number of different cards in my nortel option 11c pbx, does anyone knwo what they mean?

i replaced the clock controller today along with the TMDI card that it was attached to.

my clock controller is locked on slot 1, its not in free run.

i spoke with my carrier paetec, they tell me that they tested clean to my NIU and when they tested to my CSU they saw a lot of errors, then they tried to the NIU again and then they saw a bunch of errors including framing errors, so they are going to open up a ticket with verizon, but WE ALL KNOW HOW VERIZON IS, if they test it to their equipment fine, they wont dispatch anyone.

my t1's and their cards have been going up and down for the past 2 weeks straight, my d channel goes down, i cant recieve calls half the day, people are dropping calls, its my worst nightmare, i have 27 new people starting to work in my office this saturday, that means 27 new sets i have to build before then, and i have to get this resolved before they get here.

 

[acewarlock]

If all else fails, Try a cold reboot.

 

[jscpbxguy]

have cold rebooted about 20 times, still nothing..

does anyone know what kind of errors they are?

 

[srmega41]

DAT0019 ==> Frame Alignment Maintenance limit: This means the number of frame alignment errors since the last counter clearing, or midnight routine, has been exceeded.

DTA0021 ==> Frame Alignment alarm persisted for 3 seconds: Self explanitory

DTA0022 ==> Frame Alignment alarm has cleared for at least 15 seconds: Self explanitory

DTA0023 ==> PRI loop is up.

The maintenance limit that is being referred to is set in LD 73, under the Digital Data Block. You set a threshold grouping to your PRI when it is built, usually 0.

This sounds like you have an ESF vs. SF issue. ESF (Extended Super Frame) only uses 2000 bits of the 8000 framing bits per second for circuit syncronization. SF (SuperFrame) is a composite of 12 T1 frames, each 193 bits (24 DS0 x 8 bits plus 1) long. SF uses a robbed-bit function to calculate and recognize errors, do cyclic redundancy checking, and data link monitoring, because the extra bit in each frame is already being used for syncronization. Since ESF only uses 2000 of the 8000, the rest are used for the other error correction checks listed above, and does not need to rob any bits for other needs. ESF provides true 64KB/sec speech paths, where SF and other D-style framing formats only provide 56KB/sec.

Hope this helps,

Scott M.

 

[jscpbxguy]

is there anything i can do about the DTA019 errors?
i did an lcnt on my loop and this is the only loop taking errors, as you can see below


DTI LOOP 7
TRSH CNT:
BPV -040
SLIPD -003
SLIPR -001
CRC -000
LOSFA -062
OS_BPV -000
OS_LOSFA-000
OS_YEL -000

.
DTA019 7

AUD000

TRK130 6 4


also, do you know what the TRK130 6 4 is? do you think that i just have to recete the card?

 

[srmega41]

TRK130 is a DID trunk short hold error, relating to TN 6 4.

With the number of errors you have, like the BPV (Bi-Polar Violations), I would insist on the carrier testing and providing some circuit testing. You are seeing way too many errors. I really do not think re-seating the card will help. Is this a circuit to another site or to the Central office?

Hope this helps,

Scott M.

 

[TJoker]

Did this problem just start or have you had the problem since installation?

I have seen this in the past and it was due to an M13 set for D4 AMI and not B8Zs as Scott has suggested. We had to have the local LEC out to run head to head on the test equipment just to prove our point. They finally saw the framing miss match and were able to reset the M13.

Might want to make sure they can see 1's adn 0's when they test and make sure they test for more than 10 mins.

Dan

 

[srmega41]

Good idea. In the Qwest area, we ask for a "Round-Robin test". This tests every configuration and signalling configuration assigned from end to end.

We fought Qwest for over a month on an old T1 that was AMI, and some tech did a PM and changed out a card that defaulted to B8ZS. Not a fun time, but I actually got a call from a CO tech apologizing for all the troubles, since the kept insisting it was our equipment, forcing us to change out every piece of hardware before they would run the test.

Scott M.

 

[johnpoole]

send them a bill Scott

john poole
bellsouth business
columbia,sc

 

[srmega41]

I tried. They did give us a credit, I think it was about $10.

Scott M.

 

[jscpbxguy]

looks like verizon did their job

it was a card in the mux that went bad, they replaced it, looking good now.

still taking dta019 errors on one of the circuits in my pbx, i think it might relate to the problem you guys are discussing

thanks again for all the help.

 

[johnpoole]

check and clear the lcnt tables when they finish.. those tables will clear at midnight if you have 60 in the drol, but they can cause pri codes when they approach limits

john poole
bellsouth business
columbia,sc

 

[acewarlock]

Use RCNT to clear the counts.