need advice on upgrade from MX 6.1 to MXe 9.0 1

[brewski6666]

Hi there,
I am planning an upgrade from MX version 6.1 to MXe version 9.0
I project to proceed as follows:
- upgrade the MX from 6.0 to 8.0
- backup the MX ver8.0
recover FIM of the MX to install on MXe
-use the backup of the MX 8.0 to restore on MXe version 8.0
upgrade the MXe 8.0 to 9.0
am i right with the steps?
is there a shorter way to get the same result?
is there any thing else that i have to know or to check in order to be sure that every thing would be ok
thank you for your advice.

 

[slapin]

I would check with a VAR regarding licensing first.
You cannot move sysid module from MX to MXe because of completely different incomatible technology. MX has some sort of a chip (flash/ROM (I don't know)) and MXe has iButtonID module. So you will have to move all the licenses to another sysid through AMC or somehow else.

 

[brewski6666]

thanks slapin, i checked with AMC and because it's an upgrade for the same end-user, they told me that i will be able to move the licences from the old controller to the new one.
any thing else?

 

[kwbMitel]

Here is an excerpt from a Mitel Document on the subject.



Mxe Database Migration Guideline

This document is to provide a general guideline to determine which 3300 programming data need to be de-programmed before migrating database between 3300 platform types. The reason for these pre-migration steps is mainly due to different types of hardware level support such as AMB, the number of voicemail ports, compression, the build-in L2 switch, to name a few. This document is not intended to supersede the software release note. If one is migrating across major software release, Mitel strongly recommends reviewing all release notes and the corresponding pre-software upgrade checklist accordingly.

Pre-Setup Conditions
a> Before migrating database to a new platform, IP address assigned to RTC on the new platform MUST be set to be the same as IP address of the original platform.
b> System Name is recommended to be the same, which is programmed in Network Element Assignment
c> Sys ID on platform LX and I-button used on Cx/Cxi/Mxe/AX are not interchangeable.
d> Software version is 7.1.x.x
e> DSP may be moved from the existing platform to new platform.

Migrating Mx (100 user/200 User)

Pre-migration Steps
On MX controller, you must deprogram all embedded analog (AMB or AOB) programming as follows:
i> In the Analog Services Unit Configuration form, determine which unit is used (default unit - n is 4 ) and whether expanded analog is programmed
ii> In Telephone Directory Assignment, perform export of telephone directory if you need a backup copy. Then remove all telephone directories associated with extensions from step <i> above.
iii> In Analog Set Assignment, delete all extensions associated with AMB and/or AOB unit ( n –1-1-x, n-1-2-x)
iv> In Analog Trunk Assignment, delete all trunks associated with AMB and/or AOB unit n ( n-1-1-x, n-1-2-x)
Tips: You may have to delete trunk group first (if applicable)
v> In Miscellaneous Assignment, remove n-1-3-1 provided that MOH source is from AMB
vi> In Loudspeaker Assignment, delete paging zone n-1-4-1 ( if applicable)

Once AMB/AOB is deprogrammed, back up the database and restore the newly backed up database to Mxe.

Post –migration step.
a> After MX database restore, access System IP Configuration and program up the L2 switch IP address
b> Program the AMB in Analog Services Unit Configuration as 3300 embedded analog and/or expanded analog if applicable. Then program ONS, LS, MOH, loudspeaker associated with the new AMB and/or AOB if applicable.
c> The controller must be rebooted after changing the L2 switch IP address to make it effective.







*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[brewski6666]

thanks kwbMitel, it helps me a lot