3300 CXi on MCD 5.0 SP2 PR2 upgrade to 3300 CX 11 MiVB 9 1

[floppy1]

Hi

I have studied the migration documents and completed the update course I have also read most / all posts relating to this here but as this is the first upgrade to MiVB 9 I thought I had better seek further advice / reassurance.

I have a new platform on the way 3300 CX 11 with the correct HDD and RAM.

Looking for the most efficient way to upgrade with least amount of down time. I assume the new controller will be shipped with either MiVb 7 or 8 and my thinking is to simply take a backup of the current MCD 5.0 database and restore to the new controller. I think that this will be ok but would appreciate confirmation that this is doable or not.

Assuming this is ok I would then licence and sync the new controller on the current ARID then go ahead and run the migration tool to install MiVb 9

There is no obsolete hardware / devices on the current controller but there is the question about the 5212 IP phones although looking at posts here I think these will work but not supported. There is also some mention about MMC digital trunking cards in the migration document that I am not entirely clear about. The old controller has a MMC T1/E1 card T1E1 Resiliency-DSP-VEC-STRATUM4 MMC

I am aware that when running the audit it would bring any unsuitable hardware to light but I would rather know ahead of time so I can source a new card if required.

Thanks for any advice in advice.

 

[kwbMitel]

You will have to license before you restore but other than that you should have no difficulties

 

[floppy1]

kwbMitel


It's a relatively small system and I think we will have enough licences in our licence bank to do this. If not I can proceed anyway.

Thank you

 

[kwbMitel]

You can use the licenses from the existing system for the new system

 

[floppy1]

kwbMitel

Change of plan as we don't actually have enough spare licences to proceed as previously described.

I am going to

1. take a backup from the existing MCD 5 CXi controller
2. move the ISDN card from the existing CXi controller to the new CX11 controller
3. restore the back up to a new CX 11 controller reset the hardware ID and sync / licence the new controller on AMC
4. take another backup probably not necessary but just in case
5. proceed to migrate to MiVb 9


I was expecting to use a new CXi 11 controller but our stock guy got the below from Mitel although the current CXi controller has only 512 ram

Product Replacement

The Mitel 3300 CX II Controller with 1Gb RAM (part number 50006729) with an appropriate ethernet switch is a full replacement for the Mitel 3300 CXi II Controller with 1Gb RAM

Thanks for your input.

 

[kwbMitel]

Again, you do not need to take the Cxi out of service for licensing. The licensing can be duplicated

[ol 1]
[li]take a backup from the existing MCD 5 CXi controller[/li]
[li]reset the hardware ID and sync / licence the new controller on AMC[/li]
[li]restore the back up to a new CX 11 controller[/li]
[li]proceed to migrate CXII to MiVb 9[/li]
[li]Replace CXi with CXII after moving ISDN Card[/li]
[/ol]

 

[floppy1]

KwbMitel

Thanks for confirming I was not entirely sure if I could duplicate the licencing on the same ARID

I will follow your procedure and licence the new controller in advance of the migration and hardware move

 

[floppy1]

KwbMitel

There is no reason that I cant set up the new controller and migrate it to MiVB 9 in the lab then take it to site the following day and move the ISDN card with very little down time ?

Sorry to keep adding to this post and I have done many upgrades but am very cautious for some reason with the new MiVb 9 probably as a result if some of the posts I have read relating to MiVb 9

 

[kwbMitel]

Yes you can upgrade the system to rel 9 offsite and then do the hardware replacement with little down time

 

[floppy1]

Thank you KwbMitel

 

[Valamagules]

Just remember to resync the existing ARID back to avoid any license violations.
but yes KwbMitel is pot on there.

Clever men learns what Wise men shares!

 

[kwbMitel]

No, you do not need to resync the license back, unless you exchange the SYSID's which is not necessary

 

[floppy1]

KwbMitel

I was aware that this is the case but I am grateful for your confirmation.

I intend to disable auto sync on the existing controller by removing DNS and confirm by trying to ping sync.mitel-amc.com from it just in case it tries to sync before I get to site although I intend to do my pre configuration on the day before I deploy the new controller.

AMC and Mitel licencing support confirm that this will be ok.

The job has been pushed off for a week or so but I will post again when complete.

Thanks to all

 

[kwbMitel]

Once you sync the new controller to the AMC you do not need to worry about the old machine unless you clear the hardware ID. No need to disable sync as it will fail regardless

 

[floppy1]

Once again thank you KwbMitel for confirming this as I was not entirely sure as to whether or not I should disable auto sync in these circumstances. I am probably being over cautious but as they say better safe than sorry.

I would like to award you a star for being so helpful and patient.

 

[John Keri]

Before you do anything else, run the Migration tool's precheck against your new system.
The suggested migration path is from 7.2 to 9.0 using the Migration Tool that is a modified version of the Software Installer.
You should be able to restore the backup from your old system to 7.2 in the CX II before migrating it.

 

[floppy1]

Hi John

I did intend to run the pre migration audit anyway and thank you for the heads up regarding the compatible SW level to upgrade from !

It's interesting that the Mitel own documentation contradicts this but documentation even from Mitel can be flawed.

Database data conversion is performed during upgrade from a previous release to release 9.0. The MiVoice Business Migration Tool aids customers who are migrating from a MiVB system that is running releases supported for upgrade (i.e. release MCD 6.0 UR3+, MiVB 7.0+ and MiVB 8.0+) by auditing the existing system to see if it is compatible with MiVB 9.0.

 

[John Keri]

Software development is a backward compatible process.
That actually means the same as hindsight is 20/20.
After the fact and a pile of support cases, they might build something that works.
This should be a two-stage process, one to convert the systems boot and a separate one for the database.
Even if we use the same migration tool to perform both steps.
This way you would have a logical place for boot upgrade reversal and restore of the original database.

For now, especially if you have Tech Support coverage, run the precheck and review the report.
- also, in the Migration tool help search for the page that has all the error messages listed and actually explained, can be very useful

 

[floppy1]

update

Migration successful and system deployed no issues thanks to all for assistance.

As long as you follow the migration guidelines and the migration tool help files in detail not much to catch you out. Slightly interesting way to point the migration tool to the new software load directory but again the migration tool help files explain all.