Merlin Legend Point to Point T1 Problem 1

[Tripp74]

I got pulled into a problem with two Legends that are connected via a PTP T1 circuit. The main site is a 6.1 Legend and the remote site is a 7.0 Legend. The legends are set up with UDP, but are set up as tie lines...no PRI programming. They have been working for a year without problems, but two days ago, the main site could not call the remote, they get a fast busy, but the yellow busy lamp on the D100 is dark. The remote site hears dead air when they try to call the main. The LEC has done end to end testing and has pointed to the main site as having an equipment problem. There are no CSUs being used. The remote site has a lot of "on hook before ready" and "no external release" errors. The main site has a lot of "invalid slot interrupt" errors. We have changed the power unit on the processor cabinet at the main site, and changed the out the D100 at the main site, still no joy. I'd love to pin this on the LEC, but I'm out of ideas. I have busied out both the D100s, done a reset, then released to no avail. Both D100s status as normal. To make matters worse, the main site started doing an occasional "warn start" today. Do I have a flakey processor? or what !?!
Thanks !

 

[Tripp74]

Well, the processor at the main site was losing it's mind, and it also lost the T-1 tie-line translations. I replaced the processor and put the T-1 translations back in now all is well !

 

[merlinman]

This sounds as if your Main Site had experienced a Power Outage AND the "hold up" battery is not good.

It would be easy to test this by powering down, wait a few minutes, and then powering back up. BUT FIRST, MAKE SURE YOUR PCMCIA CARD HAS A FRESH BACK UP. (So you can restore the translations if need be.)

If if fails, then my theory is correct. If not, well, it could be anyone's guess.

http://home.comcast.net/~merlinman

-merlinmansblog.blogspot.com

 

[Tripp74]

Well Merlinman,
I've read other posts where you said, "It almost never the processor"....and you're right ! This proved to be not the processor, but a flakey surge protector/power strip that was driving the switch crazy. Once the protector was replaced, everything settled down!