This page provides some additional information to the Wrangler UCMC Migration User Guide for Cluster Consolidation migrations specifics only.
Single Consolidated Migration (recommended option)
In a single consolidated migration of two or more source CUCM clusters, all source clusters together with the target cluster are defined in a single Wrangler UCMC migration. The migration can occur in stages as required per site, but all the planned source clusters to be consolidated will need to be discovered in the same session, noting that a rediscovery can take place anytime to cover any changes in source or target over time.
The Single Consolidated migration option can be performed using Map or Template migration but not Clone migration. Sample below shows a Map migration, but the same process would be used for Template/ Simplified Dial Plan migration option.
The only difference being that a Template or Simplified Dialplan migration will push a standardized dial plan to target rather than a dial plan required to be preconfigured in target as per the Map option.
Prerequisites for Map migration
For Map migrations (selected by Use Existing Target Dialplan / Do Nothing option from Dialplan Configuration field), it is a requirement that a dialplan has already been configured in the target UCMC cluster to allow for mapping of source clusters dialplan objects to the target dialplan.
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 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 two source clusters will be displayed
Review the duplicates against the CUCM clusters. Most of the duplicates will be default items in CUCM and can safely be ignored, such as most of the Phone security Profiles, Phone Button Templates etc. However, any custom templates need to be reviewed to ensure that duplicate configuration is the same in both copies before Ignoring.
If the duplicate needs to be migrated, it will need to be corrected in the source cluster, then a new discovery performed.
When all the duplicates have been rectified as required, proceed with migration as per standard Map migration
The first cluster entered when initiating migration is the source of truth. If selecting Disable Rule And Clear Issue red button adjacent to the duplicate, the source of truth object during the migration will be migrated to target, ignoring the duplicate
Alternative Migration Options
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.
Important Note regarding these options is that duplicate objects that may exist between the second and any consecutive migrations and the target will not be flagged in the discovery.
These duplicate object configurations will be updated in the target from the last migrated cluster of the same. Thus it is important that any potential duplicates are reviewed in CUCM and be known beforehand.
If the duplicate in consecutive migrating clusters have a different configuration than the target object, and the target configuration is not to be changed, then the source cluster configuration of this object will need to be skipped, or if required, reconfigured in the source CUCM cluster.
For any of the alternative migration options managed as separate migrations but with the same target, follow the process as for a single non consolidated migration hereWrangler UCMC Migration User Guide