Method Of Procedure
This documents the process to migrate a CUCM cluster to WxC-DI using the Wrangler Clone migration option
Change History
Version | Date | Change | Author |
0.1 | 18/05/2023 | Initial draft release | Mats Age |
Document References
Document | Document Reference |
Yarnman Installation & Setup | |
Yarnman Administration | https://yarnlab.atlassian.net/wiki/spaces/YSP/pages/2730393636/Yarnman+Administration |
Wrangler UCMC/WxC-DI |
Prerequisites
Item | Details |
Connectivity | Firewall configured for access Yarnman to Source CUCM: port TCP 8443/443 Yarnman to Target CUCM: port TCP 8443/443 Engineer to Yarnman: port HTTP/HTTPS/SSH |
Access Credentials Source CUCM | |
Access Credentials Target WxC DI | |
Access Credentials Source CUC | |
Access Credentials Target CUC |
Customer details
Item | Details | Notes |
Customer Name and Code | ||
Number of Sites | ||
Sites to be migrated | ||
Device Counts per site | ||
User counts per site | ||
Yarnman/ Wrangler Server | Hostname, IP Addresses | |
Source CUCM, IM&P Details | Hostname, IP Addresses | |
Source CUC Details | Hostname, IP Addresses | |
Target CUCM, IM&P Address | Hostname, IP Addresses | |
Target CUC Details | Hostname, IP Addresses | |
3rd Party Integration | ||
LDAP Integration | Yes/No | |
UCCX or ARC | Yes/No |
Migration Process Step by Step Guide
Prepare Target UC Servers
Configure objects in target UC Servers for mapping as required
CUCM Mapping Objects
Item | Details | Complete Y/N |
CUCM CMG’s | Configure Call Manager Groups as required in target for mapping | |
CUCM CM’s | These are created automatically with each CUCM node installed | |
CUCM Dialplan Tags | Configure any Custom Dial Plan Tags as and if required | |
CUCM Dialplan/s | Load any Dialplans required in target, other than NANP that is installed by default | |
CUCM Route Partitions | Load Route Partitions required for new dial plan in target | |
CUCM CSS’s | Load Calling Search Spaces for new dial plan in target | |
CUCM IP Phone Services | Any none default IP Phone Services such as EM etc – take care to use same type as source ie Enterprise Subscription or not | |
CUCM LDAP Directory | LDAP Directory agreements to be configured and users synced in | |
CUCM MRGL’s | Media Resource Group Lists and MRG’s to be configured manually in target | |
CUCM Network Locales | Any none default network locales required | |
CUCM User Locales | Any none default user locales required | |
CUCM UC Services | Configure any UC Services in Target if required | |
CUCM Service Profiles | Configure any UC Service Profiles in Target if required | |
CUCM SIP Normalization Scripts | Any custom SIP normalization scripts to be configured in target | |
CUCM Mobile Smart Client Profiles | Configure if required | |
CUCM VPN Groups | Configure if required | |
CUCM VPN Profiles | Configure if required |
Source CM Group | Target CM Group | Comments |
Source CM | Target CM | Comments |
Source CUCM IP Phone Services | Target CUCM IP Phone Services | Comments |
Source LDAP Directory | Target LDAP Directory | Comments |
Source UC Service | Target UC Service | Comments |
Source Service Profile | Target Service Profile | Comments |
Source MRGL | Target MRGL | Comments |
Source Network Locales | Target Network Locales | Comments |
Source User Locales | Target User Locales | Comments |
Source Dial Plans | Target Dial Plans* | Comments |
*Note that NANP always loaded by default
Source Route Partitions | Target Route Partitions | Comments |
Source CSS’s | Target CSS’s | Comments |
Source Dial Plan Tags | Target Dial Plan Tags | Comments |
Source SIP Normalization Scripts | Target SIP Normalization Scripts | Comments |
Source Mobile Smart Client Profiles | Target Mobile Smart Client Profiles | Comments |
Source VPN Groups | Target VPN Groups | Comments |
Objects not migrated by Wrangler that needs to be manually loaded
CUCM
Item | Details | Complete | Notes |
Annunciators | |||
Application Servers | |||
Caller Filter Lists | |||
Conference Bridges | |||
Inter Cluster Service Profiles | |||
IVR’s | |||
Media Resource Groups | |||
MOH | |||
MTP’s | |||
Transcoders | |||
Voice Mail Ports | |||
Any None Default Network Locales |
Prepare Yarnman/ Wrangler
This will be completed prior to the actual migration.
No | Component | Item | Complete (YES/NO) | Notes |
1 | Yarnman | Install Yarnman Server. Instructions Here | ||
2 | Yarnman | Login to Yarnman Application https://XX.XX.XX.XX/administration/login  | ||
3 | Yarnman Admin | Select Administration from the Admin drop down list  | ||
4 | Yarnman Admin | Navigate to Interfaces. Create Source and target CUCM Interfaces. Instruction here https://yarnlab.atlassian.net/wiki/spaces/YSP/pages/2730393636/Yarnman+Administration#Interfaces  | ||
5 | Yarnman Admin | Navigate to Services. Create Wrangler UCMC Service and Interconnect Service. Name Service Wrangler UCMC. Instructions how to add service and Interconnect Service here  | ||
6 | Yarnman Admin | Verify the Service is added to proxy and available in the dropdown  | ||
7 | Yarnman Admin | Verify connectivity between wrangler and all other component Wrangler to CUCM Source Wrangler to CUCM Target |
Wrangler Preparation Steps
Mappings for Site Suggestions
No | Component | Item | Complete (YES/NO) | Notes |
WRANGLER | Login to Wrangler Application by selecting from switcher drop down ‘Wrangler UCMC’  | |||
WRANGLER | Navigate to Mappings-> Mapping Tables. Verify the Global Mapping has all required items (check section 3.3 for details)  |
Regexes Used
Macro | Regex | Comments |
siteId | ([a-zA-Z0-9]+) | |
defaultNameMatchAll | ([a-zA-Z0-9]+) |
Device Pool Mappings
Device Pool Name | Source Template for SiteId | Comments |
Partition Mappings
Partition Mappings may be defined in addition to Device Pool mappings above to further help partition objects such as EM profiles into sites
Partition Name | Source Template for SiteId | Comments |
Wrangler Discovery and Initial Issue Review
No | Component | Item | Complete (YES/NO) | Notes |
1 | WRANGLER | Login to Wrangler Application. Select New Customer Migration 
 | ||
