T-1 RED alarm

[Southpaw46]

The loop below was disconnected by mistake. We then had verizon reinstall this 24 channel T-1 today and it has been up and down. i can put the csu in local loop back and the switch side comes up channels enabled. also it has been up for maybe 1 minute just long enough for 5-6 calls to be placed then it goes into red alarm and all channels disable.
I thinks it's a TELCO issue BUT want to confirm.
nothing was changed as foar as hardware or programming on switch side since it was taken out of service.
thanks for your support and ideas

PRI* TRK LOOP 66 - ENBL
FFMT/LCMT/YALMT: ESF/B8Z/FDL
SERVICE RESTORE: YES
YEL ALM PROCESS: YES
ALARM STATUS : RED
CH 01 - DSBL ISA CH 02 - DSBL ISA
CH 03 - DSBL ISA CH 04 - DSBL ISA
CH 05 - DSBL ISA CH 06 - DSBL ISA
CH 07 - DSBL ISA CH 08 - DSBL ISA
CH 09 - DSBL ISA CH 10 - DSBL ISA
CH 11 - DSBL ISA CH 12 - DSBL ISA
CH 13 - DSBL ISA CH 14 - DSBL ISA
CH 15 - DSBL ISA CH 16 - DSBL ISA
CH 17 - DSBL ISA CH 18 - DSBL ISA
CH 19 - DSBL ISA CH 20 - DSBL ISA
CH 21 - DSBL ISA CH 22 - DSBL ISA
CH 23 - DSBL ISA CH 24 - DSBL ISA
DTA0019 loop
Frame alignment maintenance limit.

Severity: Critica
PRI000 66 15

PRI000 66 15

DTA023 66

OK
.stat 66

PRI* TRK LOOP 66 - ENBL
FFMT/LCMT/YALMT: ESF/B8Z/FDL
SERVICE RESTORE: YES
YEL ALM PROCESS: YES
ALARM STATUS : NO ALARM
CH 01 - BUSY ISA CH 02 - BUSY ISA
CH 03 - BUSY ISA CH 04 - BUSY ISA
CH 05 - BUSY ISA CH 06 - IDLE ISA
CH 07 - IDLE ISA CH 08 - IDLE ISA
CH 09 - IDLE ISA CH 10 - IDLE ISA
CH 11 - IDLE ISA CH 12 - IDLE ISA
CH 13 - IDLE ISA CH 14 - IDLE ISA
CH 15 - IDLE ISA CH 16 - IDLE ISA
CH 17 - IDLE ISA CH 18 - IDLE ISA
CH 19 - IDLE ISA CH 20 - IDLE ISA
CH 21 - IDLE ISA CH 22 - IDLE ISA
CH 23 - IDLE ISA CH 24 - IDLE ISA

DTA0021 loop
Frame alignment alarm persisted for 3 seconds.

Severity: Critical

 

[KCFLHRC]

Definitely a Telco issue. This loop isn't the one with the clocking is it? Print your DDB in LD 73 and make sure in LD 60 it's tracking on the primary reference.

 

[Tacosoup]

Definately double check the clocking in LD 60. SSCK 0

 

[Southpaw46]

.ssck 0
ENBL
CLOCK ACTIVE
GROUP 0
SIDE 0
CLOCK CONTROLLER - TRACK ON LOOP 2
PREF - 2
SREF - 82
AUTO SWREF CLK - ENBL
NO ERROR
>ld 73
DDB000
MEM AVAIL: (U/P): 40125715 USED U P: 9748700 1738254 TOT: 51612669
DISK SPACE NEEDED: 2568 KBYTES
REQ prt
TYPE ddb

PREF 2
SREF 82

TRSH 00
RALM 128
BIPC 0
LFAC 0
BIPV 4 3
SRTK 5 3600
SRNT 10 3
LFAL 10240 10240
SRIM 1
SRMM 127
ICS

TRSH 01
RALM 128
BIPC 0
LFAC 0
BIPV 4 3
SRTK 24 3600
SRNT 1 1
LFAL 10240 10240
SRIM 1
SRMM 127

 

[KCFLHRC]

Your clocking looks fine as this loop you are having trouble with isn't one your clocking off of. So I really believe this is a Telco issue. Red Alarm means Far End trouble.

 

[Southpaw46]

thats what I was always taught but just wanted some conformation.
thanks to all for your help

 

[bhassell2000]

I thought a yellow alarm was a far end trouble and red meant you dont see any network on your end, maybe I ma backwards, but if he goes happy when looped back he should be good inhouse

Thanks,

Buddy

Linked in Profile

http://www.linkedin.com/in/buddyhassell

 

[johnpoole]

didn't read any of the replies... red alarm is no layer one between you and the far end... unplug a cable on any t, it goes red... from the back of the switch put a loop back toward the switch... if red goes yellow. move the loop back to the next connection...

nothing you do in software can change a red alarm.. ever

john poole
bellsouth business
columbia,sc

 

[hawks]

Red alarm (local alarm)-card or transmission fault
Yellow alarm (remote alarm)-far end fault

Follow what john said but I would also verify that Telco built them back like they were before. If they built them as wrong trunk type this can happen.

 

[KCFLHRC]

The alarms can be a little misleading. Yes, a RED Alarm is a near end alarm and a yellow is far end. However, go unplug from the smart jack and see what light comes on. It sure aint the yellow. The RED and YELLOW are carrier alarms, not trunk mis match alarms. The carrier can come up and you will come out of alarm with a trunk type mismatch. Now if you have a protocol mismatch that is a different story. Print your cequ for that loop and ask the Telco if they are set up the same way. B8Zs/ESF, etc.