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

Change Server IP Address

Table Of Contents

Change Server IP Address

Change IP Address of Publisher Server

Change IP Address of Subscriber Server


Change Server IP Address


Change IP Address of Publisher Server

Change IP Address of Subscriber Server

Change IP Address of Publisher Server


Caution Changing the IP address of a publisher node will invalidate the server software license for virtual servers.

Use this procedure to change the IP address of a publisher server.

Procedure


Step 1 Complete the Pre-Change Tasks.


Note You can skip Steps 2 to 4 if the node name is not set to the IP address.


Step 2 If the cluster topology node name for the publisher node is defined by IP address, you must change the publisher node name; otherwise, skip to Step 5.

From Cisco Unified Presence Administration, perform the following tasks on the publisher server:

a. On the publisher server, navigate to Cisco Unified Presence Administration > System > Cluster Topology.

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

c. In the Node Configuration section, change the IP address of the Cisco Unified Presence server.

d. Select Save.

Step 3 Ensure that the IP address change is replicated to all subscriber nodes in the cluster by entering the following command on each subscriber node:

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 IP address has been replicated to all nodes in the cluster.

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

a. In the Cluster Topology window update the publisher node name to the old IP address.

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
 
   

d. Return to Step 1 of this procedure.

Step 4 Verify that the new IP address is listed in the application server list on Cisco Unified Communications Manager Administration. Perform the following tasks to reflect the new IP address on the publisher server:

a. From the Cisco Unified Communications Manager Administration GUI, navigate to System > Application Server.

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

c. Verify that the new IP address exists in the application server list. If the new IP address is not listed, add it.

Step 5 If you have DNS, perform the following actions:

a. Change the DNS record of the publisher server to point to the new IP address.

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

Step 6 Change the IP address of the publisher server on each subscriber server in the cluster by performing the following tasks in the CLI for each subscriber server:

a. Enter the following command:

set network cluster publisher ip new_ip_address 
 
   

b. Enter Yes and press Enter. The server restarts automatically.


Note Cluster topology configuration is now complete. The following steps address the network configuration changes.


Step 7 (Optional) If you are moving the server to a different subnet that requires a new default gateway address, complete the following steps:

a. Verify that the routing communication type is Router-to-Router by selecting Cisco Unified Presence Administration > Cluster Topology > Settings. If the routing communication type is Multicast DNS, change it to Router-to-Router.

b. Enter the following CLI command: set network gateway new_gateway

The following output displays:

admin:set network gateway 10.53.56.1
 
   
WARNING: Changing this setting will invalidate software license 
on this server. The license will have to be re-hosted.
 
   
Continue (y/n)?
 
   

Enter yes and press Enter.

Step 8 Change the IP address of the publisher server by entering the following CLI command:

set network ip eth0 ip_address netmask
 
   

where ip_address specifies the new server IP address, and netmask specifies the new server network mask.

The following output displays:

admin:set network ip eth0 10.53.57.101 255.255.255.224
 
   
WARNING: Changing this setting will invalidate software license 
on this server. The license will have to be re-hosted.
 
   
Continue (y/n)?
 
   

Enter yes and press Enter.

Step 9 If you use DNS, ensure that local resolution of the subscriber node also resolves to the new IP address by running the following CLI command:

utils network host pub-hostname 

where pub-hostname is the publisher hostname. Sample output is as follows:

admin:utils network host cup-123
Hostname cup-123 resolves to 14.86.13.11
 
   

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

utils system restart
 
   

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
 
   

NoteIt is important to verify that all nodes show a replication status of Connected and a replication setup value of (2) Setup Complete. Anything other than 2 means that there is a problem with database replication and that you need to reset replication.

You can run the utils dbreplication runtimestate command repeatedly until the replication setup value turns to 2.


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 IP Address of Subscriber Server

Use this procedure to change the IP address of a subscriber server if your servers are defined by IP addresses. To successfully change the IP address, you must complete all steps in this procedure.

When you change the IP address of more than one subscriber server, we recommend that you:

a. Change the IP address for one server at a time.

b. Restart all other servers in the cluster (including the publisher server).

c. Check the replication status. If the changed IP address reflects properly, follow the same procedure on the next server. Do not change the IP address of another server until replication is successful.

Procedure


Step 1 Complete the Pre-Change Tasks.


Note You can skip Steps 2 to 4 if the node name is not set to the IP address.


Step 2 If the cluster topology node name for subscriber node is defined by IP address, you must change the subscriber node name, otherwise, skip to Step 5.

From Cisco Unified Presence Administration, perform the following tasks on the subscriber server:

a. Navigate to System > Cluster Topology.

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

c. In the Node Configuration section, change the IP address of the Cisco Unified Presence server.

d. Select Save.

Step 3 Ensure that the IP address change is replicated to all the nodes in the cluster by entering the following CLI command:

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 IP address has been replicated to all nodes in the cluster.

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

a. In the Cluster Topology window update the subscriber node name to the old IP address.

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
 
   

d. Return to Step 1 of this procedure.

Step 4 From Cisco Unified Communications Manager Administration, perform the following tasks to reflect the new IP address on the subscriber server:

a. Navigate to System > Application Server.

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

c. Verify that the new IP address exists in the application server list. If the new IP address is not listed, add it.

Step 5 (Optional) If you are moving the server to a different subnet that requires a new default gateway address, complete the following steps:

a. Verify that the routing communication type is Router-to-Router by selecting Cisco Unified Presence Administration > Cluster Topology > Settings. If the routing communication type is Multicast DNS, change it to Router-to-Router.

b. Enter the CLI command set network gateway new_gateway

The following output displays:

admin:set network gateway 10.53.56.2
 
   
WARNING: Changing this setting will invalidate software license 
on this server. The license will have to be re-hosted.
 
   
Continue (y/n)?
 
   

Enter yes and press Enter.

Step 6 Change the IP address of the subscriber server by entering the following CLI command:

set network ip eth0 ip_address netmask
 
   

where ip_address specifies the new server IP address, and netmask specifies the new server network mask.

The following output displays:

admin:set network ip eth0 10.53.57.101 255.255.255.224
 
   
WARNING: Changing this setting will invalidate software license 
on this server. The license will have to be re-hosted.
 
   
Continue (y/n)?
 
   

Enter yes and press Enter.

Step 7 If you use DNS, ensure that local resolution of the other nodes also resolves to the new IP address by running the following CLI command:

utils network host sub-hostname 

where sub-hostname is the subscriber hostname. Sample output is as follows:

admin:utils network host cup-123
Hostname cup-123 resolves to 14.86.13.11
 
   

Step 8 Restart the publisher node with the following CLI command:

utils system restart
 
   

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

utils system restart
 
   

Step 10 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
 
   
 
   

NoteIt is important to verify that all nodes show a replication status of Connected and a replication setup value of (2) Setup Complete. Anything other than 2 means that there is a problem with database replication and that you need to reset replication.

You can run the utils dbreplication runtimestate command repeatedly until the replication setup value turns to 2.


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 11 If you are changing the IP address for more than one subscriber node, repeat this procedure on each subscriber node that you want to change.

Step 12 Complete the Post-Change Tasks.