This page provides some additional information to the Wrangler UCMC Migration User Guide for Cluster Consolidation migrations specifics only.
...
For Map migrations (selected by Use Map - Map Source Dialplan to Existing Target Dialplan / Do Nothing option from Dialplan Configuration field), it is a requirement that a dialplan Dialplan has already been configured in the target UCMC cluster to allow for mapping of source clusters dialplan Dialplan objects to the target dialplanDialplan.
To start a Map migration
Select the CUCM source interfaces of CUCM’s to be consolidated in the Source Clusters CUCM Cluster Publishers fields
Select CUCM target interface target in the Target Clusters CUCM Cluster Publishers field as per single migration.
Name the migration in Target Customer Name field.
Enter Countries in Initial Countries field.
Select required Dialplan migration option from Dialplan Configuration drop down, noting that Clone - Clone Source Dialplan migration option, whilst can be selected is not supported for Consolidated cluster migrations.
On Completion of Initial Discovery/ Allocation/ Validation, in addition to any issues experienced with a single cluster migration, any duplicates between the source clusters will be displayed
...
On completion of validation any sequencing issues are displayed and dealt with by selecting the Move Obj To “Before Any Sites Loaded” or View X Dependant Object button. This is described further in the Migration User Guide Wrangler UCMC Migration User Guide
Any duplicates here may be reviewed by selecting the Review Duplicates button to investigate further before selecting appropriate copy; or
...
Only issues specific to consolidation are mentioned on this page, for all other, refer to Wragler UCMC Migration User Guide here Wrangler UCMC Migration User Guide
Staged Migration
If for some reason, a single consolidated migration as per above can not be performed, it could be that not all source clusters that are to be consolidated can be accessed at the time of the first discovery or such, a possible approach is to perform a single migration first. Then using this migration as the consolidated dialplan for further migrations.
There are a number of variations to this option.
The Initial migration as Clone Migration or Template/ Simplified Dial Plan migration with this used as master dialplan for consecutive (mapped) migrations
A new dialplan could be deployed manually (or by engineer developed tools). The initial and consecutive migrations could then be performed as separate Mapped migrations.
Separate Clone Migrations but to the same target. This would not be a recommended option as the target cluster would end up with a separate dialplan for each source cluster migrated.
| Info |
|---|
For consecutive migration, duplicates between the new source clusters and the target cluster will be as per consolidated cluster process above |
...