PDF(25.1 KB) View with Adobe Reader on a variety of devices
ePub(98.2 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(184.9 KB) View on Kindle device or Kindle app on multiple devices
Updated:January 16, 2018
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes how to change Cisco IM&P hostname to FQDN. There are conditions that you require to change to FQDN in order to the IM&P Certificate Authority (CA) signed certificates to be accepted by Jabber client.
Contributed by Nenos Nicko, Cisco TAC Engineer.
Q. How to change Cisco IM&P node name from hostname to FQDN
If an IM&P publisher is changed, remove it as an intercluster peer on all other clusters.
Check on the IM&P admin GUI of the publisher node in each cluster to verify if alerts are displayed to restart Cisco XCP Router. If so, restart the XCP router on the nodes specified.
Navigate to Cisco Unified Communication Manager Administration > System > Presence Redundancy Groups page and disable High Availability on each Cisco Unified Presence sub-cluster.
Navigate to Cisco Unified Serviceability > Tools > Service Activation page and deactivate these services in this order on each Cisco Unified Presence node:
Cisco XCP Directory Service (If Previously Activated)
Cisco XCP File Transfer Manager (If Activated)
Cisco XCP Authentication Service
Navigate to Cisco Unified Communication Manager Administration > System > Presence Redundancy Groups page and enable High Availability again on each Cisco Unified Presence sub-cluster.
Navigate to Presence -> Inter-Clustering page on the publisher node of the other inter-cluster peers and re-add the peer entry for the node you just updated, this time with the new hostname.
Navigate to Cisco Unified Presence Administration > Presence > Inter-Clustering page to ensure all inter-cluster peers are up. If there are any errors on the Certificate Status view then perform these steps:
Click Force Manual Sync button
Ensure Also resync peer's Tomcat certificates is checked
Wait for the Inter-cluster Peer Status to refresh to see if the Certificate Status is now secure.
The Procedure is now complete. As mentioned in the notes, it can take up to 60 minutes before this change is fully pushed out to nodes on other clusters.