PDF(191.0 KB) View with Adobe Reader on a variety of devices
ePub(206.8 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(168.5 KB) View on Kindle device or Kindle app on multiple devices
Updated:August 11, 2019
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 describesa problem encountered where Jabber is unable to login after a server reboot or XCP router service stop/start.
If there is a requirement to reboot IM&P nodes following a domain name change, or to stop/start the XCP router service due to a change of IM address scheme, Jabber clients login may fail with “cannot communicate with server” error.
In order to troubleshoot this problem, verify these points:
1. If there are multiple IM&P nodes in the cluster, check the dbreplication on the IM&P primary node CLI mode and ensure the status is showing “(2) Setup Completed”: