IP Office 406 Upgrade problems - System Down!

[JustAMan]

Hi all,
I'm new here, and new to IP Office - I'm a network guy who's getting his butt kicked by this phone system.

For the past year, we have had an IP Office 406 V2 PCS 12 running 2.1(27) with a single 16 port DS expansion module. The expansion module quit working after an equipment move and while troubleshooting I discovered the version being very out of date. I decided to try to upgrade in an attempt to restore the expansion module. I was able to upgrade the first control unit (IP 406 DS) to 3.0 (999), but the second and third control unit are still on 2.1(27), not to mention my expansion module (control unit 4) is still missing). We were down to 8 lines, now we're down to 0.

I am at a loss, been scouring these forums and trying to understand this thing. Can anyone offer assistance how to get all control units upgraded?? Now of course, my phones do not work since the software versions do not match.

Working until it's fixed, please help

 

[mforrence]

Do you realize that 3.0 (999) is not really an operational version, but rather a loader upgrade? This is why Business Partners exist...

 

[JustAMan]

Your point is well taken, and we are likely going that route at some point, perhaps sooner than expected. We were sold this system by a vendor who said it's no problem to install...

Meanwhile, tonight, it would be great if I could get it reverted to 2.1(27), or upgraded to an operational version. I can't seem to find a place to download old versions, and apparently the backup I made was of a newer version, not the currently running version, 2.1(27). So, we continue to be down. Any thoughts on where I can obtain the older version to restore?

 

[Telecomboy]

If you still have your manager from 2.1.27, use it to downgrade. Otherwise, Avaya's website has 3.2 on it.

 

[JustAMan]

I was just able to upgrade to 4.1(9), which did upgrade all three control units. We are back to operational with the 8 phones. The 16 port expansion module (IP400 DS) continues to be MIA, I'm not sure what else to try short of replacing it. For tonight, at least we are operational again.

Thanks for reading!

 

[tlpeter]

Outch, you have learned the hard way!!!

Do you see the DS16 when you try to open a config?
What color is the led in front of the DS16?


BAZINGA!

I'm not insane, my mother had me tested!

 

[JustAMan]

During boot, the DS16 flashes it's lights and then ends with the middle light solid green, also all handset ports which are connected are solid green.

The DS16 does not currently appear in the configuration for the IP406. Here's how that went though. It did appear as control unit 4. After the equipment move, the phones from the DS16 did not operate. While troubleshooting, the expansion cable was moved to various ports (1-6). The DS16 still appeared as control unit 4, but the phones from that unit would not activate. I read somewhere that the DS16 would be auto-detected if deleted as a Control Unit, so that is what I did, but it has never auto-detected it again. I also ordered a replacement Avaya blue RJ45 cable, as I think the original was lost in the move and a standard Ethernet cable was being used. Still, it does not appear in the control units and the phones do not activate.

The boss has told me to order a replacement expansion module, but I want to be sure it is actually bad and not just a config issue. Any ideas?

 

[tlpeter]

Then i think it has lost it's software.
I think you better hire a qualified engineer to solve this for you.
This engineer can bring a new DS16 module with him in case it is broken.


BAZINGA!

I'm not insane, my mother had me tested!

 

[amriddle01]

Bear in mind you always need to power off before connecting or disconnecting expansion modules, they aren't hot swap

 

[JustAMan]

Just as a follow up - I followed these steps -

http://www.tek-tips.com/faqs.cfm?fid=7085

and could never receive anything but TFTP Poll Failed. I know the TFTP is functioning as the HoldMusic.wav file keeps getting transferred. I also built new config files trying different expansion ports, so I'm guessing we have a hardware failure somewhere in the expansion unit - it can't seem to communicate to the IP406. I will order a replacement module. Thanks for the help!