PRI cards seem to take out SX-200

[JimHilton]

About 2 weeks ago, the controller kept rebooting itself so I had our VAR come onsite and check it out. He felt that it was a 1 of the 2 PRI cards that was bad.

Called the local telco and they felt channel one was the problem so they swapped out both with a newer style cards.

Everything seemed happy until 2.50PM today. This time instead of restarting, it hard locked. I called the local telco and they said the connections from the co to the pri's is good.

The next thing I'm thinking that could be is the T1/E1 Framer module.

Here is some log info:

2010-APR-11 21:23:06 VOICE MAIL CARD passed at 08 11 08 01 Ext 1008
Recording dev test Alarm Code = 123
2010-APR-13 11:08:12 Recording dev test failed at 08 11 07 01
failure to answer Alarm Code = 123
2010-APR-15 15:27:00 Main Control power up!

2010-APR-15 15:27:16 T1 ISDN passed at 05 06 00 00
Card installed Alarm Code = 103
2010-APR-15 15:27:16 T1 ISDN passed at 05 08 00 00
Card installed Alarm Code = 103
2010-APR-15 15:27:17 T1 ISDN failed at 05 06 00 00
Card removed Alarm Code = 102
2010-APR-15 15:27:19 T1 ISDN passed at 05 06 00 00
Card installed Alarm Code = 103
2010-APR-15 15:27:20 T1 ISDN failed at 05 08 00 00
Card removed Alarm Code = 102
2010-APR-15 15:27:20 T1 ISDN passed at 05 08 00 00
Card installed Alarm Code = 103
2010-APR-15 15:28:00 Maintenance: D-Channel is DOWN on Bay: 5 Slot: 6
2010-APR-15 15:28:00 Maintenance: D-Channel is DOWN on Bay: 5 Slot: 8

2010-APR-15 15:35:16 Tot alarm went from No Alarm to MINOR
Alarm level change due to Bay 08 trunks
2010-APR-15 16:49:00 Main Control power up!

2010-APR-15 16:50:16 T1 ISDN passed at 05 06 00 00
Card installed Alarm Code = 103
2010-APR-15 16:50:17 T1 ISDN passed at 05 08 00 00
Card installed Alarm Code = 103
2010-APR-15 16:50:17 T1 ISDN failed at 05 06 00 00
Card removed Alarm Code = 102
2010-APR-15 16:50:18 T1 ISDN passed at 05 06 00 00
Card installed Alarm Code = 103
2010-APR-15 16:50:19 T1 ISDN failed at 05 08 00 00
Card removed Alarm Code = 102
2010-APR-15 16:50:19 T1 ISDN passed at 05 08 00 00
Card installed Alarm Code = 103
2010-APR-15 16:50:45 Maintenance: D-Channel is DOWN on Bay: 5 Slot: 6
2010-APR-15 16:50:45 Maintenance: D-Channel is DOWN on Bay: 5 Slot: 8

2010-APR-15 16:58:12 Tot alarm went from No Alarm to MINOR
Alarm level change due to Bay 08 trunks
2010-APR-15 17:00:08 T1/BRI card at 05 06 00 00
is in red alarm condition due to loss of sync
2010-APR-15 17:00:08 T1/BRI card at 05 06 00 00
was previous sync source in auto mode
2010-APR-15 17:00:08 T1/BRI card at 05 08 00 00
is current sync source and is in auto mode
2010-APR-15 17:00:08 Alarm Ind: Receiving a RED Alarm on Bay: 5 Slot: 6

2010-APR-15 17:00:08 Tot alarm went from MINOR to MAJOR
Alarm level change due to Bay 05 trunks
2010-APR-15 17:00:11 Maintenance: D-Channel is DOWN on Bay: 5 Slot: 6

