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.
Like I stated earlier in this thread, I had avaya onsite with me to witness the problem first hand. A sysmon trace wont help because the 412 doesnt get the chance to boot up all the way to let the sysmon connect to it. We did manage to capture a dte trace on boot up. The tier3 tech escalated the problem to Research and Developement where it is under review. I did tell them how all of us are having the same problem. Its not an Isolated incident. They couldnt recreate the problem in their lab, so its still up in the air as to wheather its a hardware or software problem.... Ill keep you all posted here when I hear something.
I am interested to find out if it could be carrier specific as well. If I get lucky I will be able to bring my 406v2 to my PRI and test to see if it carrier or Avaya.
What I meant was, I think it has issues initially trying to establish clock on boot-up. This has happened to me on a 412 and Dual-PRI ONLY. On two occasions. However, once the PRI was programmed (trunks, etc, and proper clocking option chosen, all was well. It never needed to be worked with again. It was just intially adding a Dual-PRI on an already functioning site.
For clocking, you can have only 1 NETWORK and 1 FALLBACK. If multiple are set for NETWORK, it can cause issues.
Kris,
What exactly are you saying? What had to be setup before the problem went away? I'm only using the first port. I have the first port completely configured and functional, yet I still have the problem. Do i need to setup the second port as well?
I'd be grateful for any advice that could solve this.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.