Page Comparison

Migration to UCMC requires at least one target cluster.

A Target UCMC cluster has not been defined

Delete migration from Tasks menu item. Then reinitiate migration ensuring that Source and target interfaces selected.

Target cluster must have equal or greater CUCM version that source cluster(s).

Source cluster/s have a later version than target cluster

Not a supported migration

Source interfaces (clusters) need to be mapped to a default target cluster.

Cource cluster have not been mapped to target cluster

Rectify and restart migration

Site(s) country must be added to the migration.

Required country not added

Using the drop down adjacent to validation issue to add country

Configuration Warning - Some CISCO device models are deprecated in some versions.

Some device models configured in source clusters have been deprecated and not supported in target cluster

Select Skip Deprecated phone button adjacent to issue.

If required in target need to configure phone device manually in target with supported end device

Configuration Warning - Some CISCO device models are not available in the target system.

Missing device pack for device in target

Device pack to be loaded in target or device skipped in migration + rediscover migration

Configuration Warning - Some CISCO phone security profiles models are not available in the target system.

Phone security profile for a migrating phone not available in the target

Device pack to be loaded in target + rediscover migration

or select ‘Skip Security Profile for Migration’ button if not required in migration

Verify directory URI partition between source and target clusters.

Directory URI in Enterprise Parameter different in source and target

Correct in target CUCM Enterprise parameter + rediscover migration

The security license is required on the target cluster.

phone security profiles and/ or SIP trunk security profile have security mode set to authenticated or encrypted and not licensed in target cluster

The security license is required on the target cluster. Load in target + rediscover migration

Check source and target cluster. Clusters UUID must be different

Same cluster selected for both source and target

Change Target cluster

Target cluster supported version is 12.5 and above

source cluster version not supported < 12.5

Upgrade source cluster

Check if CRS is enabled in source and target cluster. If IPCC extension are populated

Discovered IPCC extension in source and no CRS configured in target

Disable validation rule if UCCX not to be migrated or ensure CRS integrated to target

Site must have a target cluster selected.

Target cluster not defined for site

From Sites menu select site/s without target cluster - select Target cluster from drop down, save + revalidate

Site must have at least one source CUCM

Source cluster not defined for site

From Sites menu select site/s without target cluster - select Source CUCM’s from drop down , , save + revalidate

Site must have a country selected.

Country not defined for site

Select site country from drop down adjacent to issue or for multiple sites, bulk change. Alternatively, country can be allocated to site from Sites menu

Site must have a timezone selected.

TZ not defined for site

Select site TZ from drop down adjacent to issue or for multiple sites, bulk change. Alternatively, TZ can be allocated to site from Sites menu

Configuration warning - Users without email are present in this migration.

Warning that some users are missing email address

Populate email address as required, then revalidate, or Disable rule and clear issue

Source and target mapped object must equal site allocations.

One or more source objects flagged as not mapped to site

Map using the 'Manually Resolve Unmapped’ button next to issue or from menu item Target Mappings

Source objects template mapping is orphaned or invalid.

Objects have changed since mapping was originally executed

Remap the object

Map types must be mapped to a target object or skipped.

Map type object (object requiring mapping) must be mapped or if not required skipped

Map the source object to target Using ‘Manually Resolve Unmapped’ button next to issue or from menu item Target Mappings. There must be a target object to map to, if no object to map to in the target and the object is required, configure the missing object in Target and Re Discover Migration

If the mapped object is not required it may be skipped under Target Mappings

Transform types must be mapped to a template or skipped.

Transform type object (object requiring mapping) must be mapped or if not required skipped

Map the source object to target Using ‘Manually Resolve Unmapped’ button next to issue or from menu item Target Mappings. There must be a target object to map to, if no object to map to in the target and the object is required, configure the missing object in Target and Re Discover Migration

If the mapped object is not required it may be skipped under Target Mappings

Object can only be executed (add,update,clone) after its dependencies have.

Object tries execute before dependencies

Use the Button adjacent to the flaggd object issue to either change the object to move ‘Change At’ to same change point as dependant object/s load point or alternatively use the button for the dependant object/s to move ‘Change At’ to same change point as the flagged object

Configuration Warning - Users without Lines are present in this migration.

Warning only that there are users without lines in migration

Select Blue button ‘Resolve Invalid Users' to display the users that don’t have line allocated and rectify as required

Or if not an issue select Red Button - ‘Disable Rule and Clear Issue’