2010-APR-15 17:00:13 T1/BRI card at 05 06 00 00
is receiving a yellow alarm
2010-APR-15 17:00:13 Alarm Ind: Receiving a YELLOW Alarm on Bay: 5 Slot
: 6
2010-APR-15 17:00:18 T1/BRI card at 05 06 00 00
alarm condition is now cleared
2010-APR-15 17:00:18 T1/BRI card at 05 08 00 00
was previous sync source in auto mode
2010-APR-15 17:00:18 T1/BRI card at 05 06 00 00
is current sync source and is in auto mode
2010-APR-15 17:00:18 Tot alarm went from MAJOR to MINOR
Alarm level change due to Bay 05 trunks
2010-APR-15 17:00:33 T1/BRI card at 05 06 00 00
is receiving a yellow alarm
2010-APR-15 17:00:33 T1/BRI card at 05 06 00 00
was previous sync source in auto mode
2010-APR-15 17:00:33 T1/BRI card at 05 08 00 00
is current sync source and is in auto mode
2010-APR-15 17:00:33 T1/BRI card at 05 06 00 00
is in red alarm condition due to loss of sync
2010-APR-15 17:00:33 Maintenance: D-Channel is DOWN on Bay: 5 Slot: 6

2010-APR-15 17:00:33 Tot alarm went from MINOR to MAJOR
Alarm level change due to Bay 05 trunks
2010-APR-15 17:00:48 T1/BRI card at 05 06 00 00
alarm condition is now cleared
2010-APR-15 17:00:48 T1/BRI card at 05 08 00 00
was previous sync source in auto mode
2010-APR-15 17:00:48 T1/BRI card at 05 06 00 00
is current sync source and is in auto mode
2010-APR-15 17:00:48 Tot alarm went from MAJOR to MINOR
Alarm level change due to Bay 05 trunks


The last event before today's was some unknown error, but you can see where it says controller power up is when I restarted it.

Thoughts?

Thanks!!

Jim

 

[stsguy]

CHECK FORM 44

 

[JimHilton]

Hi, thanks for the reply. I'm not quite sure what I should be looking for in that form. It makes references to clock sources.

 

[JimHilton]

Hi, ok i looked on the actual machine that is having the problem. the First Clock is set for 05/06/00/00 comment is MAIN

Second clock is for 05/08/00/00 comment is SECONDARY.

Thanks!

 

[stsguy]

make sure form 44 clock source is set to bay 5 slot 6

 

[JimHilton]

Hi, it was originally set at 05/06 but that was one that having a syncing issue so i change first clock to 05/08.

These logs show the new results of the system:

2010-APR-17 19:05:54 T1/BRI card at 05 06 00 00
is in red alarm condition due to loss of sync
2010-APR-17 19:05:54 Tot alarm went from No Alarm to MAJOR
Alarm level change due to Bay 05 trunks
2010-APR-17 19:05:54 T1/BRI card at 05 06 00 00
is receiving a yellow alarm
2010-APR-17 19:05:38 Tot alarm went from MAJOR to No Alarm
Alarm level change due to Bay 05 trunks
2010-APR-17 19:05:38 T1/BRI card at 05 06 00 00
alarm condition is now cleared
2010-APR-17 19:00:54 Maintenance: D-Channel is DOWN on Bay: 5 Slot: 6
2010-APR-17 19:00:54 T1/BRI card at 05 06 00 00
is in red alarm condition due to loss of sync


Altho I have set the first clock opposite to what you recommend the system does not crash now. It stay active and busies out T1 link.

Obviously this is not ideal, but at least it will only dump certain ammount of callers.

Knowing this, is there a way I can make the controller "ignore" the T1 link and just use T2 until I can get our SP to better diagnose the problem?

Thanks!!

Jim

 

[stsguy]

it sound like you are getting receive errors from the network and exceeding the error threshold and shuting down the first PRI. make sure that all protocol from telco matches yours ex. NI1 or NI2,ESF or SF, B8ZS or AMI etc.

 

[JimHilton]

Hi, not quite sure what the error is, but yes your description of what the system is doing is right. The frustrating thing about this is it seems to be intermitant.

After the telco swapped out the old PRI cards for new ones the system ran fine for about 2 weeks, then it started doing this again.

I'm leaning more toward that the framer card could be defective.

I am going to go onsite and swap the network cables around to see if T2 starts acting up. If it doesn't I can only conclude that something about T1 is messed up.

Thanks!

Jim