CUCM IP Hostname

Hello, in this article you can find the configuration steps to change the CUCM IP address and hostname.

CUCM Changing IP Address & Hostname

Note 1: Before you start, if you plan to change the hostname, make sure that the corresponding DNS records are also updated. Otherwise you may experience communication problems.

Note 2: If you are going to change the IP addresses or hostnames of all nodes on a CUCM cluster, start from Publisher first. And then change the Subscribers individually.

After these warnings, now we can start:

1. Connect to CUCM OS Admin CLI via SSH and use the following command to change the hostname:

admin:set network hostname 
  
ctrl-c: To quit the input.
  
          ***   W A R N I N G   ***
 Do not close this window without first canceling the command.
  
 This command will automatically restart system services.
 The command should not be issued during normal operating 
 hours.
  
 =======================================================
  Note: Please verify that the new hostname is a unique 
        name across the cluster and, if DNS services are 
        utilized, any DNS configuration is completed 
        before proceeding.
 =======================================================
  
 Security Warning : This operation will regenerate
        all CUCM Certificates including any third party
        signed Certificates that have been uploaded.   

Note: For hostname changes, if your CUCM or cluster uses certificates that are signed by a CA, you will need to sign these certificates again according to the new hostname and upload them to the CUCM. If self-signed certificates are used, this process will be renewed automatically and your endpoints will be reset to receive the new ITL file.

2. Enter the hostname after reading the warnings:

Enter the hostname:: cucm 

3. If you want to change the IP address, subnet mask and default gateway, enter the relevant information followed by yes:

 Would you like to change the network ip address at this time [yes]:: yes
    
 Warning: Do not close this window until command finishes.
    
  ctrl-c: To quit the input.
    
            ***   W A R N I N G   ***
 =======================================================
  Note: Please verify that the new ip address is unique 
        across the cluster.
 =======================================================
     
 Enter the ip address:: 192.168.0.137
 Enter the ip subnet mask:: 255.255.255.0
 Enter the ip address of the gateway:: 192.168.0.1 

4. The information you entered will be displayed on the screen. If all are true, you can start the change process by typing yes:

 Hostname:       cucm                                                   
 IP Address:     192.168.0.137
 IP Subnet Mask: 255.255.255.0
 Gateway:        192.168.0.1
  
 Do you want to continue [yes/no]? yes 
    
 calling 1 of 5 component notification script: ahostname_callback.sh                      
 Info(0): Processnode query returned =
 name       
 ========== 
 bldr-vcm18 
 updating server table from:'oldHostname', to: 'newHostname'
 Rows: 1
 updating database, please wait 90 seconds
 updating database, please wait 60 seconds
 updating database, please wait 30 seconds
 Going to trigger /usr/local/cm/bin/dbl updatefiles --remote=newHostname,oldHostname 
 calling 2 of 5 component notification script: clm_notify_hostname.sh                   notification
 Verifying update across cluster nodes...
 platformConfig.xml is up-to-date: bldr-vcm21
  
 cluster update successfull
 calling 3 of 5 component notification script: drf_notify_hostname_change.py    
 calling 4 of 5 component notification script: regenerate_all_certs.sh                      
 calling 5 of 5 component notification script: update_idsenv.sh                  
 calling 1 of 2 component notification script: ahostname_callback.sh                       
 Info(0): Processnode query returned =
 name 
 ==== 
 Going to trigger /usr/local/cm/bin/dbl updatefiles --remote=10.10.10.28,10.67.142.24
 calling 2 of 2 component notification script: clm_notify_hostname.sh                    
 Verifying update across cluster nodes...
 Shutting down interface eth0:  

If your CUCM or cluster is in mixed-mode, and you have done this with the CTL Client, run the CTL client again and update the CTL file. If you used tokenless CTL, run utils ctl update CTLFile from CLI to update the CTL file.

Exit mobile version