cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
973
Views
0
Helpful
2
Replies

Upgrade Callmanager 3.3(2)

anton
Level 1
Level 1

Hello community,

we've ordered an upgrade from Callmanager 3 to the latest Version. Because we have a cold standby MCS I want to test all upgrade steps on this one before I deploy the updates on the live system.

This Version is installed:

Cisco CallManager System version: 3.3(2)

Cisco CallManager Administration version: 3.3(0.143)

Cisco CallManager Installation ID: CCM3.3(2)

So first, I have to upgrade to latest version of the CCM3-line, then to version 4 and then to the new linux based version with the migration tools and move to the new hardware.

I deployed the OS Upgrade packages to Version 2000.4.6 and OS Service Release to 2000.4.6sr9 and also SQL2K to SP3a(1.0.6). The Callmanager Upgrade Assistant 3.3(5) tested all validation steps with success. So i deployed "ciscocm-ffu.3-3-5.exe" to upgrade to 3.3(5). I followed the steps described here: http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/upgrade/3_3/upgr335.html

During that, it increments the databasename to "CCM0301" but after the upgrade, the tables are empty (e.g. device table). So it seems, that the configuration wasn't transfered to the new version.

Maybe you can help me to find out, what I've did wrong.

Thank you.

2 Replies 2

Tommer Catlin
VIP Alumni
VIP Alumni

Id highly recommend just simply fork lifting everything rather than doing the upgrade.  You get the chance to compeltely rebuil the cluster with new dial plan, route plan, etc.      You can really build the entire system in parrell and test everything out offline, or even online by connecting the two system via ICT trunks.  

Do you happen to know how many sites, phones, users, etc?

Thanks for your answer.

Thats what I've first wanted to do. We are talking here about 70 phones/users .. so no problem to reconfigure

The problem is, that i need the licenses for all phones connected to the active ccm 3.3 now. My distributor told me, that I have to use migration tool to "generate" this for version CUCM6/8. The migration tool only works in CCM4 so I have to upgrade to this version first ...