MA_TipsnHints

Owned by Mats Age
Nov 30, 2020
9 min read

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. The high level process steps are

  • Initial Discovery/Allocation/Validation

  • Site Allocation

  • Clone Step

  • Load Step

Initial Discovery/ Allocation/Validation issues

After initial discovery, a number of issues will likely be highlighted. These may include mappings that have to be resolved by selecting the Manually Resolve Unmapped button. These items may include items such as CUCM Call Manager, Call Manager Groups, Media Resource Lists. These wil only be shown if these items are different in target CUCM to source CUCM.

Other items that are highlighted 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 expected and no action required, select the red button to Disable Rule/ Clear the issue.

When all issues cleared - Revalidate

Site Allocation Issues

No Site Suggestions after discovery

If there are no Site suggestions detected during initial discovery/ allocation, then select Mapping Tables from menu and create mappings in the Mapping Table or change existing defaults. These can be Device Pools or such that would generally indicate a site – when updated return to migration and select ‘Re-Allocate Migration’

 

Limiting the number of Sites displayed

As during the Discovery with default settings, MA 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.

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 200 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, the object with issue is a Hunt Pilot and it is flagging that dependency Hunt List ‘Syd1-Sales-HL’ has not yet been cloned. If we select the highlighted Hunt Pilot it will bring up a detailed view of the object.

 

There are 2 ways to deal with this specific issue.

Option 1 is to Change the step at where Hunt Pilot is cloned to ensure that the dependent item is cloned first. This can be found under ‘Change At*’ where in this instance the Source Value is ‘Before Any Sites Load’ (at Customer level). We can then change this in Override Column to ‘After All Sites Loaded’ which will ensure that it is cloned after dependency. We can then go back to migration and Restart Execution Process

 

Option 2 in this instance would be to Clone the dependent items (noting that there may be multiple chained dependent items that will need to be cloned and therefore Option 1 above would here be more suitable, but described here anyway). To do this, from the detailed object view for Hunt Pilot , select the Highlighted link to dependent Hunt List

which will bring up detailed view of Hunt List object. From here select ‘Clone Now’. This will not be allowed as the Hunt List has a dependent Member Line Group that will need to be cloned first. Therefore we would select the highlighted link to Line Group, briniging up the Line Group that in turn might have dependencies that will need to be cloned first etc.

 

Example of Clone Issue 2

 

In this instance, there is an issue with CUCM-TOD-ACCESS where dependent CUCM User has not been cloned. As per previous example, we bring up the detailed object from the highlighted link

Again, we have the option to change at what stage the item is cloned or to clone dependent objects. Again, here is probably better to change the stage at where clone is done rather than clone dependent items as a User has many dependencies that would need to be cloned first

Example of Clone Issue 3

 

In this example, there is a CUCM Pick up group and a TOD issue. As TOD is described in previous example, only the Call Pick Up Group issue is described here. As per previous examples, bring up detailed CUCM-PICKUP-GROUP view. We can here see that the only dependency is a Route Partition and as a Route Partition unlikely will have a dependency, there may be here worthwhile to use the Clone option rather than changing the stage at which Pick Up group is cloned. What would be required is to first

  • Select the link to Route Partition

  • Clone the Route Partition

  • Return to the detailed view of Pick Up group to clone it

  • Then back to migration and Restart Execution Process

 

 

Example of Clone Issue 4

 

In this example, we have a CUCM user that will not clone as it has a dependency on phone devices at another sites devices that has not yet been cloned. The Wrangler has allocated the user to a particular site from Primary Extension number but is associated with 2 phone devices at another site. This can be managed in a number of different ways

  1. If this is the desired outcome in CUCM (user in one site, devices belonging to another) then in detailed view of the user and the associated phone devices, change the step at where user and devices are cloned to ‘After All Sites Loaded’ described in screenshots below

  2. This should maybe be rectified so that either the phone devices are allocated to same site as the user/ line, or the user and line (with another number allocated) be allocated to site where devices are located, noting that this is easier to perform in target CUCM post migration or rectified in source CUCM followed by rediscovery.

 

 

 

 

Example of Clone Issue 5

 

Remote Destination will not clone as dependent on TOD that is not yet cloned. In this instance, the preferred method would be to, in detailed view of the Remote Destination, change the step where it is cloned to ‘After All Sites Loaded’, Then back to migration and Restart Execution Process

 

 

 

 

 

 

 

 

 

Load Issues

 

The load is completed in a number of steps. Firstly the objects at ‘Before Any Sites Loaded’ (Customer Level) step, then objects are loaded ‘During Site Load’ (Site Level Objects) step, then there may be objects that have been selected to load ‘After All Sites Loaded’.

As there may be circular dependencies where objects at Customer level depend on objects loaded During Site Load or vice versa, these will show up as Errors under Events tab once Load stage completed.

To solve this, perform a Migration Point Change. To do this, select Bulk Changes from Menu

Then Select ‘+ Create Migration Point Change’

 

Populate the field with the step that should be reprocessed. Suggest – first run ‘Before Any Sites Loaded’ – ‘Start Migration Point Bulk Change’

Then repeat Create Migration Point Change for ‘During Site Load’ – ‘Start Migration Point Bulk Change’

 

When these Migration Point Changes have been executed – return to Migration, then Restart Execution Process

The remaining errors here post migration point changes are due to Line Groups, Hun List, Hunt Pilot that relates to Voice Mail which are not supported and would be ignored

 

 

 

 

 

 

 

Rollback Issues

 

If a Rollback is performed, then migrate again, then the mappings for softkeys are undone and need to be set again as per sample screen shots below

 

 

yarnlab website