1 Wrangler WxC-DI – Migration Tips & Hints

Wrangler WxC-DI – Migration Tips & Hints

During a clone migration, the process goes through some high level steps during which issues may be encountered that needs resolving. These high level process steps are

Initial Discovery/Allocation/Validation
Site Allocation
Dial Plan Prepare (note that this step is only for Template Dial Plan Migrations)
Clone/Prepare Step
Load Step

Initial Discovery/ Allocation/Validation

After initial discovery, a number of issues will likely be displayed as follows.

Summary Tab displays a summary of issues encountered during initial Discovery/ Allocation process
Issues & Resolutions Tab details important issues that needs to be resolved before progressing
Warnings Tab displays issues that have been detected during the initial Discovery. These are warnings only.
Site Suggestion Tab displays suggestions for sites to be selected as required.

The Issues and Resolutions tab displays items that must be resolved before proceeding. These items will include items such as mapping of CUCM Call Manager, Call Manager Groups, Media Resource Lists etc. noting that these will only be shown if the objects are different in target CUCM from source CUCM.

Suggested actions required from the issues highlighted in the screenshot above from a Sample Migration. Noting that this is a sample only and issues vary depending on the migrated source clusters configuration

Detected 4 authenticated or encrypted Phone and SIP............ - Solution: load required licences on target cluster
There are 41 CUCM-DEVICE-POOL that are not allocate to site - Solution: As Site allocation has not yet been performed, no action required until post site allocation
There are 26 EM Profiles that are not allocated to a site - Solution: As Site allocation has not yet been performed, no action required until post site allocation
There are 2 x warnings for deprecated devices- Solution: Select the Green button to Skip Deprecated Devices (if Red Button, Disabble Rule and Clear Issue is selected, MA will try and load the deves during load phase and it will fail with error)
Warning, Phone Security Profile "Cisco Webex DX80 - Standard SIP Non-Secure Profile" product modes is not avaliable in target system - Solution: Select Blue Button to Skip loading Security Profile in Target
Warning, Phone Security Profile "Cisco Webex DX80 - Standard SIP Non-Secure Profile" product modes have been renamed........- Solution is to load the device pack on the target cluster + rediscover, or Select Blue Button to Skip loading Security Profile in Target
5 CUCM-CALL-MANAGER customer objects that need to be mapped or skipped. - Solution: Select the blue button to bring up screen where Source CUCM Call Manager servers can be mapped to the required target CM servers*
9 CUCM-CALL-MANAGER-GROUP customer objects that need to be mapped or skipped. - Solution: Select the blue button to bring up screen where Source CUCM Call Manager Groups can be mapped to the required CMG’s in target*
1 CUCM-IP-PHONE-SERVICE customer objects that need to be mapped or skipped - Solution: Select the blue button to bring up screen where Source CUCM IP Phone Service objects can be mapped to reqiuired IP Phone Services in target*
14 CUCM-MEDIA-RESOURCE-LIST customer objects that need to be mapped or skipped. - Solution: Select the blue button to bring up screen where Source CUCM Media Resource Lists can be mapped to the required MRGL’s in Target*

*Will only show if the source and target mapping objects are different. Also note that the target objects must be defined manually in souce cluster prior to starting migration

Sample mapping of CUCM-CALL-MANAGER servers in screenshot below, where the 5 existing source CM servers are mapped to target CM_ucmc6 (selected from drop down) server followed by blue button to Update (Map)

Once the above issues have been cleared, proceed to next Tab - Warnings

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. Otherwise, if the issue is expected and no action is required, select the red button to Disable Rule/ Clear the issue.

Once Warnings are resolved, proceed to next Tab - Site Suggestions which is where we create the sites to be used during the migration

Site Allocation

To create a site, select the Green button 'Create Site' adjacent to the suggestions as required

How Site Suggestions are Created

