Archive for the CUCM Category

UC Data vs UC Data (Matching Data from Different Sources)

Posted in CUCM on September 18, 2013 by miskaone

Some excel basics for comparing data out of CUCM and CUE. Using directory number extensions from CUCM to match CUE phonenumber extensions to get CUE username.

Stupid-pet tricks1

Used index() and match() excel formula to correlate the available user names.

CUCM 9.1.2 Changing Just The Host Name

Posted in CUCM on September 6, 2013 by miskaone

I used the following steps to change all the host names in a cluster that was upgraded to CUCM 9.1.2.

This closely follows the CCO guide for changing host names but a little more concise.

 

hello-my-name-is

– Step 1 –

On each server  check the replication status. I prefer the CLI and the following command.

  • show perf query class “Number of Replicates Created and State of Replication”

– Step 2 –

Validate or Reset DRF services. If any of the DRF services are not active and responsive the name change will fail.

  • utils service stop Cisco DRF Local – all nodes

  • utils service start Cisco DRF Local – all nodes

  • utils service stop Cisco DRF Master -Pub Only

  • utils service start Cisco DRF Master -Pub Only

– Step 3 –

Change DNS if the dns client is enable on the servers

 

– Step 4 –

Publisher Host name change requires changing the Cluster Publisher Host Name setting on each node. This can completed via the GUI or CLI

  • set network cluster publisher hostname {host name}

 

– Step 5 –

Now you can change the host name on the server requiring the change.

  • CLI: set network hostname

Note the following scripts will run  as component notification

  • adns_verify.sh
  • clm_notify_hostname.sh
  • drf_notify_hostname_change.py
  • regenerate_all_certs.sh
  • update_idsenv.sh

Note the server will automatically reboot.

– Step 6 –

After the reboot on the node that the host name was changed run  the dropadmin table to clear the syscdr configurations.

  • utils dbreplication dropadmindb

 

– Step 7 –

Reboot all other servers in the cluster, including the Publisher.

 

– Step 8 –

Verify that the name-IP association change

  • utils network host {name}

Note Do not proceed until the change propagates to all nodes.

– Step 9 –

From Publisher force the replication to restart and rebuild the replication connections.

  • utils dbreplication reset all

 

– Step 10 –

Check replication status periodically to ensure all replication get to state 2.

  • show perf query class “Number of Replicates Created and State of Replication”

 

– Step 11 –

Repeat for each node that needs to be renamed.