Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements
You may experience some slow load times, errors, and slight inconsistencies. We ask for your patience as we finalize the launch. Thank you.

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Changing CCM server name when migrating from 4.13 to 5.03

We are beginning to plan our CCM 4 to 5 migration and for linux based servers need to follow a different naming standard than windows.

How do we go about changing the CCM 4 server names either before, during or after the migration process.

  • Other Collaboration Voice and Video Subjects
2 REPLIES

Re: Changing CCM server name when migrating from 4.13 to 5.03

Hi -

The 5.0(4) upgrade guide, which upgrades a CallManager 4.X system, does not allow you to change the host name after the Linux OS install - http://www.cisco.com/en/US/customer/products/sw/voicesw/ps556/prod_installation_guide09186a00806c3cc3.html#wp46919

It assumes a running cluster and uses the information from your backed up system prior to the upgrade. I checked on Cisco's site and only found a couple of old references, that may still apply, that indicate you cannot change the CallManager server name without a rebuild - http://www.ciscotaccc.com/kaidara-advisor/voice/showcase?case=K12982991 and this one - http://www.cisco.com/en/US/customer/products/sw/voicesw/ps556/prod_troubleshooting_guide_chapter09186a00801eb003.html#wp1105170

If no one else updates your forum entry, I would check with TAC on this.

Ginger

New Member

Re: Changing CCM server name when migrating from 4.13 to 5.03

The TAC has told me that you have to use the same exact hostname and IP address when upgrading from 4.X to 5.X because CM is very dependent on DNS. You would think that someone could have writen a script in the installation that would go through and change all the references in the old database to what the user wanted in the new database. I was trying to bring up my 4.X database on a test 5.X server before attempting the upgrade on my production server. There is no way I'm going to do the upgrade on a production server without testing everything. Unfortunately, Cisco makes this extremely difficult to do. I have two option. Either bring down my current publisher so I can steal the IP address and hostname or set up a seperate network that has the same IP range. Seems a little ridiculous.

You could always upgrade to a new server with a different IP address in the past with CM 4.X and earlier as long as the hostname matched. I don't understand why they chose to change this in 5.X.

111
Views
0
Helpful
2
Replies