Merlin Messaging error code 7801 1

[papagigo1]

I came in to a dead Merlin Messaging 4.0, it's only been in service for 1 month.

SPM said slot 10 "Not in normal OP mode" at 3:12am with an error code 7801. No power failure or cold start before that. A re-boot of the 2 carrier Merlin Magix system restored it and I did a full back up just in case..

Any similar experiences, what would you guys suggest?

Mike in NH

 

[SYQUEST]

This type of random error could be caused by many things: power surges or transients, improper equipment bonding/grounding, garbage from a port. If it keeps coming back, then I would be concerned. Make sure the modules are seated securely.

....JIM....

 

[papagigo1]

Syquest,

Thanks for responding.
This 2 carrier system is on a small UPS, so I don't think power is the problem and the history didn't indicate a cold start of the Merlin Magix. When I grounded it I used a good approved source (building frame). The slot issue could be valid, I'll try a re-seat of the card and see what comes next..

Thank you very much,
Mike in NH

 

[dagwoodsystems]

How many other -5VDC cards are in the same cabinet as the MerMSG? You're not supposed to exceed three of these items per carrier:

--MAGIX processor
--MerMSG
--100D (regardless of the flavor)
--800 BRI

In my experience, a Legend is less tolerant of a fully loaded cabinet, especially if a 100D board is present. Despite documentation, my experimentation shows that a native Legend 100D draws considerably more power than the Magix 100D. You don't say whether this is a Legend, Magix or Legend that's been upgraded to a Magix (latest software in the older plastic chassis).

It's also true that having a ton of big MLX sets will tax a carrier enough to make a voicemail or span flake out as well. By big, I mean MLX-16 and MLX-28 sets without local power. Oh and Michael, use your multimeter to get measurements from the power supply...just in case.

Tim Alberstein

http://www.dagwoodsystems.com

 

[papagigo1]

Tim,

The MM is located in carrier 2 slot 10.
Also in that carrier, ( 4 )408 and (1) 008opt.
The 408 cards have jst 20 MLX-16 sets in use.

Next step I'll test to see if the power unit "out put" is marginal.

Thanks for your thoughts on this.

Mike

 

[dagwoodsystems]

I'm only grabbing at things like power load and junk because I have a hard time trusting the preceding tech, especially when I'm called in at the eleventh hour on a busted switch. I look at EVERYTHING, which sometimes appears a little dramatic (but boy the customer never complains when I resolve the problem).

Jim could just as easily be right here. Maybe this was a one-time event that doesn't merit any consideration unless it happens again.

I just figured that you were on guard because you posted about it. You and I have gone 'round with email before, and you don't strike me as the kind of guy that takes the trouble to write about something unless the bug in the back of your head isn't quite dead.

Tim Alberstein

http://www.dagwoodsystems.com

 

[papagigo1]

Tim,

Your right, this one does "bug me" a bit and it's in another state to boot. Yesterday, after I got it working again, I downloaded the entire Voicemail system (via IP) and have ordered a replacement V4 card, just in case things get ugly..

Mike

 

[papagigo1]

Well Tim and Jim, it got "UGLY" over the weekend and the Merlin Messaging refused to boot no matter what I did. At times it would come alive and start to boot, then shut off. Last Thursday, when the trouble started, I downloaded the entire system to a common drive on our INTRANET, so that's all I had to do was swap the MM module and do a restore from the saved file. Worked like a charm.

To all,
Thanks for your tips and guidance.

Mike