IP Address, Domain and Hostname for IM and Presence Service on Cisco Unified Communications Manager, Release 9.0(1)
Modify the SIP Domain of an IM and Presence Cluster
Downloads: This chapterpdf (PDF - 79.0KB) The complete bookPDF (PDF - 586.0KB) | Feedback

Modify the SIP Domain of an IM and Presence Cluster

Table Of Contents

Modify the SIP Domain of an IM and Presence Cluster

Replace the Default Domain Value

Change the Domain Value


Modify the SIP Domain of an IM and Presence Cluster


November 30, 2012

Replace the Default Domain Value

Change the Domain Value

Replace the Default Domain Value

The domain name specifies the DNS domain name of the IM and Presence server. IM and Presence automatically defaults to the domain name DOMAIN.NOT.SET. You must replace this default domain name with the DNS domain name in order for the SRM to initialize correctly in a High Availability deployment.

If you are not using DNS in your network, and you did not set the domain at install, you must replace this default value with the enterprise wide domain and ensure the node names are configured as IP addresses or IM and Presence will not function correctly.

Perform this configuration on all nodes in your IM and Presence cluster.

Procedure


Step 1 Perform the following steps to configure the new domain value:

a. Select IM and Presence Administration > System > Cluster Topology.

b. In the right pane, select Settings.

c. Configure the Domain Name value with the new domain.

a. Select IM and Presence Administration > System > Service Parameters, and select the Cisco SIP Proxy service.

b. Configure the Federation Routing IM and Presence FQDN with the new domain.

c. You will be prompted to confirm these configuration changes. Select OK for both prompts, and then select Save.

Step 2 Use this CLI command to set the new domain:

set network domain <new_domain>

This CLI command invokes a reboot of the server.

Step 3 Manually regenerate all certificates on the local IM and Presence server.


Note When you regenerate the Tomcat certificate, you must restart Tomcat. You can restart Tomcat after you regenerate all of the certificates on the local server. Use this CLI command to restart Tomcat: utils service restart Cisco Tomcat



Change the Domain Value

Follow this procedure if you want to change the domain value (from one valid domain value to another valid IP proxy domain value).

This procedure is applicable if you have a DNS or non-DNS deployment.


Note It is highly recommended that you use a DNS deployment. In order to be considered valid, the domain value must match the DNS domain name. Using a valid domain name ensures that the SRM initializes correctly in a High Availability deployment.


Procedure


Step 1 Stop the Cisco SIP Proxy, Presence Engine and XCP Router services on IM and Presence on all nodes in your cluster.

Step 2 On the publisher node, perform the following steps to configure the new domain value:

a. Select IM and Presence Administration > System > Cluster Topology.

b. In the right pane, select Settings.

c. Configure the Domain Name value with the new domain.

a. Select IM and Presence Administration > System > Service Parameters, and select the Cisco SIP Proxy service.

b. Configure the Federation Routing IM and Presence FQDN with the new domain.

c. You will be prompted to confirm these configuration changes. Select OK for both prompts, and then select Save.

Step 3 On all nodes in the cluster, use this CLI command to set the new domain:

set network domain <new_domain>

This CLI command invokes a reboot of the servers.

Step 4 On all nodes in the cluster, manually start the Cisco Presence Engine and Cisco XCP Router services after the reboot is complete (if required).

Step 5 Manually regenerate all certificates on each node in the cluster.


Note When you regenerate the Tomcat certificate, you must restart Tomcat. You can restart Tomcat after you regenerate all of the certificates on the local server. Use this CLI command to restart Tomcat: utils service restart Cisco Tomcat


Step 6 If you use DNS in your network, update the DNS configuration for the new domain. Update any host records and any DNS SRV records that you require for the new domain.

Step 7 Configure any XMPP clients with the new domain.