Wrangler manual CUCM-USER mapping WxC-DI CI Sync
- Zane England
This process is used for wrangler 2.5.x to manually set the target mappings when Webex CI user syncronisation is used in the target WxC-DI cluster when the userId format is different between the source and target clusters.
This process needs to be done before running prepare
Export the CUCM-USER target mappings and manually map source to target usernames
The Target Mapping Name field needs to be updated with the correct values
Source Cluster | Source ID | Source Name | Source Site | Target Mapping Name | Target Mapping ID |
LDAP115-CUCM-XLS-Master | CUCM-USER_67B2F8D5-75CF-EBEF-50FC-332A3265C7B0_8078473A7D6F3408503DF10F6903CEE8 | dduck | New1 | dduck@wxc-dx.org.com |
|
LDAP115-CUCM-XLS-Master | CUCM-USER_C63B7033-DE2E-C610-84DF-EF71AD9EBEDE_8078473A7D6F3408503DF10F6903CEE8 | SMcduck | New1 | scrooge.mcduck@wxc-dx.org.com |
|
This process needs to be done in excel and care should be taken to match source and target user names in an case insensitve manner
Note that these validation rules may trigger and the validation rule cucm-user-ldap-missing-target-object may need to be disabled as these can trigger issues erroneously for all LDAP users when doing manual target mapping
Note that for clone migration the endpointLines[0].associatedEndusers[0].userId is not correctly handled in 2.5.x and manual interaction is required if this configuration is present on CUCM-LINEs
if this occurs the associatedEndUser will need to be removed
If the following error is received during load
Error execute-update-cucm-user DiscoveryUserIdentity entered for EndUser already exists. Unexpected AXL Error
Use a bulk change to find the target cluster CUCM-USER for which the change has not been completed
Verifiy the matching number of errors to results
Then set the following fields to blank
Mailid
Directory Uri
User Identity
This prevent wrangler from updating LDAP managed fields on CUCM-USER
If source LDAP users need to be converted to target local users due to those users not existing in target cluster
After load there will be errors relating to adding LDAP users, to resolve either
Manually set LDAP directory to null
Use bulk change with filters changeCompleted false on target CUCM-USER to set LDAP directory to null
Then restart load