Upgrading 3300 to new MCD 1

[IseeVoices]

We are changing out an LX controller with a NSU and per nodes to a new MXe controller. The LX is running 9.0 and the MXe will be running MCD 4.0. I am planning to take out the NSU and replace with a T1/E1 Combo Module. My question is 2 fold....1. Can I restore the saved database or do I need to import forms? and 2. Can the LX fiber modules be taken out and put in the new MXe controller because none were ordered, so are they interchangeable? Getting rolling on this project but this is what Im up against so far. Thanks

 

[kwbMitel]

LX to MXe is the easiest upgrade.

Make sure the MXe has the same IP as the original LX before restoring.

The Fibre Modules still work. (I think all modules are good to go but read the release notes to make sure)

Make sure you upgrade to MCD4.0 before trying a higher Rev.

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

 

[kwbMitel]

Here are some document notes regarding Migration from LX - MXe.


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 (or higher)
e> DSP may be moved from the existing platform to new platform.

Migrate from: LX (256, or 512 RAM), 250 User platform, 700 User platform

Pre-migration Steps
There is no requirement to pre-delete any programming from LX database; i.e. one can convert LX database to Mxe.

Post –migration step
a> After LX database restore, access System IP Configuration and program up the L2 switch IP address. The controller must be rebooted after changing the L2 switch IP address to make it effective.

b> If one is migrating from a platform with more than 250 IP device/user licenses, it is recommended that E2T card be installed on Mxe.



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

 

[SXWizard]

After you do the migration you can de-program the NSU and program the T1/E1 module.