Move TFTP firmware from vMCD 6.0 to MXE 5.2 before upgrade

[FrankGrimes]

I have to upgrade a MXE to version MCD 6.0 from version 5.2. I have 600+ phones broken up into 3 handsets each on very slow sites.
So the firmware upgrades are going to take at least 8 hours. I wanted to speed up the handset firmware upgrades but moving the firmware from a version 6 unit into the 5.2 and allowing the handsets to start upgrading as they're plugged in and out.
I can log into the TFTP of both unit but don't know where to start.

http://www.tek-tips.com/threadminder.cfm?pid=1329

 

[bobcheese]

sorry to sound pedantic but define 'very slow sites'? Nature of VOIP means you will need minimum 90kb per call (uncompressed) so in theory you should have minimum 270kb bandwidth per site.

How have you calculated 8hrs?

 

[Lundah]

What about running the TFTP server closer to the sets? SolarWinds has a decent free TFTP server that can be installed on a PC, then you just need to update the DHCP options to point to the appropriate TFTP server. You can even do this just for your upgrade then change the DHCP options again after you're done.

 

[FrankGrimes]

Bobcheese. With G729 you only require about 25kb per call, but QOS is setup on UDP tagged traffic so the upgrade will go in with everything else. As for slow I'm talking about 512kbps sites. So 600+ phone over 400+ sites, the MXE is only able to upgrade a few phones at a time therefore the last site will take about 4 to 8 hours to upgrade.

I can't stick a TFTP server closer as the phones have static assigned ICP and TFTP details to the MXE. What I was hoping for is upgrade half the hands over a month, while the handset log in and out. Then upgrade the MXE and force the other to upgrade cutting down the down time by at least half.

 

[Billz66]

Frank

I would suggest that to avoid these issues moving forward that you start changing them from fixed IP to DHCP .
Do it as a project site by site .
Set up some remote TFTP servers and change each sites from fixed to local .
Otherwise I don't see that you have much choice but to endure the outage whilst they upgrade.

I think that will mean that you may also need a local router that can handle the Mitel options or you could supply a small footprint linux box to do both tftp and dhcp.

If I never did anything I'd never done before , I'd never do anything.....

 

[FrankGrimes]

I moved the 5324 (also the 5312) firmware files from a vMCD and imported them into the MXE. The upgrades are happening as the handsets are rebooted, so one at a time. In a weeks time I'll do the big bang but this should at least keep the load down and the outage to a smaller block of users.

I can't use TFTP as the local modem doesn't options within DHCP.

Your signature comment inspired me. "If I never did anything I'd never done before , I'd never do anything....."

 

[LoopyLou]

Be aware that you may experience some issues until the MCD is at 6. It will depend on how many changes are in the MCD 6 firmware ( if any ) as opposed to MCD 5 and if the changes depend on anything in the MCD 6 code.

An apple a day keeps the doctor away. Anyone else and you need to throw it harder.

 

[FrankGrimes]

I setup a small test group and users with the new firmware, and they actually use DHCP so I point the TFTP at the vMCD. It worked for three months.
More then 200 handset have already gone across, no complaints.

 

[LoopyLou]

Good work. Not enought for a star though. Sorry

An apple a day keeps the doctor away. Anyone else and you need to throw it harder.

 

[BrianWarner]

I always thought the firmware was downloaded to the phones. I never realized it was to the handsets.

 

[Billz66]

by handsets they mean the phones ( not the handpiece)

If I never did anything I'd never done before , I'd never do anything.....