Upgrade CallManager 4.1(2) to CUCM 6.1(5)

Hi,
What is the best approch to upgrade CallManager 4.1(2) to CUCM 6.1(5)?
There will be 2 new CUCM servers available for ver 6.1(5). There are around 1000 phones.
Based on the Cisco upgrade guide, there is no direct upgrade from 4.1(2) to 6.1(5). Does it really need to upgrade to 4.1(3) first, then 6.1(5)? Is it possible to upgrade from 4.(2) to 6.1(5) using DMA tool directly?
If don't use DMA tool, but configure CUCM 6.1(5) from scratch, how difficult is it to configuration 1000 phones and 1000 users? Is there a way to export the phone and user configuration from 4.1(2) then use bulk configuration to upload file to 6.1(5)?
All suggestion/experience are appreciated.
Michael

You always need to be on the latest release from the CCM train you're on, in your case it's mandatory to be in 4.1(3) for ANY Linux upgrade.
Table 10 Supported Cisco Unified Communications Manager Upgrades for Release 6.1(5x)
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html#wp189359
You can export the a lot of data using BAT if you want to do a fresh install, however you'll need to handle the data to add all the new mandatory fields 6.1(5) has and your BAT file won't have.
It's possible but it requires some work on the CSV files.
HTH
java
If this helps, please rate
www.cisco.com/go/pdihelpdesk

Similar Messages

Upgrade from CCM 4.2 to CUCM 7.1

Is it doable to upgrade Cisco Call Manager 4.2 to Cisco Unified Communication Manager 7.1 ?

Hi there,
Yes, 4.2(3) would be the minimum required version
DMA for Cisco Unified Communications Manager Release 4.x
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html#wp57424
DMA release Notes
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_release_notes_list.html
Data Migration Assistant (DMA) Release 7.1(3) collects application data from Unified CM Releases 4.1(3), 4.2(3), and 4.3(2) system for upgrade to Cisco Unified Communications Manager Release 7.1(3). DMA exports data in the current Window based system (with SQL server database) that later gets imported to the appliance-based system (with Informix database).
Cheers!
Rob

Upgraded Callmanager to 4.1.3sr3 and ICD agents cannot go active

Upgraded PUB and SUB from 4.0.1 to 4.1.3sr3 and now my ICD clients cannot go active. They can log in but get the error "Request to change agent state failed. Unable to change agent state.

Did you run the JTAPI update utility as indicated in the following link?
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_installation_guide_chapter09186a00803f5c3c.html#wp1044748
Hope this helps. If so, please rate the post.
Brandon

Unity Connection - Certificate from cucm no more trusted for encrypted calls after upgrade to 10.5(1)

Hello Support Community,
i have a strange problem:
after upgrading my cucm and unity connection from 9.1 to 10.5(1) enctrypted calls are no more working.
situation 1: CUCM is down, Subscriber is up: Encrypted call to Unity Connection work correctly
situation 2: CUCM is up: Encrypted Calls to Unity Connection not working.
i get the following Info in the log for the Connection Conversion Manager:
19:35:21.053 |15865,,,MiuGeneral,25,Invalid Certificate: Received Certificate -----BEGIN CERTIFICATE-----
MIID8zCCAtugAwIBAgIQc/fBdUz1Zdh4CXhcPqGVuDANBgkqhkiG9w0BAQsFADBw
MQswCQYDVQQGEwJERTELMAkGA1UEChMCSVQxGzAZBgNVBAsTEkhlbGxnYXRlIFRl
XD0oD9d5MQ==
-----END CERTIFICATE-----
doesn't match with stored Certificate: -----BEGIN CERTIFICATE-----
MIIC2DCCAkGgAwIBAgIIJWCm4bSdt+kwDQYJKoZIhvcNAQEFBQAw
-----END CERTIFICATE-----
so where does Unity Connection cache this certificate and how can i delete/replace it?
the cert shown in the logs is the one from cucm: ("CallManager"), i recreated it through cucm os administration, now i see the same error message on unity connection for the new recreated certificate.

Actually It doesn't. It says he's on a MacBook. I don't know all the different types of Macs. I was having a ton of problems with iChat. I opened DMZ to my computer, knocked down all firewalls etc and left everything exposed, still with bad results. A few weeks ago my power supply went out on my D-Link. I bought a linksys. Since I'd left all firewalls off I figured it couldn't be the router. I power cycled everything n the netork, still no luck. Today I bought a universal Power supply and started up my D-Link Router. Everything worked perfectly. My wifes computer - a laptop running Tiger worked fine with the Linksys and did my machine before the Leopard upgrade. Now that I've got the D-Link online everythings working.
Message was edited by: graphico
Message was edited by: graphico

