[cisco-voip] CM6.1 Hostname vs. UCM Name

[Carter, Bill]

Thanks Wes!

 

For the groups benefit

 

Under System -> Server my server is identified by IP address.

 

System -> Cisco Unified CM, "Server" is identified by IP address; "Name"
was identified by the old Server name.

 

System -> Cisco Unified CM "Cisco Unified Communications Manager Name" I
changed this to the new name (to match the official host name)

 

Restarted UCM and all is good.

 

Under system reports here are the post-change values:

Unified CM Provisioned Servers - 192.168.X.X

Unified CM Hosts - 192.168.X.X

Unified CM Name Resolution - 192.168.X.X resolved to UCM1

Unified CM Server Connectivity - 192.168.X.X

 

 

 

 

 

________________________________

From: Wes Sisk [mailto:wsisk at cisco.com] 
Sent: Thursday, February 14, 2008 1:37 PM
To: Carter, Bill
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CM6.1 Hostname vs. UCM Name

 

In that case you may be able to get away with just changing the name in
UCAdmin.

This really hinges on what is in the hosts, rhosts, and sqlhosts files.
You can confirm the contents of those files using the Generic Reporting
Tool.  From CM6.x CCMAdmin look in upper right hand corner, select
"Cisco Unified Reporting" from the drop down.  Select System Reports
then "Unified CM Cluster Overview".  Specifically the sections:
Unified CM Provisioned Servers
Unified CM Hosts
Unified CM Name Resolution
Unified CM Server Connectivity


So long as 'CM Hosts" shows the desired names you can likely update the
database and be safe.  Before updating the database thought make sure
forward and reverse DNS resolution are in place for the new name.

/Wes

Carter, Bill wrote: 

What is strange is at the CLI level there is the new hostname.  The CM
Admin, UCM Manager Name is still the old.
 
-----Original Message-----
From: Wes Sisk [mailto:wsisk at cisco.com] 
Sent: Thursday, February 14, 2008 1:15 PM
To: Carter, Bill
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CM6.1 Hostname vs. UCM Name
 
That process is sketchy at best.  Vaguely I recall it required:
1. DMA of 4.x database
2. install 5.x for windows migration
3. during install set new hostname but original IP address
4. during DMA import phase it should reconcile the old/new name
5. after final reboot your system should show the new hostname and then 
you can change IP at will.
 
if you already have a working system it is too late to change the 
hostname.  Lots of dangerous fun here:
CSCsj89934.
 
Reference to process here:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/upgrade/5_1/upgrd511.
html#wp46919
 
This captures the request: CSCsc73821.  I believe this should be 
resolved with the above process. I'm following up with the owner to
confirm.
 
/Wes
 
Carter, Bill wrote:
  

	I upgraded from 4.1 to 6.1.  The 4.1 server was named CCM1.
According
	    

to
  

	the DMA installation guide, I could change the hostname of
CallManager
	and everything would be updated...So I did.....
	 
	At the CLI level server host name is UCM1
	 
	In UCM Administration I have
	 
	System -> Server 192.168.X.X.  
	 
	System -> Cisco Unified CM 
	"Cisco Unified Communications Manager Server 192.168.X.X"
	"Cisco Unified Communications Manager Name CCM1"
	 
	 
	Through UCM Admin, can I change UCM Name from CCM1 to UCM1 ?
	 
	 
	Bill Carter
	Sr. Business Communications Analyst
	CCIE 5022
	Sentinel Technologies
	(O) 217.391.5015
	_______________________________________________
	cisco-voip mailing list
	cisco-voip at puck.nether.net
	https://puck.nether.net/mailman/listinfo/cisco-voip
	  
	    

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20080214/11510844/attachment.html