CSA001 2

[yeddish]

We had a power failure that caused our PBX to start giving some odd error messages. It keeps giving the following errors and the DCH won't come back up, either. I'm not sure what these errors mean, but I'm assuming they are the reasont aht the DCH won't come back up.
All the other threads involving this message that I could find also involved AML errors, which I am not getting.

Thanks.
-Joel

CSA001 9 14:21:36 15/07/2007 4

CSA001 9 14:22:06 15/07/2007 4

CSA001 9 14:22:36 15/07/2007 4

CSA001 9 14:23:06 15/07/2007 4

 

[djwht]

is this an OPT11 or a CS1KS?

go to ld 22 and prin adan. look for aml 9 and tty 8

if you have both of these and no Meridian Mail, delete them, otherwise your MerMail is down

 

[yeddish]

I do have those and no MerMail...funky. I'll get rid of them.
But, this wouldn't have anything to do with my DCH, I don't think... That still won't come up.

I'll post again on that.
Thanks.
-Joel

 

[acewarlock]

LD 60
STAT


LD 96
STAT DCH

Post resuls here

 

[SwitchWitch]

These CSA messages are telling you that your CPU is having a problem another device.

Since you lost your DCH, the sytem probably tried to bring them back online automatically and couldn't do so... that's why you're getting the CSA messages.

Agree w/ ACE, provide him w/ the LD 60 (STAT) and LD 96 (DCH) info.

 

[yeddish]

Here it is:
>ld 60
DTI000
.
CSA001 9 17:43:14 15/07/2007 4
stat

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

.****
>
OVL000
>ld 96
DCH000
.stat dch
DCH 04 : DSBL RST AUTO DES : ADMIN
.

Thanks!
-Joel

 

[SwitchWitch]

You're now going to disable the D-Channel, disable the loop, renable the loop which should bring back the D-Channel.

based on your config above...DCH 4 is disabled and its on loop #1

so

1- LD 96
2- DIS DCH 04
3- LD 60
4- DISL 1 (loop # associated w/ the channel)
5- ENLL 1
6- STAT the loop that you just reset.. should read IDLE

 

[yeddish]

Thanks.
The STAT still reads like the above with MBSY instead of IDLE.

Any more ideas?

-Joel

 

[SwitchWitch]

wait a few and then re-stat.
Also.... forgive me for asking, but you've checked your CSUs... right.

 

[janaya]

Do you have an AML 9 in your system. If you don't have a mermail, then just remove aml 9.

I had those messages, but the mail was down and we had to reboot the mermail.

John

 

[yeddish]

I've tried disabling and reenabling several times now and with no luck. The CSUs are both powered on, but beyond that I don't really know how to test them.

Also, it turns out that we've always been getting the CSA001 errors on this PBX. This is just the first time I've had to work on it.

I'm really bangin' my head on the wall, here. This is odd.

Any more ideas, by chance?

Thanks.
-Joel

 

[SwitchWitch]

Possible that you're not down, but the far end is. call them.

do a lcnt rcnt in ld 60. a DTA023 01 tells you that your pri is up. the mbsy is because the far end will not enable the channels.. might try ench 01 1 to see if a single channel will idle up

 

[yeddish]

ENCH 01 1 brought the first channel to IDLE.
Also, I did a RCNT earlier today and so far there are no additional errors.

Since I can bring up individual channels with ENCH, what should I do at this point?

Thanks.
-Joel

 

[yeddish]

Ok. So, I looked at the plog and got a DCH1019. This meaning that the card is hardware disabled makes no sense since nothing has changed on the card since a few days ago when this was working fine. So, in my frustration, I yelled "Monkey Poo!" and turned the unit off, reseated the card and powered back up. Voila! It worked! The DCH established just fine without any work.

Thanks everyone for all your help!
-Joel

 

[SwitchWitch]

It was the Monkey Poo that fixed it, not the reset