AlfredSpecial
Programmer
Does anyone here know of a way to upgrade from an MX to an LX controller other than having to do a whole new retype?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
3300MX to 3300LX upgrade advise
- Thread starter AlfredSpecial
- Start date
- Status
MitelInMyBlood
Technical User
Chapter 4 in the 3300 Tech Handbook seems to cover this.
Doesn't appear to me that a "retype" is needed at all.
Datasave
Data Restore
If you move the HD over from an MX to an LX you have to manually install the system software, but that's pretty easy.
As long as you have a datasave on some external device (ftp server comes to mind) it should be a relatively simple process.
Doesn't appear to me that a "retype" is needed at all.
Datasave
Data Restore
If you move the HD over from an MX to an LX you have to manually install the system software, but that's pretty easy.
As long as you have a datasave on some external device (ftp server comes to mind) it should be a relatively simple process.
- Thread starter
- #3
AlfredSpecial
Programmer
sorry but i asked the wrong question, i meant to ask can you upgrade from a 100 user controller to an MX controller without having to do a retype?
MitelInMyBlood
Technical User
Yes you can, I have done it.
The core O/S is the same.
The SysID module is the same.
The customer database format is the same
The hardware platform of the MX controller is more robust, supports more users, faster processor, etc.
I believe you can also move the hard drive over if you're so inclined, tho I wouldn't.
Just make sure you have a good datasave (I always make two just to be safe, in two different locations) then power-down the 100-user controller.
Pull the cover off (per the procedure in the Tech Hbk (that one is a little tricky) then pull your SysID module (1 screw) and move it over.
Any MMC boards in the 100-user will move as well, i.e., Dual FIM.
Power the MX up and then perform a MANUAL software install (again, per the tech handbook).
Once you have the software installed then perform a data restore from your saved database.
Upon completion of the data restore the box should perform a spontaneous reboot and then come up.
All in all you're going to be down a couple hours start to finish.
Just me, there's enough hoop jumping going on here without complicating things with AMC.
Therefore I probably wouldn't attempt putting 6.1 on the new box until after you get it up and running with the customer's database and let it run a week or two.
Something else, don't try to be a hero by trying to jump the customer's database from a 3-dot load all the way to 5-dot or 6 in combination with this hardware upgrade.
Elephant is best served one bite at a time; if you want to be at 6.0 on the new box then I'd upgrade the customer to 6.0 now (on the 100-user controller) first before moving him across so you can do your datasave at the same O/S rev level you'll be introducing the database to on the MX before.
If you're jumping multiple loads in this upgrade be sure to review the Release Notes on all the interim loads.
I know Mitel sez this hardware switcheroo in combination with a multi-stream upgrade/data convert all in the same breath will work, but I sure wouldn't try it.
I would upgrade the software first, (on the 100-u) let it stabilize a few days, then get a datasave and then do the hardware exchange.
The core O/S is the same.
The SysID module is the same.
The customer database format is the same
The hardware platform of the MX controller is more robust, supports more users, faster processor, etc.
I believe you can also move the hard drive over if you're so inclined, tho I wouldn't.
Just make sure you have a good datasave (I always make two just to be safe, in two different locations) then power-down the 100-user controller.
Pull the cover off (per the procedure in the Tech Hbk (that one is a little tricky) then pull your SysID module (1 screw) and move it over.
Any MMC boards in the 100-user will move as well, i.e., Dual FIM.
Power the MX up and then perform a MANUAL software install (again, per the tech handbook).
Once you have the software installed then perform a data restore from your saved database.
Upon completion of the data restore the box should perform a spontaneous reboot and then come up.
All in all you're going to be down a couple hours start to finish.
Just me, there's enough hoop jumping going on here without complicating things with AMC.
Therefore I probably wouldn't attempt putting 6.1 on the new box until after you get it up and running with the customer's database and let it run a week or two.
Something else, don't try to be a hero by trying to jump the customer's database from a 3-dot load all the way to 5-dot or 6 in combination with this hardware upgrade.
Elephant is best served one bite at a time; if you want to be at 6.0 on the new box then I'd upgrade the customer to 6.0 now (on the 100-user controller) first before moving him across so you can do your datasave at the same O/S rev level you'll be introducing the database to on the MX before.
If you're jumping multiple loads in this upgrade be sure to review the Release Notes on all the interim loads.
I know Mitel sez this hardware switcheroo in combination with a multi-stream upgrade/data convert all in the same breath will work, but I sure wouldn't try it.
I would upgrade the software first, (on the 100-u) let it stabilize a few days, then get a datasave and then do the hardware exchange.
- Thread starter
- #5
AlfredSpecial
Programmer
thanks,
Mitel told me you could not restore from a 100u to mx.
Mitel told me you could not restore from a 100u to mx.
MitelInMyBlood
Technical User
Why not?
It would seem like a perfectly logical upgrade migration path to me, besides, I've done it.
OK a fine point here perhaps; the hardware upgrade I did was from a 100-u chassis to a 250-u chassis at software level 5.1.3.7, which was done prior to the actual "MX" designation and we did it via a hard disk and SYSID swap.
I would think awfully odd that you wouldn't be able to do this.
It's the exact same sx2000 call control and hence should be the same database structure.
Who told you can't do it, a dealer or Mitel Product Support in Kanata?
It would seem like a perfectly logical upgrade migration path to me, besides, I've done it.
OK a fine point here perhaps; the hardware upgrade I did was from a 100-u chassis to a 250-u chassis at software level 5.1.3.7, which was done prior to the actual "MX" designation and we did it via a hard disk and SYSID swap.
I would think awfully odd that you wouldn't be able to do this.
It's the exact same sx2000 call control and hence should be the same database structure.
Who told you can't do it, a dealer or Mitel Product Support in Kanata?
- Thread starter
- #7
AlfredSpecial
Programmer
Mitel Support UK said an upgrade from a restore is not possible.
The MX does have the provision to install the internal boards for ONS and LS trks. That might be the only reason you could not upgrade to a to an MX. If there was some type of conflict in the software. Otherwise I agree, you should be able to upgrade.
MitelInMyBlood
Technical User
I can understand how that could be the problem; the one I upgraded from a 100-u did not have the embedded AMB; mebbe it wasn't really an MX
Strange tho that the Tech Handbook mentions no such restriction or limitation.
Mitel Leader-Led training for years often didn't give you the answer but prided itself on teaching the student how to find the answer in the product documentation.
If the answer is there, I can't find it and I did look.
Time to peruse the Engineering docs.
Strange tho that the Tech Handbook mentions no such restriction or limitation.
Mitel Leader-Led training for years often didn't give you the answer but prided itself on teaching the student how to find the answer in the product documentation.
If the answer is there, I can't find it and I did look.
Time to peruse the Engineering docs.
- Status