N12 Card Alarms

I am receiving the following alarms in my 128 system:

MSG 10 MINOR ALARM CARD OFF 1 2
11:23 JULY17, 2006

MSG 135 MINOR ALRAM NET 24 ALARM RAI 1 2 4
11:23 JULY17, 2006

MSG 136 MINOR ALARM NET 24 ALARM RAI OFF 1 2 9
11:23 JULY17, 2006

MSG 132 MINOR ALARM NET 24 LINK UP 1 2 11
11:23 JULY 17, 2006

The N12 is connected to a Cisco 2620XM router with a V1MFT-T1 card and it has an AIM-VOICE-30 Module in it. Clear channel is provided to the system for signaling.

Any clue as to why the card is shutting down? I am at wits end on this one..... It happens every day.

Thank you for your assistance!

What type of DPLL daughterboard do you have? Is there a ONS or HONS in the system?

Hello SSPhone,

DPLL is 76-110-1322/3
Style A-0

No ONS or HONS.

There is a Stratum 4E DPLL Daughterboard that correct clocking issue on systems that have ONS cards. You can change the clocking to freerunning and let the N12 clock off the MPD to see if that makes a difference.

Also check the Clocking. Taking clocking from Telco is the best way. I'm ussally Free Runnig on the main Side and Primary on the far side.

I sure your splitting the t-1 with Data Because of the N-12 card. So check that the cisco isn't providing it over Telco or even if the have a channel extra programed.

Was this working fine before or a new install. If it was working fine, CHeck to see what was changed on the Data side.

The switch is set to FRRN. I have tried it on all clock settings and the result is the same. I have the cisco set to receive clock from the switch. So far no errors are showing up there. Only when the N12 restarts.....

This is a new install. FYI the cisco is providing voice/ip conversion and is providing a clear channel for signaling. Only the voice data is converted to ip. The main switch is also set to FRRN but it has a clock source from a pri. My branch location does not have a pri.

You tried primary clocking?

This works fine for a day and then the card turns off. Or it doesn't work at all.

Just guessing here, What version are you. I know that you can progran n-12 cards in sb7 but you need to be the latest 7, I think but, you should be at E2E atleast. Check with SS phones I don't have my chart and he knows all that stuff.

SSPhone, Yes I did try Primary but the results are the same.

tony3866, yes it works fine and then.....restart....then it works fine again. I can usually count on two restarts per day. I am using sb7.21 software on my laptop.

What's the version of the MPD's ( both sites). I don't think n-12 cards were supportted in early version 7 and maybe not at all. You might have to be E2E. I have to check when I get back to my office but I 80% sure about that. You should also get the latest SB7 software.

I have a SB7.36 128 with a N12 card to NY Verizon providing the T1 only issues I had was verizion and the Bell in NY couldn't keep the pipe up so we were seeing the same errors. FYI the last verision of SB7 is 7.42 there were problem corrections as well as feature changes thru the 7's. Telrad did a no cost upgrade to all users (thru the dealers of corse) with 7.20 to bring them to 7.36 which fixed several bugs. But that freebe was atleast 3 or 4 years ago. 7.42 chipsets are available just shipped out a set last month.

I remember that when the vendor came in to install our Emagen Voice Mail system they changed the chips. I don't know what they changed them to though. They also changed the Memory on the MPD units. I will have to wait for some downtime to pull the MDP to check what the chips are.

You can check on your laptop with no down time. Do you have access

Also check the frimware chips on the N12 while you have it down. They should be:
0.8(4B31) Frim
0.7(66A8) Main
0.7 (DEA3) Main

MPD400 at the Main Office:
V1 (E3AC)
V0.4 (763F)

128 at the Branch Office:
MPD 1.4 (ED46)
V1.0 (282A)

The N12s are:

0.8 (4B31)
0.7 (DEA3)
0.7 (66A8)

Please gives us the versions of the MPD 128 and the MPD of the 400. 7.XX

Hello,

On the 400 it is 7.23 with a handwritten "A" after the 7.23. This is on the module. The chips in the module have 7.39 printed on them.

On the 128 it has a "Printed" 7.20 with a handwritten 7.23 on the module.

Is there another way to check?

That's your problem. You need to be a higher version on the mpds software. At the very least 7.39

I will physically check the 128 today. I noticed these errors listed in the "display last reset alarm history" on the 128,

*** SOFTWARE ALARM MSG ***
FIRMWARE - ULD SOFTWARE ERROR
MSG (DEC) = 21 0 18 6 0h 5h F7h C1h 18h 1h 15:30 JUL 24,2006

*** SOFTWARE ALARM MSG ***
FIRMWARE - ULD SOFTWARE ERROR
MSG (DEC) = 21 0 18 6 0h 4h F7h C1h 18h 4h 15:30 JUL 24,2006

*** SOFTWARE ALARM MSG ***
FIRMWARE - ULD SOFTWARE ERROR
MSG (DEC) = 21 0 18 6 0h 4h F7h C1h 18h 9h 15:30 JUL 24,2006

*** SOFTWARE ALARM MSG ***
FIRMWARE - ULD SOFTWARE ERROR
MSG (DEC) = 21 0 18 6 0h 4h F7h C1h 18h Ah 15:30 JUL 24,2006

*** SOFTWARE ALARM MSG ***
FIRMWARE - ULD SOFTWARE ERROR
MSG (DEC) = 21 0 18 6 0h 4h F7h C1h 18h 5h 15:30 JUL 24,2006

*** SOFTWARE ALARM MSG ***
FIRMWARE - ULD SOFTWARE ERROR
MSG (DEC) = 21 0 18 6 0h 4h F7h C1h 18h Fh 15:30 JUL 24,2006

*** SOFTWARE ALARM MSG ***
FIRMWARE - ULD SOFTWARE ERROR
MSG (DEC) = 21 0 18 6 0h 4h F7h C1h 18h Ch 15:30 JUL 24,2006

*** SOFTWARE ALARM MSG ***
FIRMWARE - ULD SOFTWARE ERROR
MSG (DEC) = 21 0 18 6 0h 4h F7h C1h 18h 7h 15:30 JUL 24,2006

*** SOFTWARE ALARM MSG ***
FIRMWARE - ULD SOFTWARE ERROR
MSG (DEC) = 21 0 18 6 0h 4h F7h C1h 18h 8h 15:30 JUL 24,2006

*** SOFTWARE ALARM MSG ***
FIRMWARE - ULD SOFTWARE ERROR
MSG (DEC) = 21 0 18 6 0h 4h F7h C1h 18h Dh 15:30 JUL 24,2006

Is this being caused by having the wrong chips in the MPD?

Don't worry about these alarms.

You can check the system software in system utilities when you connected to the system.

Thanks!

In System Utilities it shows the software to be 7.39 in the 128. The 400 also shows 7.39.

I have to check to see if n-12 cards are supportted by that version. I'm 90% sure they are. Plust SS Phone has one working with 7.36.

Do you think I should pick up a Stratum 4E DPLL Daughterboad for my MPD at the Branch location? That is where I am getting the N12 shutdowns. The 400 does not have this problem.

You can try that. The 400 MPD comes with it built in. You need to be at least 7.36 on your mpd's (witch you are). I would try replacing the n-12 card or swapping them. The card shut down is where I getting me confused. I would think that all you would get is a link down MSG if it was a clocking issue.