2 | WRANGLER | Define Source and Target UCMC Interfaces as defined earlier, Optionally define Initial countries (countries covered by Source CUCM Select Dialplan Configuration ‘Map - Map Source Dialplan to Existing Target Dialplan’, then ‘Save Migration $ Start Discovery’ to kick off the migration  | ||
3 | WRANGLER | On Completion of Initial Discovery/ Allocation/ Validation we need to define Sites, and resolve any issues  | ||
4 | WRANGLER | Select ‘Site Suggestion’ tab to define Sites. Mappings created previously for Device Pool and, if required other objects, should ensure that Sites suggestion displayed match these*. Select ‘Create Site’ for each site, or select all using ‘Bulk Action’  
| ||
5 | WRANGLER | Select the Warnings Tab  Warnings tab displays issues from initial validation checks such as lines without phones, users without lines, users without emails etc. None of these issues will stop migration proceeding and may be disregarded by selecting ‘Disable Rule And Clear Issue’ Or if these issues/ some of them should be rectified prior to proceeding. Select the blue button adjacent to each object type flagged – this will display all the objects of that type with the highlighted issue. These may then be exported and the issue rectified in source CUCM followed by Fast Re-Sync All option 
| ||
6 | WRANGLER | Select the ‘Issues & Resolutions’ tab These issues must be attended to before progressing migration  Some issues and suggested solution to these are described below For a list of all validation rules, what they mean and suggested solutions to them, they may be found here Wrangler UCMC Validation Rules and Solutions There are LDAP integrated User in target not existing in source  Solve by Resyncing the target or select ‘Bulk Skip Users’ to skip users from the migration There are Device Pools that are not allocated to site  This issue may be ignored until after Reallocation performed as provided Mappings performed correctly this issue will disappear as part of Site Allocation EM Profiles not allocated to site in source cluster  This issue may be ignored until after Reallocation performed as provided Mappings performed correctly this issue will disappear as part of Site Allocation Duplicates in Target with unique configuration  This flags that there are Duplicate objects in target but with different configuration to the source duplicate. To review the duplicate difference, select ‘Review Duplicates’ which will bring up links to the duplicates for review If target is to be updated with configuration from the source duplicate object select ‘Update Target Object’ (this would generally be the selection that should be used and is always the action for LDAP integrated users) or ‘Ignore Source’ which will keep the Target object as is Mapping  These objects must have been created in Target and source object then mapped to corresponding target (note that if source and target objects have same name, they will be mapped automatically). Select the ‘Manually Resolve Unmapped’ which will bring up the unmapped objects of the type, then map as required. If there are many objects to be mapped such as with CSS’s and Route Partitions in sample, the 'Download XLSX Report' may be used and mapping done in Excel and then uploaded. Mapping process (and Issues & Resolutions) is further explained here https://yarnlab.atlassian.net/wiki/spaces/YSP/pages/2728493069/Wrangler+UCMC+Migration+User+Guide#Issues&-Resolutions-(below-description-and-samples-apply-to-single-cluster-migrations---for-multi-cluster-consolidation,-additional-info-here-[inlineCard]-) When all validation rule issues cleared, select ‘Re-Allocate Migration’  | ||
7 | WRANGLER | If after Reallocation, some issues still remain Resolve these, then Re-Validate until no further errors are detected In sample migration Sites with no Country defined  To solve these, ‘Select Country Code’ then from drop down add required country Note: Bulk Change Option may be used if there are many issues flagged of same type. How to use Bulk Change option here https://yarnlab.atlassian.net/wiki/spaces/YSP/pages/2756444161/Wrangler+UCMC+Administration+Guide#Bulk-Changes Once all issues cleared – ‘Re-Validate Migration’  | ||
8 | Once All Issues and Resolutions and Site Allocation processed, continue with Prepare Sites Step |
Prepare Sites Step
No | Component | Item | Complete (YES/NO) | Notes |
1 | WRANGLER | Select Sites from menu to enable site migration batch  Select the Sites to migrate by Clicking on the ‘Waiting’ adjacent to site in the ‘Select’ column, or to select all sites in one go, Bulk Select may be used   Return to ‘Ready’  | ||
2 | Next step is to select ‘Re-Validate Migration’  On Completion of Validation – ‘Preview Prepare’ then ‘Start Migration'   This will start the Cloning process, where all source objects are cloned in Wrangler, ready for Load Stage  On completion Select ‘Continue Migration’ which will proceed migration to Load Sites Stage |
Load Sites Stage
No | Component | Item | Complete (YES/NO) | Notes |
1 | WRANGLER | Again Select ‘Re-Validate Migration’ to proceed with pre load stage validation.  | ||
2 | WRANGLER | Select ‘Issues & Resolutions’ tab to view any pre load validation issues  Jabber Device Lines with Max Num Calls parameter set to >2  Solve by ‘Resolve With Bulk Change’ which will change all Jabber Device Lines with Max Num Calls >2 to Max Num Calls = 2 When all issues cleared – ‘Re-Validate Migration’  If no new issues appear after validation - proceed to ‘Preview Load’ Step 3 below in this section, otherwise Some new sequencing issues may reappear – as per above clear these by moving objects to ‘Before Any Sites Loaded’ or Bulk Change dependencies to ‘During Site Load’ – again Re-Validate Migration’ Repeat this until all issues cleared. Tip: If there are many sequencing issues of the same type, Bulk Change may be used to change them to different Change point – ‘Before Any Sites Loaded’ or ‘During Site Load’ stages For Example – if we wanted to change all Regions and Locations to change Point ‘Before Any Sites Loaded’ Navigate to Bulk Change, then ‘Create Bulk Change’  Select Objects to change in Filters , select Target Cluster, then ‘Search & Find Objects’  When objects show, select ‘Next’  Scroll down to Edit Overrides Header, ‘Set Allocated site’ to ‘Set to “null”’ and ‘Change At’ to ‘Before Any Sites Loaded’  Select ‘Review Bulk Changes’, then ‘Apply Bulk Changes’ 
 More on Preload validation issues and Tip here https://yarnlab.atlassian.net/wiki/spaces/YSP/pages/1833501488/Wrangler+UCMC+Tips+and+Hints#Pre-Load-Validation-Issues When all preload issues are cleared – move to Load Sites | ||
3 | WRANGLER | Start Load by selecting ‘Preview Load’, followed by ‘Start Migration’   This will load objects into target CUCM  | ||
4 | WRANGLER | On completion of Load, review any Errors by selecting ‘Events’ Tab, then ‘X Errors’  Error Details may be viewed by selecting the individual error. Within the error detail will be a link to open the object in Object Browser from where issue may be resolved by removing the issue causing the error or such
 In sample above CUCM-LINE causing error selecting highlighted link brings up object detail in Object Browser. The issue being a duplicate DN in same partition so changing partition  Once all errors have been rectified – ‘Restart Execution Process’, then migration complete, You may select ‘Continue Migration’ to move to the ‘Move Sites’ step although this step is for future use and currently perform no function   |
Revalidate and Review Issues
No | Component | Item | Complete (YES/NO) | Notes |
Appendix A – Setup Wrangler
Manual Changes In CUCM
No | Component | Item | Complete (YES/NO) | Notes |
Appendix B – Common issues
1
I