Modify Node Name

Procedure Overview

This procedure allows you to modify the node name that is associated with a IM and Presence node or group of nodes. This procedure modifies the node name as it appears in the Cluster Topology window in the IM and Presence Administration GUI.

Caution This procedure is used only when changing the node name of an IM and Presence node where there are no network level changes required. If changes to the network IP address, hostname or domain name are required, complete the relevant procedure in this document instead.

Caution Changing the node name on any node in an IM and Presence cluster will result in server restarts and interruptions to presence services and other system functions. Because of this impact to the system, you must perform this node name change procedure during a scheduled maintenance window.

This procedure supports the following node name change scenarios:

IP address to hostname

IP address to Fully Qualified Domain Name (FQDN)

hostname to IP address

hostname to FQDN

FQDN to hostname

FQDN to IP address

Note See the Configuration and Administration of IM and Presence Service on Cisco Unified Communications Manager on Cisco.com for more information about node name recommendations.

Procedure Workflow

The following table contains the step-by-step instructions for modifying the node name that is associated with an IM and Presence node or group of nodes. The detailed instructions for this procedure specify the exact order of steps for performing the change.

If you are performing this procedure across multiple clusters you must complete the changes sequentially on one cluster at a time.

Verify Database Replication

Note Use the validation mechanisms listed below to verify that the new node name(s) have been replicated across the cluster and that database replication is operational.

Procedure

Step 1 To validate that the new node name has been correctly replicated, run the following command from the Administration CLI on all nodes in the cluster:

run sql name from ProcessNode

The following example shows the command output:

admin:run sql select name from ProcessNode

name

=====================

EnterpriseWideData

server1.example.com

server2.example.com

server3.example.com

server4.example.com

Verify that there is an entry for each node in the cluster that specifies the new node name. No old node name should appear in the output. Proceed as follows:

a. If any new node names are missing or if there are references to old node names proceed to Step 2 to further validate database replication.

b. If the output is as expected, the validation has passed and you can ignore the remaining steps in this procedure.

Step 2 If the new node name is not correctly listed in Step 1, verify that database replication is in a correct state in the cluster by running the following command from the Administration CLI on the publisher node:

a. Verify that the output shows a replication status of Connected and a replication setup value of (2) Setup Complete for each node. This means that the replication network within the cluster is up and you can proceed to Step 3 to repair any mismatches between nodes in the cluster.

b. If the replication status and replication setup value are not as expected, then the replication network within the cluster is broken and you must proceed to Step 5 to attempt to reestablish replication.

Step 3 Run the following command from the Administration CLI on the publisher node to attempt to repair replication:

utils dbreplication repair all

The following example shows the command output.

admin:utils dbreplication repair all

-------------------- utils dbreplication repair --------------------

Replication Repair is now running in the background.

Use command 'utils dbreplication runtimestate' to check its progress

Output will be in file cm/trace/dbl/sdi/ReplicationRepair.2013_03_06_12_33_57.out

Please use "file view activelog cm/trace/dbl/sdi/ReplicationRepair.2013_03_06_12_33_57.out " command to see the output

Note Depending on the size of the database, it may take several minutes to repair database replication.

Proceed to Step 4 to monitor the progress of the replication repair.

Step 4 Run the following command from the Administration CLI on the publisher node to check the progress of replication repair:

utils dbreplication runtimestate

The following example shows the output when replication is complete. The text in bold highlights the final status of the replication repair: