Changing the IP Address, Hostname, Domain Name and Node Name for Cisco Unified Presence Release 8.6(5)
Change Server Hostname
Downloads: This chapterpdf (PDF - 222.0KB) The complete bookPDF (PDF - 1.24MB) | Feedback

Change Server Hostname

Table Of Contents

Change Server Hostname

Change Publisher Server Hostname

Change Subscriber Server Hostname


Change Server Hostname


Change Publisher Server Hostname

Change Subscriber Server Hostname

Change Publisher Server Hostname


Caution Changing the hostname of a publisher node may invalidate the server's software license for virtual servers.

Use the following procedure to change the hostname of a publisher server in a cluster.

Procedure


Step 1 Complete the Pre-Change Tasks.

Step 2 Perform the following actions:

a. Change the DNS record of the publisher server to point to the new hostname, for example, newhost1. (For illustration purposes, newhost1 is used in the CLI command examples in this procedure.)

b. Ensure that you correctly update both the forward (A) and reverse (PTR) records.

Step 3 Verify that the DNS change propagates to other nodes by running the following CLI command on all the cluster nodes:

utils network host newhost1

where newhost1 is the new hostname

The output of this command is as follows:

admin:utils network host newhost1
Hostname newhost1 resolves to 14.86.13.11
 
   

Step 4 If the cluster topology node name for the publisher node is defined by IP address, skip to Step 7; otherwise, from Cisco Unified Presence Administration, perform the following tasks on the publisher server:

a. Navigate to System > Cluster Topology.

b. Select the publisher node from the Cluster Topology tree-view.

c. In the Node Configuration section, update the name to reflect the new hostname as follows:

If the server is defined by hostname, replace the old hostname with the new hostname. For example, update the Name from "old-host" to "new-host".

If the server is defined by FQDN, update the FQDN value to reflect the new hostname rather than the old hostname. For example, update the Name from "old-host.example.com" to "new-host.example.com".

d. Select Save.

Step 5 From Cisco Unified Communications Manager Administration, perform the following tasks:

a. Navigate to System > Application Server.

b. Select Find from the Find and List Servers window to display the server.

c. Verify that the new node name value is listed among the servers. If the new node name value is not listed, add it.

Step 6 Ensure that the hostname change is replicated to all the nodes in the cluster. To do this, enter the following command from the CLI on all nodes in the cluster:

run sql select name,nodeid from ProcessNode
 
   

The following example shows the command output:

admin: run sql select name,nodeid from ProcessNode
name               nodeid
================== ======
EnterpriseWideData 1
10.3.90.21         4
10.3.90.5          2
 
   

Caution Do not proceed to the next step until the updated node name value has been replicated to all nodes in the cluster.

If the node name has not been replicated to all nodes in the cluster, complete the following recovery steps:

a. In the Cluster Topology screen update the publisher node name to the old hostname.

b. On the publisher node, run the following command to reset database replication:

utils dbreplication reset all
 
   

c. On the publisher node, run the following command and ensure that the replication state is 2 on all nodes:

utils dbreplication runtimestate
 
   

Note You can run this command repeatedly until the replication state turns to 2 on all nodes.


d. Return to Step 4 of this procedure.

Step 7 Change the hostname of the publisher server on each subscriber server in the cluster by entering the following command in the CLI for each subscriber server:

set network cluster publisher hostname new_hostname
 
   

For example:

set network cluster publisher hostname newhost1
 
   

Step 8 On the publisher server, change the hostname of the server as follows:

a. Enter the CLI command set network hostname newhost1

where newhost1 is the new hostname

b. Enter Yes and press Enter. This will automatically restart this server with the new hostname.

Step 9 After the publisher node has restarted, restart all subscriber nodes with the following CLI command:

utils system restart
 
   

Step 10 After all nodes have restarted successfully, run the following CLI command on the publisher node to reset replication:

utils dbreplication reset all

Note Depending on the size of the database, it may take several minutes to over an hour for replication to be reestablished.


Step 11 Verify that database replication has been successfully established by entering the following command on the publisher node:

utils dbreplication runtimestate
 
   

Sample output is as follows:

DDB and Replication Services: ALL RUNNING
 
   
DB CLI Status: No other dbreplication CLI is running...
 
   
Cluster Replication State: BROADCAST SYNC Completed on 1 servers at: 2012-09-26-15-18
Last Sync Result: SYNC COMPLETED 257 tables sync'ed out of 257
Sync Errors: NO ERRORS
 
   
DB Version: ccm9_0_1_10000_9000
Number of replicated tables: 257
Repltimeout set to: 300s
 
   
Cluster Detailed View from gwydlvm020105 (2 Servers):
 
   
                                PING            REPLICATION     REPL.   DBver&  REPL.   REPLICATION SETUP
SERVER-NAME     IP ADDRESS      (msec)  RPC?    STATUS          QUEUE   TABLES  LOOP?   (RTMT) & details 
-----------     ------------    ------  ----    -----------     -----   ------- -----   -----------------
gwydlvm020105 192.168.20.244 	0.038   	Yes   							 	Connected       	0 				match   	Yes 		 (2) PUB Setup Completed
gwydlvm020106 192.168.10.201 	0.248   Yes   									Connected       128     match   Yes     (2) Setup Completed
 
   

Note It is important to verify that REPLICATION SETUP (RTMT) & details all report a state of 2. Anything other than 2 means that there is a problem with database replication and that you need to reset replication.


