I think its the MCC card that is bad. I am not sure if it would be the MCC itself or the software card?

Here are the logs:
1:13 PM 14-JUL-11 alarm status = NO ALARM

+----------------------------------------------------------------------------+
¦ SX-200 LW19 Q18.0.3 06-DEC-2002 Logs ¦
+----------------------------------------------------------------------------¦
¦READ LOGS ALL ¦
¦2011-JUL-14 12:37:27 Tot alarm went from MAJOR to No Alarm ¦
¦ Alarm level change due to Bay 01 lines ¦
¦ ¦
¦2011-JUL-14 12:37:18 T1/BRI card at 01 06 00 00 ¦
¦ is current sync source and is in auto mode ¦
¦ ¦
¦2011-JUL-14 12:37:18 T1/BRI card at 00 00 00 00 ¦
¦ The systems previous sync source was freerun mode ¦
¦ ¦
¦2011-JUL-14 12:37:18 T1/BRI card at 01 06 00 00 ¦
¦ alarm condition is now cleared ¦
2011-JUL-14 12:36:52 T1/BRI card at 01 06 00 00 ¦
¦ is in red alarm condition due to loss of sync ¦
¦ ¦
¦2011-JUL-14 12:36:27 BAY number 01 reported cause: unass trap instn ¦
¦ at address = 0004469E ¦
¦ ¦
¦2011-JUL-14 12:33:00 BAY number 01 reset itself! ¦
¦ ¦
¦ ¦
¦2011-JUL-14 12:07:23 Tot alarm went from No Alarm to MAJOR ¦
¦ Alarm level change due to Bay 01 lines ¦
¦2011-JUL-14 11:59:00 Main Control power up! ¦
¦ ¦
¦ ¦
¦2011-JUL-14 11:56:44 Main Control software error! ¦
¦ watchdog at address = 0101BB3E ¦
¦ ¦
¦2011-JUL-14 11:56:43 Tot alarm went from No Alarm to MAJOR ¦
¦ Alarm level change due to Bay 01 pcm ¦
¦ ¦
¦2011-JUL-14 11:56:43 BAY number 01 reset itself!
¦2011-JUL-14 11:46:00 Main Control power up! ¦
¦ ¦
¦ ¦
¦2011-JUL-14 11:44:03 Main Control software error! ¦
¦ watchdog at address = 0101BB3C ¦
¦ ¦
¦2011-JUL-14 11:44:03 Tot alarm went from No Alarm to MAJOR ¦
¦ Alarm level change due to Bay 01 pcm ¦
¦ ¦
¦2011-JUL-14 11:44:03 BAY number 01 reset itself! ¦
¦ ¦
¦2011-JUL-14 11:41:57 Tot alarm went from MAJOR to No Alarm ¦
¦ Alarm level change due to Bay 01 lines ¦
¦ ¦
¦2011-JUL-14 11:41:08 T1/BRI card at 01 06 00 00 ¦
¦ is current sync source and is in auto mode ¦
¦ ¦
¦2011-JUL-14 11:41:08 T1/BRI card at 00 00 00 00 ¦
¦ The systems previous sync source was freerun mode ¦
¦ ¦
¦2011-JUL-14 11:41:08 T1/BRI card at 01 06 00 00 ¦
¦ alarm condition is now cleared ¦
¦2011-JUL-14 11:40:32 T1/BRI card at 01 06 00 00 ¦
¦ is in red alarm condition due to loss of sync ¦
¦ ¦
¦2011-JUL-14 11:40:02 BAY number 01 reported cause: watchdog timer ¦
¦ at address = 00040090 ¦
¦ ¦
¦2011-JUL-14 11:39:15 T1/BRI card at 00 00 00 00 ¦
¦ System in freerun mode no sync source available ¦
¦ ¦
¦2011-JUL-14 11:39:15 T1/BRI card at 01 06 00 00 ¦
¦ was previous sync source in auto mode ¦
2011-JUL-14 11:39:14 Tot alarm went from No Alarm to MAJOR ¦
¦ Alarm level change due to Bay 01 pcm ¦
¦ ¦
¦2011-JUL-14 11:39:14 BAY number 01 reset itself! ¦
¦ ¦
¦ ¦
¦2011-JUL-14 11:36:28 Tot alarm went from MAJOR to No Alarm ¦
¦ Alarm level change due to Bay 01 lines ¦
¦ ¦
¦2011-JUL-14 11:36:18 T1/BRI card at 01 06 00 00 ¦
¦ is current sync source and is in auto mode ¦
¦2011-JUL-14 11:36:18 T1/BRI card at 00 00 00 00 ¦
¦ The systems previous sync source was freerun mode ¦
¦ ¦
¦2011-JUL-14 11:36:18 T1/BRI card at 01 06 00 00 ¦
¦ alarm condition is now cleared ¦
¦ ¦
¦2011-JUL-14 11:35:53 T1/BRI card at 01 06 00 00 ¦
¦ is in red alarm condition due to loss of sync ¦
¦ ¦
¦2011-JUL-14 11:35:35 BAY number 01 reported cause: unass trap instn ¦
¦ at address = 0004469E ¦
¦ ¦
¦2011-JUL-14 11:33:58 T1/BRI card at 00 00 00 00 ¦
¦ System in freerun mode no sync source available ¦
¦ ¦
¦2011-JUL-14 11:33:58 T1/BRI card at 01 06 00 00 ¦
¦ was previous sync source in auto mode ¦
¦ ¦
¦2011-JUL-14 11:33:56 Tot alarm went from No Alarm to MAJOR ¦
¦ Alarm level change due to Bay 01 pcm ¦
¦ ¦
¦2011-JUL-14 11:33:56 BAY number 01 reset itself! ¦
¦ ¦

Check your Bay Control Card in Bay 1. If possible, exchange it with the BCC in Bay 2 and see if the problem follows the card.

Note: BCC is NOT, repeat NOT hot-swappable.

Further Note: BCCIII may take up to 20 minutes to boot. Do NOT power off while BCCIII is booting.

I'd agree with the BCC card. The logs say only bay 1 is going down, NOT the whole system. If the whole system was going down, you'd have logs showing the re-boot process.

I'll agree. I think he has a bad BCCIII. I also wouldn't be suprised if it had a T1 module.

If you have the opportunity (time, after hours) you might try looping the T-1 back into the PBX. You may have a synch problem with telco.

Sorry for dredging this topic up but it matches my current issue almost perfectly. Same system, same software load, same issue.

Deadwalleye, can you post what fixed this issue for you?

I have it narrowed down to the BCCII on bay 2 or the CIM connection between bay 1 and 2.

Thanks

Odds are, BCC II card is your problem. Try swapping the BCC card with Bay 1 and see if the problem follows the card.

BCC is NOT hot swappable; you MUST power down the system (or at least that bay) to pull this card.

I just wanted to add an update in case anyone needs the solution.

It was the BCCII card, as soon as we replaced that the problem disapeared.

They also had their PBX on a maxed-out power strip, so it was not getting what it needed for power.

I convinced them to put the system on a UPS and it's working perfectly now.

Thanks again for the advice.