MX Controller upgrade to MXe

[andy4uk]

Hi All,

I'm in the process of upgrading a customers MX controller to an MXe system.

I have completed a software and license upgrade onto the MXe, all the extensions bootup without any problems - however the T1/E1 looks to be fine until i plug the ISDN 30 line in, and all i get is a flashing green light.

The DTSTAT Read is showing link available........

Is the old T1/E1 still supported moving from an old system to a newer controller.

 

[MitelG]

I had a problem similar to this when I upgraded a system to MCD5 recently, the flashing green indicates layer 1 connection only, I orginally thought it was a problem with the circuit and got it reset but it turned out to be a problem with the link descriptor after the upgrade. I programmed a new descriptor the exact same as the old one and it came up, sounds strange but i've had a few issues like this when taking systems to MCD5.

 

[kwbMitel]

Did you follow the process?

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 [highlight #FCE94F]MUST[/highlight] 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 minimum 7.1.x.x
e> DSP may be moved from the existing platform to new platform.


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


**********************************************
What's most important is that you realise ... There is no spoon.

 

[LoopyLou]

What load of software you using? Not sure what you mean when you said you did a software and license upgrade. You restore a Release 9 database on MCD 4 on the MXe? or did you have 9 on the MXe and just restore the database?

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[Lundah]

Not related to the OP's problem, but falls under the topic:

Anyone come up with an elegant solution for converting the AMB/AOB interface when upgrading an MX to an MXE? The MX is an RJ-21 connector, the MXE (and II, and III) change that interface to individual RJ-11's. I'm looking for a good adapter to make the switch, does such a thing exist, or am I stuck just rewiring the whole thing back to the MDF?

 

[LoopyLou]

Lundah since the connection to the back of the MX is a 25 pair amphenol and you need a bunch or RJ11's for the MXe have you tried mounting a small patch panel at the MXe and plugging the 25 pair into it? Think Mitel even has a small patch panel the supply when you by an ASUII controller. If the sex of the amphenol is wrong you might be able to source a different patch panel or use a small "cheater" amphenol. Worst case with that is you have to shift position of some of your cross connects to line them up for the RJ11's.

When we get a new MXe we always get one of the Mitel patch panels and install it with the controller. We then use RJ11's to the MXe and run a 25 pair to the MDF where we terminate it. Sounds similar to what you need.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[Lundah]

Thanks, I'll look into it. Any chance you have a part number for that adapter?

 

[andy4uk]

Hi Guys,

Thank you for your responses so far, just to provide you all with more details.....

The old system is an MX controller with version 8.0 - as per KWBMitel I have gone through the Pre-setup conditions and the Pre-Migration steps, I have then completed a backup and completed a restore on to the MXe controller that has MCD 4.0SP4, which is licensed and has the same IP address.

Also as per MitelG i have also reprogrammed the Link discriptor and that too has made no difference.

Thanks for all your help so far guys.

Andy

 

[andy4uk]

Hi All,

Many thanks for all your help - it turns out the problem was the MXe Controller, we swapped it out and everything came to life.

Andy

 

[Lundah]

That's a new one. Thanks for the followup on the root cause. Any chance you tried putting the T1 card in a different MMC slot on the bad chassis?

 

[andy4uk]

Hi Lundah,

Tried that one - I completly removed all the programming of the T1/E1 card and started all over again......

After it didnt work again, thats when i thought it must be a faulty controller.

Andy

 

[LoopyLou]

51003344 -- 3300 ICP PATCH PANEL


I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.