sundance-communications.com/forum Forums TDM Business Telephone Systems Avaya - Lucent Telephones & Systems Definity alarm/reset

Definity G3v7i w/ 798b processor. 3 Cabs (A,B,C).

A few weeks ago we had a power supply fail in Cab B. 1 week later TDM interconnect cable from A>B went bad. When we replaced the cable, we also installed an additional 2224 digital CP in Cab B.

Since then the system has been resetting/re-initializing itself on the weekends. For the past 2 weeks it has gone down intermittently on both Saturday and Sunday sometimes for hours. Unfortunately when I came in to diagnose it, the system is back up and the error logs had been cleared.

Today it went down gracefully 3 times during normal work hours so I finally got to see what it was doing...
Red alarm light on processor
Emergency transfer occurs
All active calls kept alive (no new calls can be made/received)
System re-initializes / Drops all calls
Phones are back up within 30 seconds

The 4th time it happened today it stuck in the Emergency Xfer state so I pulled the power and rebooted. The first reboot didn't yield a successful initialization. I power cycled again and it came back up.

Any thoughts on what might be causing these symptoms/issues?

Bad CAB? Processor? Memory on proc?

Do you have a spare processor to swap around and see if that fix's it?

I'm not Definity proficient...but...might it be either a suspect cable...or...the expansion 2224 card?

Do the alarm/error/trouble logs shed any light?

I have tried 2 spare procs but neither has successfully booted the system to be fully functional. One didn't read my translations (I think the software version was off - need to have it flashed) and the other sat in a MAJ alarm state.

I have to ship the 2nd one back to my Avaya BP and they are going to check it for me.

dexman - I am going to pull the 2224 card out tomorrow since I haven't even crossconnected anything to it yet.

Unfortunately the error logs clear themselves when the system resets so all I can see is what has happened since last reset. Once the proc goes into alarm/error state I can't access ASA or pull hardware error reports.