The sites are created from mappings in the Mapping Tables. These are accesible globally from Menu item Mappings → Mapping Tables or from within migration, menu item Mapping Tables. The Mapping Tables menu item within migration allows for changing of global values (available to all migrations) as well as allowing for overriding of global values on a per migration basis with preview function.

The Site suggestions are created from the CUCM source using templates. There are a set of default regexes that can be modified as required to match source configuration.

Objects that may be used to create sites includes Device Pools, Locations, Regions, Route Partitions, CSS’s and others

Mapping Regexes contain, amongst others, The siteId template regex to match source objects that is used to define the site

Device Pool Mapping Table templates contains regexes + text to match source cluster Device Pools to create the site suggestions

Tip, it is generally best to use Device Pools to create the Site suggestions.

The Mapping Table option within the migration allows for the change of mappings on a per migration basis + preview to check if the defined templates generate site suggestions as required. To check site suggestions for a particular mapping table option - select Preview table adjacent to required mapping source - in the below sample, we select Preview Table adjacent to Device Pools

Here we can see the Object Name (Device Pools in Source) and the Template/s that provides the match.

Some other mapping samples and outcomes in table below.

Source Object	Mapping	SiteId	Comment
Dallas DP	${siteId} DP	Dallas	Site name with space with object acronym removed
USA_NY_Site	USA_${siteId}_Site	NY	Only captures the name
USA_NY_Site	${countryCode}_${siteId}_Site	NY	Captures the name and also provides the country code
062458	${siteId}	062458
062458	062${siteId}	458

Limiting the number of Sites displayed

With default settings, the migration will attempt to 'guess' what can be a site using Device Pools, Locations, Regions etc. For large deployments with multiple sites, you may want to limit the number of suggestions – Under Mappings menu, Site Suggestions, you can set minimum template matches and select to include Device Pools, Locations and Regions by using toggles.

Once the above Issues, Warnings and Site Suggestions have been completed, select Re-Allocate Migration

Now we need to rectify the remaining options + new issues occuring post Site allocation

Site XXXXXX requires country code - Solution: Individually select country from Blue Button Drop Down ‘Select Country Code’

Tip - if there are many items the same - as above with Country Code allocation, to save time, use Bulk Change option to update

There are 1 CUCM-DEVICE-POOL that are not allocated to a site. - Solution: Select the ‘View’ to the left of item to bring up link to Object Browser - then allocate this device pool to a site + set Change At to During Site Load as it is now allocated to a site.

The reason that this shows up under issues is that this particular DP was not template matched as a Site. Another fix for this could be to add template regex as per Site Suggestions creation above + run Allocation step

There are 5 EM Profiles that are not allocated to a site. - Solution: Select the ‘View’ to the left of item to bring up links to object browser for each of them - then in object browser allocate to site for each individually

When All issues are attended to - Re Validate to move on to Clone/ Prepare Step

Clone Issues

Example of Clone Issue 1

During the Clone steps, objects are prepared and cloned, ready for the loading step. By default objects are cloned at:

Step 210 where items at customer level are cloned
Step 260 where objects at site level are cloned

Where there are issues encountered that prevents an object to be cloned, the process will stop and the link to item with issue/s will be highlighted in red. Select this highlighted item, which will bring up the object/s that require attention

In this instance, if we look at the first object in the list, 25170 / Syd1-Dirnum-PT the object with issue is a CUCM Line and it is flagging that dependency with a CUCM Gateway Analog access that has not yet been cloned.

If we select the highlighted CUCM Line it will bring up a detailed view of the object. We can see from above screen that it has not been allocated to a site - currently allocated to ‘Customer’. From Object browser, Objects->Browse bring up the related AALN/S0/SU0/3@C881V-GW Gateway, we can see that it is allocated to Site Syd1

The solution to the above is to allocate the CUCM Line 25170 to site Syd1 and modify Change At to During Site Load as per below screen shot

Example of Clone Issue 2

If we look at another Clone issue from list above -

