Quick help needed with PRI expansion - Help!

[tmckeown]

I just installed a dual PRI card in our IP412 and now the stystem will not boot. The 412 flashes green then red and then scans the expansion ports. It keeps doing that cycle.
Did I miss something. I'm in a huge hurry to figure this out.

 

[IPGuru]

CrystalFusion, try double checking your CRC settings on your pri.
It is a long shot but I had exacly the same remove & reconnect the ISDN after a reboot problem on a system many years ago because CRC had been disabled.

 

[tmckeown]

You could be right. I just got a replacement IP412 and I'm doing some preliminary setup on it now. I won't actually make it live till tonight. I'm hoping it goes well, but I have some serious doubts. This should completely eliminate it being a hardware problem. I've already got 2 dual T1 modules and I have a second IP412.

I'll post again tomorrow, unless it goes horribly wrong and I need help.

 

[crystalfusion]

CRC checking is enabled on the IPO412.

 

[tmckeown]

Problem solved!
The new IP412 was able to boot with the dual T1 card installed; unlike our previous IP412.

It's interesting that the unit came with version 2.0 (16) firmware installed. Either way, I upgraded the firmware, installed all the cards, and it booted up fine. I can go home now. Hurray!

 

[crystalfusion]

Did you put the card in Slot A or B?

 

[tmckeown]

Slot A
I have not connected the T1 yet. We're working on that over the next few days.

 

[SuperJenks]

Plugging in the t-1 will be the true test.

 

[tmckeown]

Well, I plugged the T1 in and there are errors on the smart jack. I have not configured the T1 card in manager yet. There are a lot of options that I don't know anything about yet. I have some major reading to do.

 

[tmckeown]

OK, after a whole lot of messing around, I got the T1 functional. But here's an interesting tid-bit. I have the exact problem Crystalfusion has. If I reboot IP Office, I have to unplug the T1 and then plug it back in, or it will never come back up. That seems like a real problem to me. Maybe that's normal, but it seems like a problem to me.

 

[kristiandg]

I've had this issue before. DONT CONNECT the PRI CABLES until after you configure them. I've had the issue specifically on a 412 and we tried a couple of cards. Ultimately, it has to do with clocking.

Hope this helps...

Kris G.

 

[SuperJenks]

Kristiandg, Can you be more specific about clocking. Its more common to clock off the providers circuit. The PRI works and the customer makes calls fine. CRC is check as well as the CSU is activated.

 

[crystalfusion]

Not sure about the clocking since it doesn't affect my other installation. The 412 has the issue and the 406 does not. So the only differences are: carriers, 406 vs 412, and dual port vs single port.

Both my IP406v2 with single PRI card, and my IP412 with Dual PRI card have the same settings.

Clock Quality: Network
CSU Operation: On
Framing: ESF
Zero Suppression: B8ZS
Line Signaling: CPE
CRC Checking: On

 

[tmckeown]

Is it under Clock Quality? Coices are: Network, Fallback, Unsuitable

 

[crystalfusion]

I have used Network and Fallback and neither fixed the issue on the dual port card. Never tried unsuitable.

 

[photon33]

This is an interesting thread.

I have a 412w/PRI site happily running 2.1.27 for maybe the last two years, with no major problems. If the PRI went down I talked them through administrative reboot which brought the circuit back online.

I recently added a ds30 version 2 which required me to upgrade, so I went with 3.0.59 or 69.

The last time their circuit went down, a reboot would not bring it back up but I distinctly remember the IT guy saying he unplugged the rj45 from the back to bring it back up.

 

[crystalfusion]

photon, dual port card or single port?

 

[photon33]

It was a single port T1/PRI Interface, slot A if memory serves correctly.

 

[tmckeown]

So, does this seem like a software bug? or is it some configuration problem?

 

[crystalfusion]

I have a feeling it is a software bug. There could be some kind of fail over looping that gets turned on when the system reboots.

 

[tmckeown]

Have you ever presented any of this information to Avaya? Has anyone ever got a response?