Upgrade to CUCM 7.1

I need to perform an upgrade from 6.1.3 to CUCM version 7.1 for phones that support 6921.
Grateful to indicate the link of the guide which explains step by step procedure.
greetings

Bookmark this:
Cisco Unified Communications Manager (CallManager)
http://www.cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_support_series_home.html
Software Upgrades
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/cucos/7_1_2/cucos/iptpch7.html
If you've done linux to linux upgrades before, it's the same procedure.
HTH
java
if this helps, please rate
www.cisco.com/go/pdihelpdesk

** Ugrent --CUCM Upgrade 8.6 to 10.5 issue **

Hello all,
We have upgraded CUCM from 8.6 to 10.5 (direct upgrade).
After upgrade we cant make changes into CUCM Publisher. While adding phones or device profile we are facing following error:
Add failed. The Insert privilege is required for this operation.
Also, our Cisco Unified Attendant Console Enterprise Addition sync with CUCM is not successful.
CTI RoutePoint & CTI Ports are not registered gone into unknow state.
Attached are Attendant console enterprise CUCM sync reports screen shot.
DB Replication for whole cluster is good with value 2.
Need urgent help - our system is in production now & we dont have cisco support agreement at the moment.
Regards,

Here are the install logs:
admin:file view install system-history.log
=======================================
Product Name - Cisco Unified Communications Manager
Product Version - 10.5.1.10000-7
Kernel Image - 2.6.32-431.3.1.el6.x86_64
=======================================
09/12/2014 22:16:31 | root: Install 10.5.1.10000-7 Start
09/12/2014 15:45:21 | root: Boot 10.5.1.10000-7 Start
09/13/2014 02:17:53 | root: Install 10.5.1.10000-7 Success
09/13/2014 02:17:54 | root: Boot 10.5.1.10000-7 Start
09/13/2014 02:41:59 | root: DRS Restore UCMVersion:10.5.1.10000-7 Start
09/13/2014 02:55:15 | root: DRS Restore UCMVersion:10.5.1.10000-7 Error
09/13/2014 03:06:55 | root: Boot 10.5.1.10000-7 Start
09/13/2014 03:16:24 | root: DRS Restore UCMVersion:10.5.1.10000-7 Start
09/13/2014 03:55:07 | root: DRS Restore UCMVersion:10.5.1.10000-7 Success
09/13/2014 03:59:19 | root: Boot 10.5.1.10000-7 Start
09/13/2014 06:16:40 | root: DRS Restore UCMVersion:10.5.1.10000-7 Start
09/13/2014 06:21:33 | root: DRS Restore UCMVersion:10.5.1.10000-7 Error
09/13/2014 09:31:10 | root: DRS Backup UCMVersion:10.5.1.10000-7 Start
09/13/2014 10:09:25 | root: DRS Backup UCMVersion:10.5.1.10000-7 Success
09/14/2014 12:38:48 | root: Restart 10.5.1.10000-7 Start
options: q=quit, n=next, p=prev, b=begin, e=end (lines 1 - 20 of 21) :
admin:
admin:

CUCM 5.1.3 to 8.6.2 upgrade

Hello,
I have to do an upgrade of a 3-node cluster CUCM 5.1.3d (5.1.3.5000-3) to 8.6.2. Hardware will remain the same. The servers support 8.6.2.
I have two questions:
- The upgrade path that I've chosen is: 5.1.3d (5.1.3.5000-3) -> 6.1.4a (6.1.4.2000-2) -> 8.6.2a (8.6.2.20000-2). I have already downloaded the upgrade images from Cisco site, but what concerns me is this paragraph from the 6.1.4a upgrade release notes:
Caution
Use the ISO files that are mentioned in the
“Upgrading to Unified CM Release 6.1(4a) by Using the UCSInstall File” section on page 5 for upgrades from 6.1(1x) and later.
Upgrading to Unified CM 6.1(4a) from Unified CM 4.x and 5.x
Product Upgrade Tool (PUT) orthe PUT for registered customers only to obtain a media kit and license or purchase the upgrade from Cisco Sales.
Is this really the case? Will i not be able to upgrade from 5.1 to 6.1.4a using this media?
- I have an idea for "optimizing" the upgrade procedure. Because the standard approach would be to execute two separate upgrade procedures for 3 servers, this could take a lot of time. I was thinking of doing this:
1. Take a backup of the current CUCM 5.1.3d
2. Install CUCM 5.1.3d on a virtual machine and restore the backup
3. Upgrade the VM to 6.1.4a
4. Upgrade the VM to 8.6.2a
5. Take a backup of the VM CUCM 8.6.2a
6. Take one of the subscribers and do a clean install of a Publisher CUCM 8.6.2a (same hostname, IP, etc as the real publisher)
7. Restore the backup from the VM to the new publisher
8. Reseat the license on the new publisher
9. Switch the old publisher with the new one and let all phones upgrade and re-register
10. Reinstall the other 2 nodes as subscribers to the new 8.6.2a cluster.
This is much easier to me because i can execute all updates in a non-production environment with zero risk. Only when everything is verified working will an actual migration take place. Then installing two subscribers is peace of cake and can be done even in business hours.
Any ideas what could go wrong?

