| Table of Contents | ||||
|---|---|---|---|---|
|
...
Before starting the migration, the source and target CUCM, and if required CUC, interfaces must be defined.
...
The rights required for these interfaces are defined here https://yarnlab.atlassian.net/wiki/spaces/YSP/pages/2918973483/Yarnman+YM-PH+Interfaces#The-following-CUCM-permissions-are-required-for-wrangler_-WxC-DI-migrations
| Info |
|---|
Important Note: For migration to WxC-DI, an account with User Rank 1 is required which will require a special request to Cisco as by default for DI migration an account with Rank 3 will be provided. |
The minimum Required access roles in the CUCM Application User for the AXL interface are
...
Standard AXL API Access
...
Standard CCM Admin Users
...
The process to define the interfaces can be found in https://yarnlab.atlassian.net/wiki/spaces/YSP/pages/2730393636/Yarnman+Administration#Interfaces
...
Standard AXL Read Only API Access can be applied on the source cluster
...
/2730393636/Yarnman+Administration#Interfaces
Important:
Target CUCM Configuration Requirements Pre Migration
...
| Info |
|---|
Important Considerations: ● Post Migration, Extension Mobility users are logged out from their end devices and must log in. ● Passwords (if not using LDAP) and PIN’s are not migrated by Wrangler. The recommendation is to use BAT or such to set password and PIN in target cluster post migration.
|
...
Initiate Migration
To initiate a migration, from the Wrangler main menu, select Migrations, followed by + New Customer Migration
...
At completion of initial Discovery* process, a summary screen displays any issues and warnings detected during the initial Discovery process*, with the individual tabs providing detailed information of the on these.
...
*From Wrangler version 2.5.20, CUCM change notifications are supported which means that if a Rediscovery needs to take place at any time after the initial discovery has been successfully completed, Fast Re-Sync All may be selected that will detect all changes in CUCM’s since the previous full discovery was performed. (note that there is a dependency on notification queue depth in CUCM which is found in CUCM under Service Parameters)
...
When all validation issues have been completed , you need to Re-Validate Migration.
Rank ACG Cloning pre version 2.6.12
For WxC-DI migrations using Yarnman Yarn1man with version earlier than 2.6.12, an ACG clone may be created as per below.
...
As part of the migration all users will be transformed with a Rank Value of 5 and associated with the newly cloned ACG’s
Rank ACG behaviour Yarnman/wrangler_ version 2.6.12 and later
For version 2.6.12 and later migrating to WxC-DI only - the above ACG clone process is not performed, instead we have developed a process to Automap default source ACG’s to the WxC-DI Partner ACG’s as per below screenshot, thus now not requiring a Rank 1 account for the API interface credentials. (Note that this may still be required if custom ACG’s are required in the WxC-DI, as Cisco by default does not allow for the creation of ACG’s these in the WxC-DI environment)
Warnings
The Warnings tab displays items that have triggered the rules but are information warnings only that may be attended to as required in source CUCM. Items that are highlighted under warnings can be missing e164 numbers, Intercom partitions and CSS's, Devices without Lines, Lines without Devices etc. If these require updatingTo view the details of these objects, select the blue button which will take you to the item/s in question. If no action is required for the individual item, the the individual item/s, select Acknowledge and Continue (pre version 2.6.12 the Red Button + Disable Rule and Clear Issue) may be selected to clear the issue.
...
Once Warnings are resolved, proceed to next Tab - Site Suggestions which is where we define the sites to be used during the migration
...
Navigate to ‘Issues’ , the select ‘Re-Allocate Migration’
...
Option 3 - if the View link selecisted , the below screen will show, displaying which Device pool is impacted, this in turn has a link View to the Object Browser described in more detail herehttps://yarnlab.atlassian.net/wiki/spaces/YSP/pages/2756444161/Wrangler+UCMC+Administration+Guide#Browse, that shows the detail of this Device Pool. We can here allocate this object to a site as per the screen shot below.
...
We can select the sites individually by selecting the O Waiting from Select column or we can Bulk Select all sites by selecting the Green Bulk Select button
...
Phased migration enables the migration of sites individually or in batches. To assist in determining and understanding interdependencies prior to a phased migration, a new inter-site dependency report has been created where sites are placed in site groups and the report then detemines determines the dependencies between the analysed site group and other site groups.
...
| Tip |
|---|
For phased migration, it is recommended that a number of object types are moved to Before any Sites Loaded (BASL) and some objects also have their siteId set to null. This is best achieved using Bulk Changes. More on this here for version 2.6.14 or later https://yarnlab.atlassian.net/wiki/spaces/YSP/pages/edit-v2/3362750471?draftShareId=9dc3877d-7137-4220-aeda-fb8b8d7707cd#Overview or here for pre 2.6.14 https://yarnlab.atlassian.net/wiki/x/CYAtt |
...
If any issues are discovered that prevent cloning of an object, it will be highlighted in red with link to the issue. Select the Target Issues: 1 link which will display the object/s
...
In this sample it is a Line Group Syd1-Sales-LG - select the link which will bring up the issue detail for the LG
...
The issue here is Line group member 25124, to view detail, select link to source Syd1-Sales-LG which will show Object Browser detail for the Line Group
...
if all issues resolved, Target Issues will now show 0, select Release, then Restart Execution Process
...
We will now Re-Validate Migration again to validate prior to load in writing configuration into target CUCM
...
A number of issues will likely need to be resolved before loading relating to dependencies/ sequencing issues
...
Select the Issues & Resolutions Tab
...
The EM profile not allocated to site need to be resolved by selecting View link whcih will bring up Object Browser detail for the EM Profile, where site may be allocated
...
Select Preview Load, Followed by Start Migration to initiate load of objects into Target UC Clusters Cluster
...
The counters Added and Updated within each load step can be used to ensure that objects are added/ updated in into target UC clusterscluster.
We can see that during the ‘Before Any Sites Loaded’ step there were 659 out of 665 objects added and 13 out of 14 objects updated.
We can see that in the ‘During Site Load’ step there were 250 out of 251 objects loaded and 21 out of 21 updated
...