Configuration Warning - Users without Devices are present in this migration.

Warning only that there are users without devices in migration

Select Blue button ‘Resolve Invalid Users' to display the users that don’t have device allocated and rectify as required

Or if not an issue select Red Button - ‘Disable Rule and Clear Issue’

Configuration Warning - Phones and Devices without Lines are present in this migration.

Warning only that there are Phones or other devices without lines in migration

Select Blue button ‘Resolve Invalid Phones' to display the Phones/Devices that don’t have line allocated and rectify as required

Or if not an issue select Red Button - ‘Disable Rule and Clear Issue’

Configuration Warning - Phones and Devices without External Number Mask - E164 are present in this migration.

Warning only that there are Phones or other devices without E164 mask

Select Blue button ‘Resolve Invalid Phones' to display the Phones/Devices that don’t have E164 mask allocated on line and rectify as required

Or if not an issue select Red Button - ‘Disable Rule and Clear Issue’

Configuration Warning - There are devices to be added that have Pending Certificate Operation that needs to be updated to allow device to be added.

Warning that there are devices that have pending certificate update - may never have been plugged in or such

Select the Blue button 'Set to “No Pending Operation” adjacent to the issue

Configuration Warning - EM Profile need to be allocated to sites.

There are EM Device Profiles that have not been allocated to a site

If this is the first validation warning for the migration, prior to Site suggestions have been completed, then first complete Site Suggestions and reallocation before solving.

If Validation rule trips post Site allocation, select the View link nect to the object which will open page displaying the EM/s. From there open link to Object Browse for the individual EM/s then allocate CUCM-EM to site in Override Column and Save

Configuration Warning - Lines without Phones are present in this migration.

Warning only that there are lines without phones in migration

Select Blue button ‘Resolve Invalid Lines' to display the orphan lines and rectify as required

Or if not an issue select Red Button - ‘Disable Rule and Clear Issue’

Configuration Warning - CTI Route Points are present in this migration.

Warning only that there are CTI Route Points part of migration

Select ‘Disable Rule and Clear Issue’ noting that any associated third party system must be configured manually (the CTI Route Point config in CUCM is migrated)

Configuration Warning - CTI Ports are present in this migration.

Warning only that there are CTI Ports part of migration

Select ‘Disable Rule and Clear Issue’ noting that any associated third party system must be configured manually (the CTI Port config in CUCM is migrated)

Configuration Warning - Recording Profile are present in this migration.

Warning only that there are Recording Profiles part of migration

Select ‘Disable Rule and Clear Issue’ noting that any associated recording third party system must be configured manually (the recording profile config in CUCM is migrated)

Configuration Warning - Transcoders are present in this migration.

Warning only that there are Transcoders part of migration

Select ‘Disable Rule and Clear Issue’ noting that Wrangler UCMC does not migrate transcoder config

Configuration Warning - MTP IOS media type is present in this migration.

Warning only that there are MTP IOS part of migration

Select ‘Disable Rule and Clear Issue’ noting that Wrangler UCMC does not migrate MTP IOS config

Configuration Warning - Conference Bridges are present in this migration.

Warning only that there are Conference Bridges part of migration

Select ‘Disable Rule and Clear Issue’ noting that Wrangler UCMC does not migrate Conference Bridge Config

Configuration Warning - CSS with partition: Intercom is present in this migration.

Warning only that there are Intercom CSS’s part of migration

Select ‘Disable Rule and Clear Issue’

Configuration Warning - Unsupported Voicemail Ports are present in this migration.

Warning only that there are Voice Mail Ports part of migration

Select ‘Disable Rule and Clear Issue’ noting that Wrangler UCMC does not migrate Voice Mail Ports

Configuration Warning - Route Partitions with partition: Intercom is present in this migration.

Warning only that there are Intercoms RP’s part of migration

Select ‘Disable Rule and Clear Issue’

Configuration Warning - Device Pools with Elin Group are present in this migration.

Warning that there are ELIN groups part of source configuration

Select ‘Disable Rule and Clear Issue’

noting that Wrangler UCMC does not migrate ELIN groups

Configuration Warning - Jabber mobile devices must have correct MaxNumCalls value set for the version.

Jabber device in source have MaxNumCalls for line set to unsupprted value (max 2 in CUCM >=12)

Select the 'Resolve with Bulk Change' button

Configuration Warning - User and Network locales has to be present in the target system as well.

Detected that User or Network Locales used in source system not present in target

Install required Locales in target

