Overview

This guide documents the process to migrate CUCM to WxC-MT using wrangler_. This new feature is available from Yarnman version 2.6.3 and complements the existing CUCM to WxC-DI functionality.

Prerequisites

The following are prerequisites for the migration

Yarnman Server Installed. Process here https://yarnlab.atlassian.net/wiki/spaces/YSP/pages/2916941825/Yarnman+Photon+Powered+YM-PH+-+Deployment+and+Installation#Yarnman-Deployment
wrangler_ service installed. Process here Wrangler WxC Service Setup
Interface to wrangler_ API integration with Webex cloud. Process Here. Yarnman (YM-PH) Interfaces
Interface configured to source CUCM. Process here https://yarnlab.atlassian.net/wiki/spaces/YSP/pages/2730393636/Yarnman+Administration#Interfaces

Migration Process

Link to demo of a CUCM to WxC-MT migration here

https://app.vidcast.io/share/044072d0-22c8-4a52-a661-6094a0713aa3

Define Migration

To initiate the migration. From wrangler_ application select

Populate migration details including

Source Interface
Target Cloud Webex Account and Interface and Webex Org
Target Customer Name (Name the migration)

Then select ‘Save Migration & Start Discovery’ to initiate the discovery of source and target

Post Initial Discovery Tasks

On completion of the initial discovery/allocation/validation, a Summary page is displayed. From here, Sites need to be defined and validation issues/ warnings resolved

Site Creation from Site Suggestions

Selecting Site Suggestions Tab will display suggested sites. New Webex Locations can be created from the source by selecting ‘+MT Site Template “Webex Location”’ adjacent to the source siteID or the source sites can be mapped to existing Webex Locations sites by selecting ‘+MT Site Existing LOC’ followed by selecting the Webex Location to be mapped. When site selections have been completed, select the !Warnings tab

On Sites and how Site Suggestions are created can be found here https://yarnlab.atlassian.net/wiki/spaces/YSP/pages/2756444161/Wrangler+UCMC+Administration+Guide#Sites and here https://yarnlab.atlassian.net/wiki/x/AQDGr

Warnings

The Warnings tab displays items that have triggered the rules but are information warnings only that may be attended to as required. 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 updating, select the blue button which will take you to the item in question. If no action is required for the individual item, the Red Button + Disable Rule and Clear Issue may be selected to clear the issue. When Warnings have been attended to, continue by selecting the Issues & Resolutions Tab

Issues & Resolutions

The Issues and Resolutions tab displays items that must be resolved before proceeding, sample screenshot below. These items will include items such as required licenses, numbers that can not be migrated to WxC-MT, required Mappings of object types etc. A complete list of validation rules and suggested resolutions of these can be found here https://yarnlab.atlassian.net/wiki/x/D4BWp . Once these issues have been resolved - select Re-Allocate Migration to proceed

After the Reallocation has been completed, there will be a number of new issues that need to be resolved under the Issues & Resolutions Tab. Resolve these , then select Re-Validate Migration

From sample migration, worth noting are the flagged Site objects missing addressing details, these may be solved individually by selecting the blue Manually Resolve In Site button, which will take you to the site object where the required address details may be completed, or all sites details may be resolved in bulk by selecting Sites (ver <2.6.5) or Allocation->Sites (ver =>2.6.5) from the main menu and from there export CSV of the sites. These addressing details may then be added to the CSV using Excel or such, then CSV uploaded to wrangler_ using Import option. More on this here https://yarnlab.atlassian.net/wiki/spaces/YSP/pages/2756444161/Wrangler+UCMC+Administration+Guide#Sites

There may also be objects that must be mapped such as with the CUCM-CSS’s in screenshot below. These may be mapped by selecting the Manually Resolve Unmapped button or by selecting menu option Target Mappings and resolve from there. More on Target Mappings here https://yarnlab.atlassian.net/wiki/spaces/YSP/pages/2756444161/Wrangler+UCMC+Administration+Guide#Target-Mappings-WxC-MT

When all issues are resolved, select Re-Validate Migration

Prepare Sites stage

On resolving issues and revalidation successfully completed, the ‘three migration step’ screen is displayed. To progress from here, we now need to select what sites should migrate.

To do this, select Sites (ver <2.6.5) or (Allocate->Sites (ver =>2.6.5) from menu, then select sites to migrate from the Select column or all sites may be selected by using Bulk Select. When completed, select Ready

from menu

Selected sites will display under Prepare Sites heading, select Re-Validate Migration to progress migration.

On successful validation, select Preview Prepare, then Start Migration. This will transform all objects within wrangler_ database ready for load in to WxC-MT

On successful prepare of objects , select Continue Migration to proceed to the load stage

Load Stage

Display will show the migrating sites under the Load Sites heading, select Re-Validate Migration. This will perform a final validation pre the loading of objects into the target WxC-MT, verifying that objects are ready and in the correct sequence

Note, in 2.6.5 and lower versions, that wrangler_ will load Workspaces (a Workspace will be created in WxC MT for each supported phone device without owner Id in source CUCM), but it will not create and load associated phones. This needs to be done manually. Process here https://yarnlab.atlassian.net/wiki/spaces/YSP/pages/2917793858/wrangler+WxC-MT+Migration+User+Guide#Workspace-Device-Load

Resolve any issue flagged pre load - in sample migration, we need to add Timezone for the Toronto Location and Add the correct state code for London Location. Once resolved, Re-Validate Migration

Ready to Load objects into target, Select Preview Load followed by Start Migration

Objects Loading

On completion of load, check for any errors during load by selecting the Events Tab and Errors box which will display the errors. Selecting the error will display the error detail and which object failed. In sample migration, 2 phone devices failed to load as they were duplicates of existing MAC addresses. To resolve - there will be a link within the error detail linking to object detail (can also be accessed using Object->Browse from menu then finding the detail of the offending object) where the error can be corrected and load process restarted by selecting Restart Execution Process

On rectification of issues and restart all objects loads OK

Workspace Device Load

As of yarn_man version 2.6.5, wrangler_ loads Workspaces but not Workspace devices into Webex Calling Control Hub. A workspace is created for every CUCM phone device of valid phone device type with no owner UserId. The Workspace/s are named using the device name from CUCM and includes the phone number and or extension.
To load the required associated Workspace devices, from BAT phone export or such, extract Device Name, Directory Number (Extension), Device Type and Device Name, then creating a CSV file formatted as per below including header

Username	Type	Extension	Device Type	Model	MAC Address
<CUCM Device Name>	WORKSPACE	<CUCM Directory Number>	WEBEX_CALLING	<CUCM Device Type>	<MAC Address, last 12 from CUCM Device Name>
<CUCM Device Name>	WORKSPACE	<CUCM Directory Number>	IP	<CUCM Device Type>	<MAC Address, last 12 from CUCM Device Name>


Sample
SEP777777555555	WORKSPACE	35105	WEBEX_CALLING	Cisco 7841	77777655555A