Again a CUCM line - 35102 / New1-DirNum-PT - if we highlight this object by clicking on the link to object. We can see that the issue is that dependant object CUCM-EM “DDUCK 35100” has not yet been cloned and we can also see that the 35102 Line has not been allocated to site but to Customer

If we bring up the detail of object CUCM Line 35102 by selecting the link, then from within the object we find the Associated Device ‘DDUCK 35100’ flagged earlier - select the link to this object

We can see that this object has been allocated to site New1.

We now return to CUCM Line 35102 object where we can allocate this object to site New1 + Change At During Site Load, same as the dependant object

Example of Clone Issue 3

In this instance we are looking at a Route Pattern 9.!/ New1-PSTNCLIP-PT

We can see that it is dependant on CUCM-ROUTE-LIST 'New1-PSTN-RL

Select the link to the object 9.! / New1-PSTNCLIP-PT, from within the object detail, we find the link to the New1-PSTN-RL , select it

We can see that it has been allocated to site New1

Go back to the Route Pattern objcect detail for 9.! / New1-PSTNCLIP-PT, allocate to site New1 + Change At During Site Load

Example of Clone Issue 4

In this instance, we look at a Region - Lon1-REG that has been allocated to site - highlight he link

We can see that the issue here is that it has a related Region, New1, that has not yet been cloned

Now we need to decide how to deal with this - if we from within the Lon1-REG Region Object detail select Link to New1-REG

We can see here that New1 in turn have dependencies to Lon1-REG and Syd1-REG

Solution here could be to change Syd1-REG and New1-REG allocated site to Lon1 to allow them to clone + load at the same time as Lon1-REG

Once all issues are resloved, Restart Execution Process - if all clear, you will see Source Issue now 0, to proceed, select the Release + Restart Execution Process

Pre Load Validation Issues

After the prepare step in wrangler_ another validation is required. This validation step checks that there are no sequencing errors to ensure that all objects are loaded in the correct order. Additionally, it performs a configuration check to verify any anomalies that will stop objects from loading and finally it confirms that there are no site batch object dependencies missing.

Sequencing issues

Before the Load step, where all configuration is pushed to Target cluster, there is a validation required that will flag any dependency issues that must be rectified before proceeding with the load. In the below sample migration, we can see that there are a number of Issues that needs fixing.

To the left of the screen is the item that triggered the issue. Now we need to decide what to do to clear it. If we look at the first line where Device Pool has been identified as belonging to a site has a dependent object that would be loaded at the Before Any Sites Loaded step which will not work.

We now need to decide if

we want to move the Device Pool object to Before Any Sites Loaded step by pressing the first Blue button, +Move Obj To “Before Any Sites Loaded”; or
we can look at the dependant object by selecting the second blue button ‘View 1 Dependant object’ which will display the dependant object/s. We can see that it is a H323 gateway that depends on the Device Pool and that we have the option to move this object to During Site Load by selecting 'Bulk Change All Objects To “During Site Load” which will move the gateway so that it then loads at the same load stage as the related DP.

Once all the issues are attended to - Re Validate

Tip, if not sure, and you don’t want to trace back through CUCM + Wrangler UCMC for the dependencies, it is generally better to select to change the dependant object to ‘During Site Load’ rather than the flagged object to Before Any Sites Loaded.

Configuration Issues

In the preload validation, wrangler_ also looks for configuration issues that may stop the object from being loaded into the target. These may be configurations that may have been acceptable in prior version but not supported in the target version.

In the below screenshot we can see some of these

Issue - ‘Detected x jabber mobile devices with invalid MaxNumCalls value in lines’

This validation rule is triggered when there is one or more jabber type device object lines that have the parameter Maximum Number of Calls in source CUCM set to more than the allowed 2

To resolve this issue - select the 'Resolve With Bulk Change ' button which will reset the MaxNumCalls for the object/s in wrangler_ to 2 which will allow it to load into target

Issue - ‘Detected x target CUCM-USER with lines (LAAP) duplicates’

