Greetings,
Wanted to share a few lessons learned while migrating from a distributed to centralized IMP deployment. Our current setup included many CUCM/IMP distributed clusters with centralized Expressway server for MRA login. We did not wish to perform a flash cut of all users. Centralized IMP was the goal to reduce server footprint, streamline compliance, and still provide distributed telephony and cluster specific dialing habits to end users. The IMP Configuration and Administration Guide does outline the migration process for IMP but does not cover MRA extensively. Below are some notes for the migration that follow the sequencing of the guide and include additional notes in italics. This is meant to be ready in conjunction with the “Migrate Users to Centralized Deployment” section of the Configuration and Administration of the IM and Presence service guide. We are running version 12.5, link below. This guide is also recommended for deploying the centralized environment.
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/im_presence/configAdminGuide/12_5_1/cup0_b_config-and-admin-guide-1251/cup0_b_config-and-admin-guide-1251_chapter_0100011.html
Centralized CUCM/IMP Cluster deployment notes:
- Centralized Cluster SHOULD NOT be a part of Enterprise ILS network
- OAuth login required
- Initially IMP peer relationship should be established to all migrating IMP clusters (prior to Expressway configuration)
- Centralized CUCM node should be added to Cisco Expressway>Configuration>Unified Communications>Unified CM Servers
- Centralize IMP node should be added to Cisco Expressway>Configuration>Unified Communications>IM and Presence Service nodes
- We performed LDAP synchronization on Central Cluster during deployment
Migrating to Centralized IMP notes:
- Export contact Lists from migrating cluster
- Many of our Migrating Cluster did not have the Bulk Provisioning Service activated. This will cause the export job to remain in a state of pending and needs to be activated
- When exporting contacts lists using Query> “All assigned users in the cluster” this is a good opportunity to create a “Migrating Users Roster.” This includes domain and is useful if you need to send some type of bulk communication to end users advising them of the upcoming changes. Users will need to re-authenticate after being migrated.
- Configure UC Service for IM and Presence
- New UC Service for Centralized IMP servers
- Create Service Profile for IMP and Presence
- We left the “credentials source for voicemail service” at “Not Set” on the service profile in the telephony cluster
- Disable Presence Users in Telephony Cluster
- Be sure to export your contacts lists prior to performing this step.
- List of settings for End Users on telephony (migrating) cluster after updates
- Home Cluster > Checked
- Enable User for Unified IM and Presence > Unchecked
- UC Service Profile > Use newly created profile
- End User Permissions > Leave the same as prior
- Enable Oauth Authentication for Central Cluster
- This was already completed
- Disable High Availability in Central Cluster
- Did not perform this step during migrations
- Delete Peer Relationship for Central and Migrating Clusters
- Critical step will cause issues if not completed. You also must remove the peer relationships between IMP clusters that have not migrated to Centralized deployment. If you do not this will manifest as users unable to login with LERR_INTERNAL_SERVER_ERROR <31> in Jabber Problem Report. For example, say you have Cluster A – Central Cluster, Cluster B – Migrating Cluster, and Cluster C – cluster yet to be migrated. You must delete the peer relationship between Cluster C and Cluster B after migrating cluster B users to centralized deployment.
- This will require XCP Router Restarts on all IMP clusters involved.
- Stop the Intercluster Sync Agent
- Did not perform this step during migrations
- Enable IM and Presence via Feature Group Template
- LDAP sync was completed when configuring Central Cluster. We updated all settings using Bulk Admin.
- Complete the LDAP sync On Central Cluster
- This was already completed.
- Enable Users for IM and Presence via Bulk Admin
- Found the easiest way to complete this task was with bat.xlt although you can use Bulk Admin methodology of choice. Need to add one of the customizable values before the remaining columns are populated in bat.xlt. We used # as value for field to be ignored. I have attached the .csv template used to update users in Centralized environment.
- Recommend creating an Access Control Group with required permissions prior to user update
- List of Settings for End Users on Centralized Cluster
- Home Cluster > Checked
- Enable User for Unified IMP and Presence > Checked
- UC Service Profile > Created Profile
- End User Permissions > New Access Control Group (Standard CCM End Users, Standard CTI Allow Call Monitoring, Standard CTI Allow Call Park Monitoring, Standard CTI Allow Call Recording, Standard CTI Allow Calling Number Modification, Standard CTI Allow Control of All Devices, Standard CTI Allow Control of Phone supporting rollover, Standard CTI Allow Reception of SRTP Key Material, Standard CTI Enabled)
- Import Contacts Lists into Central Cluster
- It may take a while before the contacts are populated
- Start Cisco Intercluster Sync Agent
- Did not perform this step during migrations
- Enable High Availability in Central Cluster
- Did not perform this step during migrations
- Delete Remaining Peers for Migrating Cluster
- See notes on Delete Peer Relationship for Central and Migrating Clusters. At this point all peers should be removed from the migrating cluster.
Not included in guide but should be performed for MRA
- Navigate to Expressway>Configuration>Unified Communications>IM and Presence Service Nodes and delete the IMP nodes of the cluster migrated. The CUCM and CUC nodes of the telephony cluster remain.
Here is another resource for migrations to Centralized IMP.
https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_MESSAGING-UnifiedCM_IMP_Distributed_to_Centralized.pdf
