Local only DN for migration to GDM

[PureChimpie]

I am tidying up a cluster (15 x MCD's) in preperation for a migration to GDM. They are currently running MCD4.0 SP2, they will be upgraded to MCD4.0 SP4 before migration. I have a slight issue with the local only dn form. They use the same vm ports within the cluster 7021 onwards with no tel dir entry, so it's not populated to the cluster. I have made all these dn's local only, but they still come up in the MIGRATION PRECHECK. I can't remember if the SP4 load resolves this issue? I seem to remember having to delete the ports on SP4 and then re-create them and making them local only in this process??

I also have an issue with dn 0. They use this accross the cluster as a key appearance on consoles. Again, I have made this local only but flags in precheck?

 

[LoopyLou]

Think the recommendation is that you should go to MCD 4 SP4 before conversion to GBM so if that is the case you could try one site and run the migration precheck after to see if it is fixed.

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.

 

[PureChimpie]

Def upgrading to SP4 for the migration. I am doing all my precheck work on the existing SP2 load, then using the online upgrade to SP4 which will give me a nice rollback if the migration doesn't go well (SWAP). I've logged a call with Mitel to clarify and will feed back any info.

 

[bobcheese]

Just because they don't have a tel dir entry doesn't mean they are not populated to the cluster. If the sharing scope is set to share at the cluster level then the info will be shared. At least that is my understanding of it. Can you not just change the sharing scope for that form? Or exclude that range from the sharing scope?

 

[LoopyLou]

You check that the numbers don't appear in the remote dirctory number form of the other systems?

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.

 

[jrgood0852]

Do not make any local onlys! I ran in to the same issue and had to delete them before I could proceed. Get rid of them.

 

[kwbMitel]

Ok, my 2 bits

Def upgrading to SP4 for the migration. I am doing all my precheck work on the existing SP2 load

This is not necessary. The SP4 load was specifically introduced to accomodate MXeIII upgrades. Prior to SP4, you could not upgrade older moders with 256Mb Ram without using another compatible system for 4.0. The SP4 load has a nice checklist for upgrading but that is not worth the extra effort alone.

Just because they don't have a tel dir entry doesn't mean they are not populated to the cluster

Yes and no.
NO - Any DN's that are designated by the Migration Pre-check as unnamed, will be designated as local only after migration unless they are named first. You do not need to know what they are. Simply add a name such as NoName to each of the DN's and worry about it later.

YES - Any stations created after migration will be shared regardless of whether or not they are named, unless designated as local only.

They use the same vm ports within the cluster 7021 onwards with no tel dir entry, so it's not populated to the cluster.

Personally, I would renumber the VM ports so that they are unique and let them share.
System 1 renumber to 1*7021
System 2 renumber to 2*7021
System 3 renumber to 3*7021
you get the idea

Then you use speedcalls on the local system to dial the local VM hunt group and designate the speed call as not shared so that the same code can be used on each system.

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

 

[PureChimpie]

I have allocated seperate dn's for vm ports and none set as local only. I do have an issue still with using dn 0 on consoles, this flags a precheck error, although set as local only. Mitel believe upgrading to SP4 may resolve this? Alternatively, it can always be deprogrammed prior to migration and then added back in.

On none GDM model, numbers are not populated to the cluster without tel dir entry.

Thanks for your responses community!

 

[kwbMitel]

Again, to get around the dial zero problem

Designate the LDN on the console as a unique DN on each system

Use Speedcalls for zero that are not shared.

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

 

[PureChimpie]

I will give that a whirl, thanks.