This validation rule trigger for CUCM User parameter Line Appearance Association For Presence duplicates when one ore more duplicates are detected

Note: There may also be a validation rule where LAAP orphans are flagged, but the solution is the same as for LAAP Duplicates

To resolve this issue - select the View Duplicates button which will bring up screen with all the objects with duplicates, then select Resolve adjacent to each of them (A bulk change for this feature is on Roadmap)

Issue - ‘Detected 1 CUCM Phone is self reference via “Phones Primary” field’

This validation rule is triggered when there are phone/s with CUCM parameter Primary Phone field set the same as the Device Name, as per screenshot below, this is not an allowed configuration in CUCM

To resolve this issue select View Self Reference 1 Phone, then Bulk Remove Self Reference from Phone

Issue - ‘Phone “XXXXXXXXXX” has pending Certificate Operation: “Install/Upgrade” that needs to be updated to allow device to be added’

This validation rule is triggered for any device object in CUCM that has pending Certificate Operation flagged. This occurs when a CUCM certificate has been updated and these phones are unplugged from CUCM prohibiting the certificate upgrade and leaving the device objects flagged in this state which would prohibit it to load to the target

To resolve this, select Set to “No Pending Operation” which will clear this flag for the object in wrangler_ to allow it to load

Missing Objects in Target Cluster

Validation rule may trigger in preload validation for missing objects which are displayed with ‘Required object “XXXXXXXXXXXXX” (cucm-object type) does not appear to exist in cluster “Target Cluster Name”. What this means is that an object that this object depends on has not been cloned (it does not mean that it has been deleted) in the prepare step. This could be if the ’missing' object belongs in a different site batch or it failed to clone for some other reason.

Step 1- To display the dependant object , select ‘View X Dependants’ , then the object in question which will open the detailed object browser of the object

We can here see under dependencies that there is a missing object, CUCM-LINE busyLampFieldxxxx named 0288915135 / mockdata . It will show as deleted but that is not necessarily the case, but more likely means that it has not been cloned/transformed in the previous prepare step and in this instance, as I am performing a phased migration and have selected the site Syd1-DP to migrate and it looks like this line belongs in a partition mockData it is likely that it belongs in another site migration batch

Step 2 - To verify which site the ‘missing’ object belongs, we go to Objects->Browse which opens the object browser, then under All Object Types column drop down, we select CUCM-LINE

In search objects, I type the name, of the ‘missing’ object, or part of it that I am looking for - in this instance, I enter 02889. From the search result, I can see that the line 0288915135 / mockdata belongs to site mockData-AUS which is in another migration batch

We now need to decide what to do to resolve this. Our options are to

Option 1 - Remove the dependant line from the initial CUCM-PHONE object. The BLF would then need to be manually configured in the Target CUCM when the ‘missing’ line is later migrated

In Object Browse Detail for the phone with the ‘missing’ BLF line object, remove the BLF line by scrolling down to Busy Lamp Fields selecting +Override Busy Lamp Fields button, then on Busy Lamp Fields screen, select x Remove adjacent to the missing line

Option 2 - In object browse detail for the ‘missing’ line, change the site for the line, then select Clone Now in the Object Browse detail window for the CUCM-LINE. This will only work if objects listed under dependencies have already been cloned/transformed in prepare step. In our instance, we can see Standard Presence Group and mockData partition, which have likely already been cloned as they will be in Customer level for phased migration (if using BASL feature).

Note: If there were dependency objects that also belonged in other migration batch sites, these would also need to be moved to current site batch

To perform this,

Step 1 - Select the ‘Missing/Deleted’ object in Object Browse

Check Object dependencies, and if these objects have been cloned/ transformed, continue to next step

Step 2 - Scroll down to Allocated Site, then in override column, Change Site for the object to a site in current migration batch, Save Changes. When Saved, select Clone Now, then Execute Clone

Yarnlab Docs

Wrangler WxC Tips and Hints