the Rediscover migration

Source template objects need to be allocated to sites when match is set to mandatory.

The object has not been associated with a site

If this is the first validation warning for the migration, prior to Site suggestions have been completed, then first complete Site Suggestions and reallocation before solving.

If Validation rule trips post Site allocation, select the View link nect to the object which will open page displaying the Objects. From there open link to Object Browser for the individual Object/s then allocate to site in Override Column and Save

Configuration Warning - Unity User/Mailbox must have a user template in order to match to a target.

One or more User/ Mailbox in source UCXN config does not match a template in source

Create template in source that match the config of user mailbox, then rediscover

or skip and configure user mailbox manually in target UCXN

Configuration Warning - UCXN Tenants are not supported yet.

Warning that Wrangler UCMC does not support Tenants

Not Supported - manual config required in target UCXN

CUCM-USER objects which are LDAP integrated have a diffrent LDAP directory than target object.

Warning that LDAP directory config is different in source from target

Map required if name different in target from source

CUCM-USER objects which are LDAP integrated should have a target object that is also LDAP integrated.

Warning that LDAP user objects are different in target from source

Resync CUCM source + target and Rediscover migration

CUCM-ROUTE-PATTERN have a destination field that can be either routelist or gateway, but never both.

TBD

CUCM-SOFTKEY-TEMPLATE self reference.

Wrangler UCMC have detected that there is SKT template/s that refernces a base template in the source that does not exist in the target cluster

Select the View button to go to Object Browser for the SKT/s in question. There change the Base Template to one that exist in target cluster using the Override drop down

Source cluster CUCM-ACCESS-CONTROL-GROUP has custom ranks, these must be copied manually to the target cluster

User Ranks other than default >1 configured in source cluster

Ensure corresponding User Ranks configured in target - after completed, run rediscovery or disable validation rule

Orphaned CUCM-REMOTE-DESTINATION exists in source and cannot be migrated

Orphaned RD’s in source

Select Bulk change to clear

Orphaned CUCM-REMOTE-DEST-PROFILE exists in target and cannot be migrated

Orphaned RDP’s in source

Select Bulk change to clear

Orphaned CUCM-TOD-ACCESS exists in source and cannot be migrated

Orphaned TOD’s in source

Select Bulk change to clear

Orphaned CUCM-TIME-SCHEDULE exists in target and cannot be migrated

Orphaned TS in source

Select Bulk change to clear

Orphaned CUCM-HUNT-PILOT with invalid configuration, CUCM-HUNT-LIST missing and cannot be migrated

Hunt Pilot without Hunt List

Select Skip

CUCM-SERVICE-PROFILE directory password contains special characters that causes AXL error (CSCvz61706).

Invalid characters in password

Map Service Profile- disable rule

Source UCXN-CALL-HANDLER-TEMPLATES must match recipient type of the target they are mapped too

UCXN call handler templates with User Mailbox not existing in target

Create UCXN Call handler template with User Mailbox in Target

Cluster Consolidation - Sites must have different names.

In cluster consolidation, there are 2 of more source sites with the same name

Rename duplicate site name in Wrangler UCMC

Cluster Consolidation - Different length of Directory Numbers has been detected.

Warning only in cluster consolidation migration where two or more of source clusters have different length DN’s

Change number ranges as required using Transformation Renumbering option (not in MA)

or ‘Disable rule and clear issue' if it is not an issue

Cluster Consolidation - Directory Numbers duplicates has been detected.

Duplicate DN’s detected in Cluster Consolidation migration

Open Duplicate in Object Browse and change DN - Save

Cluster Consolidation - Object duplicates has been detected.

Duplicate Object detected in Cluster Consolidation migration

If the duplicate is not a default object, rename or skip the duplicate in Object Browser

Cluster Consolidation - duplicates on primary key

Duplicate object with same configuration detected in source clusters

Select the object to be used for migration. If other object also needs migration, modify primary key in source + rediscovery

Cluster Consolidation - duplicates with unique configuration

Duplicate object with unique configuration detected in source clusters

Select the object to be used for migration. If other object also needs migration, modify primary key in source + rediscovery

Cluster Consolidation - target duplicates on primary key

Duplicate object with same configuration detected in target cluster

Select Ignore source

Cluster Consolidation - target duplicates with unique configuration

Duplicate object with unique configuration detected in target cluster

Select Update Target if the target object should be updated with configuration from source (always for ldap users) or select ignore source if the target object shall remain as is