I am facing a serious issue on this upgrade.
I did a DRS backup on the original cluster 5.1(3d)
Then do a install on a staging MCS-7816 (4GB RAM) of 5.1(3c).
Then upgrade it to 5.1(3d).
Then restore the DRS backup.
So far so good everything goes smooth.
From now on i have two options for upgrade: To 6.1(2) or To 7.1(5)
Both of them fail after 1 hour or something with those errors:
02/06/2013 19:34:57 CCMInstall|(CAPTURE) installFull rc[1]|
02/06/2013 19:34:57 CCMInstall|(CAPTURE) installdb Failure [-i] 1|
02/06/2013 19:34:57 CCMInstall|(CAPTURE) Stop DBMS|
02/06/2013 19:34:57 CCMInstall|(CAPTURE) su -c 'if [ -f /usr/local/cm/db/informix/local/ids.env ]; then source /usr/local/cm/db/informix/local/ids.env l2; fi ; onmode -yck' - informix|
02/06/2013 19:34:57 CCMInstall|(CAPTURE) cm-dbl-install [1]|
02/06/2013 19:34:57 CCMInstall|Internal Error, File:instMain.c:1354, Function: handlePhase(), Failed to exec command: "/partB/usr/local/bin/base_scripts/env.sh nice -n 19 /usr/sbin/chroot /partB /usr/local/cm/script/6.1.2.1000-13/cm-dbl-install L2 PostInstall 6.1.2.1000-13 5.1.3.5000-3 /usr/local/cm/ /partB/usr/local/cm/ /common/log/install/capture.txt"|
02/06/2013 19:34:57 appmanager.sh|CCMInstall --upgrade ERROR|
02/06/2013 19:34:57 upgrade_manager.sh|Applications upgrade failed|
02/06/2013 19:34:57 upgrade_install.sh|Cleaning up download...| 02/06/2013 19:34:57 CCMInstall|(CAPTURE) installFull rc[1]|
02/06/2013 19:34:57 CCMInstall|(CAPTURE) installdb Failure [-i] 1|
02/06/2013 19:34:57 CCMInstall|(CAPTURE) Stop DBMS|
02/06/2013 19:34:57 CCMInstall|(CAPTURE) su -c 'if [ -f /usr/local/cm/db/informix/local/ids.env ]; then source /usr/local/cm/db/informix/local/ids.env l2; fi ; onmode -yck' - informix|
02/06/2013 19:34:57 CCMInstall|(CAPTURE) cm-dbl-install [1]|
02/06/2013 19:34:57 CCMInstall|Internal Error, File:instMain.c:1354, Function: handlePhase(), Failed to exec command: "/partB/usr/local/bin/base_scripts/env.sh nice -n 19 /usr/sbin/chroot /partB /usr/local/cm/script/6.1.2.1000-13/cm-dbl-install L2 PostInstall 6.1.2.1000-13 5.1.3.5000-3 /usr/local/cm/ /partB/usr/local/cm/ /common/log/install/capture.txt"|
02/06/2013 19:34:57 appmanager.sh|CCMInstall --upgrade ERROR|
02/06/2013 19:34:57 upgrade_manager.sh|Applications upgrade failed|
02/06/2013 19:34:57 upgrade_install.sh|Cleaning up download...|
Does somebody have a clue what we can do?

CUCM Upgrade from 9.1.2 to 10.5

