cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
9677
Views
0
Helpful
3
Replies

Deleting a server node from CUCM cluster

tacl75
Level 1
Level 1

Hi,

I have a cucm 8.6.2 cluster with 6 subscriber nodes and wanted to remove 1 node from it. I readup this site:

Just trying to clarify my doubt. Is executing the script necessary to remove the replication entries?
cheers,
TA
1 Accepted Solution

Accepted Solutions

Suresh Hudda
VIP Alumni
VIP Alumni

I don't think you need to run these script in cucm 8.6, the link which you have here is for 4.x

But before you delete a server, consider the following information:

•Cisco Unified Communications Manager Administration does not allow you to delete the first node in the cluster, but you can delete any subsequent node.

•Cisco recommends that you do not delete any node that has Cisco Unified Communications Manager running on it, especially if the node has devices, such as phones, registered with it.

•Although dependency records exist for the subsequent nodes, the records do not prevent you from deleting the node.

•If any call park numbers are configured for Cisco Unified Communications Manager on the node that is being deleted, the deletion fails. Before you can delete the node, you must delete the call park numbers in Cisco Unified Communications Manager Administration.

•If a configuration field in Cisco Unified Communications Manager Administration contains the IP address or host name for a server that you plan to delete, update the configuration before you delete the server. If you do not perform this task, features that rely on the configuration may not work after you delete the server; for example, if you enter the IP address or host name for a service parameter, enterprise parameter, service URL, directory URL, IP phone service, and so on, update this configuration before you delete the server.

•If an application GUI, for example, Cisco Unity, Cisco Unity Connection, and so on, contains the IP address or host name for the server that you plan to delete, update the configuration in the corresponding GUIs before you delete the server. If you do not perform this task, features that rely on the configuration may not work after you delete the server.

•The system may automatically delete some devices, such as MOH servers, when you delete a server.

•Before you delete a node, Cisco recommends that you deactivate the services that are active on the subsequent node. Performing this task ensures that the services work after you delete the node.

•Changes to the server configuration do not take effect until you restart Cisco Unified Communications Manager. For information on restarting the Cisco CallManager service, see the Cisco Unified Serviceability Administration Guide.

•To ensure that database files get updated correctly, you must reboot the cluster after you delete a server.

•After you delete the node, access Cisco Unified Reporting to verify that Cisco Unified Communications Manager removed the node from the cluster. In addition, access Cisco Unified Reporting, RTMT, or the CLI to verify that database replication is occurring between existing nodes; if necessary, repair database replication between the nodes by using the CLI. Suresh

View solution in original post

3 Replies 3

Suresh Hudda
VIP Alumni
VIP Alumni

I don't think you need to run these script in cucm 8.6, the link which you have here is for 4.x

But before you delete a server, consider the following information:

•Cisco Unified Communications Manager Administration does not allow you to delete the first node in the cluster, but you can delete any subsequent node.

•Cisco recommends that you do not delete any node that has Cisco Unified Communications Manager running on it, especially if the node has devices, such as phones, registered with it.

•Although dependency records exist for the subsequent nodes, the records do not prevent you from deleting the node.

•If any call park numbers are configured for Cisco Unified Communications Manager on the node that is being deleted, the deletion fails. Before you can delete the node, you must delete the call park numbers in Cisco Unified Communications Manager Administration.

•If a configuration field in Cisco Unified Communications Manager Administration contains the IP address or host name for a server that you plan to delete, update the configuration before you delete the server. If you do not perform this task, features that rely on the configuration may not work after you delete the server; for example, if you enter the IP address or host name for a service parameter, enterprise parameter, service URL, directory URL, IP phone service, and so on, update this configuration before you delete the server.

•If an application GUI, for example, Cisco Unity, Cisco Unity Connection, and so on, contains the IP address or host name for the server that you plan to delete, update the configuration in the corresponding GUIs before you delete the server. If you do not perform this task, features that rely on the configuration may not work after you delete the server.

•The system may automatically delete some devices, such as MOH servers, when you delete a server.

•Before you delete a node, Cisco recommends that you deactivate the services that are active on the subsequent node. Performing this task ensures that the services work after you delete the node.

•Changes to the server configuration do not take effect until you restart Cisco Unified Communications Manager. For information on restarting the Cisco CallManager service, see the Cisco Unified Serviceability Administration Guide.

•To ensure that database files get updated correctly, you must reboot the cluster after you delete a server.

•After you delete the node, access Cisco Unified Reporting to verify that Cisco Unified Communications Manager removed the node from the cluster. In addition, access Cisco Unified Reporting, RTMT, or the CLI to verify that database replication is occurring between existing nodes; if necessary, repair database replication between the nodes by using the CLI. Suresh

Deepak Rawat
Cisco Employee
Cisco Employee

There is no need to run the script. In older CM version, it was required but not anymore. Just keep the things in mind that Suresh commented and rest you should be good. In most of the cases, it is advised that you should reboot the remaining nodes in the cluster so that the entries can be removed completely. Post that, just run a replication check from CLI and pull the Database report from Cisco Unified Reporting to make sure the node is gone completely.

Regards

Deepak

tacl75
Level 1
Level 1

Thanks Kumar. At least it clarifies my doubt now. :)