Wrangler WxC Validation Rules and Solutions
This Validation Rule (Type) | Description | Suggested Solution |
|---|---|---|
Migration to WxC-DI requires at least one target cluster.(missing-target-system-cluster*) | A Target WxC-DI 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)(check-clusters-version*)  | 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(missing-source-interface-target-cluster*) | Source cluster have not been mapped to target cluster | Rectify and restart migration |
Site(s) country must be added to the migration.(site-country-not-in-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(depricated-device-models*)
| Some device models configured in source clusters have been deprecated and not supported in target cluster | Select Skip Deprecated Devices For Migration button adjacent to issue. This will remove this object from the migration.
If a device object is required to replace the deprecated object, this must be configured manually in target with supported end device |
Configuration Warning - Some CISCO device models are not available in the target system(unavailable-device-models*) | 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(unavailable-security-profile-models*)
| 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.(check-cluster-directory-uri*) (check-cluster-directory-uri*) | Directory URI Partition and/or Alias URI in Enterprise Parameter different in source and target
| To check URI partition and Alias URI issue, select Check via SQL Possible issues are
|
The security license is required on the target cluster.(check-encryption-license-requirements*) | phone security profiles and/ or SIP trunk security profile have security mode set to authenticated or encrypted which is not licensed in target cluster | The security license is required on the target cluster. Load in target CUCM + rediscover migration
|
Check source and target cluster. Clusters UUID must be different(check-cucm-source-and-target-uuid*) | Same cluster has been selected for both source and target | Change Target cluster |
Target cluster supported version is 12.5 and above(not-supported-target-version*) | Target cluster version is not supported < 12.5 | Upgrade Target cluster to version 12.5 or higher |
Check if CRS is enabled in source and target cluster. If IPCC extension are populated(check-crs-configuration*) | Discovered IPCC extension in source and no CRS configured in target | Disable validation rule if UCCX not to be migrated or ensure it is integrated to target To continue, select 'Acknowledge and Continue'
|
Site must have a target cluster selected.(site-missing-target-cluster*)
| Target cluster not defined for site | From Sites menu select site/s without target cluster - select the target cluster from drop down, save + revalidate |
Site must have at least one source CUCM(site-missing-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.(site-missing-country-code*)
| 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 a site from Allocation->Sites
|
Site must have a time zone selected.(site-missing-timezone*) | 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
|
Site must have a user-locale for WxC-MT(site-missing-user-locale*) |
| Select correct User Locale from drop down |
Site must have correct address fields for WxC-MT(ucmc-site-address-fields-for-wxc-location-transform*) | Required address details for WxC-MT location not complete | Select from drop down to enter address details manually or can be made in bulk from Menu items Sites, by export site CSV, complete details and Import
|
Configuration warning - Users without email are present in this migration.(cucm-users-missing-email*) | Warning that some users are missing email address | Select Blue button ‘Resolve Invalid Users' to display the users that don’t have email allocated, then rectify users in source CUCM as required, followed by Fast Sync or Rediscover. Note that this is a warning only and will not impede WxC-DI migration, thus if not an issue select Acknowledge and Continue Green Button |
Source and target mapped object must equal site allocations.(count-signals-group-by-type-and-raise-as-issue*) | One or more source objects flagged as not mapped to site | Allocate flagged objects to site if required Could be Device pools or objects nota allocated to site Use Object Browse for individual object to allocate them to site or Bulk Change to allocate multiple objects to site as required
|
Source objects template mapping is orphaned or invalid.(object-mapped-template-invalid*) | Objects have changed since mapping was originally executed | Remap the object in Target Mapping |
Map types must be mapped to a target object or skipped.(object-not-mapped*) | 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.(object-not-mapped*) | 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-executed-before-dependencies*) | wrngler detected that there are objects that have been flagged as out of sequence. ie. Object would execute load before dependencies | To move the flagged object to ‘Change At’ Load point BASL (Before any Sites Loaded) select the highlighted button labelled + Move Obj to ‘Before Any Sites Loaded’ which means that this object will be loaded at the first load stage before any site objects are loaded Tip - Location and Regions should be Moved to BASL or if the highlighted objects dependant object/s should be moved to the same load stage as the highlighted object, select 'View x Dependant Object which will list all the dependant objects, then select the bulk change option which will move the object to same Change At as the flagged object
Tip - if unsure of selection it is generally safer to move dependant objects to same level as flagged object except as mentioned above for Location/s, Region/s |
Configuration Warning - Users without Lines are present in this migration.(cucm-phones-without-lines*) | 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.(cucm-users-without-devices*) | 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 - User with primary line defined but no associated devices or device profiles(check-user-has-primary-line-and-device*) | CUCM-USER with prilary line configured but no associated devices | This will stop user from migrating - select the bulk fix button to remove primary line from the user |
Configuration Warning - Detected local users with same MailId or Directory URI as LDAP users in target cluster(check-user-local-ldap-mail-duplicate*) | A local user in target have same mailId as a CUCM-USER in the source | Select the bulk change fix button to remove the mailId from the user to allow it o load into target cluster |
Configuration Warning - Phones and Devices without Lines are present in this migration.(cucm-phones-without-lines*) | Warning only that there are Phones or other devices without lines in migration. As it is not possible to have 2 users in target system with same mailId, this will stop user from migrating | 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.(cucm-phones-without-e164*) | 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.(cucm-phones-capf*) | Warning that there are devices that have pending certificate update - the device may never have been plugged in or not plugged in since certificate update performed | Select the Blue button 'Set to “No Pending Operation” adjacent to the issue
|
Configuration Warning - CUCM-PHONE has a self reference for primary phone that needs to be removed to allow loading(cucm-phones-self-reference*) | A device has primary device configured referencing itself in source CUCM. This is incorrect configuration and will stop the phone device from loading to target | Select the Bulk fix button to remove the configuration in Wrangler to allow loading of the object
|
CUCM-PONE has line with intercom line (Only available in Clone Migration)(count-signals-and-raise-as-issue*) | An Intercom line exist with incorrect ring setting exist that will stop the device from loading in target cluster | Select Bulk fix button to clear the ring setting and allow phone device to migrate |
Configuration Warning - EM Profile need to be allocated to sites.(unallocated-cucm-em*) | 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 perform reallocation before solving. If Validation rule trips post Site allocation, select the View link next to the object, which will open the page displaying these EM/s. From there, open link to Object Browse for the individual EM/s then allocate CUCM-EM to site and Change At too During Site Load in Override Column, then Save It is also possible to allocate EM to site in bulk if there are dedicated number ranges per site. In this instance, select Allocation->Ranges Select +Quick Add Range, then select site and define range to be allocated to site
|
Configuration Warning - Lines without Phones are present in this migration.(cucm-lines-without-phones*) | 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. These have to be rectified in source CUCM followed by a Rediscovery
Or if not an issue select ‘Acknowledge and Continue’ |
Configuration Warning - CTI Route Points are present in this migration.(count-signals-and-raise-as-issue*) | Warning only that there are CTI Route Points part of migration | Select ‘Acknowledge and Continue’ 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.(count-signals-and-raise-as-issue*) | Warning only that there are CTI Ports part of migration | Select ‘Acknowledge and Continue’ 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.(count-signals-and-raise-as-issue*) | Warning only that there are Recording Profiles part of migration | Select ‘Acknowledge and Continue’ 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.(count-signals-and-raise-as-issue*) | Warning only that there are Transcoders part of migration | Select ‘Acknowledge and Continue’ noting that Wrangler UCMC does not migrate transcoder config
|
Configuration Warning - MTP IOS media type is present in this migration.(count-signals-and-raise-as-issue*) | Warning only that there are MTP IOS part of migration | Select ‘Acknowledge and Continue' noting that Wrangler UCMC does not migrate MTP IOS config |
Configuration Warning - Conference Bridges are present in this migration.(count-signals-and-raise-as-issue*) | Warning only that there are Conference Bridges part of migration | Select ‘Acknowledge and Continue’ noting that Wrangler UCMC does not migrate Conference Bridge Config |
Configuration Warning - Unsupported Voicemail Ports are present in this migration.(count-signals-and-raise-as-issue*) | Warning only that there are Voice Mail Ports part of migration. | Select ‘Acknowledge and Continue’ noting that Wrangler UCMC does not migrate Voice Mail Ports
|
Configuration Warning - Device Pools with Elin Group are present in this migration.(count-signals-and-raise-as-issue*) | 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.(cucm-jabber-devices-max-num-calls-limit*) | Jabber device in source have MaxNumCalls for line set to unsupported value (max 2 in CUCM >=12) | Select the 'Resolve with Bulk Change' button
|
Configuration Warning - Jabber mobile devices must have correct DND configuration set(jabber-devices-dnd-validation*) | Incorrect DND setting for target cluster stopping Jabber device from loading in target cluster | Select Bulk Fix button to clear the incorrect setting
|
Configuration Warning - User and Network locales has to be present in the target system as well.(cucm-locale-not-in-target*) | Detected that User or Network Locales used in source system not present in target | Install required Locales in target then Rediscover migration |
Source template objects need to be allocated to sites when match is set to mandatory.(unallocated-source-template-object-check*) | 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 next 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 and Change At to During Site Load in Override Column, then Save
|
Configuration Warning - Unity User/Mailbox must have a user template in order to match to a target.(ucxn-user-must-have-template*) | 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.(ucxn-tenant-not-supported*) | 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 different 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 From Target Mappings, select link to cucm-ldap-….., then select the required target from drop down, then Update x Object
|
CUCM-USER objects which are LDAP integrated should have a target object that is also LDAP integrated.(cucm-user-ldap-missing-target-object*) | Warning that LDAP user objects are different in target from source | Resync CUCM source + target and Rediscover migration; or if this is expected and no issue, then Bulk Skip Users may be selected
|
CUCM-ROUTE-PATTERN have a destination field that can be either routelist or gateway, but never both.(cucm-route-pattern-with-gateway-and-routelist*) | TBD |
|
Target object has been deleted, select bulk change to unmap target mapping. |
|
|
CUCM-SOFTKEY-TEMPLATE self reference.(cucm-softkey-template-self-reference) | Wrangler UCMC have detected that there is SKT template/s that references 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 target and cannot be migrated (cucm-remote-destination-orphaned*) | Orphaned RD’s in source | Select Bulk change Resolve to clear
|
Orphaned CUCM-REMOTE-DEST-PROFILE exists in target and cannot be migrated(cucm-remote-dest-profile-orphaned*) | Orphaned RDP’s in source | Select Bulk change Resolve to clear |
Orphaned CUCM-TOD-ACCESS exists in target and cannot be migrated(cucm-tod-access-orphaned*) | Orphaned TOD’s in source | Select Bulk change to clear |
Orphaned CUCM-TIME-SCHEDULE exists in target and cannot be migrated(cucm-time-schedule-orphaned*) | 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-orphan-hunt-list*) | Hunt Pilot without Hunt List | Select Skip Objects
|
CUCM Hunt Pilot has more than one line-group and therefore cannot be transformed to WXC-MT(cucm-hunt-pilot-has-too-many-line-groups-for-wxc-transform*) | This scenario with more than one line group associated to Hunt List is not supported in WxC-MT | Remove additional Line-Groups from Hunt List
|
CUCM-HUNT-LIST with invalid configuration, has no members and cannot be migrated.(hunt-list-has-no-members*)
| Hunt List without Line Group | Select Skip Objects
|
CUCM-SERVICE-PROFILE directory password contains special characters that causes AXL error (CSCvz61706).(cucm-service-profile-directory-password-invalid)
| Invalid characters in password |