Hi all,
I have tested upgrading CUCM from 9.1.2 to 10.5 in my lab. As i read before, we need some cop files to upload to CUCM before upgrade procedure.
Cisco named this upgrade as <Refresh Upgrade> and during this process, RHEL version will also upgrade with CUCM version.
On my test, i dont upload any cop file before upgrade. Just uprade to 10.5 version.
Before upgrade my RHEL version was 5(32 bit) and after upgrade it is 6(64 bit).
After upgrade, everything seems ok but upgrade took lots of time, like 4 hours.
During upgrade there is no connection to CUCM and i saw blue screen :)
What is your opinion? Will this method work on customer enviroment?
Do you test this procedure before?
Best Regards,
Mesut

Dear Carlo & Chris, May I ask you to clarify on below comment which is mentioned in Release note of CUCM 10.5
I don't understand why Cisco has mentioned this, if its not required ? I would appreciate your any inputs.
Preupgrade COP File
If you are upgrading to Cisco Unified Communications Manager Release 10.5(1), or later, from a release earlier than Cisco Unified Communications Manager Release 10.0(1), you must download and install ciscocm.version3-keys.cop.sgn on every node in the cluster. This Cisco Options Package (COP) file has the RSA keys that are required to validate the upgrade. Missing RSA-3 keys will result in status errors in the Software Installation/Upgrade window of the Cisco Unified Operating System Administration interface.
Suresh

CUCM 7 software upgrade

Hi There
We are going to upgrade our CUCM7.1.3 to CUCM 7.1.5. We have 1 pub and 2 subs.
According to the Cisco document, once the software being installed, we just need to switch the version and the system will start and running with the new version.
My question is do we need to install the software on all 3 nodes and then switch the version or install on the pub first, restart the node without switch version, and do the same on the 2 other sub nodes and then switch version?
Thanks

Hi,
Install the upgrade file on Publisher first
Once finished on Publisher, install the upgrade file on the subscribers one by one or simultaneously
Do a switch version on the Publisher and let it boot into the new version and allow all the services to come up
Then do a switch version on the subscribers one by one or simultaneously
HTH
Manish

Upgrading CM 4.1 to CUCM 8.6

Hi All,
I have a CUCM 8.6 which was upgraded from CM 4.1 to CUCM 8.6 about few months ago by another colleague of mine. The person has left the company, and the CUCM 8.6 has not come up into the production network.
Between that time till now, there has been alot of changes made that no one has kept track with.
Looking at the situation I can see 2 options:
a) Re-do the upgrade from 4.1 to 8.6 based on the thread: https://supportforums.cisco.com/thread/2149422
b) Trace back changes manually and make the changes (i.e Bulk admin, etc?)
Just would like to ask everyone for ideas on the best way forward.. if you have any ideas that I could avoid re-doing Option (a), I would greatly appreciate it.

It depends on how many changes were made. If it was a lot I would go with option A, if you are unsure I would also go with option A, if there was only some basic changes such as phone changes, etc and you can identify them option B would be easiest.
HTH,
Chris

Upgrading 4.x CUCM and UC to 8.6

I need to upgrade a 4.x install of CUCM (pub and sub) and UC the the newest release which is currently 8.6.
I understand that this would be a multi-step process. I'm looking for a high level breakdown just so I can get the process straight as I'm a bit confused on the step-by-steps.
For instance, what should I upgrade first, pub or sub?
When I upgrade the pub/sub, can I do this during working hours and not worry about disrupting call flow?
How are the new CUCM servers introduced to the environment?
Is the upgrade process for UC similar?
Etc.
I'm sure there are some who've done these types of upgrade before (unlike me) and am looking for a little guidance.
Thanks!

Hi "G",
This will be a very complex process which will need to be broken up into
a number of distinct steps Like you nicely noted the fist step for the
CUCM upgrade path will be to move from 4.x to 7.x so you can leverage
the DMA upgrade/files. So I would break this down to securing a perfect DMA
.tarball (work with TAC to correct ANY errors) then the 7.x upgrade......let things
get working for a bit before the 8.6 upgrade.
This doc has the required steps for this 4.x to 7.x upgrade;
Upgrading to Cisco Unified Communications Manager Release 7.1(2) from 4.x Releases
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/upgrade/7_1_2/upgrd712.html
First step will be to create the DMA files. These files will then be
used when you go to do your CUCM 7.1(x) build. The DMA (Data Migration Assistant) files will
allow you to move your data from the Windows 4.x build to the new Linux 7.x build.Here is the requisite info for DMA;
Data Migration Assistant User Guide
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/dma/7_1_2/dmaug712.html
You will have to determine what version you current servers will support this is the "master" list for Server support;
Supported Cisco Unified Communications Manager Releases by Server
http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/prod_brochure0900aecd8062a4f9.html
You will need to work with Cisco either directly via your SE, a Partner or PUT (product upgrade tool) to secure the DVD's and
pay for the proper licenses that will enable the Software feature License for your new version.
PUT (www.cisco.com/upgrade)
Fur CUC, you will have to let us know what exact version you are currently running. One good thing
about CUC is that any version 2.x or newer is compatible with any CUCM version 4.1(3) and
above. This means that the CUC portion of this project can be completed before or after the CUCM
portion and does not have to be done simultaneously.
Check out this great doc from Saurabh for the refresh upgrade notes for the final step to 8.6.
This Refresh Upgrade will also apply to your CUCM 8.6 final step;
https://supportforums.cisco.com/community/netpro/collaboration-voice-video/unified-comm-application/blog/2011/08/11/checklist-before-upgrading-to-unity-connection-86
Cheers!
Rob

