cancel
Showing results for 
Search instead for 
Did you mean: 
cancel

CUCM 11.5 change IP or FQDN to new FQDN

610
Views
5
Helpful
0
Comments

Description

The key goal of this paper is to clarify the sequence of steps and their impact on the system.

Here are a few ways to change IP or FQDN to new FQDN.

First, look carefully all recommendations related with Certificates, Replication and so on.

Changing IP Address and Hostname for Cisco Unified Communications Manager and IM and Presence Service and

Change CUCM Server Definition from IP Address or Hostname to FQDN Format

Hostname and domain name are changed. IP address is not changed.

These steps are tested with clear single CUCM-PUB11.5
* - APP = https://10.10.10.10/ccmadmin/showHome.do

* - CLI = https://10.10.10.10/cmplatform/index.jsp or CLI

=================================================================================

The first sequence of steps - to change IP to FQDN: First CLI then APP (preffered if you jump from IP to FQDN)

APP: IP = 10.10.10.10 (system -> server)
CLI: hostname=hostname1, domain=corp1.local

The goal: to change IP to FQDN along with changing both hostname1 and domain1. IP is not changed in this task.
new hostname: hostname2
new domain : corp2.local

Configuration Steps

Since this is an IP address mentioned at APP, there are no issues with changing network settings at CLI first.
A and PTR records should resolve the IP address, so DNS should be reconfigured first, otherwise :set network hostname command returns an error.

1.1) DNS: change DNS (A and PTR to match hostname2.corp1.local ;

It is a temporary record which will be changed to hostname2.corp2.local later).
1.2) CLI: change hostname :set network hostname hostname2
1.3) DNS: change DNS (A and PTR to match hostname2.corp2.local )
1.4) CLI: automatic services restart
1.5) CLI: change domain  :set network domain corp2.local
1.6) CLI: automatic system reboot
1.7) APP: (system -> server) change IP=10.10.10.10 to FQDN hostname2.corp2.local
1.8) APP: change Phone URI at Enterprise Parameters Configuration

=================================================================================

=================================================================================

The second sequence of steps - to change IP to FQDN: First APP then CLI (it is less rational but still might be used as well)

APP: IP = 10.10.10.10 (system -> server)
CLI: hostname=hostname1, domain=corp1.local

The goal: to change IP to FQDN along with changing both hostname1 and domain1. IP is not changed in this task.
new hostname: hostname2
new domain: corp2.local 

Configuration Steps

A and PTR records should resolve the IP address, so DNS should be reconfigured first, otherwise :set network hostname command returns an error.

2.1) APP: (system -> server) change IP=10.10.10.10 to FQDN hostname2.corp2.local (the targeted FQDN)
2.2) DNS: change DNS (A and PTR to match hostname2.corp1.local ;

it is a temporary record which will be changed to hostname2.corp2.local later).
2.3) CLI: change hostname :set network hostname hostname2

2.4) CLI: automatic services restart
2.5) APP: The command at step 3) changes FQDN back to hostname2.corp1.local,

Meaning, in spite of previously FQDN was changed at hostname2.corp2.local, still it is necessary to change FQDN again to hostname2.corp2.local

2.6) DNS: change DNS (A and PTR to match hostname2.corp2.local )
2.7) CLI: change domain: :set network domain corp2.local

2.8) CLI: automatic system reboot
2.9) APP: change Phone URI at Enterprise Parameters Configuration

=================================================================================

=================================================================================

=================================================================================

The third sequence of steps - to change FQDN to new FQDN: First APP then CLI

APP: FQDN = hostname1.corp1.local (system -> server)
CLI: hostname = hostname1, domain=corp1.local

The goal: to change FQDN2 to FQDN1 along with changing both hostname1 and domain1. IP is not changed in this task.
new hostname: hostname2
new domain : corp2.local

* - A and PTR records should resolve the IP address, so DNS should be corrected first,
otherwise :set network hostname command returns an error

** - Since this is FQDN mentioned at APP (System -> server), APP (System -> server) should be changed first.

If change settings at CLI before changing it at APP there will be an issue with database connection.

You will get an error after reboot while connecting at Application: Database communication error

if this happened, simply change the domain back and produce changes at APP (system -> server).

*** - the error HTTP Status 404 – /ccmadmin/showHome.do corrects by the CLI command:
:utils service list
if Cisco Tomcat is started but still there is delay in Web to bring back then
:utils service restart Platform Administrative Web Service should speed up the process

Configuration Steps

A and PTR records should resolve the IP address, so DNS should be reconfigured first,
otherwise :set network hostname command returns an error.

3.1) APP: (system -> server) change FQDN from hostname1.corp1.local to hostname2.corp2.local (the targeted FQDN)

3.2) DNS: change DNS (A and PTR to match hostname2.corp1.local ;

it is a temporary record which will be changed to hostname2.corp2.local later).
3.3) CLI: change hostname :set network hostname FROM hostname1 to hostname2

3.4) CLI: automatic services restart

If for some reason hostname portion of FQDN at APP didn't match the new one configured at CLI, the step 3) changes it automatically comprising hostname2.corp1.local (the domain portion remains unchanged). It is necessary to change APP again at the targeted one.

3.5) DNS: change DNS (A and PTR to match hostname2.corp2.local)
3.6) CLI: change domain: :set network domain corp2.local
3.7) CLI: automatic system reboot
3.8) APP: change Phone URI at Enterprise Parameters Configuration

CreatePlease to create content
Content for Community-Ad
July's Community Spotlight Awards