If replication is not set up, complete the following troubleshooting steps:

a. Reset replication by entering the following command on the publisher node:

utils dbreplication reset all
 
   

b. Run the following command again on the publisher node to check the replication status:

utils dbreplication runtimestate
 
   

Step 12 Complete the Post-Change Tasks.


Change Subscriber Server Hostname

Use the following procedure to change the hostname of subscriber servers in a cluster.

Procedure


Step 1 Complete the Pre-Change Tasks.

Step 2 Perform the following actions:

a. Change the DNS record of the subscriber server to point to the new hostname, for example, newhost1. (For illustration purposes, newhost1 is used in the CLI command examples in this procedure.)

b. Ensure that you correctly update both the forward (A) and reverse (PTR) records.

Step 3 Verify that the DNS change propagates to other nodes by running the following CLI command on all the cluster nodes:

utils network host newhost1

where newhost1 is the new hostname

The output of this command is as follows:

admin:utils network host newhost1
Hostname newhost1 resolves to 14.86.13.11
 
   

Step 4 If the cluster topology node name for the subscriber node is defined by IP address, skip to Step 7; otherwise, from Cisco Unified Presence Administration, perform the following tasks on the publisher server:

a. Navigate to System > Cluster Topology.

b. Select the subscriber node from the Cluster Topology tree-view.

c. In the Node Configuration section, update the name to reflect the new hostname as follows:

If the server is defined by hostname, replace the old hostname with the new hostname. For example, update the Name from "old-host" to "new-host".

If the server is defined by FQDN, update the FQDN value to reflect the new hostname rather than the old hostname. For example, update the Name from "old-host.example.com" to "new-host.example.com".

d. Select Save.

Step 5 From Cisco Unified Communications Manager Administration, perform the following tasks:

a. Navigate to System > Application Server.

b. Select Find from the Find and List Servers window to display the server.

c. Verify that the new node name value is listed among the servers. If the new node name value is not listed, add it.

Step 6 Ensure that the hostname change is replicated to all the nodes in the cluster. To do this, enter the following command from the CLI on all nodes in the cluster:

run sql select name,nodeid from ProcessNode
 
   

The following example shows the command output:

admin: run sql select name,nodeid from ProcessNode
name               nodeid
================== ======
EnterpriseWideData 1
10.3.90.21         4
10.3.90.5          2
 
   

Caution Do not proceed to the next step until the updated node name value has been replicated to all nodes in the cluster.

If the node name has not been replicated to all nodes in the cluster, complete the following recovery steps:

a. In the Cluster Topology screen update the subscriber node name to the old hostname.

b. On the publisher node, run the following command to reset database replication:

utils dbreplication reset all
 
   

c. On the publisher node, run the following command and ensure that the replication state is 2 on all nodes:

utils dbreplication runtimestate
 
   

Note You can run this command repeatedly until the replication state turns to 2 on all nodes.


d. Return to Step 4 of this procedure.

Step 7 On the subscriber server, change the hostname of the server as follows:

a. Enter the CLI command set network hostname newhost1

where newhost1 is the new hostname

b. Enter Yes and press Enter. This will automatically restart this server with the new hostname.

Step 8 Restart the publisher node in the cluster with the following command:

utils system restart
 
   

Step 9 Restart all other subscriber nodes in the cluster with the following command:

utils system restart
 
   

Step 10 After all nodes have restarted successfully, run the following CLI command on the publisher node to reset replication:

utils dbreplication reset all

Note Depending on the size of the database, it may take several minutes to over an hour for replication to be reestablished.


Step 11 Verify that database replication has been successfully established by entering the following command on the publisher node:

utils dbreplication runtimestate
 
   

Sample output is as follows:

DDB and Replication Services: ALL RUNNING
 
   
DB CLI Status: No other dbreplication CLI is running...
 
   
Cluster Replication State: BROADCAST SYNC Completed on 1 servers at: 2012-09-26-15-18
Last Sync Result: SYNC COMPLETED 257 tables sync'ed out of 257
Sync Errors: NO ERRORS
 
   
DB Version: ccm9_0_1_10000_9000
Number of replicated tables: 257
Repltimeout set to: 300s
 
   
Cluster Detailed View from gwydlvm020105 (2 Servers):
 
   
                                PING            REPLICATION     REPL.   DBver&  REPL.   REPLICATION SETUP
SERVER-NAME     IP ADDRESS      (msec)  RPC?    STATUS          QUEUE   TABLES  LOOP?   (RTMT) & details 
-----------     ------------    ------  ----    -----------     -----   ------- -----   -----------------
gwydlvm020105 192.168.20.244 	0.038   	Yes   							 	Connected       	0 				match   	Yes 		 (2) PUB Setup Completed
gwydlvm020106 192.168.10.201 	0.248   Yes   									Connected       128     match   Yes     (2) Setup Completed
 
   

Note It is important to verify that REPLICATION SETUP (RTMT) & details all report a state of 2. Anything other than 2 means that there is a problem with database replication and that you need to reset replication.


If replication is not set up, complete the following troubleshooting steps:

a. Reset replication by entering the following command on the publisher node:

utils dbreplication reset all
 
   

b. Run the following command again on the publisher node to check the replication status:

utils dbreplication runtimestate
 
   

Step 12 If you are changing the hostname for more than one subscriber node, repeat this procedure on each subscriber node that you want to change.

Step 13 Complete the Post-Change Tasks.