CUCM upgrade in UCCE environment

We have a CUCM cluster(v6.1.2) for our UCCE environment (ICM v7.2.5). I need to upgrade the CUCM to version 6.1.3 (due to the DST bug). Can someone tell me which components in UCCE that I will need to upgrade and/or modify for this CUCM upgrade? Or at least point me to a document that outlines this?
thanks,
Brian

You would probably have compatibility without any UCCE change, but the recommended task is to download the updated JTAPI Client plugin from your upgraded CUCM and overwrite what is there on your PGs.
That is all.
Regards,
Geoff

Callmanager Upgrade Question

Upgrading from 4.0(2) to 4.1(3).
The actual Callamanager(2pub and 2 Sub) is running on an old Hardware. We puchased new servers to install the CCM 4.1(3). Question is How to Upgrade and keep all Config of CCM 4.0(2)(phones,users...etc). Will it go like this:
1- Install CCM 4.0(2) on the New Servers
2- Run BARS Restore (assuming a Backup of CCM 4.0(2) is already taken of the old Hardware)
3- Upgrade Callmanager to 4.1(3)
Am i missing something? how about service releases...etc?
The DOc i found on Cisco is only relating to an Upgrade without Hardware Change.
Thank you

Take a look to these documents:
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/4_1/install/upgrade/upg413/replace.htm
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/4_1/install/upgrade/upg413/index.htm

Does an CUCM upgrade affect the device defaults?

Hello
we intend to do an CUCM upgrade from 9.1(2) to 9.2(2)SU2a.
However, our phones have the firmware 9-4-2-1S, different from the original firmware (9-3-1-SR2-1)
After the CUCM upgrade, will the device defaults get back to its original firmware version (9-3-1-SR2-1) or the current version will be kept?
Thank you
Marcos

Hi Marcos,
Yes, When you upgrade to a newer version of CUCM the phones will upgrade/downgrade to the Firmware version listed in the readme doc for the CUCM upgrade version as I have linked below. So in your case the the CUCM readme for 9.1(2)su2 is shown here;
http://www.cisco.com/web/software/282074295/116350/cucmreadme912su2a.pdf
In 9.1(2)su2 it looks like the Device defaults would be 9.3(1SR4.1) but it looks like the Device defaults in CUCM 9.1(2)su3 would be the same as what you are currently running so you would be good to go as they are 9.4(2.1) ;
http://www.cisco.com/web/software/282074295/122683/cucm-readme-912su3.pdf
You could also copy the current device defaults into something like notepad and re-enter them after the upgrade, but if it were me, I would go with the later CUCM version 9.1(2)su3.
Cheers!
Rob

VoIP Upgrade to 10.5

We are in the process of planning our upgrade from CallManager 8.5 to 10.5 and we have some questions. We will also be upgrading Unity, Presence, Attendant Console, Contact Center, and Emergency Responder. The question concerns Emergency Responder. Per docs on Cisco website, it is recommended to upgrade Emergency Responder prior to CallManager. We are taking our VoIP infrastructure to Cisco UCS and we are discussing the best way to do this. We pretty much have CallManager figured out, but with Emergency Responder we are looking to do a P-to-V of the physical MCS box to ESXi on UCS. Once we P-to-V the Emergency Responder we plan on upgrading to the latest version which should be 10.5 or 10.0 at the minimum. Is Emergency Responder 10.5 or 10.0 compatible with CallManager 8.5. I don't believe it will be, but the reason is we would like to upgrade Emergency Responder prior to upgrading CallManager. Would like to hear what other members of the forum have done when upgrading Emergency Responder.

The RNs for CER cover compatibility with CUCM, you can find them on CCO.

Upgrade CallManager 4.1(2) to CUCM 6.1(5)

Similar Messages

Maybe you are looking for