replacing controller MXe 11 MCD 4

[floppy1]

Hi

Apologies for the long post and my lack of knowledge in this regard despite extensive trolling through documentation I have some unanswered questions regarding this issue.

I have a MXe 11 controller that I need to replace. It’s currently running MCD 4. The backup controller is new although been on the shelf for a while so is on 9.0.

I wanted to upgrade the backup controller to MCD 4 using the SI tool before I change it out and swap the I button and so on. My question is regarding licensing can I do this before changing the hardware ID on AMC and swapping the I button. What I propose to do is

Upgrade the spare to MCD 4 “ can I use the same options password as on our current controller “ all licensing was done offline

Restore it with a backup of our current config

Swap out the faulty controller and change the I button, Embedded PRI card etc. I suppose I could just move our current HD into the replacement controller and save a lot of time.


Background. The controller is giving false alarm indications on the front panel. No alarms when checking via system admin nor are there any logs to indicate an issue.

Alarm LED alternates from red, orange to amber constantly

Disk activity LED constantly green

Power LED always red

Any advice / suggestions would be very much appreciated

 

[kwbMitel]

Don't bother with the upgrade to the second controller.

Swap the hard drive out as well.

This also gives you a fallback position should it not work.

If the Controllers have E2T cards, don't forget to modify the IP Address for it/them

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

 

[floppy1]

Thanks kwbMitel

I've come to the same conclusion it seems unnecessary to overcomplicate this.

More than anything else I wanted to know if the upgrade and licensing could be done on the spare box using our current application ID options password.

AMC say no support say yes it can be done ??

No ET2 in this case

 

[RossBC]

I have never tried to change the hardware ID on the app record to the iButton of your backup machine so you could have two controllers running at the same time with the same licensing. I am not sure if they would then let you re-use that original iButton for another system later, I think not.

as you are probably aware, the app record password (and options) is tied to the iButton (hardware ID)
if that iButton is not in the controller at the time you try to license it, you won't be able to apply the password.
if the licensing is not done before you try to restore it, the restore will fail (if plugged into the RTC maintenance port you will see "*****BAD DATA******BAD DATA****" when it restores.)

if you want to swap controllers, and not reuse the existing hard drive because you suspect it, then I think the fastest way to do it would be this.

do a manual upgrade(don't use the SI) on the new controller to the same or a newer software as the old controller and then shut it down, remove the cover and iButton.
backup the old controller and then shut it down and remove its iButton and install in the new controller.
power up the new controller and apply the licenses.(don't forget the Networking and the MiTAI/TAPI Computer Integration at the bottom). then restore your database.
expect to be down for about an hour.

also remember that the IP configuration is NOT tied to the database backup or the hard drive.

 

[floppy1]

RossBC thanks for your suggestions.

I think this is the procedure I would prefer and will give it a go on Saturday. Thanks for the reminder re : IP config form !

 

[kwbMitel]

Floppy, The application license is tied to the I-Button not the hardware. It is quite legitimate to move the hard drive and I-button to another chassis.

If you move the hard drive, the upgrade of the second chassis is not necessary. These leaves you with the greatest flexibility should your issue also occur on the backup machine.

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

 

[floppy1]

KWB

I agree that moving the hard drive will not only eliminate having to upgrade but if the issue persists we will know the hard drive is the problem and not the chassis and I agree that this may be the best approach from a troubleshooting prospective.

Management here are looking for a quick fix thus the rather unorthodox route I was initially exploring. I think I may have to be a bit more assertive on this one.

 

[kwbMitel]

As your issue is cosmetic rather that service affecting I would very strongly recommend the cautious approach. You don't want to be introducing new issues that may be service affecting for the sake of some strange lights.

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

 

[floppy1]

Thanks guys for you assistance

On reflection I agree with KWBMitel and will convince the powers that b that the cautious approach is the way to go.