| Table of Contents | ||||
|---|---|---|---|---|
|
Wrangler
...
WxC-DI Migration Assistant – 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.
...
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
...
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.
...
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:
...
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 -
...
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
...
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
...
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
Before the Load step, where all configuration is pushed to Target cluster is performed, there is a validation required that will flag any dependency issues that must be rectified before proceedding proceeding with the load. In the below sample migration, we can see that there are a number of Issues that needs recificationfixing.
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.
...