Option 11c freezes

[nightwolf91]

I have an option 11c rls 25 with 3 expansion cabinets that freezes for no apparent reason. This has been going on for awhile but seems to be becoming more frequent. It was a year between the 1st & 2nd, then 6 months for the 3rd, 3 months for the 4th, then one month for the next and now just today it was just over a week since that last freeze.

My tty 0 port does not work although it shows enabled. I have built other tty ports on the other cabinets and they work fine. The date and time is correct on the sets and all the programming for the sets is displayed, just cannot process any calls. All leds on all the cards are green. I have reseated the ssc card to see if this would fix the tty 0 port. I have replaced the cable for the tty 0 port. When the system fails the monitor I have connected to tty 1 shows MSDL0457 xxxx xxxx xxxx xxxx etc. continually repeating. Powering cycling the system restores everything and it works fine until the next event. I have gotten the following code on the monitor shortly before one of the times the 11c went down : err5234 aml 9 prio 8.

I also am running Meridian Mail 13.

Does anyone have any suggestions as to why this is happening?

Thanks.

 

[bignose21]

I would suspect the SSC card. Back it up and get the card changed out.

The only other thing I have had but usually causes a reboot is CDR enabled but no device collecting it causes Buffers to fill to the point that it stops processing calls.

 

[nightwolf91]

Thanks for the reply bignose21. I had my suspicions about the ssc card since tty 0 seems to be dead. I am using Genesis for call accounting which has been working fine. I will get a replacement ssc card and change it out.

 

[RKDavis]

Continually repeating MSDL errors can cause a system to crash or appear to frezze. This is what the MSDLerror means : MSDL0457 <first 16 words of msg> The MMIH has found a buffer in the Rx Ring message
queue with an expired timestamp. The SL1 application has not processed the
buffer's content promptly or the SSD message to the SL1 task was lost. The
buffer's timestamp is reset and the buffer is returned as a free buffer. The first
16 words (32 bytes) of the discarded message are printed, 8 words to a line.
Action: Check the traffic reports. Excessive traffic can cause a delay in the core
CPU.
Severity: Minor. Critical to Monitor: Yes. SNMP trap: Yesck up due to using up real time.

RKDavis Wilmington,NC

 

[Firebird Scrambler]

I've found this below that may be a clue?.

MSDL0305 X Y indicates that the Processor is being bombarded with D Channel Messages.
These could be ISDN FACility messages Ping Ponging due to a clash of DSCs in the NWK.
Check the DCH messaging.

MSDL0457 (not in the NTPS) generally relates to a hardware problem, but may be associated with the MSDL0305.


All the best

Firebird Scrambler
Meridian Programmer in the UK

http://www.linkedin.com/in/davidbromley

If it's working, then leave it alone!.