Upgrading MXE to virtual in a cluster

[Joe King]

Hi
Has anyone done this. I have cleared all analogue services from the Mxe and have a backup. I know the hardware ID will need resetting by our vendor on the AMC. My question is the MXe is CEID 103. Does this get saved in a backup? Do I need to remove the MXe from the cluster after is has been backup?
Thanks for any help

 

[kwbMitel]

Are you replacing or migrating?

Based on your question, I think you want to move all the IP devices to the new virtual machine but retain the old machine for PSTN access or other physical connections.

It can be complicated and it can be done in a number of ways. What is the best way might depend on your environment

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

 

[Billz66]

I read it the other way - he wants to convert it from a physical to a virtual.
if thats the case can he not remove analogs and trunks from mxe
add virtualisation license to the ARID
create mxe backup and restore that to a new vmcd and is just asking about CEID information

I would think that will all be ok as long as the virtual pabx IP address remains as it is.



If I never did anything I'd never done before , I'd never do anything.....

 

[kwbMitel]

@Billz66

is this a typo? "if thats the case can he not remove analogs and trunks from mxe "

Actually, OP must remove those things and stated in the original post that it has already been done.

If not a typo, care to explain?

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

 

[sarond]

@Billz66

is this a typo? "if thats the case can he not remove analogs and trunks from mxe "

Maybe an Aussie thing
I understand this as "If that's the case, can't he just remove analogs and trunks from mxe"

I'm taking the OP as he wants to replace physical with a virtual.

 

[Billz66]

Sorry for adding confusion , i thought he meant migrate- take all data from mxe and stick it on vMCD ( except for analog and pstn trunks)
so to migrate he can just add virtualisation license release HW ID and restore backup to a vmcd

If I never did anything I'd never done before , I'd never do anything.....

 

[kwbMitel]

Oh I get your meaning now. He cant remove the analog if he intends to still use them after the fact.

He must remove analog to migrate the database, and then restore it if he wants it for future use.

What I interpret from OP

He took a backup of his system as-is
He removed all analog devices and hardware programming
He took another backup to be used to migrate the database to the vMCD
He restored the first backup to the currently running MCD to reactivate the analog services and trunks
He wants to restore the modified backup to the vMCD
He mentions clearing the HW ID on the AMC to do so.

(I've assumed he is aware of the virtual license requirement as such or at least "vendor" is)​

He asks if the Cluster information will be restored and if he will need to remove the existing MXe after "backup" ( I assume he meant restore)

Well, that's why I asked if he is retaining the original MXe for any purpose. That word "NEED". If not being retained the answers are Yes and NO with the additional tidbit that he should try and ensure that the new vMCD matches the original IP address

If he's retaining the MXe, and that is implied by the question, then everything gets a whole lot more complicated.

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

 

[VinceWhirlwind]

I did one of these recently, but I didn't want to perpetuate a large amount of config including redundant stuff no longer required, so I reconfigured it from scratch with only what was required.

Bear in mind it's in a cluster so a large amount of config is still there.

I didn't have to do anything with the CEID. Just promoted it to vMCD in AMC, followed a couple of steps out of the THB and it was ready to go.