Cisco Unified Presence, Release 7.x -- Changing the Cluster IP Addresses for Subscriber Servers Defined by IP Addresses

From DocWiki

Jump to: navigation, search

Main page: Cisco Unified Presence, Release 7.x

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

Contents

Previous Topic
Before You Begin

If you need to change the gateway address, do so before you change the IP address. If you first change the IP address, the Cisco Unified Presence server will reboot immediately and you will not be able to change the gateway.


Procedure
  1. From Cisco Unified Presence Administration, perform the following tasks on the subscriber server:
    1. Navigate to System > Topology.
    2. Change the IP address of the Cisco Unified Presence server under Node Detail Configuration.
  2. From Cisco Unified Communications Manager Administration, perform the following tasks to reflect the new hostname on the subscriber server:
    1. Navigate to System > Application Server.
    2. Change the host name of the Cisco Unified Presence server under Application Server Configuration.
    Note: In Release 7.03 and later, Cisco Unified Presence attempts to change the hostname automatically. However, you must still verify the entry, and change it if the correct value is not automatically populated.
  3. Ensure that the host name or IP address change is replicated to all the nodes in the cluster as follows:
    1. via the Node Detail window in Cisco Unified Presence Administration (System > Topology)
    2. by entering the 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
  4. Repeat on all nodes in the cluster.
  5. If you are moving the server to a different subnet that requires a new default gateway address, change the default gateway as follows:
If you want to use: Action

Cisco Unified Communications Operating System

From Cisco Unified Communications Operating System Administration, perform the following tasks.

  1. Choose Settings > IP > Ethernet.
  2. Enter the new IP addresses.
  3. Click Save. The server reboots automatically.

Note: If you choose to use this method, perform this step at the same time as Step 6.

CLI command

1. Enter the CLI command set network gateway

The following output displays:
admin: set network gateway 10.3.90.2
*** W A R N I N G ***
This will cause the system to temporarily lose network connectivity
Do you want to continue ?
Enter "yes" to continue or any other key to abort
yes
executing...
admin:

2. Enter yes and press Enter.

6. Change the IP address of the subscriber server, and if necessary, change the default gateway to the new IP address of the subscriber server, by performing the following tasks:

If you want to use: Action Troubleshooting Tips

Cisco Unified Communications Operating System

From Cisco Unified Communications Operating System Administration, perform the following tasks.

  1. Choose Settings > IP > Ethernet.
  2. Enter the new IP addresses.
  3. Click Save. The server reboots automatically.

CLI command

1. Enter the 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.3.90.21 255.255.254.0
*** W A R N I N G ***
If there are IP addresses (not hostnames)
configured in CallManager Administration
under System -> Servers
then you must change the IP address there BEFORE
changing it here or call processing will fail.
This will cause the system to restart
=======================================================
Note: To recognize the new IP address all nodes within
the cluster will have to be manually rebooted.
=======================================================
Do you want to continue?
Enter "yes" to continue and restart or any other key to abort

2. Enter yes and press Enter.

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

  1. Change the hostname or IP address for one server at a time.
  2. Restart all other servers in the cluster (including the publisher server) to update the local name resolution files, such as hosts, rhosts, sqlhosts, and services.

Caution! Do not change the hostname or IP address of more than one server at the same time because it can cause .rhosts and sqlhosts files to be out of sync in the cluster.


7. Verify the result of the database replication.

Database Replication Status Action

If the changed hostname or IP address propagates correctly cluster-wide:

Return to Step 6 and complete the procedure on the next subscriber server.

If the changed hostname or IP address does not propagate to the other servers in the cluster:

Sign in to the CLI for each server in the cluster and complete these steps:

  1. Run the command utils dbreplication stop on the subscriber servers one at a time. Wait for the command to complete successfully.
  2. Run the command utils dbreplication stop on the publisher server. Wait for the command to complete successfully.
  3. Run the command utils dbreplication dropadmindb on the subscriber servers one at a time. Wait for the command to complete successfully.
  4. Run the command utils dbreplication dropadmindb on the publisher server. Wait for the command to complete successfully.
  5. On the publisher server ONLY, run the command utils dbreplication clusterreset. Wait for the command to complete successfully.
  6. Restart the subscriber servers.
  7. If publisher hostname or IP address changed, reboot the publisher server.
  8. Login to the publisher server CLI again and run the command utils dbreplication runtimestate on the publisher server to monitor the results of database replication. All servers should be in RTMT State 2.



Troubleshooting Tips
  • If you changed switches in addition to changing the gateway and IP address for the Cisco Unified Presence server, complete these steps while the server is automatically rebooting. Otherwise, some of the CUP scripts may fail network connectivity checks upon startup.
    • watch the reboot screen
    • enter a `ping -t' on the old IP address
    • when the pings are no longer successful, disconnect from the old switch and connect to the new switch
  • The local name resolution files, such as hosts, rhosts, sqlhosts, and services are only updated during system startup. You need to restart core network services, such as Cisco DB and Cisco Tomcat, after the files are updated. Restarting the servers ensures that the proper update and service-restart sequence for the IP address changes take effect.


Related Topics


What To Do Next

Post-Change Task List

Rating: 0.0/5 (0 votes cast)

Personal tools